Hi, Chris!
Thanks for your reply...
I knew at some point we would migrate to DSTs based on trees
and people could use the complex DST structure to select event types they
are interested in - using ROOT trees for this is the way to go and that is
why I wrote my ep-cruncher this way (before the official V3 release).
Anyway, one person is only interested in one event type at a time. So I
wrote this code based on V2_96 (when V3 is released it should be easy to
migrate) as a means to do independent analysis.
People make mistakes and we already had to re-crunch runs a few times in
the past. So I think it is important for everybody doing analysis to have
a degree of control instead of relying only on a DST produced while on
shift.
Of course people can use whichever way they want (or both, in order to
doublecheck themselves for that matter) - I think it is better to have
more alternatives (it can hurt anyway).
Cheers,
Adrian
On Mon, 15 Dec 2003, Chris Crawford wrote:
> hi adrian,
> we are releasing v3 of the BlastLib2 software today, which produces a
> complex DST tree structure, which chi has done a lot of work on
> recently. the basic idea is that the DST has all of the relevant
> information from the CODA stream, as well as all of the reconstruction
> information needed to do a second pass reconstruction or create an
> arbitrary ntuple without having to redo the reconstruction.
> typically durring their analysis, people will create their own ntuples
> from the DST, since ntuples are smaller and easier to work with, ie. for
> histogramming, and this can be used as a filter for the event types you
> are analyzing (the dst contains events of 1,2,3, or more tracks).
> --chris
>
> Adrian T Sindile wrote:
>
> >Hi!
> >So far (please correct me if I am wrong) we have been crunching runs and
> >filling ntuples (which is great for preliminary analysis)...
> >I have written code for e-p analysis (can be extended to everything else)
> >to fill ROOT TTree structures. Right now my tree has only one branch, for
> >ep tracks. This branch is in fact a dynamic array (TClonesArray class from
> >ROOT)...
> >
> >The program goes through runs and produces .coda and .root files which
> >only contain ep-events.
> >The .root files can be chained together and the analysis becomes very
> >simple, based on the tree structure...
> >
> >This is work in progress but if anyone is interested please contact me...
> >
> >Adrian
> >
> >PS: Many thanks to Tong who explained the WC reconstruction details.
> >
> >-------------------------------
> >Adrian Sindile
> >Research Assistant
> >Nuclear Physics Group
> >University of New Hampshire
> >phone: (603)862-1691
> >FAX: (603)862-2998
> >email: asindile@alberti.unh.edu
> >http://einstein.unh.edu/~adrian/
> >
> >
> >
>
>
This archive was generated by hypermail 2.1.2 : Mon Feb 24 2014 - 14:07:30 EST