I just want to emphasize again the point that eventually the montecarlo
should spit out 6 tgt bits + 1 (beam helicity) just as we do in the
data. The price to pay is to have two different cuts and to have
additional montecarlo and data variable in the reconstruction.
Which may not be terrible but certainly not very consistent. I
certainly hope this is the way dgen is going to evolve.
-- tancredi
________________________________________________________________________________
Tancredi Botto, phone: +1-617-253-9204 mobile: +1-978-490-4124
research scientist MIT/Bates, 21 Manning Av Middleton MA, 01949
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
On Fri, 13 Jun 2003, Adrian T Sindile wrote:
> Hi, Chi!
> I think I am able to write MC helicity and spin info to the CODA stream.
> However, to make sure the same reconstruction classes can be used in the
> same way for Chris' epel and DGen, I need to know which array element you
> use for helicity and which for target spin orientation...
>
> I am asking about the array POL(3) which is used by WRITECODAVERTEX()...
> IS POL(1) used for beam polarization (with +/- indicating the helicity)
> and POL(2) used for longitudinal target polarization (with +/- used for
> spin orientation along the holding field)? Then POL(3) would be used for
> transversal target polarization... but I do not need that for hydrogen.
>
> Please tell me if that is the convention, or if you have a different one!
> Thanks!
>
> Adrian
>
> PS: DGen will not be affected by these changes, the end result will be
> that we will have helicity and target spin info when running Chris's epel
> generator, like we have now for DGen.
>
> -------------------------------
> 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:29 EST