I'm using the fcvNCCPatchesOnRectu8 function that appeared in FastCV 1.5
I managed to get it working correctly. However, performance wise is slower than OpenCV matchTemplate on and Android LG G2 smartphone. A bit disappointing.
Then I found that I needed to enable the fastest implementation available with:
fcvSetOperationMode( (fcvOperationMode) FASTCV_OP_PERFORMANCE );
However when I use this initialisation code the App crashes at the fcvNCCPatchesOnRectu8 and in the LogCat I see:
E/fastcv_lib_log(28072): vendor/qcom/proprietary/fastcv-noship/src/cpu/fastcvNCCPatchC.cpp@853: (iNCC >= -128) && (iNCC <= 128) Assertion failed
As I don't have the source code I don't know how to debug this assertion. It worked correctly before I added the initialisation code.
Any help?
Hi,
In theory that error should not happen. Can you log the input data for this API and put them in a zip file? You can post it or deliver it for us to investigate the issue.
Thanks,
-Jeff
Hi Jeff,
I have made a self contained example that reproduces the assertion. See attached file.
To test it I just call my test() function from an android ndk app.
The test function just generates a random image using opencv. Then I extract a 16x16 region from the first image to use as a patch. The assertion only happens in android when I uncomment the first line of code
//fcvSetOperationMode( (fcvOperationMode) FASTCV_OP_PERFORMANCE );
If I leave it commented I don't get the assertion and I get some matching location in best_xs, best_ys
The assertion doesn't occur in Windows even if I uncomment the fcvSetOperationMode line.
Martin
I just realised I can't attach files to a reply. here is the code:
Hi Jeff,
Did you get my reply? I can't see it posted in the thread.
Martin
Oh well, now I see that my last reply appears in the thread!
I'll repost the message that I posted on the 15th Oct by pressing “Post reply” at the bottom of the page rather than the “reply” near the post.
The code below produces the assert when I uncomment the first line fcvSetOperationMode( (fcvOperationMode) FASTCV_OP_PERFORMANCE ); otherwise it runs as expected.
Martin,
Thank you for reporting this issue. A bug was found and fixed for upcoming 1.6.0 release. FastCV 1.6.0 release will be posted soon.
Appreciate your help in improving FastCV.
Cheers,
-Jeff
That's great! I look forward to trying FastCV 1.6