huanxiner's profile - activity

NUC seems to have the same startup script as master, is that a typo?

Why don't you just put the two nodes in the same group? <group ns="camera"> ... </group>

Rewriting the first piece of code like this may help with understanding. int index; for (unsigned int y = 0; y < siz

I would try calling rosbag play directly. import subprocess player_proc = subprocess.Popen(['rosbag', 'play', bag_filen

Then what is the history length value you are using? It is initialized to 1. I assume you want a larger number.

Could it be the ordering of the launch files in the robot.launch? What happens when you move led.launch to the end of ro

Do you have a 'history length' equivalent parameter in your custom plugin? It sounds like a queue size issue to me.

Try changing 'Alpha' values in the displays.

What do you mean by converting it to ROS platform? Using a catkin workspace? Or do you need any other stuff in ROS as well?

Here is an example of how to do that.

<node name="tfs" pkg="ctt_tools" type="tfs" respawn="true"/> 
    <param name="param_1" value="23.0" />
</node>

and

double param_1;
node_handle.getParam("/tfs/param_1", param_1);      
if(m.point.x > param_1 && m.point.x < 26 && m.point.y > -4.70 && m.point.y < 4.50 )
{ 
   ...
}

You could also refer to Parameters in launch file and Use parameters in roscpp for more details.

You are right.. Sorry I have no idea neither why it doesn't even subscribe to the topic. Could you post the solution if you ever find one?

I am not sure if I understand you completely, but are you looking for a topic with 'rendered' camera+marker images? If so I don't believe it is readily available in rviz..

Did you turn off single click in the rviz tool properties panel?

Try changing sensor_msgs::PointCloud2 to sensor_msgs/PointCloud2.

Not sure, one more thing that may help is to rostopic echo /clicked_point and use publish tool to click on something. If nothing shows maybe do rostopic info /clicked_point and see what's there?

Is there any output in the terminal where rviz runs when you use the publish tool?

I had a similar issue once. The solution was to delete the default config file in ~/.rviz (assuming you are using linux). Not sure if this is gonna work for you but worth a try!

http://answers.ros.org/question/99796... This might help

Thanks William, I may open a pr later then. By the way a temporary work-around was setting PublishPoint tool as the default tool and then one can always use the Escape key to go back to it...

What's the message type that you are publishing on topic /circles?

ros::Publisher pub = handle.advertise<std_msgs::Empty>("my_topic", 1);
                                      ~~~~~~~~~~~~~~~   You are missing this part

For certain reasons I would like to have a shortcut key to the rviz/PublishPoint tool, and seems like there is no default shortcut key set in the class constructor.

After a bit of research I didn't find a way to do this without modifying the original code... Do anybody have a hint on how this can be done? Thanks!

Is there any message when you echo the topic /my_cloud?

It's hard to determine what's going on with the information you provided... Are you sure anything is published to cloud_in topic? And the topic rviz should subscribe is occupied_cells_vis according to this page. Is there any message when you echo this topic?

Glad it helps :) I did quite a bit digging in the source code as well. Since interactive marker requires mouse event handling and stuff, I suspected display by itself is not enough. Then I looked into how rviz is implemented, and found this interactionTool in the default plugin.

I have always wondered if this is doable myself, so I just spent some time to figure it out. Turned out that InteractiveMarker requires not only the display, but also the 'tool' to enable interaction. The following code is developed based on your snippet.

  rviz::Display *obj_ = visualization_manager_->createDisplay( "rviz/InteractiveMarkers", "Obj Loader", true );
  obj_->subProp("Reference Frame")->setValue("base_link"); // This probably works by itself, I added the next line just in case
  visualization_manager_->setFixedFrame("base_link");
  obj_->subProp("Update Topic")->setValue("/basic_controls/update");
  obj_->initialize(visualization_manager_);
  obj_->setEnabled(true);

  rviz::ToolManager *tool_manager = visualization_manager_->getToolManager();
  tool_manager->initialize();
  rviz::Tool *interact_tool = tool_manager->addTool( "rviz/Interact" );
  tool_manager->setCurrentTool(interact_tool);
  ROS_ASSERT(obj_);

You will need to include rviz/tool_manager.h somewhere.

Try reading some papers yourself.

Yes you can first solve the time difference d in that post, then estimate travel time of each communication. But the travel time will vary each time so I don't see why you would want to calculate travel time for synchronization purpose.

>>> import rosgraph
>>> master = rosgraph.Master('/mynode')
>>> master.lookupNode("node_name')

This worked for me, but not sure if it's safe to deal with ros master directly this way.

import rosgraph master = rosgraph.Master('/mynode') master.lookupNode('node_name')

What are you aiming for? The tf messages have stamps on them, can you use that stamp for synchronization?