-
Notifications
You must be signed in to change notification settings - Fork 132
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
[cob_hardware_config] further simplify configuration structure (modules and components) #437
Comments
After cleaning up unsupported robots #588, we will start introducing a more generic robot-/module-/component-base structure for all URDF, launch and config files... as discussed with @ipa-fmw @ipa-nhg @ipa-mdl This will allow further de-duplication of code, more consistency between robots, better harmonization of HW/Sim-behavior as well as easier future maintenance and up-scaling... |
#622 is a significant step towards a simplified configuration structure I will apply a similar concept for the other "unifiable" components, e.g. torso, head, sensorring, arm(s),... |
Also, we would need to adjust the structure to the robot names we are using now to refer to a (physically existing) robot composition, i.e. The ultimate goal could be to even generate launch files based on a module configuration using a tool based on @ipa-mdl's roslaunch-dump |
@ipa-mdl asked for input about |
reminder for @ipa-fxm: extract sick scanners from base urdf + then remove nav configs for mlr bases as they do not have laser scanners anymore |
done in #654 |
atm none of the solutions proposed by @ipa-fxm and @ipa-nhg fully meet our requirements thus, I'm moving it to Backlog |
we won't work on this for now |
No need to close it. |
it's been in the sprint backlog anyway... |
The structure already got much simpler but there still is some potential.
I'm creating this issue for discussion following
This has minor priority for now...
@fmessmer FYI
The text was updated successfully, but these errors were encountered: