After running the ros_chrono node on the develop branch I noticed that stuff is broken because the rosparams are
mavs@febbo-HP-Z220-SFF-Workstation:~$ rostopic list
/Obstacle0/cmd_vel
/Obstacle0/odomObs
/Obstacle1/cmd_vel
/base_pose_ground_truth
/clicked_point
/clock
/gazebo/link_states
/gazebo/model_states
/gazebo/parameter_descriptions
/gazebo/parameter_updates
/gazebo/set_link_state
/gazebo/set_model_state
/gazebo_gui/parameter_descriptions
/gazebo_gui/parameter_updates
/hmmwv/base_footprint_link_pose
/initialpose
/lidar_points
/move_base_simple/goal
/nlopcontrol_planner/control
/obstacles
/path
/pcl
/rosout
/rosout_agg
/shutdown_requested
/tf
/tf_static
/vehicleinfo
Notice in the documentation the input output structure
https://juliampc.github.io/AVExamples.jl/latest/packages/ros_chrono/index.html#Input-1
we need to follow these conventions and make sure that if we update them it is documented and there is a reason behind it
After running the ros_chrono node on the develop branch I noticed that stuff is broken because the rosparams are
Notice in the documentation the input output structure
https://juliampc.github.io/AVExamples.jl/latest/packages/ros_chrono/index.html#Input-1
we need to follow these conventions and make sure that if we update them it is documented and there is a reason behind it