observing_procedure
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| observing_procedure [2025/12/02 15:56] – holtz | observing_procedure [2025/12/02 21:58] (current) – holtz | ||
|---|---|---|---|
| Line 18: | Line 18: | ||
| The basic robotic workflow is: | The basic robotic workflow is: | ||
| + | * touches an MJD file to show sequence has started | ||
| * wait until sunset+dt_sunset | * wait until sunset+dt_sunset | ||
| * wait until safe to open, as determined from either 2.5m open, 3.5m open or override set | * wait until safe to open, as determined from either 2.5m open, 3.5m open or override set | ||
| Line 27: | Line 28: | ||
| * loop until morning nautical twilight | * loop until morning nautical twilight | ||
| * if unsafe to observe, close dome and wait 90 seconds | * if unsafe to observe, close dome and wait 90 seconds | ||
| - | * if it has been more than dt_focus (default=1.5 unless specified by keyword), do a focus run | + | * else if dome is closed and now safe to open, open dome |
| - | * otherwise, | + | * else if it has been more than dt_focus (default=1.5 unless specified by keyword), do a focus run |
| + | * else choose best object to observe | ||
| * if not the same as last object, acquire object in guider | * if not the same as last object, acquire object in guider | ||
| * perform requested observing sequence | * perform requested observing sequence | ||
| + | * close dome, turn off fans, close louvers, stop guider, park telescope and dome (all via domeclose()) | ||
| * take morning cals | * take morning cals | ||
| * create guider movies, focus plots, reduce data, and make web page | * create guider movies, focus plots, reduce data, and make web page | ||
| + | * sends successful completion email with webcam snapshot attached, removes MJD file | ||
| + | |||
| + | Two cron jobs run at 8:00 each morning: | ||
| + | * one runs copy command to sync /data/1m to astronomy /home/1m | ||
| + | * second checks for existence of an MJD file and sends failure email if it finds one | ||
| ==== Morning ==== | ==== Morning ==== | ||
| Line 40: | Line 48: | ||
| * aposong window to see if robotic sequence completed normally, which will leave it at a python prompt | * aposong window to see if robotic sequence completed normally, which will leave it at a python prompt | ||
| * if sequence completed normally, check web pages to see what was observed, check focus curves, check throughput plots as desired | * if sequence completed normally, check web pages to see what was observed, check focus curves, check throughput plots as desired | ||
| - | * if sequence didn't complete normally, try to figure out what happened! May be useful to create the web pages, etc., manually, using < | + | * if sequence didn't complete normally, try to figure out what happened! May be useful to create the web pages, etc., manually, using < |
| ==== Troubleshooting ==== | ==== Troubleshooting ==== | ||
observing_procedure.1764691006.txt.gz · Last modified: by holtz