This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Last revision Both sides next revision | ||
handover:aov012 [2016/10/13 05:25] Jesse Swan |
handover:aov012 [2016/10/13 11:44] Jesse Swan |
||
---|---|---|---|
Line 22: | Line 22: | ||
2016.287.03:28:26 WARNING: error m5 -906 mark5 return code 6: inconsistent or conflicting request | 2016.287.03:28:26 WARNING: error m5 -906 mark5 return code 6: inconsistent or conflicting request | ||
+ | |||
+ | * Autocorrelations look a bit askew in sub-bands 7 and 9. I'll monitor them over the next few scans and configure the dbbc if they persist (Lucas) | ||
+ | |||
+ | |||
**Katherine 12m:** | **Katherine 12m:** | ||
Line 36: | Line 40: | ||
* Missed scans 287-0027 and 287-0029 (Liz) | * Missed scans 287-0027 and 287-0029 (Liz) | ||
* 0328UT alarm sounded ALARM: error m5 -900 already off, WARNING: error m5 -906 mark5 return code 6: inconsistent or conflicting request, ALARM: error m5 -900 no scans, and then fixed itself. On closer inspection, log monitor seems to be printing information about scans from the last 2 hours in quick succession over 0321-0331UT. All outputs before and after this bracket match the schedule file. Seems to be fine now, and eremote was unaffected so appears to be a strange log monitor artefact rather than anything wrong with the experiment. Will monitor for now. (Liz) | * 0328UT alarm sounded ALARM: error m5 -900 already off, WARNING: error m5 -906 mark5 return code 6: inconsistent or conflicting request, ALARM: error m5 -900 no scans, and then fixed itself. On closer inspection, log monitor seems to be printing information about scans from the last 2 hours in quick succession over 0321-0331UT. All outputs before and after this bracket match the schedule file. Seems to be fine now, and eremote was unaffected so appears to be a strange log monitor artefact rather than anything wrong with the experiment. Will monitor for now. (Liz) | ||
- | * 0509UT Happened again. Alarm at 0457UT and 0503UT. Spoke to Jamie. Log file was reading from a tmp file which he thinks was probably the cause. Made new log file on /vlbobs/~ seems to be something was interfering with the tmp file and log monitor was having to rewrite experiment history (Liz). | + | * 0509UT Happened again. Alarm at 0457UT and 0503UT. Spoke to Jamie. Log file was reading from a tmp file which he thinks was probably the cause. Made new log file on /vlbobs/~ seems to be something was26 GB |
+ | 2016.287.06:05:10 Scan name = 287-0605b interfering with the tmp file and log monitor was having to rewrite experiment history (Liz). | ||
+ | |||
+ | *Autocorrelations look a bit askew in sub-bands 1, 3 and 8. I'll monitor them over the next few scans and configure the dbbc if they persist (Lucas) | ||
**yarragadee 12m:** | **yarragadee 12m:** |