Gaze estimation example on multiple detections

Hi.

I've followed suggested implementations and made some progress. But unfortunately it works only on first frame.

My script is basically the same as in script node (manager) and it seems to work well on the first frame -> for every detection, I get node.warn recognition result received and counter is decreased to 0. But on the next frame I only see the outputs for "Frame sent to recognition", but no recognitions are returned and counter is keeps on rising. Around counter 30 the script stops working completely although "while true" loop and without any warning or error.

Any suggestions and explanations what could be wrong?

Best regards,

Vojko

Here is also a part of debug output if it helps. As mentioned before the script stops working around Counter 26.

Processing frame number: 1

Added frame seq 1

[18443010A101660F00] [6.2] [1.846] [Script(4)] [warning] New msg frame, seq 1

[18443010A101660F00] [6.2] [1.876] [Script(4)] [warning] New msg detections, seq 1

[18443010A101660F00] [6.2] [1.877] [Script(4)] [warning] synced 1. Removed older sync values. len 0

[18443010A101660F00] [6.2] [1.878] [Script(4)] [warning] Frame sent to recognition. Counter 1

[18443010A101660F00] [6.2] [1.879] [Script(4)] [warning] Frame sent to recognition. Counter 2

[18443010A101660F00] [6.2] [1.881] [Script(4)] [warning] Frame sent to recognition. Counter 3

[18443010A101660F00] [6.2] [1.881] [Script(4)] [warning] Frame sent to recognition. Counter 4

[18443010A101660F00] [6.2] [1.892] [Script(4)] [warning] Recognition result received. Counter: 3

[18443010A101660F00] [6.2] [1.897] [Script(4)] [warning] Recognition result received. Counter: 2

[18443010A101660F00] [6.2] [1.902] [Script(4)] [warning] Recognition result received. Counter: 1

[18443010A101660F00] [6.2] [1.907] [Script(4)] [warning] Recognition result received. Counter: 0

Added detection seq 1

Processing frame number: 2

Added frame seq 2

[18443010A101660F00] [6.2] [2.918] [Script(4)] [warning] New msg frame, seq 2

[18443010A101660F00] [6.2] [2.936] [Script(4)] [warning] New msg detections, seq 2

[18443010A101660F00] [6.2] [2.937] [Script(4)] [warning] synced 2. Removed older sync values. len 0

[18443010A101660F00] [6.2] [2.939] [Script(4)] [warning] Frame sent to recognition. Counter 1

[18443010A101660F00] [6.2] [2.939] [Script(4)] [warning] Frame sent to recognition. Counter 2

[18443010A101660F00] [6.2] [2.941] [Script(4)] [warning] Frame sent to recognition. Counter 3

[18443010A101660F00] [6.2] [2.942] [Script(4)] [warning] Frame sent to recognition. Counter 4

[18443010A101660F00] [6.2] [2.944] [Script(4)] [warning] Frame sent to recognition. Counter 5

Added detection seq 2

Processing frame number: 3

Added frame seq 3

[18443010A101660F00] [6.2] [3.926] [Script(4)] [warning] New msg frame, seq 3

[18443010A101660F00] [6.2] [3.946] [Script(4)] [warning] New msg detections, seq 3

[18443010A101660F00] [6.2] [3.947] [Script(4)] [warning] synced 3. Removed older sync values. len 0

[18443010A101660F00] [6.2] [3.949] [Script(4)] [warning] Frame sent to recognition. Counter 6

[18443010A101660F00] [6.2] [3.949] [Script(4)] [warning] Frame sent to recognition. Counter 7

[18443010A101660F00] [6.2] [3.951] [Script(4)] [warning] Frame sent to recognition. Counter 8

[18443010A101660F00] [6.2] [3.953] [Script(4)] [warning] Frame sent to recognition. Counter 9

[18443010A101660F00] [6.2] [3.955] [Script(4)] [warning] Frame sent to recognition. Counter 10

…

I have found my mistake.

I had passthrorugh link set in pipeline from older implementation.

Now I get the recognitions for other frames also.

Best regards,

Vojko

Hi.

I have again stumbled on similar problem as before but on another node. This time on left and right eye imageManip. It works as expected on first frame. The image and the config are sent to the nodes and all results for the first frame are returned. But for the detections on the next frame nothing gets returned from these two nodes although new img and configs are sent to the nodes. As if the nodes are waiting for something to be release and to be able to process new data or the pipeline would be broken...

Any suggestions how to pinpoint where the data flow gets stuck?

Thanks and best regards,

Vojko

Hi.

I hope trace mode would show something (I hoped for something like error: crop out of bounds), but unfortunately it doesn't seem so. At least I didn't see anything. No error at all. How could I check if I'm reading fast enough? I would suspect that in this case the behavior would be more randomly distributed.

Is there a way to upload log files on this forum? Currently I get notice: Uploading files of this type is not allowed.

Here is also image of pipeline from pipeline_graph:

Would you suggest to have multiple scripts instead of one?

Best regards,

Vojko

Hi.

I've found and remove one bug. The messages in msgs list weren't removed properly. Now the second frame starts to process, but from 5 detections on the second frame only 4 get processed entirely. The fifth gets stuck in the same place. Again the detections of left and right eye stop to return the results.

Here is the trace log:

https://files.solvesall.com/d/s/vGpw4J5pkQ2x70iKnrxbxNAN4VigGOaI/dGqiI0IDsI-8kVzv65vpMpNDu3LProic-7rPATJtiwgo

Let me know, if you will have problems accessing the file.

Best regards,

Vojko

Hi.

Perhaps I have failed to mention that previous version was processing a video. In case of live stream from camera it successfully processed 26 sequences of one person.

Here are links to logs:

debug: https://files.solvesall.com/d/s/vHKQk4pqVEdbHcDkFEugKjysdzTQaR0P/nS8zuE3klAL6Pv5zT7H2xbU4NxY9GT8A-MbrgsR7Ewgo

trace: https://files.solvesall.com/d/s/vHKQl5zawgMciQWbaDErnCm4SEnyH7RX/ZVecxa4NxLejCXCb-9p-0PYYu_GNO2wy-yLqgwIbEwgo

It's interesting why does it always stop after 26 processed sequences and I have noticed that in later stages sequences can get skipped. I guess this is due to heavy load and the camera starts to skip frames.

Best regards,

Vojko

If my assumption about skipping sequences is correct, I am a little bit worried about the performance on up to 10 people. The is no need for 30 processed frames per second, but at least 4 or 5 would be desirable.

Best regards,

Vojko