[aravis] Re: Getting Thermal Imaging data using python and ARAVIS

  • From: Emmanuel Pacaud <emmanuel.pacaud@xxxxxxxxxxxxx>
  • To: aravis@xxxxxxxxxxxxx
  • Date: Sun, 24 Dec 2017 18:38:58 +0100


Le ven. 22 déc. 2017 à 16:09, Saurabh Chatterjee <saurabhsaurc@xxxxxxxxx> a écrit :

Ok, I modified the code to print the time taken for each frame.

Indeed, what happened is that it seemed to slow down pretty bad for certain frames
Frame:  110  time taken:  0.0009679794311523438
Frame:  111  time taken:  0.001013040542602539
Frame:  112  time taken:  0.0014612674713134766
Frame:  113  time taken:  0.0010993480682373047
Frame:  114  time taken:  0.004855155944824219
Frame:  115  time taken:  0.48161911964416504
Frame:  116  time taken:  0.001965761184692383
Frame:  117  time taken:  0.0023725032806396484

Because of those bad frames, it slows down the entire frame rate.

So it is probably a packet resend problem.

Now for the bad news. I meddled with the packet resend settings and ended up even worse off- now the packet error seems to occur practically every other frame.
I don't even know how to get back to the previous settings.. Hopefully I'll work it out..

Try to run your software with ARV_DEBUG=stream:3. It will give you some statistics about resent packets.

Also, since aravis 0.5.10, packet resend requests are limited, which should avoid request storm. This limit can be adjusted using packet-request-ratio property of ArvStream.



Other related posts: