camera_pose_calibration's People
Forkers
dbolkensteyn utnuclearroboticspublic sunbuny wilson-ko c722996 drudolph0 rohitmenon86 waltyeh ziliaogithub zfxu ianoshan jkbjh eyildiz-ugoe icameling tassos asifzhcet11 jcjs fagan2888 theokast fnadon marinehorsecamera_pose_calibration's Issues
Question!
I am so sorry to bother you guys, I am pretty new in the ROS community. My question is, in what way I can set up the configuration of parameters, in order to make the extrinsic calibration, I already run both launch file but i got this message:
[ INFO] [1548793318.831677234]: waitForService: Service [/standalone_nodelet/load_nodelet] has not been advertised, waiting...
[ INFO] [1548793318.852237981]: Initializing nodelet with 4 worker threads.
[ INFO] [1548793318.874800026]: waitForService: Service [/standalone_nodelet/load_nodelet] is now available.
Best regards!!!
Pattern msg type
I am calibrating a kinect with this package but I couldnot find enough description on how to define a Pattern msg type with distance and size of the asymmetric circles pattern. I am using the pattern from this link: https://nerian.com/support/resources/patterns/ with A4 size patterns.
Can you help me fix this? Thanks in advance.
Indigo onCalibrateTopic: stuck in infinite loop
I'm getting stuck in this while loop of node.cpp:
sync.registerCallback(boost::bind(&synchronizationCallback, boost::ref(promise), _1, _2));
// Run a background spinner for the callback queue.
ros::AsyncSpinner spinner(1, &queue);
spinner.start();
ROS_INFO_STREAM("Done creating background spinner.");
while (true) { **<== I get stuck here**
if (!node_handle.ok()) return false;
if (future.wait_for(boost::chrono::milliseconds(100)) == boost::future_status::ready) break;
}
ROS_INFO_STREAM("Done waiting for the future.");
The synchronizationCallback is never called. I think this means the node is not receiving the cloud_topic and image_topic messages, but I've double-checked that the camera_pose_calibration node is subscribed correctly and the camera topics are active. I have a fork of the repo here if you want to see exactly what my service client looks like.
rviz.launch refers to 'dr_extrinsic_calibration' which doesn't exist
here.
Copy/pasta?
No output + Unclear Things
I've my pattern fixed on the workstation, and my "world" (which is another fixed frame) frame's origin, let's say, is my pattern's origin, since I don't have a robot and I don't want to have a different frame. So my camera and the world frames are basically having the same origin.
Given this, I execute the following commands:
rosrun tf static_transform_publisher 0.0 0.0 0.0 0.0 0.0 0.0 1.0 world pattern 1000
roslaunch camera camera.launch
roslaunch camera_pose_calibration nodelet.launch
rosservice call /calibrate_topic "tag_frame: 'pattern' target_frame: 'map' point_cloud_scale_x: 1.0 point_cloud_scale_y: 1.0 pattern: {pattern_width: 4, pattern_height: 11, pattern_distance: 4.0}"
However the last command doesn't return anything. No errors, no results, nothing. I check rostopic echo /detected_pattern
and there is nothing in there either. Here is my how stereo images look like:
I don't know what's wrong, but it doesn't seem to work.
Apart from that, there are a couple of issues with this package, which makes the whole process frustrating.
-
The right-top corner blob is defined as the origin
must be marked on that image. Depending on how you look at this pattern, the statement is ambiguous at the best. -
Chain of commands is missing. What to run first, what's the order? Static publisher and then the nodelet, or?
-
The pose of the camera to the fixed frame will then be returned and optionally published.
the command returns nothing, and nothing is published. There is no single error message or whatsoever. One spends a lot of time without a result. -
The circle center-to-center distance of the printed pattern.
which unit is the distance in? Cm?
target_frame parameter is unused
master branch:
When using calibrateFile, part of the service request is target_frame. This parameter appears to be unused. Here's the output when srv.tag_frame is set to calibration_circles_frame, and srv.target_frame is set to base_link. Notice that base_link doesn't appear.
Have you guys actually tested the package yet? The tf's I'm getting are not even close to aligned right, but that could very well be user error on my end.
dr_base can not be found
Hi,
i want to calibrate my kinect for more accuracy in order to build a 3D map , the problem with this package is the dependency 'dr_base' , i can not find it.
when i try to compile the package The catkin_make command give this error :
Could not find the required component 'dr_base'.
please help
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. ๐๐๐
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google โค๏ธ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.