It looks like you're new here. If you want to get involved, click one of these buttons!Sign In
It looks like you're new here. If you want to get involved, click one of these buttons!
I am currently using NCS1 with NCSDK2. I found that the largest time cost lied within the function to read final result
So I traced down the calling
sem_wait. It appears that it´s waiting for a thread to return which I don't know more information about because I cannot enduring looking deeper into the code....
Is the thread, by my guess, dealing with the computation inside stick or something else? Because by the meaning of
ncFifoReadElem, by instinct, I thought it's just reading the final output from USB. But that would be weird because the time cost for
ncFifoReadElem is much bigger than that for
ncFifWriteElem, considering the size of input image and output result.....
I would really appreciate it if someone could help me with this issue. So far I can only achieve 4 FPS at most for YOLOV2-tiny.