Date: Thu, 24 May 2012 10:27:47 -0700 Subject: Re: [sdss3-25mlog 690] Re: 2.5m obslog 20120523 (MJD 56071) From: Stephen Bailey --e89a8f234ec103b31304c0cb929e Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hi Kaike. We monitor the results and sometimes downgrade an exposure after sunrise. We discussed automating that or formalizing the procedure, but in the end decided to just leave it as is =96 i.e. no change in procedures or platewebapp needed. The problem here was that the pipeline has additional criteria like ratio of min/max SN2 so it doesn't try to combine wildly different quality exposures. But future versions of the pipeline may make a different choice so we don't necessarily want to kill an exposure just because a much better one exists. The problem of offline vs. sos disagreeing happens so rarely that I don't think we need to worry about it. Regards, Stephen On Thu, May 24, 2012 at 10:06 AM, Kaike Pan wrote: > Hi Stephen and Kyle; > > Is there a "magic" number? Say if S/N of an exposure is below that > number, observers should not count its S/N or even declare as "bad" via > APOfix. That way, plateDB will automatically exclude it too. Thanks. > > -kaike > > > > For the record: the previous observations of 5172 were a bunch of low SN2 > exposures followed by one really good one which put it over threshold. > While this was good for SOS, the full pipeline rejected some of the low > SN2 exposures and ended up with a below-threshold final result. We had > room in the schedule for this LST, so we decided to re-observe this plate= . > i.e. the re-observation of a previously "done" plate was purposeful, not > an accident. But thanks for noticing and commenting! > > Regards, > > Stephen > > >> Cart. 17, 6026 DONE >> >> Please check the mirror for dust again. >> >> ---- Observing Log ---- >> >> _____________________________________________________ > Message 690 of sdss3-25mlog - Logs of nightly APO activities. > > https://trac.sdss3.org/tracmailman/browser/private/sdss3-25mlog/all/690.h= tml > sdss3-25mlog@sdss3.org > https://sdss3.org/mailman/listinfo/sdss3-25mlog > > > --e89a8f234ec103b31304c0cb929e Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hi Kaike.We monitor the results and sometimes dow= ngrade an exposure after sunrise. =A0We discussed automating that or formal= izing the procedure, but in the end decided to just leave it as is =96 i.e.= no change in procedures or platewebapp needed. The problem here was that the pipeline has additional criter= ia like ratio of min/max SN2 so it doesn't try to combine wildly differ= ent quality exposures. =A0But future versions of the pipeline may make a di= fferent choice so we don't necessarily want to kill an exposure just be= cause a much better one exists. =A0The problem of offline vs. sos disagreei= ng happens so rarely that I don't think we need to worry about it. Regards,StephenOn Thu, May 24, 2012 at 10:06 AM, Kaike Pan <= kpan@apo.nmsu.edu> wrote: Hi = Stephen and Kyle;=A0=A0 =A0Is there a "magic= " number? Say if S/N of an exposure =A0is below that number, observers= should not =A0count its S/N or even declare as "bad" via APOfix.=A0That way, plateDB will automatically exclude it too. Thanks.= -kaikeFor the record: the previous observations of 5172 were a bunch of low SN= 2 exposures followed by one really good one which put it over threshold. = =A0While this was good for SOS, the full pipeline rejected some of the low = SN2 exposures and ended up with a below-threshold final result. =A0We had r= oom in the schedule for this LST, so we decided to re-observe this plate. = =A0i.e. the re-observation of a previously "done" plate was purpo= seful, not an accident. =A0But thanks for noticing and commenting! Regards,Stephen=A0= =A0Cart. 17, 6026 =A0DONE Please check the mirror for dust again. ---- Observing Log ---- _____________________________________________________Message 690 of sds= s3-25mlog - Logs of nightly APO activities.https://trac.sdss3.org/tracmailman/browser/private/sdss3-25mlog/all/690= .html sdss3-25mlog@sd= ss3.orghttps://sdss3.org/mailman/listinfo/sdss3-25mlog --e89a8f234ec103b31304c0cb929e--