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

[cob_hardware_config] further simplify configuration structure (modules and components) #437

Open
fmessmer opened this issue Feb 19, 2016 · 10 comments
Assignees
Labels

Comments

@fmessmer
Copy link
Member

fmessmer commented Feb 19, 2016

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

@fmessmer
Copy link
Member Author

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...

@fmessmer
Copy link
Member Author

#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),...

@fmessmer
Copy link
Member Author

fmessmer commented Mar 17, 2017

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. cob4-paul-ingolstadt...following @ipa-tif's spreadsheet Verbauliste.xlsx

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

@fmessmer
Copy link
Member Author

@ipa-mdl asked for input about roslaunch-dump (with the final goal being added to roslaunch)
ros/ros_comm#1022

@floweisshardt
Copy link
Member

floweisshardt commented Apr 6, 2017

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

@floweisshardt floweisshardt changed the title [cob_hardware_config] further simplify configuration structure [cob_hardware_config] further simplify configuration structure (modules and components) Apr 10, 2017
@fmessmer
Copy link
Member Author

extract sick scanners from base urdf + then remove nav configs for mlr bases as they do not have laser scanners anymore

done in #654

@floweisshardt floweisshardt changed the title [cob_hardware_config] further simplify configuration structure (modules and components) [cob_hardware_config] further simplify configuration structure (modules and components) (11) Apr 24, 2017
@floweisshardt floweisshardt changed the title [cob_hardware_config] further simplify configuration structure (modules and components) (11) [cob_hardware_config] further simplify configuration structure (modules and components) Apr 24, 2017
@fmessmer
Copy link
Member Author

fmessmer commented May 6, 2017

atm none of the solutions proposed by @ipa-fxm and @ipa-nhg fully meet our requirements
also current efforts require a final decision regarding future maintaining responsibilities and supported hardware

thus, I'm moving it to Backlog

@floweisshardt
Copy link
Member

we won't work on this for now

@mathias-luedtke
Copy link
Contributor

we won't work on this for now

No need to close it.

@fmessmer
Copy link
Member Author

fmessmer commented Jul 4, 2017

it's been in the sprint backlog anyway...

@fmessmer fmessmer reopened this Jul 4, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants