From: "Donor, John" Subject: Re: [sloan-25mlog 6104] 2.5m obslog 20220603 (SJD 59734) Date: Sat, 4 Jun 2022 18:56:20 +0000 --_000_a2badb76f9be42d282fb65ee87da99f1emailandroidcom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Got it. Makes perfect sense. Thanks for clarifying! On Jun 4, 2022 1:53 PM, Karen Kinemuchi wrote: [EXTERNAL EMAIL WARNING] DO NOT CLICK LINKS or open attachments unless you = recognize the sender and know the content is safe. John, We made an executive decision on Field 104552 was not going to be finished = with being over airmass 1.6 at the time. Kronos showed us we had two more = designs for this field, but not enough observability window to finish it. = With variable seeing and orographic clouds coming in, and being over HA=3D+= 4, it was difficult to finish. R1 was collecting signal much slower than B1= , and we did sit on one design for over an hour. If it was clear, we would = have finished it. We decided to cut our losses and get the other fields th= at had better observability windows by refreshing the queue again (which re= moved this field). We figured it would be strategically better to try to finish 104552 the fol= lowing night at a better hour angle/airmass, and hopefully, conditions. Ho= wever, we are expecting another smoke event, so no guarantees. So in this case, Kronos does not tell us what to do. The sky conditions te= ll us what to do! Regards, Karen On Jun 4, 2022, at 12:23 PM, Donor, John > wrote: Looks like I'm still working out edge cases on these "early completion" req= uirements we've been tweaking. I've fixed that. I think that last design probably needs another exposure? epoch sn2_r is 16= .7 and sn2_b is 9.3. That's 90% complete for blue but only ~83% for red. I = can easily mark the last design incomplete so it get's picked up tonight. Karen what happened on 104552? It looks like y'all did the first 2 designs = then moved on to 101002 and did the first design there? Why not keep going = on 104552? Did kronos tell you to only do 2 designs on that field? -John --_000_a2badb76f9be42d282fb65ee87da99f1emailandroidcom_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Got it. Makes perfect sense. Thanks for clarifying! On Jun 4, 2022 1:53 PM, Karen Kinemuchi wrote: [EXTERNAL EMAIL WARNING= ] DO NOT CLICK LINKS or open attachments unless you recognize= the sender and know the content is safe. John, We made an executive decision on Field 104552 was not going to be fini= shed with being over airmass 1.6 at the time. Kronos showed us we had= two more designs for this field, but not enough observability window to finish it. With variable seeing and orograph= ic clouds coming in, and being over HA=3D+4, it was difficult to finish= . R1 was collecting signal much slower than B1, and we did sit on one desig= n for over an hour. If it was clear, we would have finished it. We decided to cut our losses and get the other fie= lds that had better observability windows by refreshing the queue again (wh= ich removed this field). We figured it would be strategically better to try to finish 104552 th= e following night at a better hour angle/airmass, and hopefully, conditions= . However, we are expecting another smoke event, so no guarantees. So in this case, Kronos does not tell us what to do. The sky con= ditions tell us what to do! Regards, Karen On Jun 4, 2022, at 12:23 PM, Donor, John wrote: Looks like I'm = still working out edge cases on these "early completion" requirem= ents we've been tweaking. I've fixed that. I think that la= st design probably needs another exposure? epoch sn2_r is 16.7 and sn2_b is= 9.3. That's 90% complete for blue but only ~83% for red. I can easily mark= the last design incomplete so it get's picked up tonight. Karen what happ= ened on 104552? It looks like y'all did the first 2 designs then moved on t= o 101002 and did the first design there? Why not keep going on 104552? Did = kronos tell you to only do 2 designs on that field? -John --_000_a2badb76f9be42d282fb65ee87da99f1emailandroidcom_--