This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
handover:a1505 [2015/02/14 08:12] cjordan |
handover:a1505 [2015/02/14 18:15] (current) liza |
||
|---|---|---|---|
| Line 8: | Line 8: | ||
| * 19:01 UT: Experiment started OK (Ross). | * 19:01 UT: Experiment started OK (Ross). | ||
| + | * 09:21 UT: 46 GB short (vk) | ||
| + | * 10:50 UT: 56 GB short (vk) | ||
| + | * 17:45 UT: 80 GB short (Liza) | ||
| + | * 18:00 UT due to occurence of "rfpic problem" restarted monica and rxmon. It took some time (Liza) | ||
| **Katherine 12m:** | **Katherine 12m:** | ||
| Line 16: | Line 20: | ||
| * 19:01 UT: Experiment started OK (Ross). | * 19:01 UT: Experiment started OK (Ross). | ||
| + | * sband tsys consistently high (vk) | ||
| **Yarragadee 12m:** | **Yarragadee 12m:** | ||
| Line 26: | Line 31: | ||
| * 07:15 UT: ERROR m5 -104 mk5cn: time-out, connection closed. The reason for this appears to be that mk5yg has lost track of pointers. As a result, disk_pos has jumped from ~15 TB to ~30 TB. I have contacted Jim and we have decided to record to HOB+0121 for the time being, as restarting mk5yg has not appeared to fix the issue with the pointers. (vk) | * 07:15 UT: ERROR m5 -104 mk5cn: time-out, connection closed. The reason for this appears to be that mk5yg has lost track of pointers. As a result, disk_pos has jumped from ~15 TB to ~30 TB. I have contacted Jim and we have decided to record to HOB+0121 for the time being, as restarting mk5yg has not appeared to fix the issue with the pointers. (vk) | ||
| - | Disk VSN: HOB+0123 ; 0 GB | + | Disk VSN: HOB+0121 ; 0 GB |
| * 07:53 UT: Restarting schedule. Missed scans: 045-0714 to 045-0753. Corresponding to 113.8 GB. (vk) | * 07:53 UT: Restarting schedule. Missed scans: 045-0714 to 045-0753. Corresponding to 113.8 GB. (vk) | ||
| + | * xband tsys consistently low by ~20K | ||
| + | |||