You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For launching the nodes specified in a system-mode models file (SHM file) for control by the mode-manager, all these nodes have to be specified additionally in a launch file. This redundancy is error-prone and should be avoided or at least minimized.
One idea is to provide a convenience function for launch that launches all nodes specified in an SHM file.
The text was updated successfully, but these errors were encountered:
A probably quite convenient way would be to provide a LaunchDescription that reads an SMH file and starts up all nodes and a mode-manager accordingly, see #11.
Does this sound reasonable to you, @ralph-lange?
This would require that the SMH file includes the necessary details on the packages, which nodes to deploy per OS process, ... Basically, this would make the SMH file format another launch file format. I would avoid this - despite my last sentence in the first message of this thread.
For launching the nodes specified in a system-mode models file (SHM file) for control by the mode-manager, all these nodes have to be specified additionally in a launch file. This redundancy is error-prone and should be avoided or at least minimized.
One idea is to provide a convenience function for launch that launches all nodes specified in an SHM file.
The text was updated successfully, but these errors were encountered: