User Tools
handover:aov002
This wiki is not maintained! Do not use this when setting up AuScope experiments!
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
handover:aov002 [2015/04/30 20:16] David Horsley |
handover:aov002 [2015/05/04 07:22] (current) liza |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | |||
| ====== AOV002 ====== | ====== AOV002 ====== | ||
| Line 7: | Line 8: | ||
| - | Data volume at beginning: 7.9GB | + | Data volume at beginning: 7.9GB (I assume approx 7.9 TB??) |
| + | |||
| + | * 08:38 UT: 8301 GB recorded (Ross). | ||
| Line 18: | Line 21: | ||
| * The schedule start email claimed everything was fine - but mk5ke was not recording properly. It's unclear why this happened. Several "mk5cn: connection closed" messages appeared, and nothing was being recorded. The EndDIM command had no effect on the dim process. fmset took a few seconds to display values, but eventually did. I decided to reboot the mk5 via the power switch. Waiting for a few minutes and looking on the webcam showed what looked like a frozen state. Tried off, then on, but the mk5 never had lights on the front powered after this. Boot did nothing either. Contacted Jamie, now recording to mk5-2ke (USN-0169, 2TB free). Missed approximately the first hour - first real scan is 1424-418 at 120-1959a. There appears to be bad auto-correlations in DBBC channels 1 and 14, but not restarting DBBC for fear of losing more time. (Chris) | * The schedule start email claimed everything was fine - but mk5ke was not recording properly. It's unclear why this happened. Several "mk5cn: connection closed" messages appeared, and nothing was being recorded. The EndDIM command had no effect on the dim process. fmset took a few seconds to display values, but eventually did. I decided to reboot the mk5 via the power switch. Waiting for a few minutes and looking on the webcam showed what looked like a frozen state. Tried off, then on, but the mk5 never had lights on the front powered after this. Boot did nothing either. Contacted Jamie, now recording to mk5-2ke (USN-0169, 2TB free). Missed approximately the first hour - first real scan is 1424-418 at 120-1959a. There appears to be bad auto-correlations in DBBC channels 1 and 14, but not restarting DBBC for fear of losing more time. (Chris) | ||
| + | * In gap between scans 120-2335 and 120-2346, cycled power to DBBC and reprogrammed it. No scans missed but expect a clock jump. (Jim) | ||
| + | * DBBC cont cal wasn't working. Another DBBC reset required. scans 121-0004, 121-0008, 121-0010 missed. Clock jump. (Jim) | ||
| + | * Another DBBC restart required, due to large difference between formatter and maser delays. (Jakob) | ||
| + | * 08:42 UT: 476 GB recorded (Ross). | ||
| + | * 08:44:59 UT: ALARM: error m5 -104 mk5cn: time-out, connection closed (Ross). | ||
/home/www/auscope/opswiki/data/attic/handover/aov002.1430425012.txt.gz · Last modified: 2015/04/30 20:16 by David Horsley
Page Tools
