GOTHAM Operator-Driven Scripts Documentation

Scripts Written By: Andrew M. Burkhardt

Last Update: Aug 1, 2021

Project: AGBT21B_210

Summary of Autopointing Script

There are two scripts for each observing session. The first is a primary observing script, whose name always includes Autopointing_Observation_Script. This script observes the science target and runs pointing/focus automatically at a specified rate (e.g. 2 hrs). 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 science observations. Times in which last pointing occurred are saved in text files as outlined below.

---

AGBT21B_210: Ku-Band, KFPA, and Ka-Band Observations

For these observations, the scripts and pointing time files are named by the session numbers they belong to. Each script works for multiple session numbers. For example: "01_15_Ku_Additional_Pointing_Script" is for Sessions 01 and 15, whereas "05_12_19_26_KFPA_Additional_Pointing_Script.py" is for Sessions 05, 12, 19, and 26.

• 01_15_Ku_Additional_Pointing_Script
• 01_15_Ku_Autopointing_Observation_Script


• 02_16_Ku_Additional_Pointing_Script
• 02_16_Ku_Autopointing_Observation_Script


• 03_17_Ku_Additional_Pointing_Script
• 03_17_Ku_Autopointing_Observation_Script


• 04_18_Ku_Additional_Pointing_Script
• 04_18_Ku_Autopointing_Observation_Script


• 05_12_19_26_KFPA_Additional_Pointing_Script
• 05_12_19_26_KFPA_Autopointing_Observation_Script


• 06_13_20_27_KFPA_Additional_Pointing_Script
• 06_13_20_27_KFPA_Autopointing_Observation_Script


• 07_14_21_28_KFPA_Additional_Pointing_Script
• 07_14_21_28_KFPA_Autopointing_Observation_Script


• 08_22_Ka_Additional_Pointing_Script
• 08_22_Ka_Autopointing_Observation_Script


• 09_23_Ka_Additional_Pointing_Script
• 09_23_Ka_Autopointing_Observation_Script


• 10_24_Ka_Additional_Pointing_Script
• 10_24_Ka_Autopointing_Observation_Script


• 11_25_Ka_Additional_Pointing_Script
• 11_25_Ka_Autopointing_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 AGBT21B_210 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 Observation Script.


6. If pointing has not been performed in the past 2hrs, the script will slew to the pointing source, currently 0530+1331, and perform one or more 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 it continue, and proceed to Step 7. 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 slew to our science target (TMC-1).
   
   
7. 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. Brett McGuire
   2. Andrew Burkhardt
   
   
   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