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

demo.py result explanation #87

Open
Hunamic opened this issue Nov 28, 2024 · 1 comment
Open

demo.py result explanation #87

Hunamic opened this issue Nov 28, 2024 · 1 comment

Comments

@Hunamic
Copy link

Hunamic commented Nov 28, 2024

Hello,

Thank you for your excellent work on this project!

I have a question regarding the outputs generated by running the demo.py file. Specifically, I want to understand the rows in result/images.txt and saved_trajectory/results.txt. From what I gather, they seem to represent camera poses relative to the world frame.

However, when I test with the TartanAir dataset and the Seasonsforest_winter_sample_P006 sequence, which contains 330 frames, the model outputs only 165 rows for the poses—exactly half of the total video frames(and also the poses related to the world frame).

Could you please clarify the following:

  1. What do the rows in these files represent?
  2. Why does the model output only half the number of poses relative to the frames in the sequence?
    Apologies if this question is overly simplistic, and I appreciate your response in advance.

Thank you!

@herrouou
Copy link

Hi, how did you get the final result? My running seemed to get stuck there:
(poses, tstamps), (points, colors, calib) = run(cfg, args.network, args.imagedir, args.calib, args.stride, args.skip, args.viz, args.timeit)
Some return values didn't work well....

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

2 participants