|
||
Hi, 1477496933.683665 W +N C0A801C3 parameter_events rcl_interfaces::ms Thanks |
Visit Topic or reply to this email to respond.
To unsubscribe from these emails, click here.
|
||
Each ROS 2 node has a parameter API to configure node-specific parameters (similar to |
|
||
Hi Dirk, Subscribing to param changes via callback services is clumsy, so updates should be sent over topics. Is there a design decision for not having this an option (notification topic) and it seems that the topic name should be unique or follow the node name. For example, nodename_parm_event.vs parameter_event as a topic? It seems that generating a separate topic becomes messy when having a lot of nodes/topics in a network. Could the change event or flag be part of the node itself vs separate? Thanks |
|
||
There are many questions remaining open atm regarding what names should be global vs. namespaced by each node. So the current approach doesn't mean it is final. In this specific case I could see both topics as being useful depending on your use case. Also with the option to remap topics in the future if the node only publishes on one of these topics you could always change the name of the topic when starting the node. |