User Tools
operations:documentation.ivs.newstart_v3_fs9.10.5
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.ivs.newstart_v3_fs9.10.5 [2012/11/13 02:31] Jim Lovell |
operations:documentation.ivs.newstart_v3_fs9.10.5 [2018/09/25 22:09] (current) Pradyumna Kiran Kummamuru |
||
|---|---|---|---|
| Line 66: | Line 66: | ||
| > * [[operations:documentation.DBBCSetupIVS_9.10.5|DBBC Setup]] | > * [[operations:documentation.DBBCSetupIVS_9.10.5|DBBC Setup]] | ||
| - | At the start of every scan, the pcfs executes the ''setupsx'' or ''setup8f'' procedure (depending on experiment type) which sets the DBBC input channels, filters and BBC frequencies (and configues the Mark5). However, it's a good idea to execute it now so that a recorder test can be made: | + | At the start of every scan, the pcfs executes the ''setupsx'' which sets the DBBC input channels, filters and BBC frequencies (and configues the Mark5). However, it's a good idea to execute it now so that a recorder test can be made: |
| * For R1, R4, RD, RDV, T2, ANZ, CRDS, CRF, OHIG:<code>setupsx</code> | * For R1, R4, RD, RDV, T2, ANZ, CRDS, CRF, OHIG:<code>setupsx</code> | ||
| - | * For AUST, CONT:<code>setup8f</code> | + | |
| - | You can compare the DBBC IF and Frequency settings with the scheduled ones by comparing the setup in the printed procedure file with the values reported by the Field System. DBBC IF settings: | + | ''setupsx'' calls ''ifdsx'' which sets up the DBBC Conditioning module inputs, filters and power levels, then ''dbbcsx8'' (or ''dbbcsx4'' for a 4 MHz DBBC mode) which sets the BBC frequencies. Then if you type: |
| <code>iread</code> | <code>iread</code> | ||
| - | BBC Settings: | + | You will see what the current Conditioning module settings are. Output format is: |
| + | <code><time>/<Module label>/<IF input number>,<Auto or Manual gain control>,<Nyquist filter number>,<Target power level>,<attenuation>,<actual power level></code> | ||
| + | Check there’s agreement with what appears in ifdsx. The actual power level should agree pretty well with the target level. The attenuation number can be anywhere between 0 (none) and 63 (maximum). If you see it at 0 or 63, it means the Conditioning module is having trouble getting the power to the right level. You may want to contact the on-call person in this case for help on getting the levels in range. | ||
| + | |||
| + | Then type: | ||
| <code>bread</code> | <code>bread</code> | ||
| + | You will see what the DBBC has set the BBC freqs to (compare with the .prc file). Output looks like this: | ||
| + | <code><time>/<bbc name>/<Frequency (MHz)>/<Conditioning module in use>,<Bandwidth (MHz)>,...</code> | ||
| + | the Frequency, Conditioning module label and bandwidth should agree with the listing in ''dbbcsx8'' (or ''dbbcsx4''). | ||
| == Check the maser == | == Check the maser == | ||
| Line 79: | Line 86: | ||
| == Mark5 Recorder setup == | == Mark5 Recorder setup == | ||
| Next the Mark5 recorder needs to be prepared for the observations. | Next the Mark5 recorder needs to be prepared for the observations. | ||
| + | |||
| + | If the allocated Mk5 module contains data: | ||
| + | |||
| + | Check the remaining space on the module and the compare with the space required for the experiment from the summary file. disk_pos can be used for such purpose. **Do NOT delete any data** unless it is something done as test recording. | ||
| If you need to swap disk modules: | If you need to swap disk modules: | ||
| - | * Notes on [[operations:documentation.ivs.mark5_v2_swap_modules||swapping between Mark5 disk modules]] | + | * Notes on [[operations:documentation.ivs.mark5_v2_swap_modules|swapping between Mark5 disk modules]] |
| Now check that the times are all OK: | Now check that the times are all OK: | ||
| Line 102: | Line 113: | ||
| == Test recording == | == Test recording == | ||
| - | * [[operations:documentation.test_recording|Making a test recording]] | + | Test recording notes are given below. <note important>Note though that you should only test the module you'll be recording to (i.e. skip the last section where it describes how to test the second module), and //unless you are absolutely sure//, don't clear the disk module:</note> |
| + | * [[operations:documentation.test_recording_fs9.10.5|Making a test recording]] | ||
| == System Temperature (Tsys) check == | == System Temperature (Tsys) check == | ||
| Line 108: | Line 120: | ||
| == Antenna checks == | == Antenna checks == | ||
| - | * [[operations:documentation.test_antenna|Antenna checks]] | + | |
| + | **Skip** these. | ||
| + | > * [[operations:documentation.test_antenna|Antenna checks]] | ||
| == Weather checks == | == Weather checks == | ||
| Line 123: | Line 137: | ||
| == Skype == | == Skype == | ||
| * Start Skype and begin a chat session with all participating sites plus the on-call person | * Start Skype and begin a chat session with all participating sites plus the on-call person | ||
| - | |||
| - | |||
| - | ------------------ | ||
| - | |||
| - | === e-Remote Ctrl === | ||
| - | * [[operations:eRemoteCtrl_newPCFSLog|Open a new PCFS log file]] | ||
| - | * Next, [[operations:documentation.logmonitor_eremotectrl|set up the log monitor]] to provide warnings and alarms. you shouldn't need to restart it, but it will need to point to the new log file. | ||
| - | * Now [[operations:starting_eRemoteCtrl_checklist|start the Checklist]] | ||
| - | |||
| - | The checklist should now be visible. The items in the list are described below and can be ticked off as you go. If time is pressing, skip items like pointing checks, fringe checks etc. | ||
| - | |||
| - | === The Before Observation Checklist === | ||
| - | |||
| - | == Prepare the schedule file == | ||
| - | |||
| - | Hopefully this was already done well ahead of time and won't need doing now: | ||
| - | * [[operations:documentation.ivs.drudg|Preparing the schedule and procedure files]] | ||
| - | * On occasions, the Hobart data are written to disk between scans for e-transfer to Tsukuba for ultra-rapid EOP observations. Some additional changes to the schedule files are required in this case: | ||
| - | * [[operations:documentation.ivs.drudg_ureop|Additional schedule preparation for Hb ultra-rapid EOP experiments]] | ||
| - | * [[operations:starting_monitoring_urEOP|Additional tasks prior to starting Ultra-rapid EOP observations]] | ||
| - | |||
| - | == RF and IF signal path == | ||
| - | Unlikely to need changing but worth a quick check: | ||
| - | |||
| - | * [[operations:rf_if_check|Configuring the RF and IF signal paths]] | ||
| - | |||
| - | == Check the maser == | ||
| - | Skip if time is pressing: | ||
| - | |||
| - | * [[operations:maser_check|Hydrogen Maser check]] | ||
| - | |||
| - | == DBBC Configuration == | ||
| - | If the DBBC config is the same as the last experiment, nothing to do here. However, if there is a change required, these are the steps: | ||
| - | * [[operations:documentation.DBBCSetupIVS_v2|Configuring the DBBC]] | ||
| - | |||
| - | == Mark5 Recorder setup == | ||
| - | This should only be necessary if the recording mode is different. It will be necessary to confirm that data are being recorded to the correct bank and you should have received notes on this prior to the experiment from the on-call person. | ||
| - | * [[operations:documentation.ivs.mark5_v2|Mark5B recorder setup]] | ||
| - | |||
| - | == Clock and delay check == | ||
| - | * [[operations:documentation.clock_and_delay_check|Checking clock offsets and delays]] | ||
| - | |||
| - | == Test recording == | ||
| - | If time permits (and can be safely skipped if the DBBC and Mark5 modes haven't changed): | ||
| - | * [[operations:documentation.test_recording|Making a test recording]] | ||
| - | |||
| - | == System Temperature (Tsys) check == | ||
| - | Skip if there isn't enough time: | ||
| - | * [[operations:documentation.test_tsys|Tsys measurement]] check | ||
| - | |||
| - | == Antenna checks == | ||
| - | Only check pointing if there's time: | ||
| - | * [[operations:documentation.test_antenna|Antenna checks]] | ||
| - | |||
| - | == Weather checks == | ||
| - | * [[operations:documentation.weather_check|Weather conditions]] | ||
| - | |||
| - | == Fringe check == | ||
| - | This is time consuming but worth doing if you have ~15 min to spare: | ||
| - | * [[operation:fringe_checking|Fringe checking procedure]] | ||
| - | |||
| - | == Send a Station Ready email == | ||
| - | Be sure to note any items skipped due to short change-over time (or recently checked): | ||
| - | * [[operations:documentation.station_ready_email|Sending a station ready email to IVS]] | ||
| - | |||
| - | == Skype == | ||
| - | * Check all participating sites plus and the on-call person are included | ||
| ===== Starting ===== | ===== Starting ===== | ||
| - | The usual startup procedure can now be done: [[operations:documentation_ops2#starting_and_monitoring|Starting and Monitoring]] | + | The usual startup procedure can now be done: [[operations:starting_monitoring_9.10.5|Starting and Monitoring]] |
/home/www/auscope/opswiki/data/attic/operations/documentation.ivs.newstart_v3_fs9.10.5.1352773882.txt.gz · Last modified: 2012/11/13 02:31 by Jim Lovell
Page Tools
