Merge branch 'main' into tickets/SITCOM-1475

4

@@ -0,0 +1,21 @@
+[?1049h[>4;2m[?1h=[?2004h[?1004h[?12h[?12l[?25l"~/Documents/GitHub/observatory-ops-docs/.git/rebase-merge/git-rebase-todo" 32L, 1485Bnoop
+
+# Rebase be4d319..be4d319 onto be4d319 (1 command)
+#
+# Commands:
+# p, pick <commit> = use commit
+# r, reword <commit> = use commit, but edit the commit message
+# e, edit <commit> = use commit, but stop for amending
+# s, squash <commit> = use commit, but meld into previous commit
+# f, fixup [-C | -c] <commit> = like "squash" but keep only the previous
+#commit's log message, unless -C is used, in which case
+#keep only this commit's message; -c is same as -C but
+#opens the editor
+# x, exec <command> = run command (the rest of the line) using shell
+# b, break = stop here (continue rebase later with 'git rebase --continue')
+# d, drop <commit> = remove commit
+# l, label <label> = label current HEAD with a name
+# t, reset <label> = reset HEAD to a label
+# m, merge [-C <commit> | -c <commit>] <label> [# <oneline>]
+#create a merge commit using the original merge commit's
+#message (or the oneline, if no original merge commit was[?25h[?4m[?2004l[>4;m[?1004l[?2004l[?1l>[?1049l[>4;m

AuxTel/Non-Standard-Operations/ATCS/AuxTel-Verify-Telescope-and-Dome-Drives-Interlocks.rst

@@ -0,0 +1,92 @@
+.. This is a template for operational procedures. Each procedure will have its own sub-directory. This comment may be deleted when the template is copied to the destination.
+
+.. Review the README in this procedure's directory on instructions to contribute.
+.. Static objects, such as figures, should be stored in the _static directory. Review the _static/README in this procedure's directory on instructions to contribute.
+.. Do not remove the comments that describe each section. They are included to provide guidance to contributors.
+.. Do not remove other content provided in the templates, such as a section. Instead, comment out the content and include comments to explain the situation. For example:
+	- If a section within the template is not needed, comment out the section title and label reference. Include a comment explaining why this is not required.
+    - If a file cannot include a title (surrounded by ampersands (#)), comment out the title from the template and include a comment explaining why this is implemented (in addition to applying the ``title`` directive).
+
+.. Include one Primary Author and list of Contributors (comma separated) between the asterisks (*):
+.. |author| replace::  *Franco Colleoni, Jacqueline Seron*
+.. If there are no contributors, write "none" between the asterisks. Do not remove the substitution.
+.. |contributors| replace:: *List-of-contributors*
+
+.. This is the label that can be used as for cross referencing this procedure.
+.. Recommended format is "Directory Name"-"Title Name"  -- Spaces should be replaced by hyphens.
+.. _ATCS-Verify-AuxTel-Telescope-and-Dome-Drives-Interlocks:
+.. Each section should includes a label for cross referencing to a given area.
+.. Recommended format for all labels is "Title Name"-"Section Name" -- Spaces should be replaced by hyphens.
+.. To reference a label that isn't associated with an reST object such as a title or figure, you must include the link an explicit title using the syntax :ref:`link text <label-name>`.
+.. An error will alert you of identical labels during the build process.
+
+############################################
+Verify Telescope and Dome Drives Interlocks
+############################################
+
+
+
+.. _AuxTel-Telescope-and-Dome-Drive-Interlocks-Overview:
+
+Overview
+========
+
+.. This section should provide a brief, top-level description of the procedure's purpose and utilization. Consider including the expected user and when the procedure will be performed.
+
+This procedure outlines the steps to verify if the AuxTel telescope 
+and dome drives have a **triggered interlock** due to the gate being open, 
+the gate being in error, an E-STOP action, or a general failure.
+
+
+.. _AuxTel-Telescope-and-Dome-Drives-Interlocks-Precondition:
+
+Precondition
+============
+
+- You are uncertain of the state of the telescope and dome drives.
+
+
+.. _AuxTel-Telescope-and-Dome-Drives-Interlocks-Post-Condition:
+
+Post-Condition
+==============
+
+- You’ve identified any triggered interlocks for the AuxTel telescope and dome drives.
+- You can now take corrective actions to restore the system.
+
+
+.. _AuxTel-Telescope-and-Dome-Drives-Interlocks-Procedure-Steps:
+
+Procedure Steps
+===============
+
+
+* Check the **Pilz controller** inside the AuxTel Main Cabinet
+
+* According to the **lights**, if they are:
+    * *Off*, an interlock is triggered.
+    * *Illuminated*, the system is functioning correctly.
+
+
+
+.. figure:: ./_static/pilz-controller-status.png
+      :width: 500px
+
+      Pilz controller status at the AuxTel Main Cabinet
+
+
+
+
+.. _AuxTel-Telescope-and-Dome-Drives-Interlocks-Troubleshooting:
+
+Troubleshooting
+===============
+
+If an interlock has been triggered, follow one of the procedures below based on the cause:
+
+
+* Gate open, gate in error: :ref:`Safety Gate procedures <Safety-Systems-Safety-Gate-Procedures>`.
+
+* E-STOP activated: :ref:`E-stop procedure <AuxTel-Non-Standard-Procedures-E-Stop-Procedure>`.
+
+* General failure: :ref:`Recovery after a Shutdown <AuxTel-Non-Standard-Operations-AuxTel-Recovery-after-Shutdown>`.

AuxTel/Standard-Operations/Daytime-Operations/Daytime-Checkout.rst

@@ -40,8 +40,8 @@ The scripts can all be found under the standard scripts panel in the *LOVE ATQue
 The order of script execution is nominally:
 
 * :file:`auxtel/enable_latiss.py` - Can be skipped if LATISS enabled 
-* :file:`auxtel/daytime_checkout/latiss_checkout.py`
 * :file:`auxtel/enable_atcs.py` - Can be skipped if ATCS already enabled
+* :file:`auxtel/daytime_checkout/latiss_checkout.py`
 * :file:`auxtel/daytime_checkout/atpneumatics_checkout.py`
 * :file:`auxtel/daytime_checkout/telescope_and_dome_checkout.py`
 * :file:`auxtel/daytime_checkout/slew_and_take_image_checkout.py`
@@ -51,6 +51,11 @@ The order of script execution is nominally:
 
 Bring *LATISS* to an enabled state to prepare for checkout. 
 
+*auxtel/enable_atcs.py*
+=======================
+
+Bring the *ATCS* into an enabled state to prepare for checkout. 
+
 *auxtel/daytime_checkout/latiss_checkout.py*
 ============================================
 
@@ -62,11 +67,6 @@ In case the image fails to appear, promptly communicate the issue in the channel
 
 You can also check if images are arriving correctly at Rubin's SLAC facility using `USDF RubinTV`_.
 
-*auxtel/enable_atcs.py*
-=======================
-
-Bring the *ATCS* into an enabled state to prepare for checkout. 
-
 *auxtel/daytime_checkout/atpneumatics_checkout.py*
 ==================================================
 
@@ -114,99 +114,6 @@ This procedure was last modified on |today|... |author| replace:: *E. Dennihy*
 .. _`summit's RubinTV`: https://summit-lsp.lsst.codes/rubintv/summit/auxtel 
 .. _`USDF RubinTV`: https://usdf-rsp-dev.slac.stanford.edu/rubintv 
 
-##################
-Daytime Checkout 
-##################
-
-
-To ensure the Auxiliary Telescope is fully operational and ready for nighttime use, 
-we have created a series of SAL Scripts that successively checkout each of the major components, 
-culminating in a full test of the system involving slewing to a target, tracking, and taking a test image with LATISS. 
-The goal of these scripts is to test the functionality of each component within the current software environment,
-and alert the daytime staff to any operational issues before going on-sky. 
-These tests are designed to be run using the script queue on LOVE during the daytime with an Observing Specialist 
-or other personnel available to verify their results. 
-
-The scripts are intended to be run in order, 
-but offer some flexibility in what state to leave the Auxiliary Telescope 
-(e.g. ready to take calibrations, ready to observe at night, or simply parked and shutdown). 
-They can also be run individually if a single component is undergoing maintenance 
-and requires a check of basic functionality. 
-
-**None of the scripts require configuration.**
-
-.. Important::
-
-    The daytime checkout scripts involve Telescope, Dome, and Instrument component movement. 
-    Before running, ensure that the area surrounding the telescope is and dome is clear for movement. 
-    You MUST announce that you are running the checks on the #summit-announce slack channel before execution. 
-
-The scripts can all be found under the standard scripts panel in the *LOVE ATQueue* view. 
-The order of script execution is nominally:
-
-* :file:`auxtel/enable_latiss.py` - Can be skipped if LATISS enabled 
-* :file:`auxtel/daytime_checkout/latiss_checkout.py`
-* :file:`auxtel/enable_atcs.py` - Can be skipped if ATCS already enabled
-* :file:`auxtel/daytime_checkout/atpneumatics_checkout.py`
-* :file:`auxtel/daytime_checkout/telescope_and_dome_checkout.py`
-* :file:`auxtel/daytime_checkout/slew_and_take_image_checkout.py`
-
-*auxtel/enable_latiss.py*
-=========================
-
-Bring *LATISS* to an enabled state to prepare for checkout. 
-
-*auxtel/daytime_checkout/latiss_checkout.py*
-============================================
-
-This script will take a bias and an engineering frame with *LATISS* 
-and ensure that they are ingested by the *OODS*.
-
-Verify that the bias appears on the `summit's RubinTV`_. 
-In case the image fails to appear, promptly communicate the issue in the Slack channel *#summit-auxtel*. 
-
-You can also check if images are arriving correctly at Rubin's SLAC facility using `USDF RubinTV`_.
-
-*auxtel/enable_atcs.py*
-=======================
-
-Bring the *ATCS* into an enabled state to prepare for checkout. 
-
-*auxtel/daytime_checkout/atpneumatics_checkout.py*
-==================================================
-
-This script will first turn on the valves and check that the line pressure is sufficient for operations. 
-Next, the telescope will be slewed to the park position, if it is not already there. 
-Then, it will turn on/off the *ATAOS* corrections before lowering the mirror back down onto its hard points.
-Finally, the mirror cover and vents are opened and closed. 
-
-*auxtel/daytime_checkout/telescope_and_dome_checkout.py*
-========================================================
-
-This script starts by performing a slew of the telescope without dome movement. 
-Then, sidereal tracking for the telescope is enabled and the system is left to track for a few minutes. 
-Tracking is disabled and then the dome is commanded to move to a new position, without telescope movement. 
-Finally, the telescope and dome are returned to a park position and left enabled.
-
-*auxtel/daytime_checkout/slew_and_take_image_checkout.py*
-=========================================================
-
-This script will slew the telescope and dome to two different targets, 
-track each target for 3 minutes and take a single verification image. 
-The mirror covers remain closed during the duration of the script. 
-At the end of the script, the telescope and dome are parked. 
-
-Check that the verification images pop up in the monitor at `summit's RubinTV`_.
-
-*auxtel/daytime_checkout/prepare_for/flat.py*
-=============================================
-This is the default end-of-checkout script. 
-It will leave the telescope in position to start taking afternoon calibrations. 
-If you are not sure how you want to leave the telescope,
-consider running this script as it will further exercise the system. 
-
-Other options include: :file:`prepare_for/onsky.py`, :file:`prepare_for/vent.py` or :file:`shutdown_all.py`
-
 Quick Troubleshooting
 =====================
 

AuxTel/Standard-Operations/Daytime-Operations/latiss-daily-calibrations-BIAS-DARK-FLAT-all-filters-empty-procedure.rst

@@ -40,15 +40,14 @@ Post-Condition
 Procedure Steps
 ===============
 
-#. Calibrations images should only be taken if the LATISS WREB temperature is under temperature control. Check the LATISS WREB temperatures under the `AuxTel (LATISS) Temperatures and Pressures dashboard`_ in Chronograf. WREB temperatures are visible in the lower middle panel labeled *WREB On Board*. If the *mean_temp2* (top blue line) is between 26-29 degress C, the temperature is suitable for taking calibrations. During the daytime, the fan on the WREB board may not be sufficient to cool the WREB down to these temperatures, so during warmer months you may have to wait until later in the day or early in the morning for it to reach the desired temperature. If the temperature is too high, do not proceed to the next steps.
 #. Enable ATCS and LATISS using the standard scripts :file:`enable_atcs.py` and :file:`enable_latiss.py` with no configuration. 
-#. Enable ``Scheduler:2`` with a valid scheduler configuration. Use the standard script :file:`auxtel/scheduler/enable.py` with the configuration required for the run and available in the corresponding night log. 
+#. Enable ``Scheduler:2`` with a valid scheduler configuration. Use the standard script :file:`auxtel/scheduler/enable.py` with the configuration specified in the AuxTel Scheduler-Driven Survey Test Case (BLOCK-T19). 
 #. **Setup LATISS calibrations** BLOCK will setup ATCS and white light for calibrations. It enables and turns on the ATWhiteLight, enables OCPS:1 and commands AuxTel mount and dome to the FLAT position. Run the script :file:`add_block.py` to the ATQueue  with the following configuration:
 
     .. code-block:: text
       :caption: :file:`add_block.py`
 
-      id: setup_latiss_calibrations
+      id: BLOCK-309
 
     The BLOCK with :file:`setup_latiss_calibrations` configuration will queue the scripts aimed to setup the system. It will start with the :file:`set_summary_state.py` script to enable ATWhiteLight CSC with the following configuration:
 
@@ -75,19 +74,19 @@ Procedure Steps
     .. code-block:: text
       :caption: :file:`auxtel/calibrations/power_on_atcalsys.py`
 
-    The :file:`auxtel/prepare_for/flat.py` script (empty configuration) will position the telescope and dome in FLAT position. The telescope will point towards the dome flat screen (mount Az = 188.7 deg, mount El = 39.0 deg, dome Az= 2.59 deg). Confirm in the cameras aux-cam01 or aux-cam02 that the white light is on, and telescope is pointing to the dome flat screen.
+    The :file:`auxtel/prepare_for/flat.py` script (empty configuration) will position the telescope and dome in FLAT position. The telescope will point towards the dome flat screen (mount Az = 188.7 deg, mount El = 39.0 deg, dome Az= 2.59 deg). Confirm in the cameras "aux-cam01" or "aux-cam02" that the white light is on, and telescope is pointing to the dome flat screen.
 
     .. code-block:: text
       :caption: :file:`auxtel/prepare_for/flat.py`
   
     .. Note: We need to document and link here how to access the aux-cam01/02cameras.
 
-#. The **LATISS daily calibrations** BLOCK will queue the scripts focused on the calibration image adquisition. Run the script :file:`add_block.py` to the ATQueue  with the following configuration:
+#. The **LATISS daily calibrations** BLOCK will queue the scripts focused on the calibration image acquisition. Run the script :file:`add_block.py` to the ATQueue  with the following configuration:
 
     .. code-block:: text
       :caption: :file:`add_block.py`
 
-      id: latiss_daily_calibrations
+      id: BLOCK-295
 
 
     Depending on which filters are currently installed in LATISS, the :file:`auxtel/make_latiss_calibrations.py` script may take different calibration sets. The calibration images displayed in `RubinTV`_ are post-ISR images and should have BIAS and DARK corrections applied. This means that BIAS and DARK images should display with maximum count rates of about 10 ADUs. In the case of FLAT images, counts must be below the :math:`\approx` 30000 ADUs. In the process of building the daily PTC (see below), the FLAT saturation is intended, and achieved at around the 123000 ADUs (with exposure time of about 25 seconds). In case daily FLATS are taken, they reach values of :math:`\approx` 68000 ADUs. If you see large deviations from these values, which can be related with a problem in the instrument signature removal in `RubinTV`_, then RAW count rates are being displayed, please report it. Check the calibration sets and their configurations for each filter installed and the grating.
@@ -260,7 +259,7 @@ Procedure Steps
     .. code-block:: text
       :caption: :file:`add_block.py`
 
-      id: shutdown_latiss_calibrations
+      id: BLOCK-310
 
 
     The BLOCK with :file:`shutdown_latiss_calibrations` configuration finishes with the :file:`auxtel/calibrations/power_off_atcalsys.py` SAL script with no configuration. It will turn off the lamp, close the shutter and shutdown the chiller. At this stage, the script completion time is 15 minutes.