Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@keenan-burnett @lisusdaniil
I added additional plots to understand better in which parts of the trajectory the error is greater.
boreas-2024-01-25-11-44_path_r_err.pdf
boreas-2024-01-25-11-44_path_t_err.pdf
boreas-2024-01-25-11-44_rl_frame.pdf
boreas-2024-01-25-11-44_rotational_error_per_length.pdf
boreas-2024-01-25-11-44_tl_frame.pdf
boreas-2024-01-25-11-44_translational_error_per_length.pdf
Instead of computing the average over the frames and plot the errors over the subsequence lengths I computed the average of subsequence lengths per each frame (where the frame considered is the starting point of the subsequence). In this way is possible to see the error over the trajectory and figure out the critical points. The first two plot are about the rotational and translational error over the estimated trajectory. The last 4 are over the frame numbers