This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
handover:aug033 [2016/11/25 05:50] Bryn Emptage |
handover:aug033 [2016/11/25 19:33] (current) Bryn Emptage |
||
---|---|---|---|
Line 40: | Line 40: | ||
* 19:33UT Experiment started 3 minutes late due to delay in setup resulting from issues with ke eremotecontrol. First scan 329-1939, source= 1144-379. | * 19:33UT Experiment started 3 minutes late due to delay in setup resulting from issues with ke eremotecontrol. First scan 329-1939, source= 1144-379. | ||
* 05:48UT Alarm source not reached in time. There was a wind stow. Affected scans between 5:44 and 05:49 UT. (Lucia) | * 05:48UT Alarm source not reached in time. There was a wind stow. Affected scans between 5:44 and 05:49 UT. (Lucia) | ||
+ | * 06:42UT - Wind stowed for scans 330-0644 to 330-0708. Still too windy so schedule was halted because alarm sounds every single scan. Missed scans 330-0711 to 330-0806 (80 GB).(Ellen) | ||
+ | * 08:08UT - Wind settled down. First scan back 330-0811. (Ellen) | ||
+ | * 17:04UT Alarm sounded,"Previous source in this schedule not reached before new source was commanded" doesn't seem to be because of wind stow or any other system error. Next source was reached on time, and is now tracking. Affected scan 330-1704. Will monitor for recurrence and possible causes. (Liz) | ||
+ | * 18:59UT "Previous source in this schedule not reached before new source was commanded" happened again. This time, live page indicates wind stow. Waiting for self-recovery, however, doesn't seem to be windy enough to stow. Checking wiki but may run out of time on the experiment (Liz) | ||
+ | * 19:31Ut According to Jamie, it has been windy enough to stow so this is nothing to worry about. Missed scans 330-1858 to 330-1932 (Liz) | ||
+ | |||
+ | |||
+ |