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:aum [2021/11/23 13:56]
Warren Hankey [Field system set up]
operations:aum [2022/01/17 16:18]
Jamie McCallum [Preparing the schedule files]
Line 3: Line 3:
 ====== Preparing the schedule files ====== ====== Preparing the schedule files ======
  
-  * For mixed mode observations (AUA/AUM/AOV experiments), this can now be done from the standard slogit scripts. Please use either <code>schedules $exper hb ke</code> to download and drudg the schedues. Alternatively <code>slogit.auscope.sh $exper $station</code> will also work. When you are asked to check the prc files, please make sure that the values for bbcs017-032 are is the range of 2200-2950 MHz and bbc001-bbc012 are in the range of 300-450 MHz. These correspond to the X- and S-band frequencies, observing at dual linear polarisations.+  * For mixed mode observations (AUA/AUM/AOV experiments), this can now be done from the standard slogit scripts. Please use either <code>schedules $exper hb ke</code> to download and drudg the schedues. Alternatively <code>slogit.auscope.sh $exper $station</code> will also work. When you are asked to check the prc files, please make sure that the values for bbcs033-048 are is the range of 2200-2950 MHz and bbc001-bbc012 are in the range of 300-450 MHz. These correspond to the X- and S-band frequencies, observing at dual linear polarisations.
  
 ====== RF configuration ====== ====== RF configuration ======
Line 22: Line 22:
   * Check the status of the DBBC/mark5 with ''midob'' - this will call many monitoring commands. Some things to look for in the output are listed below   * Check the status of the DBBC/mark5 with ''midob'' - this will call many monitoring commands. Some things to look for in the output are listed below
       * ''iread'' - Check that the IF power levels match the targets **NB** - Hobart often has problems with A/B due to RFI so variations of ~20% are not unusual       * ''iread'' - Check that the IF power levels match the targets **NB** - Hobart often has problems with A/B due to RFI so variations of ~20% are not unusual
-      * ''bread'' - Confirm that all channels are in AGC mode and that the power levels are ~15000 for bbc017-32 and between ~8000 and 30000 for bbc001-bbc012 (S-band RFI)+      * ''bread'' - Confirm that all channels are in AGC mode and that the power levels are ~15000 for bbc017-32 @Ke ]/[ bbc033-048 @ Hb ] and between ~8000 and 30000 for bbc001-bbc012 (S-band RFI)
       * ''wth'' should return temperature/pressure/humidity values at Hb. Ke data still not available unfortunately.       * ''wth'' should return temperature/pressure/humidity values at Hb. Ke data still not available unfortunately.
       * ''clkoff'' and ''maserdelay'' should have a stable difference (~-0.11 microsec at Katherine, ~0.6 microsec at Hb).        * ''clkoff'' and ''maserdelay'' should have a stable difference (~-0.11 microsec at Katherine, ~0.6 microsec at Hb). 
Line 31: Line 31:
       * The ''samplers'' output contains all the details of the DBBC3 samplers and is intended for debugging purposes. The main things to check are that in each sampler block, the Power readings are relatively similar (to within a few percent) and that the Corr readings are all > 180E6 for Hobart12 and > 170E6 for Katherine.  The samplers output is difficult to scan by eye, and a script that uses the multicast messages from the DBBC is preferable, see next point.       * The ''samplers'' output contains all the details of the DBBC3 samplers and is intended for debugging purposes. The main things to check are that in each sampler block, the Power readings are relatively similar (to within a few percent) and that the Corr readings are all > 180E6 for Hobart12 and > 170E6 for Katherine.  The samplers output is difficult to scan by eye, and a script that uses the multicast messages from the DBBC is preferable, see next point.
       * Log in to terminals on each of pcfs-2hb and pcfs-2ke and run''~/AuscopeVLBI/dbbc3_multicast.py'' The summarised output gives a green OK or red NO when things are out of range. Hobart12 often has issues with the power readings for A/B, due to RFI.  (Not available on pcfshb or pcfske where we are running the fs)       * Log in to terminals on each of pcfs-2hb and pcfs-2ke and run''~/AuscopeVLBI/dbbc3_multicast.py'' The summarised output gives a green OK or red NO when things are out of range. Hobart12 often has issues with the power readings for A/B, due to RFI.  (Not available on pcfshb or pcfske where we are running the fs)
-      * Ke requires IF's ABCD to be good (ignore EF) +      * Ke requires IF's ABCD to be good (ignore EF, not used
-      * Hb requires IF's ABEF to be good (ignore CD)+      * Hb requires IF's ABEF to be good (ignore CDGH, not used)
  
 ====== Test recording ====== ====== Test recording ======