Subject: Re: [sloan-25mlog 2299] 2.5m obslog 20150508 (SJD 57151)
From: "John K. Parejko"
Date: Sat, 9 May 2015 13:45:57 -0400
This is odd...
On 9May 2015, at 07:44, gfreischlad@apo.nmsu.edu wrote:
> Guider failed and was restarted immediately. No apparent cause.
> 08:03:46 APO.viktorm.sop 799 guider w text=3D"Failed to take exposure"
Checking the logs, the guider failed because the gcamera exposure =
command exceeded the time limit (14s exposure + 20s overhead). The =
gcameraICC received the exposure command, but apparently didn't start =
the exposure until 18s later! I don't think I've ever seen this before.
Here's the guider waiting on and then failing the exposure:
2015-05-09 08:03:12.1783Z  'client.v128 3598 expose time=3D14.000000 =
stack=3D1\n'
2015-05-09 08:03:16.3287Z < '2 3598 i version=3D"v2_1"'
2015-05-09 08:03:23.8602Z < '2 3598 i stack=3D1'
2015-05-09 08:03:23.8606Z < '2 3598 i cameraConnected=3DTrue'
2015-05-09 08:03:23.8608Z < '2 3598 i binning=3D2,2'
2015-05-09 08:03:23.8610Z < '2 3598 i dataDir=3D/data/gcam/57151; =
nextSeqno=3D831'
2015-05-09 08:03:23.8613Z < '2 3598 i flatCartridge=3D7; =
darkFile=3D/data/gcam/57151/gimg-0001.fits.gz; =
flatFile=3D/data/gcam/57151/gimg-0785.fits.gz'
2015-05-09 08:03:23.8616Z < '2 3598 i =
cooler=3D-40.0,-40.1,4.0,45.6,1,Correcting'
2015-05-09 08:03:23.8619Z < '2 3598 i simulating=3DOff,None,1'
2015-05-09 08:03:23.8690Z < '2 3598 d text=3D"found =
flat=3D/data/gcam/57151/gimg-0785.fits.gz =
dark=3D/data/gcam/57151/gimg-0001.fits.gz cart=3D7"'
2015-05-09 08:03:23.9000Z < '2 3598 i stack=3D1'
2015-05-09 08:03:30.5182Z < '2 3598 i =
exposureState=3D"integrating",14.0,14.0'
2015-05-09 08:03:46.1497Z < '2 3598 i exposureState=3D"reading",2.0,2.0'
2015-05-09 08:03:47.7848Z < '2 3598 i text=3D"writing FITS files for =
gimg-0831.fits (3 threads)"'
2015-05-09 08:03:47.8244Z < '2 3598 i text=3D"wrote =
/data/gcam/57151/gimg-0831.fits.gz"'
2015-05-09 08:03:47.8262Z < '2 3598 : exposureState=3D"done",0.0,0.0; =
filename=3D/data/gcam/57151/gimg-0831.fits.gz'
The only thing I can guess is that the ICC took several seconds to =
confirm that the camera connection was alive. See gcameraICC: =
Commands/CameraCmd.status() and alta/altacam._expose(): if the camera is =
responding slowly, we'll get the version key, then potentially a long =
delay before the next message, as above. Similarly for the delay between =
the second 'stack=3D' and the state becoming 'integrating'.
I've added an additional warning message to the guider when the gcamera =
times out, so we can at least keep track of these timeouts. It will be =
installed next engineering, when the pointing-model updated guider is =
installed.
John
--
*************************
John Parejko
john.parejko@yale.edu
http://www.astro.yale.edu/~jp727/
203 432-9759
JWG 465
Department of Physics
Yale University
New Haven, CT
**************************