Versions Compared

Old Version 2

changes.mady.by.user Kenichi Nakano

Saved on

compared with

New Version 3

changes.mady.by.user Kenichi Nakano

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The components follow the standard SpinQuest package hierarchy; namely "e1039-resource", "e1039-share" and "e1039-core".

Development of e1039-core

You are recommended to use "spinquestgpvm01.fnal.gov" to develop "e1039-core" since the E1039 environment at Rivanna has been set up for normal use (=analysis) at present.  But you can make your own version of e1039-core at Rivanna, by executing the following commands.

DIR_INST=~/e1039/core-inst
mkdir -p $DIR_INST
cd ~/e1039
git clone https://github.com/E1039-Collaboration/e1039-core.git
cd e1039-core
cp -p script/this-core-org.sh $DIR_INST/this-core.sh
source /project/ptgroup/spinquest/this-e1039.sh

export ROOT_INCLUDE_PATH=$ROOT_INCLUDE_PATH_E1039_SHARE
source $DIR_INST/this-core.sh
./build.sh

b

User-Level Files

User-level files for the SpinQuest MC event generation are located under "/project/ptgroup/Akbar", such as "DY_Target_script". 

...

You can activate this version on text terminal by sourcing "this-e1039.sh";

source /project/ptgroup/spinquest/devel/this-e1039.sh

The analysis modules for the MC event generation (i.e. "AnaTrkQA" and "AnaTrkQAv2") have been complied and are available under "devel/".

...