Skip to content

Conversation

@joshua-liberman
Copy link
Contributor

  • Docs describing how to set up the AO system on-sky, prior to starting science observations

@joseph-long
Copy link
Member

Thanks for this, @jlibermann. It looks like something funky happened with index.rst. It could be windows line endings. Could you correct that so the only edited lines are the one you actually added?

@jaredmales jaredmales self-assigned this Aug 4, 2024
Copy link
Member

@jaredmales jaredmales left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great job @jlibermann. A few details to clean up. I think we want to reorganize a little to add an alignment procedure, based on the one I put on slack and is pinned, as a separate thing that happens before acquisition and loop-closing. You can get higher quality figures for the guis using your remote operations ability and screen-shotting them.

1. Modulating the WFS

* Set the FPS on the ``camwfsctrl`` GUI to ``2000``
* In CursesINDI, type ``fxngensync`` and toggle the state to ``On`` (see the `cursesINDI guide <./software/guis/cursesINDI>`__ if you need a refresher)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

state of what? it's C1outp

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

#. In the web interface, set ``fwpupil`` to ``bump-mask``.
#. Now use the ``Pupil Plane`` buttons in the ``coronAlignGUI`` to align the bump mask on the pupil. Set the step size to ``100`` and press the down arrow 3 times. This is typically enough to align the bump mask. However, if the bump mask still appears slightly misaligned, reduce the step size to ``5`` and use the left/right arrow keys for fine adjustments.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is correct, but assumes that the alignment was already done on the soruce to get the mask close. just re-making the point that we need a separate alignment procedure (like the one that is pinned on slack)

Closing the Pupil Alignment Loop
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

#. In the ``Pupil Alignment`` GUI, use the keypad in the lower-righthand corner to drive the x and y avg values to 0. After each translation, wait a few seconds for the readings to stabilize. Also note that the x-axis is much more sensitive than the y-axis. When moving x-axis avg to 0, use step sizes of about 0.1. When moving y-axis to 0, higher step sizes can be used.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the idea is correct. It's really something like "when x is within 0.2, steps sizes of 0.05 should be used. The y-axis steps size can remain 0.1"

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

#. In the ``Pupil Alignment`` GUI, use the keypad in the lower-righthand corner to drive the x and y avg values to 0. After each translation, wait a few seconds for the readings to stabilize. Also note that the x-axis is much more sensitive than the y-axis. When moving x-axis avg to 0, use step sizes of about 0.1. When moving y-axis to 0, higher step sizes can be used.
#. Once the x, y avgs are at roughly 0, set the pupil alignment loop gain to 0.1 and turn on the pupil alignment loop.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

change "roughly 0" to "0 +/- 0.1"

@joseph-long
Copy link
Member

What's going on here? It looks like a lot more changes and some regressions (introducing old typos etc)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants