forked from moveit/moveit
-
Notifications
You must be signed in to change notification settings - Fork 5
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
WIP: simplify state space selection in the OMPL interface #2
Open
JeroenDM
wants to merge
13
commits into
master
Choose a base branch
from
ompl-interface-simplification
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Failed test, but only sometimes, why is it not repeatable? Maybe related to caching of the planning context?
|
12 tasks
badba89
to
613a1d4
Compare
bde019e
to
194818f
Compare
…he ompl interface
…reation + small doc update
ab95225
to
26a2b3c
Compare
6 tasks
6 tasks
6 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
This is a proposal to simplify the OMPL interface by changing how the state space type is selected. It removes the flexibility of the current priority system. But, as there are only two different state spaces, it seemed a bit overengineered.
Before
The current system created a state space in two steps:
The planning context manager has a map with state-space factories. Based on the planning request, each factory gets a priority, calculated by
ModelBasedStateSpace::canRepresentProblem
. For a specific request, the factory with the highest priority is selected, unlessenforce_joint_model_state_space
is true (specified by the user inompl_config.yaml
).The priority is calculated based on
The priority values and selection process is shown below:

After
The factories and priority system is replaced with an if-else statement to select the correct state space type:
or in code:
Things that I think are less ideal with this implementation
PARAMETERIZATION_TYPE
is a generic string. It would be nice if it were some kind of class enum or something.selectStateSpaceType
andcreateStateSpace
could be combined in a single method, were it not for the fact that state spaces are cached using their parameterization type. But I don't know a better way.Alternatives
We can also keep the state space factories and only remove the priority system.
Checklist