| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
Hi all, I'm trying to load a YAML file into the parameter server programmatically in C++.
I know it is possible with Python, from this question here, but I couldn't find a way to do it in C++.
I'm using Melodic on Ubuntu 18.04.
Thanks @praskot, but I did not specify that I don't want to depend explicitly on yaml-cpp. I've resolved by invoking the rosparam command from the code. Assuming that cfg_file_path is a valid boost::filesystem::path object:
namespace fsys = boost::filesystem;
if(!fsys::exists(cfg_file_path) ||
!(fsys::is_regular_file(cfg_file_path) || fsys::is_symlink(cfg_file_path)))
{
ROS_WARN_STREAM("Could not open camera param file " << cfg_file_path.string());
} else {
// load the YAML file using the external rosparam command
std::string command = "rosparam load " + cfg_file_path.string();
int result = std::system(command.c_str());
if(result != 0){
ROS_WARN_STREAM("Could not set config file " << cfg_file_path.string()
<< " to the parameter server.");
}
}
https://github.com/jbeder/yaml-cpp
Checkout the https://github.com/jbeder/yaml-cpp/wi...
ros::NodeHandle nh;
yaml_params_ = YAML::LoadFile(yaml_filename);
for (YAML::const_iterator it = yaml_params_.begin(); it != yaml_params_.end(); ++it) {
nh.setParam(it->first.as<std::string>(), it->second.as<double>());
}
PS: Not sure if there is a better way, but this is how I do it. Obviously, there is ddynamic_reconfigure & dynamic_reconfigure, where you can store the params to *.yaml and save/load them as needed.
For future readers: I believe it's important to point out that in case a node does this, and the node is started via a .launch file, parameters set by this node will not be visible to other nodes, unless they are started after the parameter-setting node (and there is no way to enforce that, at least not in ROS 1).
Seeing as the order of starting nodes with roslaunch is not guaranteed, there is no way to guarantee these parameters will show up on the parameter server before they are accessed by other nodes.
This is one of the reasons why parameters are set first by roslaunch, and only then are nodes started.
Asked: 2020-08-10 15:18:56 -0500
Seen: 2,156 times
Last updated: Aug 11 '20
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
