You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It appears that the translation returned by get_extrinsic_parameters(...) is provided in meters, which seems unusual given that the depth data is in millimeters. This discrepancy can cause problems when using this information for custom depth-to-point-cloud conversions (outside of the k4a framework). What was the rationale behind returning the values in meters?
I assume that changing this behavior might cause applications to no longer function as expected. However, it should at least be explicitly mentioned in the method's documentation.
The text was updated successfully, but these errors were encountered:
It appears that the translation returned by
get_extrinsic_parameters(...)
is provided in meters, which seems unusual given that the depth data is in millimeters. This discrepancy can cause problems when using this information for custom depth-to-point-cloud conversions (outside of the k4a framework). What was the rationale behind returning the values in meters?https://github.com/etiennedub/pyk4a/blob/master/pyk4a/calibration.py#L211
I assume that changing this behavior might cause applications to no longer function as expected. However, it should at least be explicitly mentioned in the method's documentation.
The text was updated successfully, but these errors were encountered: