Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 5 Current »

The 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.

  • No labels