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.
| Next revision | Previous revision | ||
|
operations:documentation.ivs.newstart_v3_fs9.10.5 [2012/11/13 01:26] Jim Lovell created |
operations:documentation.ivs.newstart_v3_fs9.10.5 [2018/09/25 22:09] (current) Pradyumna Kiran Kummamuru |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Following on with another observation ====== | ====== Following on with another observation ====== | ||
| - | Sometimes, another IVS observation will follow from the one just finished. In this case, some of the setup procedure will need repeating. Specifically: | + | Sometimes, another IVS observation will follow from the one just finished. In this case, some of the setup procedure will need repeating. Here's a run-down of what needs doing and what can be skipped: |
| + | |||
| + | === Prepare the schedule file === | ||
| + | |||
| + | **This should already be done and can be skipped.** However, you can check for schedule and procedure files on the pcfs machines. For example, for Hobart there should be the following files on pcfshb for r4556: | ||
| + | <code>/usr2/sched/r4556hb.snp | ||
| + | /usr2/proc/r4556hb.prc</code> | ||
| + | > If they aren't there, follow the following steps to prepare them: | ||
| + | > * [[operations:documentation.ivs.drudg_9.10.5|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_9.10.5|Additional schedule preparation for Hb ultra-rapid EOP experiments]] | ||
| + | |||
| + | === Timing PC Software === | ||
| + | |||
| + | This software should still be running from the previous experiment. **Skip.** | ||
| + | |||
| + | > For reference, here's a description of [[operations:documentation.ivs.timingsw|software on the timing PC]] | ||
| + | |||
| + | === Field System Software === | ||
| + | |||
| + | As you shouldn't have terminated the Field System, this should still be running. **Skip.** Again, for reference: | ||
| + | * [[operations:starting_fs|Starting the PC Field System Software]] | ||
| + | * [[operations:documentation:fs_antenna_9.10.5|Some notes on antenna control and monitoring]] using the new version of the Field system | ||
| + | |||
| + | === System Monitor === | ||
| + | |||
| + | Should still be running. **Skip.** | ||
| + | |||
| + | >If you do need to re-start: [[operations:starting_sysmon|Start the System Monitor]] | ||
| === e-Remote Ctrl === | === e-Remote Ctrl === | ||
| + | |||
| + | This should still be running too, but there are a few things to do here. | ||
| + | |||
| + | >If for some reason you need to re-start eRemoteControl, here's how: | ||
| + | > * [[operations:starting_eRemoteCtrl|Start e-Remote Ctrl]] | ||
| + | eRemoteControl will still be writing a local log file and pcfs_log_monitor will still be monitoring it. Although that log file has a name that doesn't match the new experiment, it's not essential to start a new local log (as it's only used locally and the master log on the pcfs is used at the correlator). | ||
| + | |||
| + | > If you do want to start a new local log and monitor it, click on the red dot icon in econtrol to make the green bar go away: \\ {{:operations:econtrol_log_recording.png|}}. | ||
| + | > Then [[operations:documentation.logmonitor_eremotectrl|set up the log monitor]] to provide warnings and alarms | ||
| + | |||
| + | To keep all log messages related to the new experiment in the same file, the next thing to do is | ||
| * [[operations:eRemoteCtrl_newPCFSLog|Open a new PCFS log file]] | * [[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 start the Checklist by loading the procedure file for the experiment, then ''exper_initi''. e.g for R1556 at Hobart: <code>proc=r1556hb |
| - | * Now [[operations:starting_eRemoteCtrl_checklist|start the Checklist]] | + | exper_initi</code> |
| - | 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 checklist should now be visible. The items in the list are described below and can be ticked off as you go, but many can be skipped in a follow-on experiment. |
| === The Before Observation Checklist === | === The Before Observation Checklist === | ||
| - | == Prepare the schedule file == | + | The RF and IF signal paths, and DBBC are now configured through the Field System. |
| - | + | ||
| - | 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 == | == 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]] | + | Should already be setup and correct. **Skip.** |
| - | == Check the maser == | + | >For referenece here are notes on [[operations:rf_if_check_9.10.5|configuring the RF and IF signal paths]] |
| - | Skip if time is pressing: | + | |
| - | + | ||
| - | * [[operations:maser_check|Hydrogen Maser check]] | + | |
| == DBBC Configuration == | == 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]] | + | The DBBC should already be running and the PCFS should be able to communicate with it. |
| + | |||
| + | >There should be no need to start any software on the DBBC but for reference here are the notes on setting up the DBBC: | ||
| + | > * [[operations:documentation.DBBCSetupIVS_9.10.5|DBBC Setup]] | ||
| + | |||
| + | 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> | ||
| + | |||
| + | ''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> | ||
| + | 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> | ||
| + | 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 == | ||
| + | * [[operations:maser_check|Hydrogen Maser check]] | ||
| == Mark5 Recorder setup == | == 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. | + | Next the Mark5 recorder needs to be prepared for the observations. |
| - | * [[operations:documentation.ivs.mark5_v2|Mark5B recorder setup]] | + | |
| + | 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: | ||
| + | * Notes on [[operations:documentation.ivs.mark5_v2_swap_modules|swapping between Mark5 disk modules]] | ||
| + | |||
| + | Now check that the times are all OK: | ||
| + | |||
| + | <code>mk5=dot?</code> | ||
| + | |||
| + | look for ''syncerr_eq_0'', and that the final number is less than ~5 ms. | ||
| + | If you see something like ''syncerr_gt_3'' then ''fmset'' may need to be run to synchronise the clocks. To do this, open a terminal on pcfs[hb|ke|yg], and type | ||
| + | <code>fmset</code> | ||
| + | When the interface appears, type | ||
| + | <code>s</code> | ||
| + | then confirm with a | ||
| + | <code>y</code> | ||
| + | Following this, the clocks should all be synchronised and agree with UT. Press the [Esc] key to exit ''fmset''. Then check the times again: | ||
| + | |||
| + | <code>mk5=dot?</code> | ||
| == Clock and delay check == | == Clock and delay check == | ||
| Line 42: | Line 113: | ||
| == Test recording == | == Test recording == | ||
| - | If time permits (and can be safely skipped if the DBBC and Mark5 modes haven't changed): | + | 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|Making a test recording]] | + | * [[operations:documentation.test_recording_fs9.10.5|Making a test recording]] |
| == System Temperature (Tsys) check == | == System Temperature (Tsys) check == | ||
| - | Skip if there isn't enough time: | ||
| * [[operations:documentation.test_tsys|Tsys measurement]] check | * [[operations:documentation.test_tsys|Tsys measurement]] check | ||
| == Antenna checks == | == Antenna checks == | ||
| - | Only check pointing if there's time: | + | |
| - | * [[operations:documentation.test_antenna|Antenna checks]] | + | **Skip** these. |
| + | > * [[operations:documentation.test_antenna|Antenna checks]] | ||
| == Weather checks == | == Weather checks == | ||
| Line 57: | Line 128: | ||
| == Fringe check == | == Fringe check == | ||
| - | This is time consuming but worth doing if you have ~15 min to spare: | + | |
| + | **Skip** this unless you have at least an hour to spare! | ||
| * [[operation:fringe_checking|Fringe checking procedure]] | * [[operation:fringe_checking|Fringe checking procedure]] | ||
| == Send a Station Ready email == | == 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]] | * [[operations:documentation.station_ready_email|Sending a station ready email to IVS]] | ||
| == Skype == | == Skype == | ||
| - | * Check all participating sites plus and the on-call person are included | + | * Start Skype and begin a chat session with all participating sites plus the on-call person |
| ===== 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.1352769997.txt.gz · Last modified: 2012/11/13 01:26 by Jim Lovell
Page Tools
