Operator Instructions for The GBT L1544 Unbiased Complex Organics SurvEy (GLUCOSE)

Scripts Written By: Andrew Burkhardt & Modified By: Samantha Scibelli

Last Update: August 6, 2024

Project: AGBT24B-077 (Previously: AGBT22A-899)

Summary of Autopointing Script

These instructions are copied and modified from those written by Andrew M. Burkhardt for the GOTHAM project and can be found here.

There are two scripts for each observing session. The first is a primary observing script, whose name always includes Autopointing_Calibration_Observation_Script. This script observes the science target, runs pointing/focus automatically at a specified rate (e.g. 2 hrs) and does calibration scans at a specified rate (12 hours). Once submitted, the scripts run AutoPeakFocus twice. The script will then pause and request observer/operator to check quality of pointing solution. If the pointing solution is not adequate, the observer/operator will need to abort script and run the second script associated with that session, whose name always includes Additional_Pointing_Script. Otherwise, the primary script can be un-paused and continue onto calibration scans and then onto a second pointing before moving onto science observations. Times in which last pointing and calibration has occurred are saved in text files as outlined below.

For these observations, the scripts and pointing time files are named by the session numbers they belong to. Each script belongs to a certain session number. For example: "02_Ka_Additional_Pointing_Script" is for Sessions 02.
  • 01_Ka_Additional_Pointing_Script
  • 01_Ka_Autopointing_Calibration_Observation_Script

  • 02_Ka_Additional_Pointing_Script
  • 02_Ka_Autopointing_Calibration_Observation_Script

    • Please use the script appropriate for the session number that has been scheduled for the project.

    Workflow

    1. Once the appropriate receiver is in place (or if it is already in place from the previous session), please close and re-open ASTRID.

    2. Open project AGBT22A-077 as scheduled in ASTRID.

    3. In DataDisplay tab, click the Pointing Tab. Then, open the Tools dropdown menu, select Options, and click the Heuristics tab. Make sure this is set to Relaxed.

    4. Back in the DataDisplay Page, click the Focus tab and repeat everything in the previous step that was done in the Pointing Tab.

    5. In the Observation Management tab, submit the appropriate Autopointing Calibration Observation Script.

    6. The script will check if calibrations have been done in the past 12 hours. If no calibrations have been done, the script configures for the calibration setup, and if they have been done it configures to the science setup. In either case, we start with pointing and focus scans.

    7. Pointing and focusing will be done automatically every 2 hours and requires approval from the user. The script will slew to the pointing source, currently 0319+4130, and perform two AutoPeakFocus scans. After the second, the script will pause and request user input:

      • If the pointing/focus is adequate (see images below), do not abort the script, let the observing block continue. Please use your best judgement for the quality of the pointing. The examples below represent what we consider an 'excellent' pointing and a 'poor' pointing. Certainly many good solutions will fall between these, and the quality will vary given weather and time of day.

      • If the point/focus is not adequate, abort the script and run the appropriate Additional Pointing Script until pointing/focus improves.

      • Once pointing/focus has improved, resubmit the appropriate Autopointing Observation Script which should automatically move onto the next step.

    8. Next, during calibration the script will automatically slew to and run `OffOn' two times for 0319+4130, Uranus and lastly L1544.
    9. After the calibration is done, the script will point and focus again on 0319+4130. Follow instructions in step 7 above to manually approve or abort script depending on pointing success.
    10. The script will then slew and continue to run `OffOn' scans for our science target (L1544) until it is time for the next pointing/focus.
    11. When allotted time is completed, abort the script preferably at the end of an OffOn subscan. You should be able to determine when to stop with about 5 minutes left in allotted time.

    Troubleshooting

    1. If the script crashes, attempt to restart the script.

    2. If aborting and restarting the script does not work, or there are any other issues, please contact:

      1. Samantha Scibelli

      All persons contact information are in the GBT system. If it is after 9 p.m., you may need to call twice to break through any Do Not Disturb Functionality. Regardless, please document errors, irregularities, or other issues and add as notes in the observing report.

    Example of Good Pointing and Focus

    Examples of Bad Pointing and Focus