User Tools

Site Tools


observing_procedure

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
observing_procedure [2026/09/11 21:03] – [Status window] jasonjobserving_procedure [2026/09/11 22:33] (current) 24.4.246.2
Line 8: Line 8:
   * guider : process that waits for guide commands from aposong   * guider : process that waits for guide commands from aposong
   * video1m : shows a continuous webcam view using the VLC player (more practical than the web interface for the webcam, which you would need to point the webcam). There should be a browser open for the web interface if needed.   * video1m : shows a continuous webcam view using the VLC player (more practical than the web interface for the webcam, which you would need to point the webcam). There should be a browser open for the web interface if needed.
-  * override : xxx+  * override : runs the webapp that allows APO operators to allow 1m to open even if their telescopes are not yet open, if they deem conditions reliable
  
-On the second desktop, +On the second desktop, have a vnc window logged into spec1m (vncviewer spec1m.apo.nmsu.edu from a song1m terminal), which should have running:  
 +  * spectro_app : runs the Alpyca server for control of chiller, relays 
 +  * ASCOM Remote : provides Alpaca access to ASCOM driver for QHY 600 (click the desktop icon to start it) 
 + 
 +On the third desktop, have a vnc window logged into pwi1m (vncviewer pwi1m.apo.nmsu.edu from a song1m terminal),  
 +  * PWI4 : open from desktop icon 
 +  * ASCOM Remote : provides Alpaca access too ASCOM drivers for telescope, CCD cameras (open from desktop icon) 
 +  * dome_app : runs the Alpyca server for control of stages, iodine thermal controll
  
-On the third desktop, 
  
-In addition to this, processes must be running on the machines dome1m, pwi1m, and spec1m, but these are generally fairly stable, and only need to be checked in case of issues. 
  
 Under normal operations, robotic observing is accomplished with a single command in aposong. For example: Under normal operations, robotic observing is accomplished with a single command in aposong. For example:
Line 21: Line 26:
 robotic.observe(focstart=33200,display=disp) robotic.observe(focstart=33200,display=disp)
 </code> </code>
-where focstart is an inital focus guess, and disp is a pyvista display object if you want to see images as they are being taken.+where focstart is an inital focus guess that may need to be adjusted seasonally, and disp is a pyvista display object if you want to see images as they are being taken.
  
 The basic robotic workflow is: The basic robotic workflow is:
Line 50: Line 55:
 ==== Status window ==== ==== Status window ====
  
-The status process shows a diagnostic window such as the figure below+The status process running on song1m shows a diagnostic window such as the figure below
  
 {{ :software:status_window.png?direct&400 |}} {{ :software:status_window.png?direct&400 |}}
  
-This window shows+This window has a few important  diagnostics to understand and keep an eye one:
   * x   * x
   * y   * y
Line 75: Line 80:
   * if not closed, or if closed but telescope not in park position, issue domeclose() command from an aposong window (you may wish to start a new one if you want to leave the incompleted observing one open for inspection)   * if not closed, or if closed but telescope not in park position, issue domeclose() command from an aposong window (you may wish to start a new one if you want to leave the incompleted observing one open for inspection)
   * if dome does not close, may need to call APO!   * if dome does not close, may need to call APO!
 +  * if telescope is not parked, make sure mirror covers are closed with mirror_covers() and then T.park()
   * to determine failure mode:   * to determine failure mode:
     * attempt to understand where script failed     * attempt to understand where script failed
     * check guider window to see if guider program is still running     * check guider window to see if guider program is still running
     * check for any errors in status window     * check for any errors in status window
-    * check pwi1m computer to see if Planewave had issues, either diconnected or one axis disabled+    * check pwi1m computer to see if Planewave had issues, either disconnected or one axis disabled
     * check spec1m computer to ensure ASCOM Remote and Alpyca server are running     * check spec1m computer to ensure ASCOM Remote and Alpyca server are running
  
observing_procedure.1789160606.txt.gz · Last modified: by jasonj