-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
L515-How to extract poses and the intrinsics of the camera #11057
Comments
Hi @Ceciliammm You can retrieve the L515 camera's intrinsics and the extrinsics (which include translation and rotation) with the pre-made Windows version of the RealSense SDK's rs-enumerate-devices tool using the instructions at #3569 (comment) |
but can I extract the intrinsics and extrinsics from the recorded BAG file of the camera L515? |
You can set a bag file as the data source for a script instead of a live L515 camera using the SDK instruction cfg.enable_device_from_file and the script will behave as though a live camera is is being used with it. If you are able to use Python scripting then #2869 (comment) has a Python script for getting intrinsics with the get_intrinsics instruction. #10457 has Python scripting for accessing extrinsics with the get_extrinsics_to instruction. |
but when I add a bag file as the source, when I run the script that extract intrinsics, something goes wrong with the following result: |
In the script at #10457 they had not included cfg.enable_device_from_file in the script to tell the program to use the bag as the data source instead of a live camera. The enable_device_from_file instruction should also be placed before the pipeline start line, like in the example code at the link below. Can you confirm please that your extrinsics-accessing code has the enable_device_from_file instruction and that the instruction is placed before the pipe start line in your script, please? |
My problem has been solved. Thank you very much! |
You are very welcome, @Ceciliammm - thanks very much for the update! |
Please provide a description of the problem
The text was updated successfully, but these errors were encountered: