Changes between Version 1 and Version 2 of AnnotatedJobHarp

Timestamp:

Jan 21, 2009, 8:43:20 PM (15 years ago)

Author:

gallmei

Comment:

--

AnnotatedJobHarp

@@ -1 @@
-= Annotated Jobcard "jobHarp" =
-
-The jobcard explained here in little bit more detail is the file "jobHarp" from Release 1.2. This jobcard may be used in order to calculate particle spectra in pion or proton induced reaction on nuclei. The designated energies are 3 upto 50 GeV, as e.g. possible within the HARP and NA61/Shine experiments.
-
-For more information we refer to our [http://theorie.physik.uni-giessen.de/~gibuu/Documentation/ online documentation]
+= Annotated Jobcard "jobHARP" =
+
+The jobcard explained here in some detail is the file "jobHARP" from Release 1.2. This jobcard may be used in order to calculate particle spectra in pion or proton induced reaction on nuclei. The designated energies are 3 upto 50 GeV, as e.g. possible within the HARP and NA61/Shine experiments.
+
+The given jobcard is shrinked to a minimal set of parameters to give. There are many other possible namelists and also in the namelists given here many other possible parameters. All these are set to sensible default values.
+
+''Please note:'' 
+ * Text after an exclamation mark is considered as a remark.
+ * This file is not conform with fortran standard. Code compiled with some compilers complains about our convention starting and ending a namelist by "$!NameOfNamelist" and "$end$"
+
+For more information of the given switches and parameters we refer to our [http://theorie.physik.uni-giessen.de/~gibuu/Documentation/ online documentation].
 
 
@@ -52 +58 @@
       num_runs_SameEnergy=2  ! number of runs per energy
 }}}
