-
Notifications
You must be signed in to change notification settings - Fork 25
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
Generalize odometry inspector #971
Comments
Now we need to detect if the collection is fixed or dynamic so that when the marker is moved we affect only the selected collection (if the transform is dynamic) or affect all the transformations (if the transform is static). @Kazadhum you were doing this just yesterday, right? |
Indeed, I wrote a check for if a given TF was fixed! It's not a separate function, but its here:
Keep in mind this comes in the context of the I can reorganize it into a function quickly if needed! |
This is were I have done it before
|
I think all is done for now. I have use the dataset['transforms'] that exist in newer datasets. Perhaps we will need to create a dataset migrate tool ... opened #973 for this. |
Missing the creation of a transform_corrector.launch ... should be done in the configure_calibration_package. |
Closing. |
Because of #970 we now seem to have problems in the initial transforms for another sensor.
That means we have to generalize the odometry inspector to run be able to cope with any transformation.
Ultimately we will remove the set initial estimate working from the bagfile, and create a dataset_playbag 2.0 that will allow us to correct annotations and manually set any transformations we'd like.
The text was updated successfully, but these errors were encountered: