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

Create a Configuration Assistant Analog to MoveIt #1721

Closed
SteveMacenski opened this issue May 11, 2020 · 1 comment
Closed

Create a Configuration Assistant Analog to MoveIt #1721

SteveMacenski opened this issue May 11, 2020 · 1 comment

Comments

@SteveMacenski
Copy link
Member

Moveit has long has a QT configuration assistant. MoveIt also has a bunch more auto-generated files required to work and more complex things to describe with kinematic chains than we do so that has made sense.

However, having some configuration assistant could be extremely beneficial to get users on their way with minimum friction. I don't know if we'll be able to cover every single parameter, but we should be able to cover the broad strokes with the costmap, how to layer them, select a URDF and frames making sure they comply with standards, planner, perhaps controller through the Qt GUI and show how the parameters effect the robot, etc

@SteveMacenski SteveMacenski changed the title Create a Configuration Assistent Analog to MoveIt Create a Configuration Assistant Analog to MoveIt May 11, 2020
@SteveMacenski
Copy link
Member Author

While we may come back to this in the distant future, we have now a complete first time robot setup guide with explanations, images, and examples https://navigation.ros.org/setup_guides/index.html. While that doesn't quite meet this need, it does provide instruction to help a user setup Nav2 for the first time with graphical examples.

Closing this since unlike moveit, we could not meaningfully display graphically all of the parameterizations needed for a first time setup with Nav2 (e.g. AMCL params or DWB sampling params) and would mostly be useful for setting up the costmaps, which will shortly have dynamically reconfigurable parameters again #956

If someone is interested in working on this, I'd love to brainstorm and make it happen, but for now I think we're going to drop this from the long term roadmap.

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

1 participant