Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

can not find frame_trajectory.txt #17

Open
houyiliang opened this issue Aug 10, 2023 · 4 comments
Open

can not find frame_trajectory.txt #17

houyiliang opened this issue Aug 10, 2023 · 4 comments

Comments

@houyiliang
Copy link

./build/run_tum_rgbd_slam_with_line -v ./orb_vocab/orb_vocab.dbow2 -d ../datasets/TUM/rgbd_dataset_freiburg3_large_cabinet/ -c ./example/tum_rgbd/TUM_RGBD_rgbd_3.yaml --eval-log
or
./build/run_tum_rgbd_slam_with_line -v ./orb_vocab/orb_vocab.dbow2 -d ../datasets/TUM/rgbd_dataset_freiburg3_large_cabinet/ -c ./example/tum_rgbd/TUM_RGBD_rgbd_3.yaml --eval-log frame_trajectory.txt
Hello, I've tried adding both "--eval-log" and "--eval-log frame_trajectory.txt" to the command, but I couldn't find the corresponding trajectory file after running it. Can you please help me? Thank you.

@C-H-Chien
Copy link

You can turn the if(eval_log) statement off so that it forces you to write the results to files.
I have tried that and the frame_trajectory.txt appears in the repository directory.

@rangingwaves
Copy link

@C-H-Chien,I still couldn't find the corresponding trajectory file after running it.

@rangingwaves
Copy link

I understand now; the results are generated only after closing the visualization window.

@C-H-Chien
Copy link

I understand now; the results are generated only after closing the visualization window.

Glad it works for you now. The file is written right after SLAM.shutdown(); which requires closing the visualization window.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants