Instructions to run GDIGS-Low observations (AGBT22A_437)

General instructions

  • The scripts are under project AGBT22A_437 and can use either the 800 MHz or 342 MHz receiver.

  • The scheduling blocks should be run in numerical order, for example: 01_setup, 02_peak, 03_balance, 04_flux_cal, 05_800MHz_map_RAwRef, 06_increase_session_number, 07_setup, 08_balance, 09_flux_cal, 10_800MHz_map_DecwRef and 11_end. the names and numbers of the blocks might change, what matters is running them in order
    • The name of the scheduling block, after the number, specifies the general purpose of the scheduling block. The different types, and some of the possible associated errors are described below.
    • The scheduling blocks will be updated before the observations by the observers.
    • If the last scheduling block finishes running, and there is still time left for the project, please re-submit the last scheduling block. For example if 10_800MHz_map_DecwRef finished and the next script is 11_end, please re-submit 10_800MHz_map_DecwRef.
    • The names

Scheduling block instructions

A description of the individual scheduling blocks, and how to check the quality of the results is given below. If one of the scripts does not pass the quality check, aborts or produces an error, please re-submit it. For mapping scheduling blocks it is necessary to modify the scheduling block before resubmitting (see below for details).

  • setup : Defines variables, such as source names, integration times and configuration, that are used by the rest of the scheduling blocks throughout the observation.

  • peak : Performs an AutoPeakFocus.
    • After running a peak scheduling block, check the peak scans via the data display tab/pointing solutions in AstrID.
      • Example of good solutions:
        good peak.png

      • Example of bad solutions:
        bad peak.png

  • balance : Balances the telescope IF.
    • After running a balance scheduling block check the AstrID log for errors balancing the PF or VEGAS (it helps to have the trace enabled). Also, check that the power levels going into VEGAS are close to -20±2. For the 800 MHz observations, only VEGAS banks A and B are used (both channels in each bank). For the 342 MHz observations VEGAS bank C is not used, all other banks are used. If the power levels are not close to -20±2 after the balance, re-run the balance scheduling block.

  • flux_cal : Observes a standard flux calibrator using an OffOn scan.
    • While doing the On scan portion of a flux_cal scheduling block you will get error messages about the input power levels being too high. These errors are expected (since the balance is done on the target) and no action should be taken.

  • 800MHz_map_RAwRef : Observes the target field using a RALongMapWithReference scan setup for the 800 MHz receiver.
  • 800MHz_map_DecwRef : Observes the target field using a DecLatMapWithReference scan setup for the 800 MHz receiver.
  • 342MHz_map_RAwRef : Observes the target field using a RALongMapWithReference scan setup for the 342 MHz receiver.
  • 342MHz_map_DecwRef : Observes the target field using a DecLatMapWithReference scan setup for the 342 MHz receiver.
    • If any of the above four mapping scheduling blocks aborts or needs to be stopped, then please make a note of the current Subscan and then edit the mapping script to start from the last valid scan. For example, if the scheduling block 06_800MHz_map_DecwRef was stopped at Subscan 12 of 15, then modify the scheduling block by setting start=12 in the DecLatMapWithReference command before re-submitting it.

  • increase_session_number : When you reach this scheduling block, please increase the session number by one. This is for bookkeeping purposes only.

  • end : If you reach this scheduling block, and there is time left, please re-submit the previous scheduling block.
    • For example, if 05_800MHz_map_RAwRef finished and the next script is 06_end, please re-submit 05_800MHz_map_RAwRef.

-- PedroSalas - 2022-03-09
Topic attachments
I Attachment Action Size Date Who Comment
bad_peak.pngpng bad_peak.png manage 274 K 2022-03-09 - 21:27 PedroSalas Example of bad peak scans
good_peak.pngpng good_peak.png manage 263 K 2022-03-09 - 21:28 PedroSalas Example of good peak scans
Topic revision: r10 - 2022-11-15, PedroSalas
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding NRAO Public Wiki? Send feedback