Date: Tue, 16 Mar 2010 14:43:22 -0400
Subject: Re: [SDSS3-infrastructure 2763] Re: 2.5m obslog 20100315 (MJD 55271)
From: Craig Loomis
  Partly because of the retries and because there used to only be a
single status command which returned everything. And the ICC used to
control exposure timing. So you could not be sure of getting the
status and/or the timing right for any exposure below, say, 5s.
  As Russell points out, in v3 the controller now generates the
Hartmann and Shutter status in response to each exposure command. The
ICC should use those.
 - craig
On Tue, Mar 16, 2010 at 2:27 PM, jegunn  wrote:
>
> Why not just check for these? Why does getting specmech status take
> time??
>
> thanks
>
> --jim
>
> On Tue, 16 Mar 2010, Craig Loomis wrote:
>
>> =A0The hartmann screen position reporting is wrong for biases and
>> darks, but I'd be surprised if it has changed recently (since specmech
>> v3).
>> =A0The longer story is that the icc no longer queries for screen &
>> shutter status at the start of exposures, because there was no
>> sensible way of doing it in time. But the specmech exposure commands
>> do check the screen and shutter switches and explicitly fail if they
>> are not right, so the ICC can defer to the controllers and just stuff
>> the requested positions into the headers. But the wrong test is
>> applied for bias and dark exposures, and they are incorrectly listed
>> with HARTMANN=3D"Out"
>>
>> - craig
>>
>> On Tue, Mar 16, 2010 at 12:29 PM, David Schlegel
>> wrote:
>>>
>>> Audrey (and Craig),
>>>
>>> While digging into this, I notice that the hartmanns are reported as
>>> "Out"
>>> during bias frames. =A0I think that didn't used to be the case, and
>>> something
>>> we probably don't want?
>>>
>>> -David
>>
>> _______________________________________________
>> Message 2759 of sdss3-infrastructure -
>> sdss3-infrastructure@sdss3.org
>> https://sdss3.org/mailman/listinfo/sdss3-infrastructure
>
> _______________________________________________
> Message 2763 of sdss3-infrastructure -
> sdss3-infrastructure@sdss3.org
> https://sdss3.org/mailman/listinfo/sdss3-infrastructure
>