-
Notifications
You must be signed in to change notification settings - Fork 0
Normalizing Each Objective Class's motionCost() #66
base: main
Are you sure you want to change the base?
Normalizing Each Objective Class's motionCost() #66
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added some tests in test_distance_objective
that we should use for the other objectives:
sample_states()
: commented out checking that all states are valid, which I think is what we want right?find_maximum_motion_cost()
- Implicitly test by comparing
max_motion_cost
to a hardcoded value - Tried to test
find_maximum_motion_cost()
directly but was not able to get the type ofstates
correct so I commented it out for now- Update: fixed and uncommented
- Implicitly test by comparing
If you want to merge this PR today and aren't able to finish the tests, I'm ok with merging this PR and working on the tests in another PR. Just leave some # TODO: <message>
comments
Thanks for adding the unit tests. |
Yes and ensure that they are the sampled states are valid. The validity checker currently is just a placeholder but it will be good to set this up now anyways. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems like sometimes the normalized cost is greater than 1: https://github.com/UBCSailbot/local_pathfinding/actions/runs/7688802043/job/20950435771
As discussed, just need to resolve merge conflicts:
|
Description
Verification
Resources