DRIVE OS Version: Provide DRIVE OS version. Example: 7.0.3
Issue Description: Provide issue description and attached logs as text message instead of images
When I ran the sample app “nvmimg_ldc” on the Thor devkit (DriveOS 7.0.3) to perform lens distortion correction on a 3840x2160 YUV data set with an output image size of 1024x512, the average processing time was 1774µs. Similarly, when I ran “nvmimg_ldc” on the Orin devkit (DriveOS 6.0.10), the average processing time was 1056µs. I expected the processing time to be faster on Thor, so why is it so slow?
On the other hand, when comparing without changing the output size, Thor performed better by correcting the distortion from 3840x2160 and keeping the output size at 3840x2160. In this case, Thor took 2386us and Orin took 4935us.
Dear @yuki.ito.j8s ,
Could you please share repro steps and needed files?
I uploaded the logs earlier, did you find the cause of the problem?
Dear @yuki.ito.j8s ,
Could you please share the config file and input file to repro the issue?
ldc_resize_repro.zip (22.3 MB)
Since I cannot provide the original config and YUV data, I’ve provided dummy config and YUV data. I’ve attached the following to help you reproduce the issue, so please check them out. Even with these, Thor takes longer to process than Orin.
・Input file: test_cam_0_out_1.yuv
・orin conf file: ldc_sample_orin.conf
・thor conf file: ldc_sample_thor.conf
Also attached are the execution result logs.
・orin_ldc_resize_from3840x2160to1024x512.log
・thor_ldc_resize_from3840x2160to1024x512.log
Thank you for sharing the logs. I am able to repro the issue. Let me check with engineering team and update you.
1 Like