roslaunch and rosparam

[dragonfly91]

Create launch files for each module. Move all parameters to the launch file and fetch them during run time using rosparam. Follow this link: http://wiki.ros.org/roscpp_tutorials/Tutorials/Parameters to understand what code to add to fetch params during run time. This link: http://wiki.ros.org/roslaunch/XML/param gives a simple example of how to include the parameters in the launch file. Finally, this link: http://wiki.ros.org/Parameter%20Server gives an idea of what all types of parameters you can give via rosparam.

[sidakpreet]

Don't use rosparam, use configuration files. It is a bit messy than rosparam but we have to try to minimize ros usage as much as possible!

On May 8, 2014 5:58 AM, "Samuel Anudeep" notifications@github.com wrote:

Create launch files for each module. Move all parameters to the launch file and fetch them during run time using rosparam. Follow this link: http://wiki.ros.org/roscpp_tutorials/Tutorials/Parameters to understand what code to add to fetch params during run time. This link: http://wiki.ros.org/roslaunch/XML/param gives a simple example of how to include the parameters in the launch file. Finally, this link: http://wiki.ros.org/Parameter%20Server gives an idea of what all types of parameters you can give via rosparam.

— Reply to this email directly or view it on GitHub.

[dragonfly91]

We are finding it very hectic to not use rosparam. I believe we need to use it at least till IGVC. We may aim for ROS agnostic code during this milestone: https://github.com/AGV-IIT-KGP/freezing-batman/issues?milestone=4&state=open

EDIT: We won't change the parameter access for the existing code, but all the new nodes to be created from now on would use rosparam if required. They can be made ROS agnostic once you can come up with a self written param package.

@hargup @NightFury37 please comment and assign / close this issue ASAP!!