hi adrian,
you're right. you'll have to deal with that by hand for the time
being. epel is about to be swallowed up by DGen, which already handles
this, so i don't plan on adding this feature to epel.
--chris
Adrian T Sindile wrote:
>Hi!
>I ran Chris' polarized e-p generator (with version 3 blastmc) for 400K
>events like the following:
>
>100K: kine 10 0.85 85. 25. 25. -25. 0.7 0.55 45.
>100K: kine 10 0.85 85. 25. 25. -25. -0.7 0.55 45.
>100K: kine 10 0.85 85. 25. 25. -25. 0.7 -0.55 45.
>100K: kine 10 0.85 85. 25. 25. -25. -0.7 -0.55 45.
>
>Is that the way to run it for +/-70% beam polarization and +/-55% target
>polarization (flipping the helicity and target)? I assumed this was
>correct, but please tell me if I did it wrong.
>Anyway, crunching the .coda files with two versions of lrn.C (using
>BlastLib2 version 2) did not give me any helicity or target information.
>Detector information was fine.
>
>Does anyone have any idea what is wrong and how this could be fixed
>(detailed, step-by-step and to the point explanations welcome)?
>I think it would be useful to set up an MC asymmetry analysis, to see how
>our latest codes behave in an ideal world before we do that with real
>data...
>Thanks!
>
>Adrian
>
>-------------------------------
>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