Hello,
is there any updates you can provide us on our questions above?
Also, can you please tell us which camera and objective you are using exactly for the camera calibration? We would then purchase the exact same camera for the camera calibration.
1 Like
Hi @VickNV ,
we tried installing DriveWorks 4.0 but had big issues doing so. We can’t afford spending more time on trying to install DriveWorks 4.0, which is why we are still using the NVIDIA DRIVE Software 10.
Nevertheless, can you please answer this question from my previous post:
Thank you very much.
Please share the output messages in the console.
Please create a topic for this. Maybe we can help you with it.
The most used cameras should be those in Hyperion. They are ON Semi - AR0231 ones listed in DRIVE Ecosystem - Hardware and Software | NVIDIA Developer. You can refer to DRIVE Hyperion Kit Quick Start Guide.
Hi @VickNV ,
I did not mean the car cameras. My question was regarding the external camera you are using for the camera calibration. Can you please tell us the exact model and objective of the external camera you are using for the camera calibration process?
Hello @VickNV ,
In the following the output messages of the console in a text file:
console_output_camera_calib (243.1 KB)
We cannot really tell why the calibration does not work.
Can you please provide us with information as soon as possible. I hope the console output messages help you.
Thanks in advance!
The information is in the forum topic I shared. Thansk.
As we still have not been able to successfully complete the camera calibration, I am writing in this forum post again.
In the meantime, we bought the same camera and lens you are using, namely the Sony A6000 with the SEL-20F28 lens, which you specified here:
With this new camera we collected new calibration data.
However, this still did not lead to a successful calibration.
In the following, I will again show the new results we obtained and also provide our data to you and would kindly ask you to check what is wrong with our calibration process.
First, it can be seen in the following image, that the corners of the calibration target can be detected by the calibration tool. But still, as mentioned above, only the blue dots are visible and the green overlay is not:
What is the reason for this?
Further, the validation-intrinsics-<camera>.jpg images again only show the blue points, but the red points and the yellow lines are not visible (which should be visible according to the documentation):
What is the reason for this?
Also, I would like to note that the the json-files of the car cameras, which are generated after the intrinsic calibration (where one needs to record a video of a target moving in front of every car camera), are approximately 400kB ~ 850kB. This file sizes are quite big (for text files) and the files cannot be opened (the PC crashes). Is it normal that these json-files are that big? If not, what could be the reason for this? How big should these files approximately be? How long should the recorded videos be for the intrinsic calibration?
In the following, you can find the data we used for the camera calibration: Download File (dlr.de)
Also, in the following you can find the terminal output after executing ./calibration-graph-cli --dir=<calib_data_path>:
terminal_output_camera_calibration (275.1 KB)
Can you please examine why the calibration is not working?
Thank you very much in advance!
May I know which DRIVE OS and DriveWorks versions you are using? Did you make sure autofocus is disabled?
We use DRIVE Software 10.0 and we disabled autofocus.
Besides focus, did you make sure you didn’t change any intrinsics during the process (e.g. zoom, images-stabilization)?
Do you have a chance to try on DRIVE OS 5.2.6 and DriveWorks 4.0? DRIVE Software 10 is quite an old release.
Yes, we made sure that we did not change any intrinsics during the process.
We already tried to install DRIVE OS 5.2.6 and DriveWorks 4.0 many times. However, we were not able to successfully update to the new release. For now, we cannot afford to spend more time on trying to update to the new release, but we will try to do so again in the near future. Also, all the other software we developed is already running on DRIVE Software 10.0. The only thing we need to do now is to calibrate the cameras. Besides, we already checked the forum and confirmed that other developers have been able to successfully calibrate the cameras with the DRIVE Software 10.0 release, which should therefore also work in our case.
Thanks for your confirmation. I’ll check it with our team.
Please check the information from 4.3.3 Extrinsic Calibration Validation and 4.1.1 targets.json respectively, and see if correcting the unit of the bar lengths can help with this issue. Thanks.
Thank you for your answer, that helped. We now get the green overlay on the targets, as seen in the following picture:
However, the ground plane is leaning towards the right and is not horizontal. Does this mean that the data we collected is not good and that we have to collect new data?
The coordinate frame is defined by the ground and wheel targets, so you should double-check that the special-targets.json contains the correct entries.
Yes, it is solved. I marked the solution above.
Thank you very much for your help.
1 Like
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.