We evaluated the sparse optical flow by the following method on Orin:
Here is the results of three test datasets by the same PyrLK parameters:
These results show that vpiSubmitOpticalFlowPyrLK() systemically has larger errors comparing with its peers: cv::cudaSparsePyrLkOpticalFlow() and cv::calcOpticalFlowPyrLK(). Our question is that is it normal or we made some mistakes on parameter settings?
Moving this to the Jetson category for visibility.
Discussions relating to the Jetson DevKits and other Embedded computing devices
Do you have sources/instructions to reproduce this issue?
So we can check this with our internal team?
Hi Tom, Thanks for reply. Yes, i just created a public repo at:
you can check out our source code and datasets to repeat this work
Just want to confirm the environment as well.
Which JetPack version do you use? Is it JetPack 5.1.2?
nvidia@nvdia-desktop:~$ sudo apt-cache show nvidia-jetpack
Maintainer: NVIDIA Corporation
Depends: nvidia-jetpack-runtime (= 5.0.2-b231), nvidia-jetpack-dev (= 5.0.2-b231)
Jetson - Embedded AI Computing Platform | NVIDIA Developer
Description: NVIDIA Jetpack Meta Package
Would you mind testing this on the latest JetPack 5.1.2?
Usually, enhancement won’t backport to the previous release.
Does 5.1.2 update nv-vpi libs?
Hi Aasta, Thanks for the suggestion, I am wondering if you have NVIDIA internal nv-vpi sparse optical flow accuracy test report?
Finally I had a chance to update my JetPack to 5.1.2, and redo the process. The results are identical with the previously posted plots.
Thanks for the testing.
We will check this issue with our internal team and get back to you.
We don’t guarantee that our result will be aligned with the OpenCV’s output.
However, there are several parameters in the Pyramidal LK Optical Flow.
Have you tried to tune them?
For example, how many pyramid levels are you using for VPI? Is it the same as OpenCV?
Yes, I used the same parameters as that in opencv PryLK algorithm. Do you have an internal evaluation document to share? I am just curious how do you engineers evaluate it? Thanks a lot!
We cannot share internal evaluations and reports here.
But we can check if any info for you with our internal team.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.