Daily Startup
=============

The steps below assume that the steps in :doc:`startup` are complete. This will
generally be the instrument state on a daily basis.

1. Ensure MagAO-X processes are started on AOC, ICC and RTC.  We do this by running `xctrl status` on each machine.

   ::

      # starting with AOC:
      [xsup@exao1 ~]$ xctrl status
      # verify processes are all green/running
      # next on ICC:
      [xsup@exao1 ~]$ ssh icc
      [xsup@exao3 ~]$ xctrl status
      # verify processes are all green/running
      [xsup@exao3 ~]$ exit
      # now for RTC:
      [xsup@exao1 ~]$ ssh rtc
      [xsup@exao2 ~]$ xctrl status
      # verify processes are all green/running
      [xsup@exao2 ~]$ exit

  A useful further check is to run `getINDI` on each machine to verify that INDI server is communicating.

.. note::
     All software on all machines should be up and running with good INDI communications. If it is not you can not begin to power up because you won't be able to observe what happens.

2. Ensure that you have working GUIs which are connected to INDI.

.. note::
     This must include a display of the log stream that you are able to see at all times.

3. On the **pwrGUI** *ninja* tab, verify the following items are on:

   -  pdu3.blower
   -  pdu3.rackfans
   -  pdu3.instCool
   -  usbdu0.rhtweeter
   -  usbdu1.rhncpc

.. warning::
    If any of these indicate off, stop and investigate.  These are safety issues and you should not go on.

4.  On the **pwrGUI** *ninja* tab, verify that the following items are on:

   -  pdu0.dcpwr
   -  pdu0.compicc
   -  pdu0.comprtc

.. note::
    If any of these are off, the instrument probably won't work.

.. warning::
       You must be monitoring the relative humidity for ``dmtweeter`` and ``dmncpc`` any time their power is on.

5. Use the **pwrGUI** to power up the MagAO-X components

   - Verify that humidity for both ``rhtweeter`` and ``rhncpc`` are below 15%.

      .. note::

         The most foolproof way to get the latest measurements is running ``getINDI rhtweeter rhncpc`` on AOC. They are also reported on the data dashboard and as an overlay on the rtimv DM viewers.

   - On the user tab power everything on.
        - ``camvisx`` and ``stageff`` can be left off if not needed
        - ``camacq`` and ``flipacq`` are only used on-sky
        - If you are using GMT HCAT, all devices on ``pduhcat`` can be powered on (you won't see this at LCO)

   - If you plan to use either ``camflowfs`` or ``camllowfs``, check their power in the *ninja* tab.  If they are not powered up:
            - begin with both cameras powered off
            - on exao3/ICC: ``xctrl shutdown camflowfs camllowfs``
            - power on one or both cameras
            - as a non-xsup user, on exao3/ICC, run ``sudo /opt/pvcam/drivers/in-kernel/pcie/hotplug_pcie.sh``, verify the number of "active cameras" it reports
            - on exao3/ICC: ``xctrl startup camflowfs camllowfs``

6. Once power up is complete, switch to lab mode by running the `xlabmode` script as `xsup` on `aoc`:

    ::

      # Run on AOC:
      [xsup@exao1 ~]$ xlabmode

    This will move `stagepickoff` to the lab position and ensure the ADCs and K-mirror are in the correct position.

7. Set the flat on the ``dmwoofer``, ``dmtweeter``, and ``dmncpc``.

8. Now on the Alignment GUI:

   - :guilabel:`set` the pyramid modulator under "Modulation"
   - :guilabel:`set` TTM Pupil
   - :guilabel:`set` TTM Peri

9. **Optional, but recommended** Set the toggles on ``sysMonRTC.set_latency.toggle`` and ``sysMonICC.set_latency.toggle`` to "On" using cursesINDI.

10. At this point you should see a PSF image on ``camtip``, probably with a fair amount of aberration.


   .. figure:: figures/camtip_psf_initial.png
      :width: 300px
      :alt: Aberrated camtip PSF

      An AO system would clean that right up.

   - If you do not see anything, use the system block diagram to troubleshoot. The most likely causes are that you forgot to power something on (the source?) or that ``stagepickoff`` is in the wrong position.
     Another possibility is that `flipwfsf` is `in`, but `fwtelsim` is in `VisOpen` which blocks IR light.

11. Setup camwfs using the ``camwfsCtrl`` GUI:

    - set the FPS to the desired loop speed (for the ``default`` calibration, 2000 Hz)
    - toggle ``synchro`` to "on"
    - close the shutter
    - take a dark
    - open the shutter

12. On the Alignment GUI, under "Modulation":

   - input the :guilabel:`Frequency [Hz]` (for the ``default`` calibration, that is 2000 Hz) and hit :kbd:`enter`
   - input the **Radius [l/D]** (for ``default``, 3 lambda/D) and hit enter
   - **Note that your newly entered values won't appear until modulation begins.**
   - click :guilabel:`Modulate`
   - the status text should change to ``CONFIGURING``.  Wait for it to say ``MODULATING``.
   - confirm that the PSF on ``camtip`` has become a donut

13. The cameras with temperature control will start cooling themselves down immediately on software startup, and should be cold by now. Check on them.

14. **Optional, but recommended** Set the toggles on ``sysMonRTC.set_latency.toggle`` and ``sysMonICC.set_latency.toggle`` to "On".

15. Setup CACAO for closing the high-order loop as in :doc:`cacao`

16. Now align the system as in :doc:`alignment <./alignment>`