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

Warn if optimization objective does not match expected values #2213

Merged

Conversation

stephanie-eng
Copy link
Contributor

Currently, if you specify an optimization objective that does not match any of the expected values, the path length optimization objective will be used without warning the user. This can lead to unexpected behaviour if you have mistyped the optimization objective name. This PR adds a warning for this case.

@codecov
Copy link

codecov bot commented May 31, 2023

Codecov Report

Patch and project coverage have no change.

Comparison is base (f9d44b6) 50.52% compared to head (8dd20eb) 50.52%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2213      +/-   ##
==========================================
- Coverage   50.52%   50.52%   -0.00%     
==========================================
  Files         386      386              
  Lines       31735    31736       +1     
==========================================
  Hits        16030    16030              
- Misses      15705    15706       +1     
Impacted Files Coverage Δ
...mpl_interface/src/model_based_planning_context.cpp 58.57% <0.00%> (-0.11%) ⬇️

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

Copy link
Contributor

@sjahr sjahr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for making that change! What do you think about printing a warning in both cases?

…ontext.cpp

Co-authored-by: Sebastian Jahr <sebastian.jahr@tuta.io>
@sjahr sjahr merged commit b98bb6b into moveit:main Jun 2, 2023
8 checks passed
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

Successfully merging this pull request may close these issues.

None yet

3 participants