User Tools

Site Tools


operations:documentation_ops2_austral15day

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.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
operations:documentation_ops2_austral15day [2013/11/27 03:42]
Jim Lovell [Observatory Checking]
operations:documentation_ops2_austral15day [2013/11/28 02:30]
Jim Lovell [Module Swaps]
Line 3: Line 3:
   * [[#​schedule_overview_and_module_usage|Observing schedule and module usage overview]]   * [[#​schedule_overview_and_module_usage|Observing schedule and module usage overview]]
   * [[#​schedule_changeover|Schedule changeover procedure]]   * [[#​schedule_changeover|Schedule changeover procedure]]
 +  * [[#​module_swaps|Swapping Mark5 modules]]
   * [[#​observatory_checking|Observatory checking procedure]] (every 3 days)   * [[#​observatory_checking|Observatory checking procedure]] (every 3 days)
   * [[#​fringe_checks|Fringe Checks]]   * [[#​fringe_checks|Fringe Checks]]
Line 53: Line 54:
   * [[operations:​startmessage|Send a start message to IVS]]. ​   * [[operations:​startmessage|Send a start message to IVS]]. ​
   * Send off the log files to IVS. Refer to the page [[operations:​documentation.ivs.commentsfile|Prepare the comments file and transfer the logs]] for details. Note that all modules for AUSTRAL experiments from Yarragadee and Katherine are shipped to Hobart, and all AUSTRAL data are eTransfer-ed to Curtin for correlation.   * Send off the log files to IVS. Refer to the page [[operations:​documentation.ivs.commentsfile|Prepare the comments file and transfer the logs]] for details. Note that all modules for AUSTRAL experiments from Yarragadee and Katherine are shipped to Hobart, and all AUSTRAL data are eTransfer-ed to Curtin for correlation.
 +
 +===== Module Swaps =====
 +
 +Module swaps should be coordinated with local staff at the observatories. Someone at the site will phone when they want to change a module. ​
 +
 +It's important that the new module is powered up during a scan gap as this draws significant power and the Mark5 can't record to the other module at the same time (and will probably crash). So, when someone from the observatory calls, consult the observation summary file and find an upcoming period of time of at least one minute between a ''​Stop Data''​ and a ''​Start Data''​ to carry out the swap. For example, in the schedule below, the period between Scans ''​332-2104''​ and ''​332-2110''​ would be a good choice as there'​s a gap of almost 4 minutes (from ''​21:​06:​18''​ to ''​21:​10:​01''​). However, a module change between Scans ''​332-2118b''​ and ''​332-2122''​ would not be a good idea as the gap is only 25 seconds (from ''​21:​22:​29''​ to ''​21:​22:​54''​):​
 +
 +<​code>​
 +                                         ​Start ​    ​Stop ​                     Record
 + ​Scan ​     Line#  Source ​  Az El Cable    Data      Data      Dur    Gbyte
 +date = 2013NOV28 ​ DOY = 332
 + ​332-2101 ​    7 0648-165 254  6 CCW    21:​01:​11 ​ 21:​02:​05 ​   0:54      .0 XXX   
 + ​332-2102b ​  24 1606+106 ​ 50 27 NEUTR  21:​02:​57 ​ 21:​04:​13 ​   1:16     ​6.9 ​ *    ​
 + ​332-2104 ​   41 1622-253 ​ 89 48 NEUTR  21:​04:​52 ​ 21:​06:​18 ​   1:26    16.6  *    ​
 + ​332-2110 ​   58 0454-810 188 31 CW     ​21:​10:​01 ​ 21:​11:​30 ​   1:29    27.6  *    ​
 + ​332-2111 ​   75 0230-790 184 26 CW     ​21:​11:​54 ​ 21:​18:​16 ​   6:22    39.0  *    ​
 + ​332-2118b ​  92 2052-474 140 13 CW     ​21:​18:​58 ​ 21:​22:​29 ​   3:31    87.9  *    ​
 + ​332-2122 ​  109 2300-683 166 18 CW     ​21:​22:​54 ​ 21:​24:​35 ​   1:41   ​114.9 ​ *    ​
 + ​332-2125 ​  126 0727-115 260  6 CW     ​21:​25:​51 ​ 21:​26:​21 ​   0:30   ​127.9 ​ *    ​
 +</​code>​
 +
 +=== Procedure ===
 +
 +  * Any time before the scan gap, ask the local person to power down the module to be removed (by tuning its key) and take it out for storage. It's safe to do this as powering down a module shouldn'​t draw significant power and therefore interrupt a recording.
 +  * The new module can be inserted, **but don't turn the key yet!**
 +  * Wait for the time of the end of the identified scan, and confirm that recording has stopped by making sure that the 4 disk activity lights on the '​live'​ module go out.
 +  * Ask the local person to turn the key on the new module
  
 ===== Observatory Checking ===== ===== Observatory Checking =====
/home/www/auscope/opswiki/data/pages/operations/documentation_ops2_austral15day.txt · Last modified: 2014/11/25 03:36 by Jim Lovell