Changeset 1337 for trunk/examples/extended/electromagnetic/TestEm7/README
- Timestamp:
- Sep 30, 2010, 2:47:17 PM (14 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/examples/extended/electromagnetic/TestEm7/README
r807 r1337 1 $Id: README,v 1. 17 2007/12/04 12:06:28 vnivanchExp $1 $Id: README,v 1.22 2009/11/21 22:02:51 maire Exp $ 2 2 ------------------------------------------------------------------- 3 3 … … 35 35 36 36 2- PHYSICS LIST 37 38 Physics lists can be local (eg. in this example) or from G4 kernel 39 physics_lists subdirectory. 40 41 Local physics lists: 42 - "local" standard EM physics with current 'best' options setting. 43 these options are explicited in PhysListEmStandard 44 - "standardSS" standard EM physics with single Coulomb scattering 45 instead of multiple scattering; 46 - "standardNR" standard EM physics with single Coulomb scattering 47 process G4ScreenedNuclearRecoil instead of the 48 multiple scattering for ions with energy less than 49 100 MeV/nucleon; the new process was developed 50 by M.H. Mendenhall and R.A. Weller from Vanderbuilt 51 University and published in NIM B 277 (2005) 420. 52 In later Geant4 releases the process will be a part 53 of Geant4 source, currently it is released together 54 with its mathematical tool c2_functions in current 37 55 38 The following EM physics lists are available in this example:39 - "standard" standard EM physics (default)40 - "livermore" low-energy EM physics using Livermore data41 - "penelope" low-energy EM physics implementing Penelope models42 - "standardSS" standard EM physics with single Coulomb scattering43 instead of multiple scattering; G4ionIonisation is44 substituted by G4ionGasIonisation for GenericIons45 - "standardNR" standard EM physics with single Coulomb scattering46 process G4ScreenedNuclearRecoil instead of the47 multiple scattering; the new process was developed48 by M.H. Mendenhall and R.A. Weller from Vanderbuilt49 University and published in NIM B 277 (2005) 420.50 In later Geant4 releases the process will be a part51 of Geant4 source, currently it is released together52 with its mathematical tool c2_functions in current53 example54 56 55 Alternatively, the user may use predefined Geant4 builders: 56 - "emstandard" G4EmStandardPhysics builder 57 - "emstandard_opt1" G4EmStandardPhysics_option1 builder 58 - "emstandard_opt2" G4EmStandardPhysics_option2 builder 59 See geant4/source/physics_lists/History for details 60 61 Optional components can be added: 62 - "elastic" elastic scattering of hadrons 63 - "HElastic" 64 - "QElastic" 65 - "binary" QBBC configuration of hadron inelastic models 66 - "binary_ion" Binary ion inelastic models 57 From geant4/source/physics_lists/builders: 58 - "emstandard_opt0" recommended standard EM physics for LHC 59 - "emstandard_opt1" best CPU performance standard physics for LHC 60 - "emstandard_opt2" 61 - "emstandard_opt3" best current advanced EM options. 62 analog to "local" above 63 - "emlivermore" low-energy EM physics using Livermore data 64 - "empenelope" low-energy EM physics implementing Penelope models 65 66 Optional components can be added: 67 - "elastic" elastic scattering of hadrons 68 - "HElastic" 69 - "QElastic" 70 - "binary" QBBC configuration of hadron inelastic models 71 - "binary_ion" Binary ion inelastic models 72 73 Physics lists and options can be (re)set with UI commands 74 75 Please, notice that options set through G4EmProcessOPtions are global, eg 76 for all particle types. In G4 builders, it is shown how to set options per 77 particle type. 67 78 68 79 3- AN EVENT : THE PRIMARY GENERATOR … … 81 92 A RUN is a set of events. 82 93 94 95 4- DOSE IN 'TEST-VOLUMES' 96 97 The energy deposited in the test-volumes (tallies) defined in 98 DetectorConstruction are printed at EndOfRun, both in MeV and gray. 83 99 84 4- VISUALIZATION100 5- VISUALIZATION 85 101 86 102 The Visualization Manager is set in the main(). … … 95 111 96 112 97 5- HOW TO START ?113 6- HOW TO START ? 98 114 99 115 - compile and link to generate an executable … … 112 128 113 129 114 6- HISTOGRAM OF THE BRAGG PEAK130 7- HISTOGRAM OF THE BRAGG PEAK 115 131 116 132 Testem7 computes the total energy deposited along the trajectory of … … 121 137 (command /testem/stepMax ) 122 138 123 The result is a 1D histogram which is the total energy deposited along 124 the trajectory of the incident particle. 125 126 The histogram is saved in hbook format (testem7.hbook) 139 The result is a 1D histogram, which is the total energy deposited 140 along the trajectory of the incident particle. 127 141 128 142 The bin size is egal to stepMax. The number of bins is determined by … … 130 144 The total energy deposited is plotted in MeV/mm per incident particle. 131 145 132 Note that, by default, histograms are disabled. To activate them, uncomment 133 G4ANALYSIS_USE in GNUmakefile. 134 135 7- DOSE IN 'TEST-VOLUMES' 146 The next histogram alowing to have a zoom around the Bragg peak. Its binning 147 should be defined via UI command: 148 /testem/histo/setHisto 1 nbins xmin xmax 149 150 The last histogram shows the projectile range. Its binning should be defined 151 similary by the UI command: 152 /testem/histo/setHisto 2 nbins xmin xmax 153 154 8- USING HISTOGRAMS 155 156 By default the histograms are not activated. To activate histograms 157 the environment variable G4ANALYSIS_USE should be defined. For instance 158 uncomment the flag G4ANALYSIS_USE in GNUmakefile. 136 159 137 The energy deposited in the test-volumes (tallies) defined in 138 DetectorConstruction are printed at EndOfRun, both in MeV and gray. 139 160 To use histograms, at least one of the AIDA implementations should be 161 available. See InstallAida.txt 140 162 141 8- USING HISTOGRAMS 142 143 By default the histograms are not activated. To activate histograms 144 the environment variable G4ANALYSIS_USE should be defined. For instance 145 uncomment the flag G4ANALYSIS_USE in GNUmakefile. 146 147 It is possible to choose the format of the histogram file (hbook, root, XML): 148 comment/uncomment 1 line in RunAction::bookHisto(). 149 150 Before compilation of the example it is optimal to clean up old files: 163 Before compilation of the example it is optimal to clean up old files: 151 164 gmake histclean 152 165 gmake 153 166 154 To use histograms, at least one of the AIDA implementations should be 155 available (see http://aida.freehep.org). 156 157 8a - PI 167 It is possible to choose the format of the histogram file (hbook, root, XML): 168 /testem/histo/setHistoType root 158 169 159 A package including AIDA and extended interfaces also using Python is PI, 160 available from: http://cern.ch/pi 161 162 Once installed PI or PI-Lite in a specified local area $MYPY, it is required 163 to add the installation path to $PATH, i.e. for example, for release 1.2.1 of 164 PI: 165 setenv PATH ${PATH}:$MYPI/1.2.1/app/releases/PI/PI_1_2_1/rh73_gcc32/bin 166 167 CERN users can use the PATH to the LCG area on AFS. 168 Before running the example the command should be issued: 169 eval `aida-config --runtime csh` 170 171 8b - OpenScientist 172 173 OpenScientist is available at http://OpenScientist.lal.in2p3.fr. 174 175 You have to "setup" the OpenScientist AIDA implementation before compiling 176 (then with G4ANALYSIS_USE set) and running your Geant4 application. 177 178 On UNIX you setup, with a csh flavoured shell : 179 csh> source <<OpenScientist install path>/aida-setup.csh 180 or with a sh flavoured shell : 181 sh> . <<OpenScientist install path>/aida-setup.sh 182 On Windows : 183 DOS> call <<OpenScientist install path>/aida-setup.bat 184 185 You can use various file formats for writing (AIDA-XML, hbook, root). 186 These formats are readable by the Lab onx interactive program 187 or the OpenPAW application. See the web pages. 188 189 190 With OpenPAW, on a run.hbook file, one can view the histograms 191 with something like : 192 OS> opaw 193 opaw> h/file 1 run.hbook ( or opaw> h/file 1 run.aida or run.root) 194 opaw> zone 2 2 195 opaw> h/plot 1 196 opaw> h/plot 2 170 The default name "testem7" can be changed: 171 /testem/histo/setHistoName myname
Note: See TracChangeset
for help on using the changeset viewer.