Versions Compared

Version Old Version 1 New Version Current
Changes made by

Josh Walawender

Josh Walawender

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Tip

Welcome to your new space

Use it to create something wonderful.

To start, you might want to:

  • Customise this overview using the edit icon at the top right of this page.

  • Create a new page by clicking the + in the space sidebar, then go ahead and fill it with plans, ideas, or anything else your heart desires.

Info

Need inspiration?

  • Get a quick intro into what spaces are, and how to best use them at Confluence 101: organize your work in spaces.

  • Check out our guide for ideas on how to set up your space overview.

    • If starting from a blank space is daunting, try using one of the space templates insteadThe proposed three layers of checkout:

    1) Verification

    • Can be run at any time (including during observing)

    • Similar in many ways to the current role of testAll and ct/ctx

    • Can be run by anyone (OA, SA, Day Crew, etc.)

    Our current plan is to make these keyword based, rather than script based. Kyle is currently drafting code to handle the non-keyword components we have already identified (e.g. ping and ps | grep). This would mean that the instrument verification will be an always available keyword that is continuously updated.

    2) Quick Checkout

    • A brief (a few minutes max) checkout.

    • May move instrument mechanisms or take a test exposure, so instrument can not be observing.

    • Hatch closed only (other instruments may be observing).

    • Use this for the day crew departure check / instrument release.

    • Could also be run before an instrument change during the night.

    • Can be run by anyone who has been trained.

    This is a slightly more in depth check of the instrument than the verification step above as it may use the instrument to move mechanisms, take a test exposure, etc.

    3) Full Checkout

    • Similar to existing pre-run checkouts.

    • Verify/measure instrument performance.

    • Requires extensive use of instrument, so instrument must be released.

    • Run by instrument experts.