Content Comparison

Here is a list of the actions that make up the MOSFIRE testAll

• Ping various computer/network hardware to confirm they are alive

  • kaimama

  • control1

  • eds1

  • mpulizzi1

  • mpulizzi2

  • iolan1

• Check lastalive keyword on software (Servers)

  • mosfire

  • mcsus

  • mdhs

  • mds

  • mfcs

  • mmdcs

  • mmf1s

  • mmf2s

  • mmgss

  • mmgts

  • mmprs

  • mp1s

  • mp2s

  • mpas

  • mscs

  • mtcs

• Verify PIDs exist for software

  • write_image

  • fcstrack

  • ds9relay

  • lickserv

• Verify power status

  • glycol_power = on

  • CSU_controller_power = on

  • CSU_drives_power = on

  • Jade2_power = on

  • computer_power = on

  • Lantronix_power = on

  • guider_focus_power = on

  • ion_pump_power = on

  • MAGIQ_guider_power = on

  • temp_control_power = on

  • motor_box_power = on

  • power_supply_power = on

  • FCS_controller_power = on

  • dewar_heater_power = on

  • CCR_1_power = on

  • CCR_2_power = on

• Verify stages

  • dust cover, mmdcs status is OK

  • filter wheel 1, mmf1s status is OK

  • filter wheel 2, mmf2s status is OK

  • grating turret, mmgts status is OK

  • grating shim, mmgss status is OK

  • pupil rotator, mmprs status is OK or TRACKING

  • CSU, mcsus status is OK

• Check Settings

  • glycol flow (mdhs glysup = Flow)

  • detector temp (mtcs curtmp1 = 77 +/- 0.1)

  • bulkhead temp (mtcs curtmp2 = 120 +/- 1)

  • CCR remote control (mscs chremote = 1)

  • CCR 1 Speed (mscs dacout1r = 45 +/- 1)

  • CCR 2 Speed (mscs dacout2r = 45 +/- 1)

  • window heater voltage (mdhs tmp5 = 17.5 +/- 1.5)

  • CSU electronics temp (mdhs tmp2 = 0-30)

  • cabinet temp (mdhs tmp3 = 0-30)

  • thermocouple pressure (mpas g1str = 0-1e-4)

  • ion pump 1 pressure (mpas g3str = 0 - 1e-7)

  • ion pump 2 pressure (mpas g4str = 0 - 1e-7)

  • cabinet door status (mdhs ebaydoor = Closed)

  • FCS correcting (mfcs active = 1)

  • datataking system (mds ready = 1)

  • current instrument (dcs currinst = mosfire)

Here is the current (17 Apr 2020) testAll script for MOSFIRE for reference.

...

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.