Subject: Re: [infrastructure 14173] Re: [sloan-25mlog 2936] 2.5m obslog 20160419 (SJD 57498): Right hartmann door issue on SP2?
From: Kai Zhang
Date: Wed, 20 Apr 2016 11:12:03 -0400
Hi Kaike, all,
    It is strange that this only happens to Cart6. Sorry I can not =
contribute much to this problem, if you need me to do something, let me =
know. Could you please take a hartmann for Cart6 this afternoon when it =
is plugged today to see if the problem still exists? If the problem does =
not go away then we need to be cautious not using it in the next dark =
run.=20
     Best~
                                              Kai
> =D4=DA 2016=C4=EA4=D4=C220=C8=D5=A3=AC=C9=CF=CE=E710:40=A3=ACKaike Pan =
 =D0=B4=B5=C0=A3=BA
>=20
> Hello All,
>=20
>    When I checked (quick) hartmann data on cartridge 6, I noticed
> that there are only very weak lines (100 count above bias level) in =
the
> upper readout windows for in red cameras while the lower window has
> many strong lines. I am wondering whether lines in the upper window =
are
> strong enough.=20
>=20
>  Information on the hartmann data:=20
>   Three pairs of hartmann: 219483-84, 219485-86, 219487-88
> were taken on the plate.=20
>=20
>  lines are in 219483 on all four cameras, but only on SP1 cameras, not
> appears on frames for SP2 in the frame of 219484. Fits header =
indicated
> all lamps are on. Since SP1 frames are good, I assume that lamps are
> really on.
>=20
> No lines in in the second exposure for SP2. The same as the first =
pair.
>=20
> The third pair is a full hartmann exposures. No lines in the 2nd =
frames for SP2.
>=20
> So, right hartmann exposures on all three pairs don=A1=AFt have lines. =
It looks to me
> a right hartmann door issue.
>=20
> However, I ran another hartmann pair on cart 14, 219512-13, everything =
is=20
> fine.=20
>=20
>   If you need more information on this, please let me know. Thanks,
>=20
>  -kaike
>=20
>=20
>>=20
>> Notes:
>>=20
>> On Cartridge 6, there was no light in the hartmanns for SP2. We ran =
GoToField
>> twice, and tried sop collimateBoss with the same results. The log =
window also
>> had an error of "Failure from sp2mech: Failed Hartmann screen move =
timed out",
>> with more information in the Problems section. We were unable to find =
the cause
>> or solution, as this was APOGEE-led and the final cartridge of the =
night.=20
>>=20
>>=20
>> 10:53:04  loadCart: ct=3D6, pl=3D8631;
>> 10:53:04 survey: APOGEE-2&MaNGA;  lead: APOGEE lead
>>=20
>> 10:54:17  sop.gotoField =3D running; =20
>> 10:55:34  sp1.motor.move=3D 0, 0, -1
>> 10:55:34  sp2.motor.move=3D 0, -1, 0
>>=20
>> 10:55:43  boss exposure    4.0, file=3D219483, C
>> 10:56:23  boss exposure    4.0, file=3D219484, C
>>=20
>> 10:57:05 Hartmann collimate output on cart #6
>> Hartmann failed
>>  sp1: offset: r=3D 1649 (Out of focus);  b=3D -4.2 (Out of focus)=20
>>  sp2: offset: r=3D ? (?);  b=3D ? (?)=20
>>  sp1: pred. move: spAverageMove=3D ?
>>  sp2: pred. move: spAverageMove=3D ?
>>  sp1: pred. resid: r=3D ?, b=3D ?, txt=3D ?, spTemp =3D 6.3
>>  sp2: pred. resid: r=3D ?, b=3D ?, txt=3D ?, spTemp =3D 5.7
>> 10:57:06  sop.gotoField =3D failed; =20
>> 10:58:19  sop.gotoField =3D running; =20
>> 10:59:03  boss exposure    4.0, file=3D219485, C
>> 10:59:44  boss exposure    4.0, file=3D219486, C
>>=20
>> 11:00:25 Hartmann collimate output on cart #6
>> Hartmann failed
>>  sp1: offset: r=3D 1649 (Out of focus);  b=3D -4.2 (Out of focus)=20
>>  sp2: offset: r=3D ? (?);  b=3D ? (?)=20
>>  sp1: pred. move: spAverageMove=3D ?
>>  sp2: pred. move: spAverageMove=3D ?
>>  sp1: pred. resid: r=3D ?, b=3D ?, txt=3D ?, spTemp =3D 6.2
>>  sp2: pred. resid: r=3D ?, b=3D ?, txt=3D ?, spTemp =3D 5.7
>> 11:00:25  sop.gotoField =3D failed;=20
>>=20
>> 11:03:39  boss exposure    4.0, file=3D219487, C
>> 11:04:52  boss exposure    4.0, file=3D219488, C
>>=20
>> Tried sop collimateBoss instead of using SOP GoToField.
>> 11:06:14 Hartmann collimate output on cart #6
>> Hartmann failed
>>  sp1: offset: r=3D 1649 (Out of focus);  b=3D -4.2 (Out of focus)=20
>>  sp2: offset: r=3D ? (?);  b=3D ? (?)=20
>>  sp1: pred. move: spAverageMove=3D ?
>>  sp2: pred. move: spAverageMove=3D ?
>>  sp1: pred. resid: r=3D ?, b=3D ?, txt=3D ?, spTemp =3D 6.2
>>  sp2: pred. resid: r=3D ?, b=3D ?, txt=3D ?, spTemp =3D 5.7
>=20
>=20
> ____________________________________________________________
> Common APO Hardware and Software
> =
https://trac.sdss.org/tracmailman/browser/private/infrastructure/index.htm=
l