-
Notifications
You must be signed in to change notification settings - Fork 5
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
Hanging pc_completion_client when testing pipeline #1
Comments
first run:
Then when everything starts up run:
you want to tell the client what topic to use to complete the individual objects, not what channel to listen for the pointcloud from. I had been running the same scene through various networks so I made the node doing the individual object completions easier to change at runtime. |
actually you will want to use:
This is where the scene completion node determines how each segmented partial object will be completed. It is probably hanging right here: As I don't have any ROS_INFO statements prior to the waitForServer line. If you add a print statement there to say what server it is waiting on, could you make a pull request please. |
I get an error from pc_cnn_mesh: `[ INFO] [1513345551.781055825]: received new CompleteSceneGoal 2017-12-15 08:45:52.848653: E tensorflow/stream_executor/cuda/cuda_dnn.cc:385] could not create cudnn handle: CUDNN_STATUS_INTERNAL_ERROR And here is the log: |
I was able to force keras to not try to use all the gpu memory and got: empty result... can this be related to the transforms used? what can lead to empty meshes? |
I am trying to use the pc_scene_completion framework to complete shapes of a static (for now) point cloud. The point cloud is generated from a single RGB-D image saved as .pcd and then posted as /camera_cloud topic using ros. I am starting a pc_scene_completion_client node like this in python:
result = pc_scene_completion_client.complete_scene('/camera_cloud')
After that I start the pc_completion pipeline:
roslaunch pc_pipeline_launch pc_pipeline.launch
In rviz I can see my cloud and the /filtered_pc part but the client never gets any results (hangs)
rostopic list gives:
/SceneCompletion/cancel /SceneCompletion/feedback /SceneCompletion/goal /SceneCompletion/result /SceneCompletion/status /camera_cloud /camera_info /clicked_point /depth/object_completion/cancel /depth/object_completion/feedback /depth/object_completion/goal /depth/object_completion/result /depth/object_completion/status /depth_tactile/object_completion/cancel /depth_tactile/object_completion/feedback /depth_tactile/object_completion/goal /depth_tactile/object_completion/result /depth_tactile/object_completion/status /filtered_pc /initialpose /move_base_simple/goal /myshape /parameter_descriptions /parameter_updates /partial_object_completion/cancel /partial_object_completion/feedback /partial_object_completion/goal /partial_object_completion/result /partial_object_completion/status /rosout /rosout_agg /tf /tf_static
and
rosnode list gives:
/my_pcl_tutorial /pc_cnn_mesh /pc_filter/pc_filter /pc_scene_completion /pc_scene_completion_client /rosout /rviz_1513189826137779454
Also tried using /filtered_pc as input to complete_scene with no more success.
The text was updated successfully, but these errors were encountered: