Date: Wed, 30 Nov 2022 15:10:46 -0700
Subject: Re: [sloan-25mlog 6375] 2.5m obslog 20221128 (SJD 59912)
From: "Daniel Oravetz"
> 2. I thought there are always data in the netburner. After she reloaded
> the
>> controller, Audrey tried to recover the exposure with "boss exposure
>> recover”, but  got an “No exposure to act on” error. Any thought
>> on this.
>> ====
>> 10:19:12 CmdStarted: APO.aoravetz_2 80 boss exposure recover
>> 10:19:13 APO.aoravetz_2 80 boss f text="No exposure to act on."
>> 10:19:13 CmdDone: APO.aoravetz_2 80 boss exposure recover
>> ========
>>
>
> I'm not totally sure, the logic in the code has never been totally clear
> to
> me and I would need to do a deep dive. But I think if you abort the
> exposure exposure recover won't work?
If "abort" means that a 'boss exposure abort' were to get issued, then
that changes the exposureState to ABORTED, but it's still able to be read
with a 'boss exposure readout' command. But when exposureState is stuck on
"READING 0.0" that should be when the 'boss exposure recover' command
works. I don't remember how nit-picky the 'boss exposure recover' command
is in terms of what state it expects for exposureState, but I do know that
the 'boss exposure readout' command looks for either a LEGIBLE or ABORTED
exposureState.
Of course if "abort" carries some context besides just referring to
exposureState=ABORTED, then that probably means the exposure would be
altogether lost, but since we've seen that error message before and been
able to recover, I don't think "abort" means that it flushes whatever was
in the DAQ.