Difference: GENIE (10 vs. 11)

Revision 112021-04-20 - WilliamSeligman

Line: 1 to 1
 
META TOPICPARENT name="WilliamSeligman"

Running GENIE at Nevis

To run the GENIE Neutrino Monte Carlo at Nevis, you can take one of two approaches:

Deleted:
<
<
  • Access the version maintained at Fermilab.
 
  • Use a software suite (GENIE and its external packages) installed at Nevis by WilliamSeligman.
Added:
>
>
  • Access the version maintained at Fermilab.
  I recommend against trying to install it on your laptop or in your own work area on the cluster; GENIE requires quite a few external packages, is finicky about those packages' versions, and the complete build/installation process has a number of pitfalls. Even the supposedly pre-configured lamp scripts, which are supposed to install all of GENIE's dependencies for you, do not work reliably.
Line: 76 to 76
 

What's next?

Added:
>
>
The output of gevgen and related applications is a ROOT file that can only be conveniently read using another GENIE application. To convert that output file into a form that can be read by a non-GENIE program, you probably want to use gntpc. In this example, the output will be a "gtrac" file that can be read using ROOT without involving GENIE load libraries:

gntpc -i gntp.inuke.0.ghep.root -f rootracker

gntpc is described on page 147 of the manual.

 As described in the GENIE manual, to turn various models on/off you need to generate new spline files. The program for doing that is gmkspl, described on page 103 of the manual. You'll want to copy the directory $GENIE/config/ to your work area, then copy and edit file EventGeneratorListAssembler.xml; that revised file will become an input list to gmkspl. An possible example (νμ on Ar40, up to 10 GeV):
gmkspl -p 14 -t 1000180400 -e 10 \

Line: 83 to 91
  --output-cross-sections my-splines.xml
Deleted:
<
<
Note that gmkspl typically takes several hours to run.
 \ No newline at end of file
Added:
>
>
Note that gmkspl typically takes several hours to run. You may want to learn about the tmux command for interactive sessions that won't be killed if your connection is lost.
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2022 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback