[d2n-analysis-talk] transversity db tracking

[Brad Sawatzky]

On Fri, 16 Jul 2010, posik at jlab.org wrote:

>    I just remembered that about a month ago I did a diff on our d2n
> bigbitelib and the transversity bigbitelib, and there were more than
> just shower classes that were different between the two. There were
> some optics and a projection file that were different as well. Since I
> used the transversity bigbitelib for my replay and both of those files
> (optics and projection) would affect the reconstructed tracks, this may
> be the reason for the increase in tracks.
> 
> Below I attached the diff that was carried out, diff.txt just lists the
> differing files and the tar file has a full description of the
> differences.

Quite a few changes there.  Some look trivial, others I don't understand
based on a quick look.

It would be good to switch to the updated Transversity library, but we
can not do it blindly -- please check the Transversity CVS logs and see
why the changes were made (check with Ole or Jin if you're not sure what
commands to use).  In addition to the usual DB compatibility issues (are
there any?), I worry about introducing some subtle Transversity-only
tweak into our analysis.

If the change summary for the code makes sense, and you (and/or Diana,
etc) can demonstrate that the new code works better then the old code,
then we can push it out to the default analyzer when I get back in a
couple of weeks.

-- Brad

-- 
Brad Sawatzky, PhD <brads at jlab.org>  -<>-  Jefferson Lab / Hall C / C111
Ph: 757-269-5947  -<>-  Fax: 757-269-5235  -<>- Pager: brads-page at jlab.org
The most exciting phrase to hear in science, the one that heralds new
  discoveries, is not "Eureka!" but "That's funny..."   -- Isaac Asimov