- Table of contents
g4numi code consists of code to build a representation of the NuMI beamline geometry and interface it with the Geant4 physics tools. The same geometry is also used for the Flugg simulation. A simple model of incoming proton beam is used as a source of initial particles. The primary output of the this code is an ntuple representing the decays of secondaries that give rise to neutrinos.
There is a FNAL Geant4 Effort to improve the physics list used to control (mostly hadronic) interactions in order to better agree with data (e.g. NA49, NA61, etc) in physics regimes that are relevant for the NuMI beam.
Important note about entry values¶
The following are additions to the base
g4numi ntuple (
nudata). Unlike the rest of the ntuple which uses cm (for lengths) and GeV (for energies and momenta) this portion uses mm and MeV, so take care.
These hold information about the ancestor between the original proton and the neutrino. The arrays are a fixed length of 10 entries, though it is possible for the actual history chain to be longer than that (in which case it is truncated). For any one entry only the indices
min(ntrajectory-1,9) are meaningful. Elements
ntrajectory and beyond are filled with junk left over from previous entries; do not use them.
Int_t ntrajectory; Bool_t overflow; Int_t pdg; Int_t trackId; Int_t parentId; Double_t startx; Double_t starty; Double_t startz; Double_t stopx; Double_t stopy; Double_t stopz; Double_t startpx; Double_t startpy; Double_t startpz; Double_t stoppx; Double_t stoppy; Double_t stoppz; Double_t pprodpx; Double_t pprodpy; Double_t pprodpz; TString proc; TString ivol; TString fvol;