Date: Thu, 13 Feb 2014 16:40:05 -0700 (MST)
Subject: Re: [sdss3-25mlog 1632] 2.5m obslog 20140212 (MJD 56701)
From: "Daniel Oravetz"
Thanks for the clarification, John. That actually was not clear to us. We
were (mistakenly) working under the assumption that having FFS bypassed in
SOP was actually only bypassing the _status_ of the FFS (to accommodate
windy guiding), but commanded _moves_ would still get through (to continue
observing normally). In fact, wasn't the original motivation to include
the FFS bypass in SOP originally a product of windy conditions and failed
guiding?
> Just for clarity:
>
> Yes, having FFS bypassed in SOP means FFS commands from SOP don't happen
> at all. That bypass lets us, e.g., run commands that require moving the
> FFS while the dome is closed. It does mean that if you do want to move the
> FFS, you have to either clear the bypass or command the move manually via
> the mcp.
>
> I suppose a more general system for dealing with flapping FFS might be
> better than the current, rather crude, "ignore anything to do with them"
> method. I'll have to give this some thought, though, since it impacts on a
> number of different subsystems.
>
> John
>
> On 13Feb 2014, at 09:10, doravetz@apo.nmsu.edu wrote:
>
>>                       APACHE POINT OBSERVATORY SDSS 2.5M
>>
>>                                 OBSERVING LOG
>>                          Wednesday February 12, 2014
>>
>>                                  (MJD 56701)
> ...
>> When we look at the image, it doesn't look like a flat; it looks like a
>> 5-read
>> exposure of the sky, which suggests that having FFS bypassed in SOP to
>> accommodate guiding in windy conditions also prevented the FFS from
>> closing for
>> the dome flat.
>
> --
> *************************
> John Parejko
> john.parejko@yale.edu
> http://www.astro.yale.edu/~jp727/
> 203 432-9759
> JWG 465
> Department of Physics
> Yale University
> New Haven, CT
> **************************
>
>
>
>
>
>
>