At the lyon computing system a fully compiled PYTHIA simulation linked to Comgeant and CORAL. Files which can provide the ala carte setup and pythia C++ wrappers which give some filtering options are included (Pearl and Shell scripts also).

The end output is a mini DST.

You may use it however please keep attention to the following specifications.

  • PYTHIA version: 6.2
  • Comgeant Version compiled: 7.02 (Trigger bug in file /7.02/code/src/include/omgeant/ already corrected)
  • CORAL Version: prod-2007-10-5-slc4/

Location: $THRONG_DIR/Pythia_Chain/ or /afs/
What can you do:

1. Change certain kinematics in the scattering

2. Prefilter data to make smaller sized mDST's

3. Check out all of the code to your area and recompile to make it work with different CORAL/CG versions.

4. Analyze with your own PHAST version.

What you cannot do:

While I have compiled PHAST in this same Pythia_Chain central directory, it is advisable that you use your own compiled PHAST version and UserEvents.


-I Installed PHAST 7.101 which has an improved Mu' finding algorithm's by Konrad Klimaszewski <>.

The Phast Version installed in the chain has been modified to be compatible with the coral version used as the HIT_MAP_SIZE of PHAST is different than in the CORAL version used. Keep this in mind for your analysis.

A solution given by Sergei Gerassimov <> is as following:

The number of entries in the map which are transfered from CORAL to PHAST is defined by the HIT_MAP_SIZE of PHAST. If the CORAL setting CSTRACK_MAPSIZE is smaller than the HIT_MAP_SIZE, then PHAST tries to access entries beyond the actual size of the CORAL information, resulting in (more or less) random values for those.

Replacing in coral/

for(int iw=0; iw < HIT_MAP_SIZE; iw++){


for(int iw=0; iw < CSTRACK_MAPSITE; iw++){

should remove the error without the need to modify CORAL.



Marking directories: Before you begin a few directories need to be created.

  • Your $HOME directory should be set as /afs/
i.e. for me Astrid its is /afs/ check that indeed your home default is setup as such. Normally this part should not require any fiddle.
  • Create $HOME/Src , $HOME/Src/Prod/ and $HOME/Src/Prod/Options/
  • Create $HOME/public (check that you don't have it first) and $HOME/public/HighPt

Copy Modify-able Files Go to /afs/ and copy the following

  • /filesToCopy/public_HighPt to your $HOME/public/HighPt folder
  • /filesToCopy/Src_Prod_Options to your $HOME/Src/Prod/Options/

Make Sim links Go to your $HOME/Src/ Folder and do the following sim links:

  • /afs/ CSoft
  • /afs/ Comgeant
  • /afs/ Coral
  • /afs/ CoralUser
  • /afs/ Phast
  • /afs/ bin
  • /afs/ lib
Modyfing Files You need to make sure you specify the right output directories and user name. The instructions in this section will be detailed file by file.

FILES UNDER $HOME/Src/Prod/Options/ :




FILES UNDER $HOME/public/HighPt/



OTHER Files of interest

There are a few files which are linked by default which define detector behaviour which depends year by year. For 2004 muon data the following files are included in the compilation of Comgeant, however one can easily copy these files to one's directory and modify CG behaviour. Just remember to change the addresses in makephast_cg72.opt and/or highptlinks

RUNNING THE CHAIN (and producing output)

NOTE: If you are using the beam file which is defaulted (beam and halo option 3) you may want to ensure that pileup is disabled in COMGEANT otherwise you will double count [fort.15/main_muon_072.ffr]: PILEUP 0 100 5

After specifying output names and home directories the chain can be ran from : $HOME/public/HighPt/

Just run the pearl script as such: ./ N Where N is the number of jobs (mDST's) you will like to submit/create. Each job equals one mDST.

Using qjob lets you see the progress, i.e:

> qjob

user jobname status time worker cputime prio

astrid I1107582 RUNNING 02/17-09:22 G.ccwl0060 81/280000 1010

astrid I1107583 RUNNING 02/17-09:22 G.ccwl0071 3726/280000 1010

astrid I1107580 STARTED 02/17-09:22 G.ccwl0144 0/280000 1010

To delete a job just do qdel jobname

FREE HINT: A super cool PAGE that gives you usage definitions on things like qdel , id can be found HERE


-- AstridM - 24 Nov 2009

Edit | Attach | Watch | Print version | History: r8 < r7 < r6 < r5 < r4 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r8 - 2010-03-23 - CharmoniaWorkService
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Compass/HighpTLowQ2 All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2023 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback