Replies: 1 comment
-
I like this - PR, please:-)? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The current method for importing crazyflie 'robots' is through the crazyflies.yaml file in the config folder. This is a great default, but makes it difficult for managing multiple projects that use Crazyswarm2. It would be great if a user can have different versions of crazyflies.yaml in their own ROS2 package config folder and just replace the default one in Crazyswarm2. Right now this option seems to be kind of available through the server_yaml_file parameter, but it doesn't support all the yaml replacements done in the launch.py file. Therefore, you would have to import a server_yaml_file and motion_capture_content file while keeping track of the robots in both files. It would be great to only be able to import the crazyflies.yaml option. That way users can make their own launch scripts and specify their crazyflie yaml file as an argument. It also allows them to have multiple versions for simulation, hardware scenarios, etc. I tried to make one and found the OpaqueFunction as a tool to do this since we have to open the yaml file within the launch file. What do you guys think?
Beta Was this translation helpful? Give feedback.
All reactions