Subject: Re: [sdss3-25mlog 1115] 2.5m obslog 20130312 (MJD 56364)
From: Kaike Pan
Date: Wed, 13 Mar 2013 09:47:17 -0600
Hi John,
  I added one step in my recovery procedure  for the netBurn problem on =
"observing tip" page,
1. After "boss reloadControllers controllers"  we added:=20
"2. boss ping      (make sure that all controllers are there: cam, daq, =
mech, total 6 OKs there)"
Hope this will help. Should be add the same step for the procedure in =
changeNote page. BTW,
we have "boss reloadControllers" instead "boss reloadControllers =
controllers", do both function the same?
Thanks,
-kaike
On Mar 13, 2013, at 7:16 AM, viktorm@apo.nmsu.edu wrote:
>=20
>                       APACHE POINT OBSERVATORY SDSS 2.5M
>=20
>                                 OBSERVING LOG
>                          Tuesday March 12, 2013
>=20
>                                  (MJD 56364)
>=20
> ----  Observing Team ----
>=20
> Karen Kinemuchi
> Viktor Malanushenko
> Elena Malanushenko (afternoon)
> John Parejko (by phone)
>=20
> ---- Observing Plan ----
>=20
> 12 Mar 2013  56364.0  0.10  02:17 12:08  06:37 16:30  BOSS  9.9 hours
>=20
>=20
> ---- Observing Summary ----
>=20
> Clear sky all the night; good seeing.
> We lost 1 hour at the Netburner problem.=20
>=20
> ct=3D10, pl=3D5724 DONE
> ct=3D11, pl=3D6662 DONE
> ct=3D12, pl=3D6649 DONE
> ct=3D13, pl=3D6441 DONE
> ct=3D14, pl=3D6479 DONE
> ct=3D15, pl=3D6488 DONE
> ct=3D16, pl=3D6622 not DONE=20
> We had troubles with the third exposures (see remarks at the end of =
section and
> in to Log section).=20
> So, we have question to Kyle:=20
> Is it need of third exposure? - i.e. we had two exposure with enough =
S/N.
> ct=3D17, pl=3D6631 DONE
>=20
> APOGEE
> ct=3D4, pl=3D6094,  sd=3DA;  1xABBA
> --------------------
> As Jon requested, I took a look at the arc from the evening cals from =
last night
> and this evening (Jon requested we run APOGEE evening cals at 04:10Z). =
=20
>=20
> The 4 arc files from MJD 56363 are 08010005, 08010006, 08010007, =
08010008.
> The 4 arc files from MJD 56364 are 08020030, 08020031, 08020032, =
08020033.
>=20
> Doing a 1-to-1 comparison of each arc (e.g. 08010005 to 08020030) I =
find:
>=20
> 08010005 to 08020030:  0 pix shift of arc lines.
> 08010006 to 08020031: 0.76 pix shift
> 08010007 to 08020032: 0.76 pix shift
> 08010008 to 08020033: 0 pix shift
>=20
> I used the files found on hub25m, under directory =
/data/apogee/utr_cdr/56363,
> 56364  and just displayed the images with ds9.  After registering the =
frames, I
> did a blink comparison and compared the pixel values for one of the =
arc line's
> locations on each paired image.
>=20
> The pixel offsets appear to be reasonable, so as Jon requested, we =
will try
> twilight observations and do APOGEE morning cals.  If anything looks =
weird, we
> will stop and report in the night log what happened.
>=20
> -------------------
>=20
> At 10:24Z, we received an error:
>=20
> 10:23:28 APO.karen.sop 995 boss w text=3D"Readout timeout expired, =
aborting
> exposure."
> 10:24:00 APO.karen 149 sop w text=3D"1 tasks failed to respond: boss"
> 10:24:00 APO.karen 149 sop f text=3D"Failed to take science exposure"
> 10:24:00 CmdDone: APO.karen 149 sop doScience nExp=3D3 expTime=3D900.0
>=20
> And noted that in the BOSS instrument window, the readout bar was =
hung.
>=20
> I followed the procedure described on the Change Notes:
>=20
> reloadControllers controllers
>=20
> but I received an error:
> 10:24:24 APO.karen 152 hub f NoTarget=3D"the target named =
reloadControllers
> is not connected"
>=20
> I issued it once more, but this time copying the command directly from =
the
> website, and received the same error.
>=20
> It turns out this command was missing the name of the actor (boss).
>=20
> I issued the next three commands, which executed fine, and a bias was
> taken at the end.  However, the readout hung on this test image.
>=20
> We called John Parejko, as instructed on Change Notes, at 10:30Z
>=20
> John found the error with the reloadControllers controllers command on
> Change Notes and fixed it, and investigated whether we recovered the =
last
> BOSS image (file 158020), but found that b2/r2 did not copy over.
>=20
> Copies of the test bias did come through, and they are marked as test =
on
> sos under Cart 16 and 17.  (files 158021, 158022, 158023)
>=20
> We did a final bias test (file 158024) and visually inspected them -
> looked like a bias.  We issued a goToField command and commenced =
taking
> data for Cart 17.
>=20
>=20