User Tools
Sidebar
This wiki is not maintained! Do not use this when setting up AuScope experiments!
This is an old revision of the document!
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. 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:
/usr2/sched/r4556hb.snp /usr2/proc/r4556hb.prc
If they aren't there, follow the following steps to prepare them:
* 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:
* 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 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:
- 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: Start the System Monitor
e-Remote Ctrl
This should still be running too. If for some reason you need to re-start eRemoteControl, here's how:
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:
.
Then 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
- Now start the Checklist by loading the procedure file for the experiment, then
exper_initi. e.g for R1556 at Hobart:proc=r1556hb exper_initi
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 RF and IF signal paths, and DBBC are now configured through the Field System.
RF and IF signal path
DBBC Configuration
The Digital Base-Band Converter (DBBC) takes the IF signals from the telescope and digitises them for the Mark5 recorder. The DBBC needs to be properly configured prior to an observation. Check that the DBBC is healthy and the server software is running:
To configure the DBBC with the correct IF and frequency settings, use the following command
setupsx
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:
iread
BBC Settings:
bread
Check the maser
Mark5 Recorder setup
Next the Mark5 recorder needs to be prepared for the observations.
Clock and delay check
Test recording
System Temperature (Tsys) check
- Tsys measurement check
Antenna checks
Weather checks
Fringe check
Send a Station Ready email
Skype
- Start Skype and begin a chat session with all participating sites plus the on-call person
e-Remote Ctrl
- Next, 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.
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:
- 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:
RF and IF signal path
Unlikely to need changing but worth a quick check:
Check the maser
Skip if time is pressing:
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:
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.
Clock and delay check
Test recording
If time permits (and can be safely skipped if the DBBC and Mark5 modes haven't changed):
System Temperature (Tsys) check
Skip if there isn't enough time:
- Tsys measurement check
Antenna checks
Only check pointing if there's time:
Weather checks
Fringe check
This is time consuming but worth doing if you have ~15 min to spare:
Send a Station Ready email
Be sure to note any items skipped due to short change-over time (or recently checked):
Skype
- Check all participating sites plus and the on-call person are included
Starting
The usual startup procedure can now be done: Starting and Monitoring
