Operator GUI launch
Launch wrapper for the mtc_gui_client executable. Beamline/robot configuration comes from BEAMBOT_BEAMLINE_CONFIG in the process environment, with no declared launch arguments.
src.mtc_gui.launch.mtc_gui_client.launch · Source
Operator GUI · Guide · Symbol index
How it is used
ROS launch calls generate_launch_description() to start the mtc_gui_client executable. The GUI reads robot and beamline settings from BEAMBOT_BEAMLINE_CONFIG in its process environment; this wrapper declares no launch arguments.
This entry covers process startup. GUI behavior and ROS communication are implemented by the main window and its ROS bridge.
Start here
Callable |
Purpose |
|---|---|
Construct one mtc_gui_client Node action with screen output. |
Functions
generate_launch_description()
Construct one mtc_gui_client Node action with screen output.
Entry point · Source
generate_launch_description()
Returns: LaunchDescription containing the GUI node action.
Errors: Launch object errors propagate; GUI display/config validation happens in the launched process.
Side effects: Builds an action; executing opens the ROS GUI client.