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
I have a nested launch structure. In one launch file, I used TimerAction to launch a Node with a time delay. This launch file is included in another launch file using IncludeLaunchDescription. If this IncludeLaunchDescription is used directly, it works. If it is again nested inside a GroupAction, it gives me an error.
Both launch files are in the same folder, I launch it with ros2 launch ./main_launch.py and get the following error:
[ERROR] [launch_ros.actions.node]: Error while expanding or validating node name or namespace for 'package=demo_nodes_py, executable=listener, name=None, namespace=<launch.substitutions.launch_configuration.LaunchConfiguration object at 0x7c5cff6e60b0>':
[ERROR] [launch]: Caught exception in launch (see debug for traceback): launch configuration 'robot_namespace' does not exist
(Similar behavior can be seen, if the launch files are properly organised in packages.)
Debugging in the upper level launch files was quite confusing, since putting something in a GroupAction shouldn't change its behavior much (from my understanding).
It also works, if alternatively you don't use TimerAction in nested_launch.py or if you have everything within one launch file. It seems to be a problem with this combination.
System
Ubuntu 22.04.5 LTS
ROS2 humble
The text was updated successfully, but these errors were encountered:
I have a nested launch structure. In one launch file, I used
TimerAction
to launch a Node with a time delay. This launch file is included in another launch file usingIncludeLaunchDescription
. If thisIncludeLaunchDescription
is used directly, it works. If it is again nested inside aGroupAction
, it gives me an error.Minimal example:
main_launch.py
has following content:nested_launch.py
has following content:Error
Both launch files are in the same folder, I launch it with
ros2 launch ./main_launch.py
and get the following error:(Similar behavior can be seen, if the launch files are properly organised in packages.)
Debugging in the upper level launch files was quite confusing, since putting something in a GroupAction shouldn't change its behavior much (from my understanding).
How it works
It works, if the
main_launch.py
instead ends withIt also works, if alternatively you don't use
TimerAction
innested_launch.py
or if you have everything within one launch file. It seems to be a problem with this combination.System
Ubuntu 22.04.5 LTS
ROS2 humble
The text was updated successfully, but these errors were encountered: