User Tools
operations:documentation_ops2_cont14
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 | ||
|
operations:documentation_ops2_cont14 [2014/04/30 06:30] Jim Lovell |
operations:documentation_ops2_cont14 [2014/05/07 10:31] (current) Vasaant Krishnan [Some Additional Ho 26m Notes] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | |||
| ====== CONT14: Notes for operators ====== | ====== CONT14: Notes for operators ====== | ||
| Line 14: | Line 13: | ||
| ===== Schedule Overview and Module Usage ===== | ===== Schedule Overview and Module Usage ===== | ||
| - | Please read the [[operations:documentation_cont14_overview|Overview Page]] for information on the observations, start and stop times etc. The google calendar on the [[operations:schedule|schedules page]] describes experiment and shift times. | + | Please read the [[operations:documentation_cont14_overview|Overview Page]] for general information on the CONT14 observations as well as session notes from IVS. The google calendar on the [[operations:schedule|schedules page]] describes experiment and shift times. |
| <note>Mark5 Nomenclature: "**Bank swap**" means changing where the data are recorded from one bank to the other. This does NOT mean modules are powered on/off or physically moved. | <note>Mark5 Nomenclature: "**Bank swap**" means changing where the data are recorded from one bank to the other. This does NOT mean modules are powered on/off or physically moved. | ||
| Line 20: | Line 19: | ||
| </note> | </note> | ||
| - | The CONT14 schedules are named ''C14nn'' where ''(nn = 01, 02, 03, ... , 15)''. They all start at 00:00 UT and finish at 23:57 UT so there is only a 3 minute gap, just enough time to change schedule files and modules (if needed). Every day, an hour is set aside for detailed system checks at each site. They are staggered so that only one antenna is out of the array at a time. System check times for our sites are as follows: | + | The CONT14 schedules are named ''C14nn'' where ''(nn = 01, 02, 03, ... , 15)''. They all start at 00:00 UT and finish at 23:57 UT so there is only a 3 minute gap, just enough time to change schedule files and banks (if needed). Every day, an hour is set aside for detailed system checks at each site. They are staggered so that only one antenna is out of the array at a time. System check times for our sites are as follows: |
| ^ Site ^ Check time (UT) ^ Check time (Hobart) ^ | ^ Site ^ Check time (UT) ^ Check time (Hobart) ^ | ||
| Line 52: | Line 51: | ||
| The other difference is that the S/X receiver on the 26m is cryogenic and can warm up. It's a good idea to keep an eye on the cryo temperatures and warn Brett if they start to increase. More on this and other things to keep an eye on are described in [[operations:documentation.eRemoteControl_checklist_midob26|Description of checklist parameters for the 26m telescope]]. | The other difference is that the S/X receiver on the 26m is cryogenic and can warm up. It's a good idea to keep an eye on the cryo temperatures and warn Brett if they start to increase. More on this and other things to keep an eye on are described in [[operations:documentation.eRemoteControl_checklist_midob26|Description of checklist parameters for the 26m telescope]]. | ||
| + | |||
| + | Also please note that the VNC session that is running the Field System software can be found by typing <code>vncviewer newsmerd:1</code> | ||
| ===== Schedule and procedure files ===== | ===== Schedule and procedure files ===== | ||
| Line 57: | Line 58: | ||
| All schedule and procedure files for the period from C1401 to C1415 should already be prepared and ready to use before your shift. | All schedule and procedure files for the period from C1401 to C1415 should already be prepared and ready to use before your shift. | ||
| - | Note that for CONT14 the procedure for setting up the Mark5 and DBBC is called ''setup8f'', NOT ''setupsx''. | + | <note important>Note that for CONT14 the procedure for setting up the Mark5 and DBBC is called ''setup8f'', NOT ''setupsx''.</note> |
| Line 66: | Line 67: | ||
| * [[operations:documentation.eRemoteControl_checklist_midob26|Description of checklist parameters for the 26m telescope]] | * [[operations:documentation.eRemoteControl_checklist_midob26|Description of checklist parameters for the 26m telescope]] | ||
| + | Also please keep the [[operations:handover|Handover notes]] page up to date. | ||
| ===== Schedule Changeover ===== | ===== Schedule Changeover ===== | ||
| Line 82: | Line 84: | ||
| Please make sure: | Please make sure: | ||
| * The new schedule starts. Look in the "Status Monitor" section of eRemoteCtrl and check that SCHED is set to the correct file | * The new schedule starts. Look in the "Status Monitor" section of eRemoteCtrl and check that SCHED is set to the correct file | ||
| - | * Type the command <code>mk5=bank_set?</code> and check that the correct module is selected. The first one in the list is the active bank and the number between the slashes is the module capacity in GB. For example: <code>17:28:12.83/mk5/!bank_set? 0 : B : HOB+0025/6000/1024 : A : NYAL-019/2000/1024 ;</code> says the module in Bank B is active, has a VSN of HOB+0025 and is 6000 GB (6 TB) in capacity. | + | * Type the command <code>mk5=bank_set?</code> and check that the [[operations:documentation_cont14_timetable|correct module]] is selected. The first one in the list is the active bank and the number between the slashes is the module capacity in GB. For example: <code>17:28:12.83/mk5/!bank_set? 0 : B : HOB+0025/6000/1024 : A : NYAL-019/2000/1024 ;</code> says the module in Bank B is active, has a VSN of HOB+0025 and is 6000 GB (6 TB) in capacity. |
| - | If for some reason the new schedule hasn't started or the wrong bank is selected then you will need to issue these commands by hand. | + | If for some reason the new schedule hasn't started or the wrong bank is selected then you will need to issue the ''bank_set'' and ''schedule'' commands by hand. |
| Once the new schedule has started: | Once the new schedule has started: | ||
| * [[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 CONT14 experiments from Yarragadee and Katherine are shipped to Hobart, and all data are eTransfer-ed to Bonn for correlation. | + | * Send off the log files from the previous experiment 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 CONT14 experiments from Yarragadee and Katherine are shipped to Hobart, and all data are eTransfered to Bonn for correlation. |
| ==== Schedule Changeover at Katherine ==== | ==== Schedule Changeover at Katherine ==== | ||
| - | At Katherine the System Checkout period occurs in the hour before a schedule change on every day except Sunday, when it occurs in the hour after a schedule change. In either case, the procedure is to carry out the System Checkout first (see below), then make sure the correct module bank is selected, then start the new schedule by hand. | + | At Katherine the System Checkout period occurs in the hour before a schedule change on every day except Sunday, when it occurs in the hour after a schedule change. In either case, the procedure is to carry out the System Checkout first (see below), then make sure the [[operations:documentation_cont14_timetable|correct module bank]] is selected, then start the new schedule by hand. |
| - Do the [[operations:cont14_observatory_check|System Checkout]] | - Do the [[operations:cont14_observatory_check|System Checkout]] | ||
| - | - Type the command <code>mk5=bank_set?</code> and check that the correct module is selected. The first one in the list is the active bank and the number between the slashes is the module capacity in GB. For example: <code>17:28:12.83/mk5/!bank_set? 0 : B : HOB+0025/6000/1024 : A : NYAL-019/2000/1024 ;</code> says the module in Bank B is active, has a VSN of HOB+0025 and is 6000 GB (6 TB) in capacity. | + | - Type the command <code>mk5=bank_set?</code> and check that the [[operations:documentation_cont14_timetable|correct module]] is selected. The first one in the list is the active bank and the number between the slashes is the module capacity in GB. For example: <code>17:28:12.83/mk5/!bank_set? 0 : B : HOB+0025/6000/1024 : A : NYAL-019/2000/1024 ;</code> says the module in Bank B is active, has a VSN of HOB+0025 and is 6000 GB (6 TB) in capacity. If for some reason the the wrong bank is selected then you will need to issue these commands by hand: |
| - | If for some reason the the wrong bank is selected then you will need to issue these commands by hand: | + | - <code>mk5=bank_set=inc</code> Wait about 15 sec |
| - | - <code>mk5=bank_set=inc</code> | + | |
| - | - wait about 15 sec | + | |
| - <code>mk5=bank_set?</code> | - <code>mk5=bank_set?</code> | ||
| - Start the schedule. The command to send is as follows (where "nn" is the schedule number and "xx" is the two-letter station code): | - Start the schedule. The command to send is as follows (where "nn" is the schedule number and "xx" is the two-letter station code): | ||
| - <code>schedule=c14nnxx,#1</code> | - <code>schedule=c14nnxx,#1</code> | ||
| - | + | - Please make sure the new schedule starts. Look in the "Status Monitor" section of eRemoteCtrl and check that SCHED is set to the correct file and the time next to NEXT is in the (near) future. | |
| - | Please make sure the new schedule starts. Look in the "Status Monitor" section of eRemoteCtrl and check that SCHED is set to the correct file and the time next to NEXT is in the (near) future. | + | |
| Once the new schedule has started: | Once the new schedule has started: | ||
| * [[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 CONT14 experiments from Katherine are shipped to Hobart, and all data are eTransfer-ed to Bonn for correlation. | + | * Send off the log files from the previous experiment 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 CONT14 experiments from Katherine are shipped to Hobart, and all data are eTransfer-ed to Bonn for correlation. |
| ===== Observatory Checking ===== | ===== Observatory Checking ===== | ||
| Note that the observatory checking procedure requires you to interrupt the schedule and miss some scans. This allows us to skip checks if necessary but also means if the checks take less than the allocated hour we can be observing again as soon as possible. | Note that the observatory checking procedure requires you to interrupt the schedule and miss some scans. This allows us to skip checks if necessary but also means if the checks take less than the allocated hour we can be observing again as soon as possible. | ||
| + | |||
| + | Note that Observatory checks coincide with schedule changeovers at Katherine. See the notes above for the procedure at Katherine, but for all other sites, please read on... | ||
| Please follow this [[operations:cont14_observatory_check|Observatory System Checkout]] Procedure | Please follow this [[operations:cont14_observatory_check|Observatory System Checkout]] Procedure | ||
| Line 121: | Line 121: | ||
| Now make a note in the log that the schedule has been restarted following system checks. e.g. <code>"Schedule resumed following system checks</code> Also, if there were any problems during the checks or anything else of note, now is a good time to do it. For example, if the weather was too cloudy to verify the pointing: <code>"Pointing check not successful, probably due to bad weather</code> | Now make a note in the log that the schedule has been restarted following system checks. e.g. <code>"Schedule resumed following system checks</code> Also, if there were any problems during the checks or anything else of note, now is a good time to do it. For example, if the weather was too cloudy to verify the pointing: <code>"Pointing check not successful, probably due to bad weather</code> | ||
| + | ===== Some Additional Ho 26m Notes ===== | ||
| + | It is useful to be able to graphically view the 20K and 70K receiver temperatures, as well as the pressure vary with time. | ||
| + | |||
| + | On Ops2 start by: | ||
| + | <code>>> ssh oper@hobart | ||
| + | >> cd /usr2/log/ | ||
| + | >> logpl</code> | ||
| + | This will open up a GUI called: **LogPlotter 2**. | ||
| + | |||
| + | Now open a log file by clicking **File** --> **Open Log** in the header of the GUI. In the new window that pops up, input the log name (e.g. c1403ho.log) and open the file. | ||
| + | |||
| + | Go to **Plotting** and select | ||
| + | <code>rx-9-70k | ||
| + | rx-9-20k | ||
| + | rx-9-pres</code> | ||
| + | |||
| + | The plots do no update automatically, so restart the process with **File** --> **Open Log** when an update is required. | ||
/home/www/auscope/opswiki/data/attic/operations/documentation_ops2_cont14.1398839436.txt.gz · Last modified: 2014/04/30 06:30 by Jim Lovell
Page Tools
