We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi, in the paper referenced here: https://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=6385773&tag=1, absolute_trajectory_error is defined as the root mean squared error, but instead in the code it is computed as square root of sum of squared errors as referenced below.
absolute_trajectory_error
rpg_trajectory_evaluation/src/rpg_trajectory_evaluation/compute_trajectory_errors.py
Line 70 in 995e584
Is there a specific reason for doing this?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hi, in the paper referenced here: https://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=6385773&tag=1,
absolute_trajectory_error
is defined as the root mean squared error, but instead in the code it is computed as square root of sum of squared errors as referenced below.rpg_trajectory_evaluation/src/rpg_trajectory_evaluation/compute_trajectory_errors.py
Line 70 in 995e584
Is there a specific reason for doing this?
The text was updated successfully, but these errors were encountered: