From: "Donor, John" Subject: Re: [sloan-25mlog 6998] Re: 2.5m obslog 20240109 (SJD 60319) Date: Wed, 10 Jan 2024 17:45:00 +0000 --_000_PH7PR16MB5216427DF9017C1F6B3DC3A5FE692PH7PR16MB5216namp_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable That's quite reasonable. It looks like 3 designs for that field will be sch= eduled for tonight; I'll leave that be then. Conner: please use those three designs to finish the epoch. The tally on th= e field's detail page, and plan observing, should be correct. Bug me if any= thing seems off. Thanks, John ________________________________ From: Morrison, Sean Stephen Sent: Wednesday, January 10, 2024 11:40 AM To: Donor, John ; Daniel Oravetz ; = cscoresby@apo.nmsu.edu ; jonathan.trump@uconn.edu Cc: obs-report-25m@apo.nmsu.edu Subject: Re: [sloan-25mlog 6998] Re: 2.5m obslog 20240109 (SJD 60319) [EXTERNAL EMAIL WARNING] DO NOT CLICK LINKS or open attachments unless you = recognize the sender and know the content is safe. Hey All, The code for coadding an epoch in the BOSS pipeline uses the "max_length" f= rom the database, so I would prefer to not break that epoch length. Sean ________________________________ From: Donor, John Sent: Wednesday, January 10, 2024 11:32 AM To: Daniel Oravetz ; cscoresby@apo.nmsu.edu ; Morrison, Sean Stephen ; jonathan.= trump@uconn.edu Cc: obs-report-25m@apo.nmsu.edu Subject: Re: [sloan-25mlog 6998] Re: 2.5m obslog 20240109 (SJD 60319) This is basically correct. The epoch is allowed 2.5 days to complete. I hav= e scripts that clean up partial epochs that don't complete in this time, on= e runs in the morning and one in the afternoon to try to clear up everythin= g be ready for a queue to be generated for that night. Technically the difference between last night's exposures and the first nig= ht's is ~3.1 days. So something just barely got missed on the automatic scr= ipts I guess? Or possibly the queue I generated in the morning for ZTF was = never refreshed in the afternoon. I probably should have been more careful = about that; that's probably what happened. Anyway, if 3.1 days is ok I'll mark the last design complete and this epoc= h will be done. CC Jon and Sean. Otherwise we can try to get some more sign= al tonight. Thanks, John ________________________________ From: sloan-25mlog on behalf of Daniel Orav= etz Sent: Wednesday, January 10, 2024 9:41 AM To: cscoresby@apo.nmsu.edu Cc: obs-report-25m@apo.nmsu.edu Subject: [sloan-25mlog 6998] Re: 2.5m obslog 20240109 (SJD 60319) [EXTERNAL EMAIL WARNING] DO NOT CLICK LINKS or open attachments unless you = recognize the sender and know the content is safe. Hi Conner, > 1. Field 112361 (dark_rm) started a new epoch tonight but KRONOS queued > only 4 designs. These designs were completed then continued with next > queued designs. Good eye noticing the full suite of designs wasn't scheduled. I think in this case it was deliberate and makes sense, though: RM is allowed 3 days for the max epoch length and field 112361 had been observed on 60316, reaching ~75% completion that night, so last night's (60319) scheduling of only 4 designs was intended to finish-off the remaining ~25% for the epoch that started on 60316. Dan ____________________________________________________________ Logs of Nightly APO Activities https://urldefense.com/v3/__https://trac.sdss.org/tracmailman/browser/priva= te/sloan-25mlog/index.html__;!!K6Z8K8YTIA!HavBgus919ioV1kBnwb01fvNP61GojyH2= aH6vja4SrQrFwg8ghwfXy0RDAU2WqPG2oWr1lccRZIFx7xLNdYK$ --_000_PH7PR16MB5216427DF9017C1F6B3DC3A5FE692PH7PR16MB5216namp_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable P {margin-top:0;margin-bo= ttom:0;} That's quite reasonable. It looks like 3 designs for that field will be sch= eduled for tonight; I'll leave that be then. Conner: please use those three designs to finish the epoch. The tally on th= e field's detail page, and plan observing, should be correct. Bug me if any= thing seems off. Thanks, John From: Morrison, Sean Stephe= n Sent: Wednesday, January 10, 2024 11:40 AM To: Donor, John ; Daniel Oravetz ; cscoresby@apo.nmsu.edu ; j= onathan.trump@uconn.edu Cc: obs-report-25m@apo.nmsu.edu Subject: Re: [sloan-25mlog 6998] Re: 2.5m obslog 20240109 (SJD 60319= ) [EXTERNAL EMAIL WARNING= ] DO NOT CLICK LINKS or open attachments unless you recognize= the sender and know the content is safe. Hey All, The code for coadding an epoch in the BOSS pipeline uses the "max_leng= th" from the database, so I would prefer to not break that epoch lengt= h. Sean From: Donor, John Sent: Wednesday, January 10, 2024 11:32 AM To: Daniel Oravetz ; cscoresby@apo.nmsu= .edu ; Morrison, Sean Stephen ; jonathan.trump@uconn.edu Cc: obs-report-25m@apo.nmsu.edu Subject: Re: [sloan-25mlog 6998] Re: 2.5m obslog 20240109 (SJD 60319= ) This is basically correct. The epoch is allowed 2.5 days to complete. I hav= e scripts that clean up partial epochs that don't complete in this time, on= e runs in the morning and one in the afternoon to try to clear up everythin= g be ready for a queue to be generated for that night. Technically the difference between last night's exposures and the first nig= ht's is ~3.1 days. So something just barely got missed on the automatic scr= ipts I guess? Or possibly the queue I generated in the morning for ZTF was = never refreshed in the afternoon. I probably should have been more careful about that; that's probably what = happened. Anyway, if 3.1 days is ok I'll mark the last design complete and this= epoch will be done. CC Jon and Sean. Otherwise we can try to get some more= signal tonight. Thanks, John From: sloan-25mlog <= sloan-25mlog-bounces@sdss.org> on behalf of Daniel Oravetz Sent: Wednesday, January 10, 2024 9:41 AM To: cscoresby@apo.nmsu.edu Cc: obs-report-25m@apo.nmsu.edu Subject: [sloan-25mlog 6998] Re: 2.5m obslog 20240109 (SJD 60319) [EXTERNAL EMAIL WARNING] DO NOT CLICK LINKS or= open attachments unless you recognize the sender and know the content is s= afe. Hi Conner, > 1. Field 112361 (dark_rm) started a new epoch tonight but KRONOS queue= d > only 4 designs. These designs were completed then continued with next > queued designs. Good eye noticing the full suite of designs wasn't scheduled. I think in this case it was deliberate and makes sense, though: RM is allowed 3 days for the max epoch length and field 112361 had been observed on 60316, reaching ~75% completion that night, so last night's (60319) scheduling of only 4 designs was intended to finish-off the remaining ~25% for the epoch that started on 60316. Dan ____________________________________________________________ Logs of Nightly APO Activities https://ur= ldefense.com/v3/__https://trac.sdss.org/tracmailman/browser/private/sloan-2= 5mlog/index.html__;!!K6Z8K8YTIA!HavBgus919ioV1kBnwb01fvNP61GojyH2aH6vja4SrQ= rFwg8ghwfXy0RDAU2WqPG2oWr1lccRZIFx7xLNdYK$ --_000_PH7PR16MB5216427DF9017C1F6B3DC3A5FE692PH7PR16MB5216namp_--