-
Notifications
You must be signed in to change notification settings - Fork 13
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
Error when calling create_source with OpenNISubscriber as 2nd argument #7
Comments
Did you call something like:
from somewhere in your python script? This initialises the underlying c++ node. |
right. danke! Still doesn't work but now is opencv complaining about some incompatibilities between images. Maybe there's something weird on the creation of the cv::Mat, or maybe is some exotic property on Senz3D generated images.
|
You could be running into the same problem on ecto 0.6.8 as being hunted in plasmodic/ecto#272. As it is there, suspicious that you're dropping into Get the ecto sources and checkout the 0.6.7 tag to make sure. |
mmm.... don't think so, as it works for the images provided by kinect (well... actually, it also fails but something different and later. confirmed : it also fails with 0.6.7 tag. Must be an issue with the Senz3D BGR format. Maybe it's just too big! (the resolution is 720x1280) |
Hi, not sure if this is an issue at all, or I'm just trying to over abuse camera_base. Feel free to close this if so!
I'm trying to run object_recognition_capture orb_template with a non OpenNI camera (see this post on ORK group), so I pass OpenNISubscriber to create_source instead of OpenNISource (and also remove the mask_depth from the outputs_list). But I get an error complaining that this is not a ROS node:
I crudely tried to call rospy.init_node but changes nothing. So it's really a missing ros::init() in a C++ ecto cell?
Please note that I'm trying to use ORK in an undocumented way, so... it's probably that I'm just trying something stupid without understanding the ecto_image_pipeline.
The text was updated successfully, but these errors were encountered: