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.

Sign up for GitHub

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

Jump to bottom

In CAMM GPSVelocityUp is always 0, should be based on change in elevation #3

Open
himynamesdave opened this issue Nov 8, 2022 · 2 comments
Open

In CAMM GPSVelocityUp is always 0, should be based on change in elevation #3

himynamesdave opened this issue Nov 8, 2022 · 2 comments
Assignees
@karamvirup
Labels
_bug different bug then what the ticket is built for camm
Milestone
0.1

Comments

@himynamesdave
Copy link
Member

As described here: https://www.trekview.org/blog/2021/calculating-velocity-between-two-sequence-photos/
@himynamesdave himynamesdave added the bug Something isn't working label Nov 8, 2022
@himynamesdave himynamesdave added this to the 0.1 milestone Nov 8, 2022
@karamvirup karamvirup added enhancement New feature or request camm and removed bug Something isn't working labels Nov 15, 2022
@karamvirup
Copy link
Contributor

@himynamesdave please review some camm videos, the one i have has the value 0, it is already in the code, if we need to change it we can, just need to make sure if we need to do it.

@himynamesdave
Copy link
Member Author

@karamvirup the camm examples you are looking at are lazy, and not calculating this. We should.

@himynamesdave himynamesdave added _bug different bug then what the ticket is built for and removed enhancement New feature or request labels Nov 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@karamvirup karamvirup

Labels
_bug different bug then what the ticket is built for camm
Projects
None yet
Milestone
0.1
Development

No branches or pull requests
2 participants
@himynamesdave @karamvirup