| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
Hi,
I work with a little team to make a variation of ROS for Home Automation (same philosophy as ROS-Industrial) all the code is available on https://github.com/rosalfred
But how to name the package more specific ? and make my sensor msg generic for all other project of the same type ? (best efforts for the community)
Thank
re: how to make msgs generic: by encoding as few assumptions about use-cases as possible in them (their names, their fields, etc). If you start assuming your msgs will be used in a certain way, or only with certain nodes, that reduces re-usability drastically when those conditions aren't met.
Asked: 2016-05-29 11:35:15 -0500
Seen: 545 times
Last updated: Jun 14 '17
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
I think you'll need to clarify this question a little: what do you mean exactly?
FYI: http://wiki.ros.org/iot_bridge
ROS+OPENHAB
When i push the packages stack to ROS DISTRO. The ROS team ask to make my package name more specific. https://github.com/ros/rosdistro/pull... I don't want to rename it (and dependencies) many time. And I ask the community of ROS to help me to choose a name "generic" for Home automation.
I know the bridge to OpenHab. But I start my project 2 years ago (the bridge is come after...). And is not the same target. In my case the home know her environment (for example howto connect openHab on octomap ?)
@ChriMo: your post was not an answer, so I moved it to the comment section.
@theosakamg: in ROS-Industrial we typically prefix package names with the name of the mfg (for hw i'faces), or with the name of a project. In your case that could be
alfred(just an example).If we rename all "generic" package with smarthome_ ( eg: smarthome_media_msgs , smarthome_heater_msgs ... ) . And keeps my specific stack (not generic) of our porject with the prefix alfred_ . It is ok for all ?
I can't speak for everyone, but prefixing everything will most likely address the main concern of @tfoote. What that prefix should be is more of a subjective matter.
Btw: see also REP-144 for some guidelines on package naming.