This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
handover:r1756 [2016/09/06 23:57] Jesse Swan |
handover:r1756 [2016/09/07 12:32] (current) Jesse Swan |
||
---|---|---|---|
Line 1: | Line 1: | ||
====== R1756 ====== | ====== R1756 ====== | ||
**General Comments** | **General Comments** | ||
- | * I messed up, and didn't start the telescopes at 1700UT. By the time I realised it was 2300UT. All telescopes running by 2320UT | + | * I messed up, and didn't start the telescopes at 1700UT. By the time I realised I was on, it was 2300UT. All telescopes running by 2320UT (JS) |
Line 9: | Line 9: | ||
Disk VSN:HOB+0120 | Disk VSN:HOB+0120 | ||
- | Data volume at beginning: 5730 GB | + | Data volume at beginning: 11660 GB |
- | * 1400UT Experiment started OK (JS) | + | * 2320UT Experiment started 6 hours late (JS) |
- | * 0020UT Tracking outside tolreance messages in eremote control. Accordign to the wiki this happens on windy days, keeping an eye on this. (AK) | + | * 23:32UT, bad scan 250-2332 at 2016.250.23:32:31, incorrect data mode ! (WH) |
- | * 0022UT Wind stow activated (00:22:18) | + | * 23:36UT first good scan 250-2336 at 2016.250.23:36:01 with 11683 GB on disk, exp down 790 GB (WH) |
- | * 0027UT Wind stow released (00:27:31). Scans affected** 250-0023** through to **250-0027**. (AK) | + | * 12:09UT Note that delay seems to be drifting. Seems to be steady at this point, not changing by a huge amount. Drift started at 0800 UT. (Bryn) |
- | * 0157UT Auto-stow sequencing from 01:57:24 to 02:03:05. Scans affected 250-0157 to 250-0202 | + | |
- | * 0210UT Auto-stow sequencing 02:10:59 to 02:16:09. Scans affected 250-0210 to 250-0215 | + | |
- | * 0310UT Auto-stow sequencing 03:10:23 to 03:34:54. Scans affected 250-0311 to 250-0334 | + | |
- | * 0335UT Auto-stow sequencing 03:35:54 to 03:55:13. Scans affected 250-0335 to 250-0354 | + | |
- | * 0356UT Auto-stow sequencing 03:56:20 to 04:01:57. Scans affected 250-0356 to 250-0401 | + | |
- | * 0404UT Auto-stow sequencing 04:04:28 to 04:23:00. Scans affected 250-0403 to 250-0422. | + | |
- | * 0650 UT disk_pos lagging by at approx 20 Gb at last check. (AK) | + | |
- | * Final disc pos 56 GB behind schedule (Ellen) | + | |
**Katherine 12m:** | **Katherine 12m:** | ||
- | Disk VSN:HOB+0051 | + | Disk VSN: USN-0097 4000 GB |
- | + | ||
- | Data volume at beginning: 0 GB | + | |
- | * 1400UT Experiment started OK (JS) | + | |
- | * 0650 UT disk_pos lagging by approx 55 Gb at last check. (AK) | + | |
- | * Final disc pos 62 GB behind schedule (Ellen) | + | |
+ | Data volume at beginning: 0 GB (WH) | ||
+ | * 23:43UT first good scan 250-2343a at 2016.250.23:43:11 with 0 GB on disk, exp down 806 GB (WH) | ||
**Yarragadee 12m: ** | **Yarragadee 12m: ** | ||
Disk VSN: USN+0225 | Disk VSN: USN+0225 | ||
- | Data volume at beginning: 0 GB | + | Data volume at beginning: 5367 GB |
- | * 1400UT Experiment started OK (JS) | + | * 2320UT Experiment started 6 hours late (JS) |
- | * 2059UT WARNING: error ib -4 gpib device time-out on response c1. Both clkoff and maserdelay are responsive, nothing seems wrong. (AK) | + | * 23:21UT first good scan 250-2321a at 2016.250.23:21:15 with 5367 GB on disk, exp down 773 GB (WH) |
- | * 0040UT disk_pos is lagging by approx 60 gb. (AK) | + | |
- | * 0650 UT disk_pos lagging by approx 100 Gb at last check. (AK) | + | |
- | * Final disc pos 143 GB behind schedule (Ellen) | + |