Double entry into "processing" state
lacker opened this issue · comments
Right after startup we get:
[2022-10-18 23:19:04,970 - INFO - automator.py:200] New state: not-tracking
[2022-10-18 23:19:04,972 - INFO - subarray.py:38] New subarray object for array_1
[2022-10-18 23:19:04,972 - INFO - automator.py:251] Initialised new subarray object: array_1 in state not-tracking
[2022-10-18 23:19:04,972 - INFO - automator.py:388] No active recording for endof track for array_1
[2022-10-18 23:19:18,795 - INFO - automator.py:200] New state: tracking
[2022-10-18 23:19:18,796 - INFO - automator.py:311] array_1 in tracking state with nshot = 0
[2022-10-18 23:19:18,796 - INFO - automator.py:313] Preparing for processing.
[2022-10-18 23:19:18,796 - INFO - automator.py:319] ['blpn0/0', 'blpn1/0', 'blpn2/0', 'blpn3/0', 'blpn4/0', 'blpn5/0', 'blpn6/0', 'blpn7/0', 'blpn8/0', 'blpn9/0', 'blpn10/0', 'blpn11/0', 'blpn12/0', 'blpn13/0', 'blpn14/0', 'blpn15/0', 'blpn16/0', 'blpn17/0', 'blpn18/0', 'blpn19/0', 'blpn20/0', 'blpn21/0', 'blpn22/0', 'blpn23/0', 'blpn24/0', 'blpn25/0', 'blpn26/0', 'blpn27/0', 'blpn28/0', 'blpn29/0', 'blpn30/0', 'blpn31/0', 'blpn32/0', 'blpn33/0', 'blpn34/0', 'blpn35/0', 'blpn36/0', 'blpn37/0', 'blpn38/0', 'blpn39/0', 'blpn40/0', 'blpn41/0', 'blpn42/0', 'blpn43/0', 'blpn44/0', 'blpn45/0', 'blpn46/0', 'blpn47/0', 'blpn48/0', 'blpn49/0', 'blpn50/0', 'blpn51/0', 'blpn52/0', 'blpn53/0', 'blpn54/0', 'blpn55/0', 'blpn56/0', 'blpn57/0', 'blpn58/0', 'blpn59/0', 'blpn60/0', 'blpn61/0', 'blpn62/0', 'blpn63/0']
[2022-10-18 23:19:18,809 - INFO - automator.py:321] 300.0
[2022-10-18 23:19:18,809 - INFO - automator.py:325] Starting tracking timer for 310.0 seconds
[2022-10-18 23:21:22,570 - INFO - automator.py:200] New state: not-tracking
[2022-10-18 23:21:36,582 - INFO - automator.py:200] New state: tracking
[2022-10-18 23:21:36,582 - INFO - automator.py:311] array_1 in tracking state with nshot = 0
[2022-10-18 23:21:36,583 - INFO - automator.py:313] Preparing for processing.
Subsequently there are more errors but I think this is the first point at which things seem troubled. We shouldn't start processing twice here. And FWIW at the end of all this there are no files on buf0.
The real mystery here is why we didn't move to processing at the not-tracking event at 2022-10-18 23:21:22,570 . It looks like nshot should have been zero from before. But we didn't enter processing. Hmm.
I think nshot isn't 0 - it's "0". hehe
fixed in 408c1fe