Subject: Re: [sdss3-25mlog 1507] Re: 2.5m obslog 20131202 (MJD 56629)
From: Karen Kinemuchi
Date: Tue, 3 Dec 2013 13:21:45 -0700
On Dec 3, 2013, at 12:29 PM, John K. Parejko wrote:
> On 3Dec 2013, at 07:59, marchante@apo.nmsu.edu wrote:
>=20
>>                                OBSERVING LOG
>>                         Monday December 02, 2013
>>=20
>>                                 (MJD 56629)
>> ...
>> Had an issue with sos not getting updated, at 14 minutes in to next =
exposure,
>> had to use poke.py to push 170441 info to sos.=20
>=20
> What do you mean "poke.py"? Are you referring to NFS_poke.py? That's =
still running, and I would be very surprised if starting a new one would =
make any difference.
>=20
Yes, we ran NFS_poke.py on boss-icc.  We cntl-c'd out of script we =
started when we were closing up shop in the morning.  We did not notice =
any other sos delays in posting the BOSS data after this incident.
> How long after you ran it did it take for SoS to see the exposure?
>=20
The files appeared on the sos webpage immediately after this script was =
run.  To make sure, we also ran plate3 on the plate and the exposure =
registered. We also checked hub25m and the files were all there before =
we did anything.