[bug] ctest failure on compilation and low accuracy #219
Description
Hello,
I've cloned and compiled the latest version of CCTag available on github (commit 3cb3b00) with
- cmake -DCCTAG_BUILD_APPS=ON -DCCTAG_BUILD_TESTS=ON -DCCTAG_WITH_CUDA=OFF ../CCTag
- cmake --build .
My main system is Arch Linux with gcc 14.2.1 but I've also compiled/tested CCTag with gcc 13.1.1 for compatibility with nvcc. I've compiled it with and without CUDA support and in either case there are no errors during configuration or compilation but when I run ctest then the first test fails. Here's the output:
Test project /home/me/Documents/build/CCTag/build
Start 1: cctag_fitEllipse.test_ellipseFitting
1/2 Test #1: cctag_fitEllipse.test_ellipseFitting ...***Failed 0.03 sec
Start 2: geometry_ellipse.test_ellipse
2/2 Test #2: geometry_ellipse.test_ellipse .......... Passed 0.03 sec
50% tests passed, 1 tests failed out of 2
Total Test time (real) = 0.06 sec
The following tests FAILED:
1 - cctag_fitEllipse.test_ellipseFitting (Failed)
Errors while running CTest
Output from these tests are in: /home/me/Documents/build/CCTag/build/Testing/Temporary/LastTest.log
Use "--rerun-failed --output-on-failure" to re-run the failed cases verbosely.
When I run the test sample then only one or two markers are recognized (it varies by run) - also it takes very little time to run...
~/D/b/C/b/Linux-x86_64> ./detection --input ../../CCTag/sample/02.png -n 3
You called ./detection with:
--input ../../CCTag/sample/02.png
--nbrings 3
--bank
--params
--output
******************* Image mode **********************
Total time: 0.170000s wall, 0.180000s user + 0.020000s system = 0.200000s CPU (117.6%)
#frame 0
Detected 1 candidates
1476 827.272 17 1
1 markers detected and identified
The same happens with my own images. I also used a fresh Arch Linux install in a virtual box and I got the same result (so I don't think that some peculiarity of my specific system is causing it). When I ran the same process on Ubuntu 20.04 LTS in a virtual box it worked fine. Both ctests passed and all tags were recognized (it took much longer but that's probably in part because it ran in a VB with limited resources):
You called ./detection with:
--input ../../CCTag/sample/02.png
--nbrings 3
--bank
--params
--output
******************* Image mode **********************
Total time: 7.118771s wall, 8.590000s user + 0.080000s system = 8.670000s CPU (121.8%)
#frame 0
Detected 6 candidates
1449.76 666.733 67 1
408.464 782.559 11 1
1703.4 513.985 16 1
1476.09 827.202 17 1
785.149 875.716 22 1
947.186 769.549 25 1
6 markers detected and identified
Then I installed Ubuntu 24.04 LTS in a virtual box and I got similar results as on my Arch Linux installations (the first ctest failed and one, two or at most three markers were recognized in the samples). Since this happens on both Arch Linux and Ubuntu I don't think that my use of Arch Linux is the problem.
I've also tested CCTag version 1.0.3 on my Arch Linux and on Ubuntu 24.04 LTS with the same results.
Another issue that may be related to this one is that my AliceVision installation compiles and runs without problems if I compile without CCTags (well, almost without problems, there is a seg fault just when I exit Meshroom...) but when I compile with CCTags then AliceVision seg faults (in cameraInit) as soon as I import one or more images.
Have you come across this issue? Have you been able to run CCTag on an up-to-date Linux installation? Do you think it's an issue with CCTag or am I doing something wrong? Maybe the new versions of some dependencies (boost, opencv, ...) cause an issue - I haven't tested that yet.
Thanks for your help!