-(see above)
+See above. The given value 2 is just for test purposes. Real production runs (approx 2 weeks CPU time) need values as the also given 10000.
 {{{
 
@@ -60 +66 @@
 {{{
       freezeRealParticles = .TRUE.
+}}}
+The testparticles for the nucleons are kept fix at their spatial position during the time evolution, albeit carrying Fermi momentum. 
+{{{
 
       DoPrLevel(1) = .FALSE.
       DoPrLevel(2) = .FALSE.
+}}}
+These lines reduce the verbosity of the code, necessary for long calculations.
+{{{
 
       path_To_Input = '~/WC/buuinput'
-
+}}}
+The path to the directory, where the code finds the directory "buuinput" in the local installation. 
+{{{
 $end
 
@@ -71 +85 @@
 !      LesHouchesFinalParticles_Pert=.true. ! if you want that output
 $end
-
+}}}
+Setting this flag to true will print for every subsequent run a XML file according the
+[http://arxiv.org/pdf/hep-ph/0609017 "Les Houches Event Files Standard"], holding the perturbative particle vector after the last time step and all particle decays.
+{{{
 $initRandom
       SEED=45678                ! Seed for the random number
 $end
-
+}}}
+The seed for the random number generator.
+{{{
 $initDensity
       densitySwitch=2           ! 1=dynamic, 2=analytic
 $end
+}}}
+This selects the kind of calculating the nuclear density during the run. Here we choose to have it via a Woods--Saxon--density profile. The other choice would recalculate the density in every timestep according the spatial distribution of the testparticles for the nucleons. 
+{{{
 
 $initPauli
       pauliSwitch=2             ! 1=dynamic, 2=analytic
 $end
-
+}}}
+As for the density above we select the option that Pauli Blocking is based on a analytic description contrary to actual phase space densities of testparticles.
+{{{
 $propagation
       coulomb=.false.           ! Whether to use coulomb in propagation
@@ -117 +141 @@
       use_cutoff=.true.
 $end
-
+}}}
+All definitions above are given in the context that we switch off potentials in these calculations. Has been tested to be a good approximation for the energies covered by this jobcard: several GeV upto tens of GeV.
+{{{
 
 !************************************************************
@@ -138 +164 @@
 !      target_Z= 82, target_A=208 ! Pb
 $end
+}}}
+Here we provide a (not complete) list of possible target nuclei. Above A=12 all (A,Z) combinations are possible. The first line indicates the possibility to switch on/off Fermi motion of the nucleons. (In the case of A<2 this is a necessary option.) 
+{{{
 
 !************************************************************
 
 $HiPionNucleus           ! EVENTTYPE = 12
+}}}
+Here we start the namelist directly connected with the event type we selected at the very top: High energetic pions/protons on a nucleus. This steers the initialization of the testparticles.
+{{{
       distance=10.              ! distance of pions to nucleus
+}}}
+All projectile testparticles are initialized 10 fm apart from the nucleus in (negative) beam direction.
+{{{
       impact_parameter=-99      ! impact-parameter<0: impact-parameter integration
+}}}
+This selects the impact parameter. A negative value indicates, that we average over all impact parameters; the beam test particles are initialized in a disk around the beam direction.
+{{{
       DoProton=.TRUE.
+}}}
+Since historically this kind of init was for ''pions'' on nuclei, this flag tells the code that the "pion" is indeed a nucleon. 
+{{{
       charge=1                  ! charge of pions
+}}}
+This selects the charge of the beam particle (being a pion or a proton, as selected above).
+{{{
       numberPions= 25           ! number of pions per ensemble
+}}}
+For every real pion we initialize 25 testparticles.
+{{{
 
 !      ekin_lab=515.             ! kinetic energy in system where nucleus rests
 
 !      ekin_lab = 2.205 ! p= 3GeV
-!      ekin_lab = 4.149 ! p= 5GeV
+      ekin_lab = 4.149 ! p= 5GeV
 !      ekin_lab = 7.117 ! p= 8GeV
 !      ekin_lab =11.099 ! p=12GeV
-      ekin_lab = 30.000 ! T2K
+
+
+}}}
+This gives a selection of beam energies (e.g. 3,5,8,12 GeV beam momentum for HARP)
+{{{
 
 
       doPerturbativeInit=.TRUE. ! Do perturbative init
+}}}
+In this special initialization type ("HiPion") we have the possibility to not only initialize the beam (test)particles (pions or nucleons) in some distance from the nucleus, which then have to propagate in every time step towards the nucleus until they first interact with some specific nucleon, but also run this in some "fast motion" mode and to hit the beam particle already to this nucleon. This means, we first start at time 0 with a bunch of beam particles at some distance, then also at time 0 hit a selected nucleon, and also at time 0, the beam test particles are replaced by the particles produced in this interaction.
+{{{
       DoOnlyOne = .TRUE.
+}}}
+For some processes the cross section has been proven to follow a A^1^ dependence, instead of A^2/3^ as given by this transport approach. Setting the above flag to .false. attends for this possibility by allowing the beam particle to interact with many nucleons in beam direction. 
+{{{
       minimumMomentum=0.1       ! minimum momentum for particles to propagate
+}}}
+Particles with momenta smaller the given value are simply erased from the particle vector in order to speed up the calculation.
+{{{
 $end
 
@@ -176 +236 @@
 !      threeBodyProcesses=.false.
 $end
+}}}
+In this namelist one has the possibility to switch on/off particle decays, 2-Body collisions and 3-Body collisions in the propagation. The chosen values here represent a sensible choice for these kind of processes.
+{{{
 
 $insertion
       minimumEnergy=0.100       ! minimal kinetic energy of produced nucleons (GeV)
 $end
+}}}
+Here we decide, that protons and neutrons coming as outgoing particle from some collision during the propagation are erased from the particle vector, if their momenta are below 100 MeV. This is one very essential speed up of the calculations, not changing particle spectra above some hundreds of MeV in energy or momentum.
+{{{
 
 $master_2Body
       correctEnergy_message=.false.
 $end
-
+}}}
+Reducing the verbosity.
+{{{
 
 !************************************************************
@@ -192 +260 @@
       temperatureSwitch=1 ! 1=groundstate calculations (T=0,mu=E_F)
 $end
-
+}}}
+Setting a default (do not touch).
+{{{
 
 !************************************************************
@@ -203 +273 @@
 
 }}}
+Here one sets steering parameters for the included PYTHIA implementation. Many of the common block parameters there are tunable here. We refer to the Pythia manual for the description of all of this bunch. 
+
+The above parameters select the value of intrinsic transverse momentum, and while compiled against a Pythia version 6.4 switches the handling of the collisions to the most recent behavior.