Update latiss-daily-calibrations procedure to remove WREB temperature… #132
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Kelks19
approved these changes
Sep 13, 2024
| #. 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. | ||
| #. **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: | ||
|
|
There was a problem hiding this comment.
Line 77 : I think aux-cam01 or aux-cam02 should be quotes and perhaps italics as they are names of instrument (just something to highlight that )
| #. 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. | ||
| #. **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 |
There was a problem hiding this comment.
I wonder whether we should include a note /warning saying that ATWhitelight may be turned on even if the script fails or that the script fails to turn it on. And the scripts to be run in each scenario. What do you think?
Perhaps it should go as a mini troubleshooting page instead of including the information here .....
There was a problem hiding this comment.
I hope that some of those failures will go away now that we have removed the monochromator from the block (this was only put in place on Friday Sept 13th). In the past, when we just ran the whitelight it was pretty reliable. Based on that I think a mini troubleshooting page might be better, maybe one for the calsys itself.
| @@ -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. | |||
There was a problem hiding this comment.
needs explicit mention of the Zephyr test cycle instead of "nightlog"
… requirement and update block ids.
edennihy
force-pushed
the
tickets/SITCOM-1611
branch
from
26acdd1
to
651d494
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
… requirement and update block ids.