Difference between revisions of "Software"
From E12-11-009
Jump to navigationJump to search| Line 1: | Line 1: | ||
== Simulation Codes == | == Simulation Codes == | ||
| − | The collaboration has work space at /work/hallc/c-gen/ (accessible on the ifarm machines). Contact Brad Sawatzky <mailto:brads@jlab.org> for write access. | + | The collaboration has work space at /work/hallc/c-gen/ (accessible on the ifarm machines). |
| + | Contact Brad Sawatzky <mailto:brads@jlab.org> for write access. | ||
| + | |||
| + | === Using the JLab Farm === | ||
| + | |||
| + | * Quick Start page here: https://scicomp.jlab.org/docs/getting_started | ||
| + | |||
| + | * Environment setup information for ROOT/G4 etc is here: https://data.jlab.org/ | ||
| + | |||
| + | * Basically, run a few short test jobs on an interactive node (ie. ifarm65.jlab.org) just as you would on your desktop. | ||
| + | ** Source code and binaries can reside in your /home directory. (If space is an issue, let me know.) | ||
| + | ** Large output (*.root) files '''must''' be written to '''<code>/volatile/hallc/cgen/<your_jlab_username>/</code>''' | ||
| + | *** Note the delete policy for the /volatile file system here: https://scicomp.jlab.org/docs/volatile_disk_pool | ||
| + | *** Basically, if it's something that we want for long term, then you must push it to tape and access it through the /cache filesystem.) | ||
| + | |||
| + | * Once the code is working, then generate a control script for a batch job and submit it using 'jsub': https://scicomp.jlab.org/docs/jsub | ||
| + | ** There are a number of examples here: https://scicomp.jlab.org/docs/auger_examples | ||
| + | ** A few parameters you'll need are: | ||
| + | PROJECT : cgen | ||
| + | TRACK : simulation | ||
| + | OS : centos65 | ||
| + | |||
| + | * Note the best practices / FAQ here: https://scicomp.jlab.org/docs/batch_job_faq | ||
| + | |||
| + | * Watch jobs in the queue here: http://scicomp.jlab.org/scicomp/#/auger/jobs | ||
| + | |||
| + | * Large file transfers to/from your institution work well with Globus: https://scicomp.jlab.org/docs/node/23 | ||
| + | ** You can set up a local 'endpoint' on your machine and this system can take care of shuffling large files around, retrying if needed, synchronizing directories, etc. ('scp' works too, of course.) | ||
=== GEANT4 Simulation === | === GEANT4 Simulation === | ||
Revision as of 10:05, 7 October 2015
Simulation Codes
The collaboration has work space at /work/hallc/c-gen/ (accessible on the ifarm machines). Contact Brad Sawatzky <mailto:brads@jlab.org> for write access.
Using the JLab Farm
- Quick Start page here: https://scicomp.jlab.org/docs/getting_started
- Environment setup information for ROOT/G4 etc is here: https://data.jlab.org/
- Basically, run a few short test jobs on an interactive node (ie. ifarm65.jlab.org) just as you would on your desktop.
- Source code and binaries can reside in your /home directory. (If space is an issue, let me know.)
- Large output (*.root) files must be written to
/volatile/hallc/cgen/<your_jlab_username>/- Note the delete policy for the /volatile file system here: https://scicomp.jlab.org/docs/volatile_disk_pool
- Basically, if it's something that we want for long term, then you must push it to tape and access it through the /cache filesystem.)
- Once the code is working, then generate a control script for a batch job and submit it using 'jsub': https://scicomp.jlab.org/docs/jsub
- There are a number of examples here: https://scicomp.jlab.org/docs/auger_examples
- A few parameters you'll need are:
PROJECT : cgen TRACK : simulation OS : centos65
- Note the best practices / FAQ here: https://scicomp.jlab.org/docs/batch_job_faq
- Watch jobs in the queue here: http://scicomp.jlab.org/scicomp/#/auger/jobs
- Large file transfers to/from your institution work well with Globus: https://scicomp.jlab.org/docs/node/23
- You can set up a local 'endpoint' on your machine and this system can take care of shuffling large files around, retrying if needed, synchronizing directories, etc. ('scp' works too, of course.)
GEANT4 Simulation
[NMU-NPOL]: (Github) GEANT4 model developed by W. Tireman et al. (NMU)
- Some discussion of this code may be found in this [talk]
FLUKA + MCEEP
- Andrei Semenov (U of Regina) has a simulation using Fluka 2011.2.9 + MCEEP-generated neutrons. Contact Andrei for details.
JLab
- Pavel Degtiarenko (JLab) was contacted in Sep 2014 regarding any local codes that might be useful. Unfortunately nothing really suitable is available at the moment. The old GEANT3 model is still used for dose related calculations. A planned G4 model has (tentatively) been replaced by a future FLUKA model -- neither is in a useful form yet.
