Robotics StackExchange | Archived questions

Practice to make new ROS Stack as generic as possible (home/building automation)

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

Asked by theosakamg on 2016-05-29 11:35:15 UTC

Comments

But how to name the package more specific

I think you'll need to clarify this question a little: what do you mean exactly?

Asked by gvdhoorn on 2016-05-30 01:58:42 UTC

FYI: http://wiki.ros.org/iot_bridge

ROS+OPENHAB

Asked by ChriMo on 2016-05-30 05:40:16 UTC

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

Asked by theosakamg on 2016-05-30 05:43:45 UTC

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 ?)

Asked by theosakamg on 2016-05-30 05:50:57 UTC

@ChriMo: your post was not an answer, so I moved it to the comment section.

Asked by gvdhoorn on 2016-05-30 06:01:42 UTC

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

Asked by gvdhoorn on 2016-05-30 06:03:18 UTC

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 ?

Asked by theosakamg on 2016-05-30 13:09:51 UTC

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.

Asked by gvdhoorn on 2016-05-30 14:52:17 UTC

@gvdhoorn : Thank a lot.

If any other people has a different point of view ? or proposal... Say it ! (I start the rename)

Asked by theosakamg on 2016-05-31 05:01:10 UTC

And thank to @ChriMo for the link.

Asked by theosakamg on 2016-05-31 05:02:29 UTC

Probably too late on board, but @theosakamg "smarthome" refers to a proprietary entity unless that's what you intend.

Asked by 130s on 2017-06-14 13:50:45 UTC

Answers

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 by gvdhoorn on 2016-05-30 06:04:09 UTC

Comments