All antennas, scan 2 (003-066) waiting at limit. Source not risen yet? Scan missed. Turns out this happens a lot. Was this schedule scheduled for the correct day/time?
grep -B 40 'ERROR fl' aum005ke.log | grep scan_name for ke,yg grep -B 40 'ERROR fl' aum005hb.log | grep "source="
to get list of missed scans.
Missed scans problem is a scheduling issue - all scans/all telescopes are in the counter-clockwise wrap (W in SKD file)
also, for HB12m, there is now a delaylive2 which will plot the maser to dbbc3 difference.
on ops8: delaylive2 hb
Disk VSN: flexbuff | Data volume at beginning: - GB
Missed scans: 2018.230.16:00:50.00:source=0003-066,000340.29,-064017.4,1950.0,ccw 2018.230.16:02:54.00:source=2255-282,225522.47,-281425.6,1950.0,ccw 2018.230.16:14:04.00:source=0229+131,022902.51,130940.6,1950.0,ccw 2018.230.16:17:37.00:source=1759-396,175913.50,-394012.1,1950.0,ccw +++++++++++ many more
Disk VSN: | Data volume at beginning: 11622.083 GB
Missed scans due to source below limit: 2018.230.16:02:55.88:scan_name=230-1603,aum005,ke,92,92 2018.230.16:17:38.83:scan_name=230-1618,aum005,ke,200,200 2018.230.16:31:26.85:scan_name=230-1632,aum005,ke,71,71 2018.230.16:33:26.87:scan_name=230-1634,aum005,ke,48,48 +++++++ run bash from top for full list
Disk VSN: | Data volume at beginning: 1316.247 GB
Missed scans due to source below limit: 2018.230.16:14:00.03:scan_name=230-1615,aum005,yg,146,146 2018.230.16:17:37.08:scan_name=230-1618,aum005,yg,200,200 2018.230.16:31:29.03:scan_name=230-1632,aum005,yg,69,69 +++++ many more. Run bash from top.