Date: Tue, 13 Oct 2009 11:18:01 -0400
Subject: Re: 2.5m obslog 20091012 (MJD 55117)
From: Craig Loomis
  The tests for the hartmann state are only required until a) we (I)
confirm that the failures are now being handled correctly and b) sop
recovers and checks correctly. Those changes might be done today.
 - craig
On Tue, Oct 13, 2009 at 7:02 AM, Dan Oravetz  wrote:
>
> Here is a procedure to ensure Hartmann screens are in fact OUT prior to
> science exposures:
>
> =A0 =A0 =A0 =A0 =A0Issue "boss status" and look for screenStatus in the S=
TUI Log.
>
> =A0 =A0 =A0 =A0 =A0If screenStatus=3D0x05,0x05, then Hartmann screens are=
 OUT and you are
> =A0 =A0 =A0 =A0 =A0good to go.
>
> =A0 =A0 =A0 =A0 =A0If screenStatus has something like 0x06 or 0x09, then =
this indicates
> =A0 =A0 =A0 =A0 =A0that not all Hartmann screens are OUT and you should m=
anually move =A0 =A0 =A0 =A0 =A0 =A0 =A0them out:
>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0boss hartmann out spec=3Ds=
p1
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0boss hartmann out spec=3Ds=
p2
>
> =A0 =A0 =A0 =A0 =A0Check status again with "boss status" and look for 0x0=
5 values.
>
> =A0 =A0 =A0 =A0 =A0Also, check image headers for the HARTMANN keyword val=
ue to check
> =A0 =A0 =A0 =A0 =A0that the screens are moving as expected.