This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
handover:r1758 [2016/09/19 16:36] Jesse Swan |
handover:r1758 [2016/09/20 00:30] (current) Jim Lovell |
||
|---|---|---|---|
| Line 7: | Line 7: | ||
| Data volume at beginning: 23293.563 GB | Data volume at beginning: 23293.563 GB | ||
| + | |||
| + | * 17:00UT Experiment started OK. (AK) | ||
| + | * 00:09UT Paused to swap modules. Back observing with scan 264-025. Scans missed 264-0009b to 264-0020 inclusive (Jim) | ||
| **Katherine 12m:** | **Katherine 12m:** | ||
| Line 15: | Line 18: | ||
| * During setup, ke dbbc needed a power cycle, This fixed the issue of drifting time difference and bad auto correl spectra. (AK) | * During setup, ke dbbc needed a power cycle, This fixed the issue of drifting time difference and bad auto correl spectra. (AK) | ||
| + | * 17:00UT Experiment started OK. (AK) | ||
| + | * 17:11UT had the following error "error s5 -104 rfpcn: time-out, connection closed" Restarted rxmon and ifbox. First clean scan without this error was 17:45, took me a while to realise I need su not sudo to login as super user (sleep deprived :P ) (AK) | ||
| + | * 20:58UT reconfigured the dbbc, between scans so no data should be affected. (AK) | ||
| + | * 21:00UT had to sync fmset, halted the schedule. **Missed scans 263-2102 and 263-2104b** . Reconfiguring the dbbc and synccing the fmset seems to have fixed the bad channel in auto correlation spectra and returned the tsys values. (AK) | ||
| + | * 23:51UT Halting to reconfigure DBBC. Scans lost from 263-23 to 264-002a inclusive (Jim) | ||
| **Yarragadee 12m:** | **Yarragadee 12m:** | ||
| Line 21: | Line 29: | ||
| Data volume at beginning: 1.987 GB | Data volume at beginning: 1.987 GB | ||
| + | |||
| + | * 17:00UT Experiment started OK. (AK) | ||