From: Alex Conley (aconley@panisse.lbl.gov)
Date: Tue May 13 2003 - 09:32:25 PDT
Hi Greg,
The roblight file is in error. Somebody mistakenly called the JKT
images INT when they loaded them into the database. Luckily, because
of the 'local standard star' step of the analysis, this doesn't matter
much (the only error induced is that the same extinction term was
incorrectly used for the JKT and the INT, but since they are at the same
observatory it should be pretty good). So Rob's table is correct.
Here is my previous email on the subject:
http://panisse.lbl.gov/collab/archive/hstpaper/0257.html
>If nobody else wants to do it have Conley do it indeed!
>
>The situation is actually a bit complicated because apparently there was
>an error in the loading, and we have multiple telescopes labelled int.
>
>Some refer to the INT 2.5m with the WFC (Wide Field Camera) and some
>to the 1.0m Jacobus Kapteyn Telescope (JKT), again using the WFC.
>
>I hope you didn't use the same zero point for both sets...
>
>Here is the breakdown
>
>Jan 4th : 2.5m
>Jan 5th : 2.5m
>Jan 21st : 1m JKT
>Jan 22nd : 1m JKT
Alex
On Tue, 13 May 2003, Greg Aldering wrote:
>
> Hi Rob,
>
> I looked at the roblight file for SN1997ek/97226 and determined that
> the "JKT" telescope entries in Table 15 should really be "INT". Also,
> tracker confirms that SN1997ek/97226 was not observed with the JKT.
> (Interestingly, tracker does find WHT images for this SN, which are not
> in the lightcurve table - there is probably some good reason for that.)
> Other SNe also claim JKT observations - those claims must also be
> checked. I assume that you have some code that is performing a
> translation to telescope names, so that could be a source of the
> problem (although other INT entries appear to be correct).
>
> If none of the "JKT" entries ends up being real, then the telescope
> key on page 39 will have to be updated.
>
> - Greg
>
This archive was generated by hypermail 2.1.4 : Tue May 13 2003 - 09:32:26 PDT