-
Notifications
You must be signed in to change notification settings - Fork 7
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
Update RGBD camera config files #94
Comments
The |
Currently missing specs (ASUS Xtion Pro Live, ref):
|
Sensor transform and depth accuracy estimations for Kinect 1, Kinect 2 and ASUS Xtion Pro Live: Filippo Basso, Emanuele Menegatti, and Alberto Pretto, "Robust Intrinsic and Extrinsic Calibration of RGB-D Cameras", 2018 (arxiv). |
Kinect 1 & Kinect 2 resolution, FOV and depth distance (thanks, @jgagom; https://github.com/roboticslab-uc3m/sign-language-papers/issues/19#issuecomment-479110680): |
Kinect intrinsics (includes distortion params) and extrinsic transform (ref):
I guess this is the Kinect 1 sensor, but given resolution values look suspicious. |
Even moar params for both Kinects at Diana Pagliari and Livio Pinto, "Calibration of Kinect for Xbox One and Comparison between the Two Generations of Microsoft Sensors", 2015 (full text): resolution, distance, FOV, intrinsics (given in millimeters and pixels)... |
Commit d8af84b unbreaks the ASUS Xtion for recent YARP releases. |
Kinect2 depth parameters as used in OpenCV's rgbd module samples (link): namespace Kinect2Params
{
static const Size frameSize = Size(512, 424);
// approximate values, no guarantee to be correct
static const float focal = 366.1f;
static const float cx = 258.2f;
static const float cy = 204.f;
static const float k1 = 0.12f;
static const float k2 = -0.34f;
static const float k3 = 0.12f;
}; // namespace Kinect2Params |
PR robotology/yarp#1960 added a new required
physFocalLength
parameter to groupsRGB_INTRINSIC_PARAMETERS
andDEPTH_INTRINSIC_PARAMETERS
. We should update share/sensors/conf/asus-xtion.ini. Featured in YARP 3.2.0.The text was updated successfully, but these errors were encountered: