split openni_launch for resource-constrained systems [closed]

asked 2012-05-07 06:38:49 -0500

daniel_maier gravatar image

updated 2016-10-24 08:34:00 -0500

ngrennan gravatar image

What is the best way to split openni_launch into some modules running on a (resource-constrained) robot with an Asus Xtion Pro Live sensor providing raw data, and processing modules running on a (powerful) remote PC, performing registration and point cloud construction?

edit retag flag offensive reopen merge delete

Closed for the following reason question is not relevant or outdated by tfoote
close date 2015-03-03 01:39:21.037522