Subject: Re: [sloan-25mlog 2579] Re: 2.5m obslog 20150913 (SJD 57279) From: Elena Malanushenko Date: Mon, 14 Sep 2015 17:23:17 -0600 --Apple-Mail=_3877067F-989C-4AD7-9DA2-BE13E406DF95 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 Kaike, I will fix it tonight, it is obvious.=20 On 09 /14/ 15, at 5:21 PM, Kaike Pan wrote: >=20 >> On Sep 14, 2015, at 4:40 PM, John K. Parejko = wrote: >>=20 >> On 14Sep 2015, at 12:22, Elena Malanushenko = wrote: >>=20 >>> This output is showed the keywords values=20 >>> which are still the same after fail.=20 >>>=20 >>> I will suppress their output if the status >>> of command is failed, thank you for this point. >>=20 >> Yes, this is the correct behavior: when the command finishes with = status 'f', you should either display a "failed" message in the script, = or display nothing. Please file a ticket against the Scripts about this. >=20 > I agree. If the recent hartmann fails, the logFunction script should = just report the failure status instead of hartmann=92s output from the = previous set of hartmann.=20 >=20 > Elena, can your script tell (from the time stamps) the most recent one = just fails? If so, it seems not hard to fix the script.=20 >=20 >>=20 >>> John probably can zero hartmann keywords after we load new = cartridge,=20 >>> and zero them if command failed, or we just know how does it works.=20= >>=20 >> The keywords should not be zeroed. If you need to know whether they = were updated as part of a given command, I think that there's an opscore = function to do that. I don't recall what it is offhand (man, I wish we = had an API or at least some searchable sphinx help pages!). You can = always check if the timestamp property on a keyVar is less than some = reasonable amount (say, a minute?). >>=20 >> John >>=20 >>> On 09 /14/ 15, at 6:26 AM, viktorm@apo.nmsu.edu wrote: >>>=20 >>>> We slewed to the field, and BOSS cameras were in uncertain status = (after >>>> stopping previous exposures). >>>> SOP complained that it cannot take Hartmanns, but it reported about = moving pistons: >>>>=20 >>>> 05:05:51 Hartmann collimate output on cart #3 >>>> sp1: offset: r=3D 3628 (Out of focus); b=3D -9.3 (Out of focus)=20 >>>> sp2: offset: r=3D 1262 (Out of focus); b=3D 3.8 (In Focus)=20 >>>> sp1: pred. move: spAverageMove=3D 3292 >>>> sp2: pred. move: spAverageMove=3D 32 >>>> sp1: pred. spResiduals: r=3D 336, b=3D 1.1, txt=3D OK, spTemp =3D = 14.3 >>>> sp2: pred. spResiduals: r=3D 1229, b=3D 3.9, txt=3D OK, spTemp =3D = 27.5 >>>> 05:05:52 sop.gotoField =3D failed; =20 >>>> 05:06:19 sop.gotoField =3D running; =20 >>>> 05:06:27 Hartmann collimate output on cart #3 >>>> sp1: offset: r=3D 3628 (Out of focus); b=3D -9.3 (Out of focus)=20 >>>> sp2: offset: r=3D 1262 (Out of focus); b=3D 3.8 (In Focus)=20 >>>> sp1: pred. move: spAverageMove=3D 3292 >>>> sp2: pred. move: spAverageMove=3D 32 >>>> sp1: pred. spResiduals: r=3D 336, b=3D 1.1, txt=3D OK, spTemp =3D = 14.3 >>>> sp2: pred. spResiduals: r=3D 1229, b=3D 3.9, txt=3D OK, spTemp =3D = 27.5 >>>=20 >>> ____________________________________________________________ >>> Logs of Nightly APO Activities >>> = https://trac.sdss.org/tracmailman/browser/private/sloan-25mlog/index.html >>=20 >> -- >> ************************* >> John Parejko >> john.parejko@yale.edu >> http://www.astro.yale.edu/~jp727/ >> Department of Physics >> Yale University >> New Haven, CT >> ************************** >>=20 >>=20 >>=20 >>=20 >>=20 >>=20 >>=20 >> ____________________________________________________________ >> Logs of Nightly APO Activities >> = https://trac.sdss.org/tracmailman/browser/private/sloan-25mlog/index.html >=20 --Apple-Mail=_3877067F-989C-4AD7-9DA2-BE13E406DF95 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252 Kaike, I will fix it tonight, it is = obvious. On 09 /14/ 15, at 5:21 = PM, Kaike Pan = wrote:On = Sep 14, 2015, at 4:40 PM, John K. Parejko wrote:On 14Sep 2015, at 12:22, Elena Malanushenko = wrote:This output is showed = the keywords values which are still the same after fail. I will suppress their output if the statusof = command is failed, thank you for this point.Yes, this is the correct = behavior: when the command finishes with status 'f', you should either = display a "failed" message in the script, or display nothing. Please = file a ticket against the Scripts about this.I agree. If = the recent hartmann fails, the logFunction script should just report the = failure status instead of hartmann=92s output from the previous set of = hartmann. Elena, can your = script tell (from the time stamps) the most recent one just fails? If = so, it seems not hard to fix the script. John probably can zero = hartmann keywords after we load new cartridge, and zero = them if command failed, or we just know how does it works. The keywords should not be = zeroed. If you need to know whether they were updated as part of a given = command, I think that there's an opscore function to do that. I don't = recall what it is offhand (man, I wish we had an API or at least some = searchable sphinx help pages!). You can always check if the timestamp = property on a keyVar is less than some reasonable amount (say, a = minute?).JohnOn 09 /14/ 15, at 6:26 = AM, viktorm@apo.nmsu.edu wrote:We slewed to the field, = and BOSS cameras were in uncertain status (afterstopping = previous exposures).SOP complained that it cannot take = Hartmanns, but it reported about moving pistons:05:05:51 Hartmann collimate output on cart #3sp1: offset: r=3D 3628 (Out of focus); b=3D -9.3 (Out = of focus) sp2: offset: r=3D 1262 (Out of focus); b=3D 3.8 (In = Focus) sp1: pred. move: spAverageMove=3D 3292sp2: = pred. move: spAverageMove=3D 32sp1: pred. spResiduals: r=3D= 336, b=3D 1.1, txt=3D OK, spTemp =3D 14.3sp2: pred. = spResiduals: r=3D 1229, b=3D 3.9, txt=3D OK, spTemp =3D 27.505:05:52 sop.gotoField =3D failed; 05:06:19 sop.gotoField =3D running; 05:06:27 Hartmann collimate output on cart #3sp1: offset: r=3D 3628 (Out of focus); b=3D -9.3 (Out = of focus) sp2: offset: r=3D 1262 (Out of focus); b=3D 3.8 (In = Focus) sp1: pred. move: spAverageMove=3D 3292sp2: = pred. move: spAverageMove=3D 32sp1: pred. spResiduals: r=3D= 336, b=3D 1.1, txt=3D OK, spTemp =3D 14.3sp2: pred. = spResiduals: r=3D 1229, b=3D 3.9, txt=3D OK, spTemp =3D 27.5____________________________________________________________Logs of Nightly APO Activities https://trac.sdss.org/tracmailman/browser/private/sloan-25mlog/= index.html--*************************John Parejkojohn.parejko@yale.eduhttp://www.astro.yale.edu/~jp727/Department of PhysicsYale UniversityNew Haven, CT**************************____________________________________________________________Logs of Nightly APO Activities https://trac.sdss.org/tracmailman/browser/private/sloan-25mlog/= index.html= --Apple-Mail=_3877067F-989C-4AD7-9DA2-BE13E406DF95--