-
Notifications
You must be signed in to change notification settings - Fork 30
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
ConcreteRobot uses ranker for PlantoTSR #503
Merged
Merged
Changes from all commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
600eec3
ConcreteRobot uses ranker for PlantoTSR
gilwoolee 2775b7e
Update include/aikido/robot/ConcreteRobot.hpp
aditya-vk ca3238e
Update include/aikido/robot/util.hpp
aditya-vk fac8462
Address PR comments
gilwoolee 6f830bc
Update src/robot/util.cpp
brianhou 00584f4
Address PR comments
gilwoolee b686a52
Merge branch 'robot_uses_ranker' of https://github.com/personalroboti…
gilwoolee 773763b
Merge branch 'master' into robot_uses_ranker
gilwoolee 41032c7
Update CHANGELOG.md
gilwoolee eaa38cd
Update CHANGELOG.md
brianhou 7200224
Use ConfigurationRanker in ConfigurationToTSR planner, make Configura…
gilwoolee f7174ce
Clang format
gilwoolee 681102e
Merge branch 'master' into robot_uses_ranker
gilwoolee f42a431
Merge branch 'robot_uses_ranker' of https://github.com/personalroboti…
gilwoolee File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
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
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
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
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
Oops, something went wrong.
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.
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.
Why do we need to create another pointer here? Can we not do:
In
robot/utils/planToTSR
, the ranker has been taken with aconst
pointer so I guess that's fine there. Alternatively, we can leave this like this and change the data member toconst
since we are initializing it in the constructor anyway.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.
Summarizing my slack discussion with @aditya-vk , I think we should keep it as is, for the following reasons:
mConfigurationRanker = nullptr
, the expectation is that a NominalConfigurationRanker would be created when this method is called and be initialized with thestartState
. So if we change the member variable as you suggested, the planner now has been mutated and it cannot be reused in the same way. Next time it is called, it'd use this ranker.const mConfigurationRanker
so that it never gets changed. Unfortunately, to my best understanding, because this class becomes a TSRPlanner via the templated adapter, it does not have access tomConfigurationRanker
during the initialization, i.e. I can't do: mConfigurationRanker(std::move(ranker)) { ... }
. It only has access to the constructor parameters of the PlannerAdapter, which is thestateSpace
andmetaSkeleton
. See stackoverflow .Hence, in order to keep the member variable as-is (as if it's a const) and initialize it in constructor if it's passed in, I think we need to keep it the way I have it now.
@aditya-vk @brianhou please confirm!
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.
That's right, there's no way to have it in the initialization list. Hmm.
I think what we have now is good then. Since we don't give an option to change the ranker at all unless a new planner is created, I think it should be fine 👍