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

Why is there a 0.5 coefficient for trajectory critics scoring? #91

Open
willxxx0909 opened this issue Sep 29, 2021 · 1 comment
Open

Comments

@willxxx0909
Copy link

double getScale() const override {return costmap_->getResolution() * 0.5 * scale_;}

In the getScale() function of map_grid.cpp, I understand the getResolution() * scale_ for mapping the score into map frame with a scale num, but why is it multiplied with a 0.5?

@DLu
Copy link
Collaborator

DLu commented Oct 7, 2021

Reference

The short answer is that the scales for the dwb_critics were tuned to match dwa_local_planner, but digging through that code, I can't immediately find the reason for the 0.5.

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