[Halld-offline] pythia-geant.map, back to basics

[Kei Moriya]

Hi Mark,

I assume this proposed change affects the geantId code that you
checked in?

Just for reference, I ran 6400 bggen runs (64M events) yesterday
and found no runs with REST not finishing, and one run with
no final REST file
(I couldn't figure out what happened from the log file).
There were 85 runs which had small file sizes, probably
due to an event failing in hdgeant or mcsmear.

At the very least we can assume that the REST not stopping
problem is solved.

In previous batch runs most of the failures I saw were from
either REST getting stuck at one event or not finishing,
which I assumed to be a database connection problem,
but that seems to be gone. One difference though is that
in previous times I used the cluster within our group,
whereas now I use the BigRed2 machine. I can run some jobs
on our cluster and see if this is a true statement.

I can start analyzing the bggen events I currently have,
or if there will be significant changes to the geantId
due to the new changes, I can wait to generate/simulate
a new batch.

	Kei

On 12/18/13 10:23 AM, Mark Ito wrote:
> Folks,
>
> I am proposing we go back to the original Eugene Chudakov version of
> pythia-geant.map (revision 3195, attached fyi) as the default in the
> bggen/run directory.
>
> This version allows all particles to be decayed in pythia except for the
> core 32 particles defined by Geant (Gamma=1 through Antiomega+=32).
> These 32 are passed on to Geant. See
> http://wwwasdoc.web.cern.ch/wwwasdoc/geant/node72.html .
>
> Note that this means:
>
> • etas and pi0s are decayed by Geant
> • eta prime, rho0, and omega0 are decayed by pythia
>
> Although rho0 and omega0 are mentioned in the file, they are decayed by
> pythia due the minus sign in their "Geant type". They are retained in
> the file as an example of how to pass a resonance onto the output file
> undecayed. My understanding is that they can be dropped completely from
> this file with no effect on the output.
>
> Why do this now? With the new decay chain reporting scheme checked in
> last week, passing to Geant exactly those particles known (by default)
> to Geant should not be a problem, in principle. If while doing a study
> one wants to know, for example, which two photons go with which pi0,
> that information is available in the HDDM now even if the decay happens
> in Geant.
>
> My plan is to check in this change in on the trunk later this week
> unless I hear objections. Sooner if people want.
>
> -- Mark
>
>
>
> _______________________________________________
> Halld-offline mailing list
> Halld-offline at jlab.org
> https://mailman.jlab.org/mailman/listinfo/halld-offline
>