From: Alexander Conley (AJConley@lbl.gov)
Date: Thu Sep 16 2004 - 21:07:52 PDT
This isn't a snminuit problem. It was a read hamuy problem. The
issue is that read_hamuy was producing two lightcurve files
(one for B and one for V) where the dates were not on the same
scale. That is, the input to the snmin fit was wrong, and so the fit
was wrong. There is no ambiguity in this -- you can look at the
actual corrlight files that snmin was reading and they don't
correspond to the correct lightcurve.
On Sep 16, 2004, at 5:33 PM, Don Groom wrote:
>
> "Example: 92ae. The brightest B point occured on date 8807.82, and
> the brightest V point on 8805.83. These were both considered to occur
> at date 0 when the joint fit was done, and so the V maximum was
> computed incorrectly."
>
> Maybe I misunderstand you, but I don't think that's quite right.
> snminuit
> of its day gave the first lightcurve priority and treated the 2nd as
> 2nd.
> (Most of the I data were crappy, hence the rationale). Of course, you
> could tell the code about them in either order; it was color blind.
>
> But then for a *dual* fit, the time came from the first in line, and
> the
> 2nd used it. The code understood only that there were a few more
> parameters, and treated t0 and s as common to both curves.
>
> D
>
> --
> |-+|-+|-+|-+|-+|-+|-+|-+|-+|-+|-+|-+|-+|-+|-+|-+|-+|-+|-+|-+|-+|-+|-
> +|-+|
> Don Groom (Particle Data Group, Supernova Cosmology Project)
> DEGroom(at)lbl(dot)gov www-ccd.lbl.gov 510/486-6788 FAX: 510/486-4799
> Analog: 50R6008//1 Cyclotron Road//Berkeley Lab//Berkeley, CA
> 94720-8166
>
>
This archive was generated by hypermail 2.1.4 : Thu Sep 16 2004 - 21:09:49 PDT