-
Notifications
You must be signed in to change notification settings - Fork 109
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dynamic Configuration Written to .yamls #33
Comments
i second this - as it would be a huge time-saver on large networks ( ie, 6 machines... editing yamls is a full time job, even with distributed shell) |
I'll follow up with the chela team about potentially implementing this. |
The ROS standard way to dump configuration parameters is using |
The following exampe shows how to save the configuration of a node:
Note: for these commands to work correctly you need to update to the latest version of the packages. See ros/dynamic_reconfigure#51 @jburkeucla @lthursdayl do you want me to add this information to the wiki? What would be the best place to put this? In future work we should think of further automating this process, for example to automatically keep track of the name of the saved node so as to restore to the same one on loading. One option is to add save/load buttons to the current gui or create a new gui for our needs. |
We would like the detection and tracking dynamic configuration (rosrun rqt_reconfigure rqt_reconfigure) to write directly to the associated .yaml file, then automatically restart the sensor(s) that the change was made to, thus applying the changes to the sensor.
The text was updated successfully, but these errors were encountered: