Manuale Phits
Manuale Phits
Manuale Phits
Ver. 3.17
User’s Manual
English version
Preface
This manual is the Particle and Heavy Ion Transport code System (PHITS) user’s guide. PHITS is a general-
purpose Monte Carlo particle transport simulation code that is used in many studies in the fields of accelerator
technology, radiotherapy, space radiation, etc. For details on the physical models and important functions imple-
mented in PHITS, see the main article 1 , benchmark study 2 , and papers citing them. This manual explains how to
execute PHITS and which parameters should be used in the system.
The contents of this manual correspond to the PHITS version number shown on the title page and are subject
to change without notice. If you have any question or comment regarding this manual, please contact the PHITS
office (phits-office@jaea.go.jp).
1 T. Sato, Y. Iwamoto, S. Hashimoto, T. Ogawa, T. Furuta, S. Abe, T. Kai, P.-E. Tsai, N. Matsuda, H. Iwase, H. Shigyo, L. Sihver, and K.
Niita, Features of Particle and Heavy Ion Transport code System (PHITS) version 3.02, J. Nucl. Sci. Technol. 55, 684-690 (2018).
2 Y. Iwamoto, T. Sato, S. Hashimoto, T. Ogawa, T. Furuta, S. Abe, T. Kai, N. Matsuda, R. Hosoyamada, and K. Niita, Benchmark study of
the recent version of the PHITS code, J. Nucl. Sci. Technol. 54:5, 617-635 (2017).
I
Contents
1 Recent Improvements and Development Members 1
1.1 Recent Improvements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.2 Development members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.3 Reference of PHITS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4 Input File 27
4.1 Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
4.2 Reading control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
4.3 Inserting files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
4.4 User-defined variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
4.5 Using mathematical expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
4.6 Particle identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
4.7 Array sizes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
5 Sections format 34
5.1 [ Title ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
5.2 [ Parameters ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
5.2.1 Calculation mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
5.2.2 Number of history and Bank . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
5.2.3 Cut-off energy and switching energy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
5.2.4 Cut-off time, cut-off weight, and weight window . . . . . . . . . . . . . . . . . . . . . . 41
5.2.5 Model options (1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
5.2.6 Model options (2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
5.2.7 Model options (3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
5.2.8 Model options (4) - stopping power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
5.2.9 Model options (5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
5.2.10 Output options (1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
5.2.11 Output options (2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
5.2.12 Output options (3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
5.2.13 Output options (4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
5.2.14 Voxel and tetrahedron geometry options . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
5.2.15 About geometrical errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
5.2.16 Input-output file name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
5.2.17 Others . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
5.2.18 Physical parameters for low energy neutrons . . . . . . . . . . . . . . . . . . . . . . . . 58
5.2.19 Physical parameters for photon and electron transport based on the PHITS original model 59
5.2.20 Parameters for EGS5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
ii
5.2.21 Dumpall option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
5.2.22 Event Generator Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
5.3 [ Source ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
5.3.1 <Source> : Multi-source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
5.3.2 Common parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
5.3.3 Cylinder distribution source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
5.3.4 Rectangular solid distribution source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
5.3.5 Gaussian distribution source (x,y,z independent) . . . . . . . . . . . . . . . . . . . . . . 73
5.3.6 Generic parabola distribution source (x,y,z independent) . . . . . . . . . . . . . . . . . . 73
5.3.7 Gaussian distribution source (x-y plane) . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
5.3.8 Generic parabola distribution source (x-y plane) . . . . . . . . . . . . . . . . . . . . . . . 74
5.3.9 Sphere and spherical shell distribution source . . . . . . . . . . . . . . . . . . . . . . . . 75
5.3.10 s-type = 11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
5.3.11 s-type = 12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
5.3.12 Cone shape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
5.3.13 Triangle prism shape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
5.3.14 xyz-mesh distribution source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
5.3.15 Tetra-mesh source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
5.3.16 Surface definition source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
5.3.17 Reading dump file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
5.3.18 User definition source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
5.3.19 Definitions for energy distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
5.3.20 Definitions for angular distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
5.3.21 Definition for time distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
5.3.22 Example of multi-source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
5.3.23 Duct source option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
5.4 [ Material ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
5.4.1 Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
5.4.2 Element (nuclide) definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
5.4.3 Composition ratio definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
5.4.4 Material parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
5.4.5 S (α, β) settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
5.4.6 Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
5.5 [ Surface ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
5.5.1 Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
5.5.2 Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
5.5.3 Surface definition by macro body . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
5.6 [ Cell ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
5.6.1 Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
5.6.2 Description of cell definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
5.6.3 Universe frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
5.6.4 Lattice definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
5.6.5 Repeated structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
5.7 [ Transform ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
5.7.1 Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
5.7.2 Mathematical definition of transformation . . . . . . . . . . . . . . . . . . . . . . . . . . 144
5.7.3 Examples of [transform] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
5.8 [ Temperature ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
5.9 [ Mat Time Change ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
5.10 [ Magnetic Field ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
5.10.1 Charged particle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
5.10.2 Neutron . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
5.10.3 Implementation of the magnetic field map . . . . . . . . . . . . . . . . . . . . . . . . . 150
5.10.4 Format of magnetic field map file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
5.11 [ Electro Magnetic Field ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
5.12 [ Delta Ray ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
5.13 [ Track Structure ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
iii
5.14 [ Super Mirror ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
5.15 [ Elastic Option ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
5.16 [ Data Max ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
5.17 [ Frag Data ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
5.18 [ Importance ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
5.19 [ Weight Window ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
5.20 [ WW Bias ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
5.21 [ Forced Collisions ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
5.22 [ Volume ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
5.23 [ Multiplier ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
5.23.1 Multiplier subsection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
5.24 [ Mat Name Color ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
5.25 [ Reg Name ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
5.26 [ Counter ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
5.27 [ Timer ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
iv
7 Tally input format 197
7.1 [ T-Track ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
7.2 [ T-Cross ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
7.3 [ T-Point ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
7.4 [ T-Deposit ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
7.5 [ T-Deposit2 ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
7.6 [ T-Heat ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
7.7 [ T-Yield ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
7.8 [ T-Product ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
7.9 [ T-DPA ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
7.10 [ T-LET ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
7.11 [ T-SED ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
7.12 [ T-Time ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
7.13 [T-Interact] section (formerly named [T-Star]) . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
7.14 [ T-Dchain ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
7.15 [ T-WWG ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
7.16 [ T-WWBG ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
7.17 [ T-Volume ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
7.18 [ T-Userdefined ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
7.19 [ T-Gshow ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
7.20 [ T-Rshow ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
7.21 [ T-3Dshow ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
7.21.1 Box definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
7.21.2 3dshow example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
13 FAQ 281
13.1 Questions related to parameter setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
13.2 Questions related to errors occurred in compiling or executing PHITS . . . . . . . . . . . . . . . 282
13.3 Questions related to Tallies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
13.4 Questions related to source generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
13.5 Other questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
v
APPENDIX 285
A List of physical processes that cannot be handled by PHITS . . . . . . . . . . . . . . . . . . . . 285
index 286
vi
1
From ver. 3.17, the following function has been implemented, and some bugs have been fixed. (2019/10/29)
• A new option foamout=2 to output the tetrahedral-mesh tally results in csv format has been implemented.
• The bug in the [t-deposit] calculation using EGS5 was fixed. This bug was due to uninitialization of a
certain variable in PHITS, so it occasionally causes a serious influences on the tally results, but in most case
not.
• The calculation procedures for ‘sum over’ in many tallies have been revised.
• The bug in the motion of cut-off particles with energy struggling when nedisp=1 has been fixed.
• The parameters used in the biological dose calculation using “usrdfn2.f” were changed from those given in
T.Sato et al. Radiat. Prot. Dosim. 143, 491-496 (2010) to T.Sato et al. Radiat. Res. 171, 107-117
(2009).
From ver. 3.16, the bug for sangel parameter has fixed. The other bug in ver. 3.15 that [t-track] tally does
not output “ err” files has also been fixed. (2019/09/26)
From ver. 3.15, the following bugs have been fixed. (2019/09/12)
• A bug that [t-deposit] overestimates contributions of the energy cut-off in EGS5 has been fixed. Fur-
thermore, another bug when using EGS5 and lattice structure has been fixed. The former and latter bugs
occurred from version 3.13 and 3.10, respectively.
• A bug regarding the function when setting itall=3 has been fixed. Segmentation errors occurred depending
on input files. This bug occurred from version 3.13.
• A bug of DCHAIN, which occurred only in version 3.14, has been fixed.
From ver. 3.14, the following functions have been implemented, and some bugs have been fixed. (2019/08/18)
• DCHAIN-SP has been improved in terms of the following two features; (1) several neutron activation li-
braries and decay-data libraries have been developed based on the latest evaluated data, and (2) statistical
uncertainties of the induced activities can be evaluated considering those of the production yields calculated
by PHITS. Owing to these improvements, some parameters have been added to [t-dchain] section (see
section Sec. 7.14 in detail). The new version of DCHAIN will be called DCHAIN-PHITS to be distinguished
with the previous versions.
• A new function to calculate the DNA damage yields has been developed, using the track structure mode and
user-defined tally. Their sample data are contained in “/phits/utility/usrtally/DNAdamage.”
• Two bugs occurred only in version 3.13 have been fixed, which are related to [t-interact] and the track
structure mode.
From ver. 3.13, the following functions have been implemented, and some bugs have been fixed. (2019/08/02)
• The default value of the cut-off energy for proton, pion, muon, and ions has been decreased from 1 MeV/u
to 1 keV/u.
• A new source type (s-type=26) has been introduced to define a surface source which generates source
particles on the surface(s) that has/have been pre-defined in the [surface] section. Please see Section
5.3.16 for more details.
• A new option, itall=3, has been implemented to plot the trend of tally results and their statistical uncer-
tainties for each batch with the ongoing PHITS calculation. This option is available only for [t-track]
and [t-point] at this moment.
2 1 RECENT IMPROVEMENTS AND DEVELOPMENT MEMBERS
• A new parameter, istdcut, has been introduced to the [parameter] section. It enables the termination of
the tally calculations of which the statistical uncertainties have reached the stdcut setting. This function
is particularly useful when the types of tallies which consume much longer computational time, such as
[t-point] and [t-sed], are written in the same input file with other tallies. Another new parameter,
istdbat, has been introduced to inactivate stdcut at the early stage of the PHITS simulation.
• In stopping power calculations using ATIMA, the ionization potential of water is expected to automatically
adjust to 75 eV. However, this function was valid only when the material of water was explicitly specified by
the isotope 1H, i.e. material consists of natural abundant hydrogen is not treated as water in this particular
respect. We modified the program, so that the material of water which is defined by naturally-abundant
hydrogen isotopes, such as in the format of H 2 O 1 and H -0.1111 O -0.8889, is now regard as water
for stopping power calculations. Owing to this modification, the ranges of charged particles in water increase
slightly (less than 1% in most cases) compared to the results obtained from the previous versions. The valid
condition of ih2o parameter has been also revised in the same way.
• Some bugs have been fixed, such as ignorance of stdcut in the MPI version, strange behavior of particles
when mirror surfaces are used in lattice structure, and a rare bug in EGS5.
From ver. 3.12, the following functions have been implemented, and some bugs have been fixed. (2019/06/20)
• The new parameters cnt(1), cnt(2), and cnt(3) have been introduced in [source] section to specify
the initial counter values for each multi-source subsection <source>. The maximum number of <source>
subsections is extended from 200 to 500.
• A function to consider the decrease of target radioactive nuclides due to nuclear reactions has been imple-
mented in [t-dchain]. DCHAIN has also been revised in correspondance to the [t-dchain] improve-
ment. Note that former versions of DCHAIN cannot read the outputs from the improved [t-dchain].
• The itall = 1 option has become available in the Windows OpenMP version of PHITS.
• Some bugs regarding the FLUENT-PHITS coupled calculations have been fixed, including the incorrect
translation of the material densities between FLUENT and PHITS.
From ver. 3.11, the following bugs have been fixed. (2019/05/16)
• The bug of MPI parallel calculations with tetrahedral-geometry stopped abruptly in ver. 3.10 has been fixed.
• The bug that the magnetic field maps given in r-z grid (type = -2 or -4) cannot be properly considered
has been fixed.
• Annihilation photons are double counted in the RI source generation function when the production of both
positron and photon are considered. To avoid the problem, a new parameter iannih has been introduced to
exclude the annihilation photons in the case of proj = photon.
From ver. 3.10, the following functions were implemented, and some bugs were fixed. (2019/03/13)
• Procedure for coupling PHITS with thermal analysis software such as ANSYS Fluent is established. For
this purpose, a function to read tetrahedral-mesh geometry written in bulk-data format of NASTRAN is
implemented. A new mesh option, mesh=tet, is introduced in [t-track], [t-deposit], [t-yield],
[t-product], and [t-dpa] to output the tallied quantities in each tetrahedral mesh. Field-data format used
in OpenFoam, which can be directly read by thermal analysis software, has become selected as an output
format.
• As a part of the improvements for coupling with thermal analysis software, a new option, unit=5, is intro-
duced in [t-deposit] to output the deposition energy in J/m3 /source.
• Sample files for using high-energy nuclear data library JENDL-4.0/HE are provided in the PHITS package.
Please see \phits\recommendation\jendlHE in more details.
• A function to read magnetic field maps written in xyz or r-z grid is implemented.
• [t-dchain] has become applicable to mesh=xyz. In reply to this improvement, DCHAIN is also updated.
Note that the function to visualize the induced activities in xyz mesh has not been developed yet.
1.1 Recent Improvements 3
• A nuclear reaction model to handle the reactions by electron-, mu-, tau-neutrino and their antiparticles up
to 150 MeV of incident energy is incorporated. Neutrinos can interact with orbital electrons, 1 H, and 2 H
whereas the nuclei heavier than 2 H are currently out of the range of this model.
• INC-ELF, an intra-nuclear cascade model developed by Kyushu University, is updated to consider collective
excitation of the target nucleus and to precisely calculate charged particle emission barriers.
• User-defined energy resolution function has been implemented to [T-deposit] in order to reproduce en-
ergy resolution which cannot be realized by dresol and dfano. Users can define the functional forms of
energy resolution in “usresol.f,” which is activated by defining negative dresol. As a sample, the default
“usresol.f” contains a numerical model proposed by Meleshenkovskii et al. to reproduce asymmetric peaks
of a CdZnTe detector.
• A new option, gshow=5 and [t-gshow] with output=10, is introduced to visualize the geometry in the
pixel format. This option is useful for properly visualize the geometries with fine structure such as voxel and
tetrahedral phantoms.
• Some parameters in the muonic atom cascade program have become adjustable.
• The third user-defined function, “usrdfn3.f,” is introduced for weighting the results of [t-deposit]. The
default program of usrdfn3.f can convert the absorbed dose to the water equivalent dose, which is frequently
used in medical physics.
• In [t-cross] with mesh=xyz or r-z, a new option, enclose=1, is introduced for calculating incoming
and outgoing particle fluxes (or currents) from each mesh.
• Deposition energies in the cells with the same ID but placed in different lattice coordinates can be separately
analyzed in the case of [t-deposit] with output=deposit.
• Nuclear data libraries containing more than 1000 γ-ray spectra such as the latest version of ENDF and JEFF
have become acceptable in PHITS.
• The fixed charge mode, ifixchg=1, is introduced for calculating the stopping power of particles with a
certain charge state. Note the charge exchange reaction has not been implemented yet, so the fixed charge
mode is appropriate only when target material is extremely thin at this moment.
• Several bugs are fixed, including the problem in positron transport when emin(12) is specified without
specifying emin(13), and that in electron and positron transports in the magnetic field defined at a lattice
structure.
From ver. 3.08, the following changes have been made. (2018/08/20)
• The user-defined activation cross section data can be used in the [t-yield] and [t-dchain] sections.
Please refer to Section 7.7 for further detail. This new function was supported by the R&D program entitled
“Reduction and Resource Recycling of High-level Radioactive Wastes through Nuclear Transmutation” in
the Impulsing Paradigm Change through Disruptive Technologies Program (ImPACT).
• For RI sources, characteristics x-ray and internal conversion electron are now considered.
• Tetrahedral geometries that are converted from CAD can now be used, even when the surface of tetrahedron
does not perfectly match the boundary surfaces.
• The parameters (c1-c99) specified in the input file can be used in the user-defined source file (“usrsors.f”).
4 1 RECENT IMPROVEMENTS AND DEVELOPMENT MEMBERS
• The high-speed mode of ANGEL, which does not check numerical data while plotting the results, has be-
come the default.
• For cylindrical sources (s-type=1), a few bugs, such as the bug occurring when a source particle is sampled
between 0 and r1 with the setting of r0=r1, have been fixed.
From ver. 3.07, mesh=xyz became available in [weight window] for EGS5. Conversion coefficients for soft
error rates on semiconductor devices were added to default data of [multiplier]. In addition, some bugs for
JAM were fixed. (2018/07/05)
From ver. 3.06, the following functions were implemented, and some bugs were fixed. (2018/05/29)
• By defining igamma as negative, Doppler effect owing to the motion of the emitter nuclei is disregarded.
Specific gamma-rays are observed as mono-energetic peak in the energy spectrum.
• GEM Ver.2 including nucleon-gamma emission competition was developed. This version is available by
setting ngem=2 in [parameters] section.
• New format of [transform] was implemented to define rotation around z,y,x axes simply.
• The distributed-memory parallel computing using a MPI protocol became available on Windows. This
development was performed under support of NAIS Inc.
From ver. 3.05, the following functions were implemented, and some bugs were fixed. (2018/03/14)
• The function to calculate the deposition energy using kerma approximation, which used to be implemented
only in [t-heat], became available in [t-deposit]. Necessity of the use of kerma approximation in the
energy deposition calculation is automatically judged based on the status of e-mode and negs specified in
[parameters] section. Owing to this improvement, we recommend to use [t-deposit] instead of [t-heat]
in all situations of deposition energy calculations.
• [t-deposit] with output=deposit can be used in the case that weight is not always 1 unless weights
of energy depositing particles change within one history. Then, this mode works in the cases that you set
s-type=9 and dir=-all in [source] section, or you use [forced collisions] for neutral particles.
• The graph style for [t-cross] with axis=z is changed from histogram to dot & line.
• Specification of z-type=1 and nz=0 is allowed for [t-cross] to calculate fluences of particles passing
through a certain surface.
• Numbers of delta-rays produced by ions (including protons) and knock-on electrons produced by electron
scattering can be separately calculated in [t-interact] section. In addition, they can be distinguished in
[counter] section too.
• RI source function was improved to produce Auger electrons even when the Auger electron spectrum data
are not included in RIsource.ack.
• A bug in [t-product] in the case of iMeVperu=1 was fixed.
From version 3.04, the probability density of the number of interactions by individual history can be outputted
from [t-star]. The number of interactions occurred in the track-structure mode can be also counted in the tally.
In addition, the tally name was changed to [t-interact] in order to explicitly state that it is the tally for counting
the number of interactions, though the former name [t-star] can still be accepted. (2018/02/16)
From ver. 3.03, the following functions were implemented, and some bugs were fixed. (2018/02/01)
• A new function to generate source particles from tetrahedron geometry was implemented. See Section 5.3.15
in more detail.
• mesh = xyz became available in [weight window] and [t-wwg] sections.
• Coefficients depending on particle type can be defined in [multiplier] section, using part parameter.
Owing to this improvement, several types of radiation doses can be directly calculated using pre-defined
[multiplier] sections.
1.1 Recent Improvements 5
• [t-deposit] with output=deposit can be used in the case that source weight is not 1.
• A bug in [t-deposit] in the cases of output=deposit, dresol, 0, and part,all was fixed.
• A bug in the range calculation of charged nuclei in some tallies when iMeVperu=1 was fixed.
From ver. 3.02, the following functions were implemented, and some bugs were fixed. (2017/12/01)
• New parameters nudtvar and udtvar(i) were introduced for [t-userdefined]. After variables udtvar(i),
(i = 1, · · · , nudtvar) was set in an input file, these can be used in subroutine usrtally. There is no
upper limit of the number of udtvar(i) unlike udtpara before ver. 3.01. udtpara can be also set after this
version.
• New options were implemented for the unit of [t-let] and [t-sed].
• Position of the source generation was adjusted to just on the spherical surface for s-type=9 with dir=iso.
This revision influences only when some materials are placed outside the source sphere.
• A bug related to [counter] section was revised. Before this revision, occurrence of atomic interactions
were ignored in calculating counter when negs was set to -1 (only photon transport mode).
• A bug in the calculation of the restricted stopping power when δ-rays are generated by [delta ray] was
fixed.
• The bug in the calculation of angular straggling using nspred = 2 was fixed. This bug was introduced
in PHITS2.96, and calculation results for charged particle beam using the versions between 2.96 and 3.01
might be strange.
From ver. 3.01, the following functions were implemented, and some bugs were fixed. (2017/10/31)
• A special ANGEL parameter sangel was introduced to insert all ANGEL parameters into tally output
files. This function was developed by Mr. Takamitsu Miura of RIST, and was supported by Center for
Computational Science & e-Systems, JAEA.
• Reading algorithm for tetrahedral geometry was revised to reduce the computational time.
• ANGEL was revised to reduce the computational time for making eps files of tally results with 2-dimensional
type such as axis=xy.
• A bug for ignoring stdcut in [t-deposit] was fixed.
From ver. 3.00, the Kurotama model was used as the default model to give nucleus-nucleus reaction cross
sections, and the natural isotope expansion was effective in input files of DCHAIN generated by [t-dchain]. In
addition, some bugs were fixed. (2017/10/04)
From ver. 2.97, the following functions were implemented, and some bugs were fixed. (2017/09/21)
• A new parameter iMeVperu was introduced to convert the unit of nucleus energy [MeV] to [MeV/u] in
outputs of all tallies. By setting of iMeVperu=1 in [parameters], all tally results are output with the unit
of MeV/u for the nucleus energy. This function was developed by Mr. Takamitsu Miura of RIST, and was
supported by Center for Computational Science & e-Systems, JAEA.
• New parameters r-from, r-to in [t-cross] with mesh=reg were added, because conventional parame-
ters r-in, r-out were confusing. r-from, r-to can be used instead of r-in, r-out, respectively.
• The option of the stopping power ndedx=3 became applicable for target nuclei with the mass number of
93 ≤ Z ≤ 97 (from Np to Bk). See Section 5.2.8 for more detail.
• By adding “$OMP=N” (N is the number of CPU cores to be used) before the first section in a PHITS input
file, the shared-memory parallel computing using OpenMP is executed. Even when infl: is set, a line of
“file=input file name” is not required. In Mac OS, a terminal window is opened when PHITS is executed
by drag and drop on the Dock. Note that these function are not available when to run PHITS on the command
line on Linux and so on.
6 1 RECENT IMPROVEMENTS AND DEVELOPMENT MEMBERS
• The default value of the switching energy from JQMD to JAMQMD, ejamqmd, was changed to 3GeV.
From ver. 2.96, the following functions were implemented, and some bugs were fixed. (2017/08/28)
• A new section [ww bias] and a new tally [t-wwbg] were implemented to bias [weight window] to
obtain better statistics for a certain direction. See Section 5.20 and 7.16 in more detail.
• The numerical data of tally results are outputted after each batch is finished even for itall=0 (default).
Thus, the difference between itall=1 and 0 is whether the image (*.eps) files are generated or not. Owing
to this revision, the parameter stdcut works in the default setting.
• Only related tallies to the setting of the icntl parameter work. For example, all tallies except for [t-volume]
are disabled when icntl=14, while [t-volume] is disabled when icntl,14. Warning is outputted when
infl or set command is written in the disabled section.
• Some ANGEL parameters were introduced to change the length or time axis of figures. For example, you
can draw a figure of spatial dose distribution with the axis in nm scale by setting angel=cmnm in the tally.
See section 6.7.10 in more detail.
• PHITS execution is terminated when two or more [parameters] sections exist in one input file.
• Some bugs are fixed in terms of the systematic equation for calculating the giant-dipole resonance cross sec-
tions, the angular straggling function for very short range particle, high-energy nucleon-nucleon interaction
model JAMQMD2, and the formula for calculating the source spectrum with the Maxwell distribution.
From ver. 2.95, the procedure for s-type depending on the setting of the energy of source particles was
changed. The mono-energetic and energy-distributed sources can be defined by setting e0 and e-type, respec-
tively, irrespective of the value of s-type. If both e0 and e-type are defined, the energy is decided according to
the previous procedure of s-type. In addition, some bugs were fixed. (2017/07/21)
From ver. 2.94, bug in [t-track] and [t-cross] was fixed. Before this revision, the energy of electrons
and positrons passing through vacuum is slightly different from the real value when EGS5 is used. Note that this
revision only influences the tally results, and has no relation with particle transport simulation itself. In addition,
bugs in track-structure mode were fixed. (2017/06/30)
From version 2.93, the following functions were implemented, and some bugs were fixed. (2017/06/16)
• A new parameter file(1) was introduced to specify the PHITS installation folder name. When you properly
set this parameter, you do not have to specify the name of other input files i.e. file(7, 20, 21, 24, and
25) unless you have changed the folder structure of PHITS.
• A new parameter nucdata was introduced to automatically adjust emin(2) and dmax(2) parameters suit-
able for JENDL-4.0. The default value of this parameter is set to 1, i.e. neutrons below 20 MeV are
automatically transported using nuclear data library.
• A new option for negs parameter, -1, was introduced. When you set negs=−1, PHITS treats photon transport
using the original algorithm (i.e. not EGS5), and ignores the electron and positron transport. This option is
selected as the default setting.
• The default value of ides parameter was changed to 1, i.e. photon does not produce electrons in the PHITS
original algorithm. If you would like to transport electrons and positrons, you have to use EGS5.
• The default value of igamma parameter was changed to 2, i.e. γ-rays are produced in the de-excitation
process based on EBITEM model in the default setting.
• RI source function was improved to be applicable to α and β decays including Auger electron production.
See Table 5.57 in more detail.
• Track-structure mode was developed in PHITS. Using this mode, PHITS can analyze ionization, excitation,
and oscillation induced by electrons and positrons event-by-event. See Section 5.13 in more detail.
1.1 Recent Improvements 7
• A new method for calculating the energy loss of charged particles with explicitly generating δ-rays was
developed, based on their restricted stopping power. This method is selected as the default setting, i.e.
irlet=1.
• JAMQMD, which is used for simulating nucleus-nucleus interactions above 3 GeV/u, was improved to
consider the relativistic effect.
• [t-dpa] was improved to be capable of calculating DPA by electrons, positrons, pions etc.
• Bug in the normalization process of the self-fission source (ispfs option) was fixed.
From ver. 2.92, the default setting of output in [t-dchain] tally changed to cutoff in order to score
particles stopped in specified regions. Note that in the previous setting output=product heavy ions produced
in a thin target were scored even though the ions don’t stop in the target. In addition, we replaced a place where
the version of PHITS is shown in eps files by that of ANGEL. We fixed a bug about triangle prism shape source.
(2017/04/18)
From version 2.91, a following function was implemented, and some bugs were fixed. (2017/02/20)
• A new function to display error bars of statistical uncertainties in eps files of tally results was implemented.
This function is available by setting epsout=2 in each tally section. It should be noted that the setting is
ignored when the output format is 2-dimensional type such as axis=xy.
• A bug in the combination of EGS5 and [t-cross] was fixed. This bug affected calculations in which
electrons or positrons were scored with [t-cross] using EGS5.
• A new function to analyze the motion of electrons and positrons in the electro-magnetic fields was imple-
mented. This implementation was performed under support of NAIS Inc.
• The default value of the ascat2 parameter introduced in version 2.77 was revised from 0.088 to 0.038, in
accordance with the original paper 3 . The PHITS results obtained by setting nspred = 2 without specifying
ascat2 will be changed.
• A new function to generate xyz-mesh distribution source was implemented. Using this function, you can
reproduce sources having a complex spatial distribution. See Section 5.3.14 in more detail.
• A new tally named [t-volume] was developed in order to automatically calculate the volume of each cell.
See Sections 7.17 in more detail.
• A new parameter timeout was introduced in the [parameters] section. When CPU time exceeds this
value, the PHITS simulation is automatically stopped. This check function works at the end of each batch.
• A new parameter stdcut was introduced in each tally. When the all statistical uncertainties of the tally
results become less than this value, the PHITS simulation is automatically stopped. This check function
works at the end of each batch.
• Nuclear and atomic interactions are explicitly distinguished in [t-product], [t-star], and [counter].
Information on further detailed channels such as the production of bremsstrahlung can be also deduced. See
Sections 7.8, 7.13, 5.26 for more detail.
• In the default setting, c became unusable as comment marks in [material] section in order to avoid an
error that the elemental symbol for carbon, C, is read as comment marks. When you use c as comment
marks in the section, set icommat=1 in [parameters] section.
• A new option of [t-deposit] was developed to sum up the deposit energies weighted by user defined
conditions. This option can be applied to simulation, for example soft errors in semiconductor devices.
3 G.R. Lynch and O.I. Dahl, Nucl. Instrum. Methods Phys. Res, B 58, 6-10 (1991).
8 1 RECENT IMPROVEMENTS AND DEVELOPMENT MEMBERS
• A new function to use results of tallies as an energy distribution of source particles was added in [source].
This function can be used by specifying e-type=20.
• User defined function 2 (usrdfn2.f) in [t-deposit] was changed to the new option to estimate biological
dose on the basis of Microdosimetric Kinetic Model. See the paper 4 in more detail.
From version 2.88, the following functions were implemented. (2016/09/29)
• The sumtally function became applicable to the [t-dchain] tally.
• Two user-defined cross section function options were developed: a function to extrapolate from given data
for incident energies, emission angles, and emission energies; and a function that is effective in cases in
which no differential cross section data are available. Nuclear reaction models can only be used to simulate
nuclear reaction events with total reaction cross section data.
• A bug occurring from ver. 2.83 in which all neutrons with energy lower than emin(2) decay was fixed.
From version 2.87, the following functions were implemented. (2016/09/15)
• The arrows to indicate the xyz coordinates are depicted in the [t-3dshow] tally.
• The algorithm for calculating tetrahedral geometry was revised to reduce the computational time.
• The geometry-error information file name format (“*.err”) was changed to (“* geo.out”).
• A bug in the use of MTn, i.e., the S (α, β) table in the [material] section was fixed. This bug occurred only
in version 2.86.
From version 2.86, the following functions were implemented. (2016/08/23)
• A new tally [t-wwg] was introduced. Using this tally, it is possible to automatically determine an appropri-
ate setting for the [Weight Window] section. See Section 7.15 for more detail.
• A function to output the tally results in the xyz-mesh in the input format of ParaView, which is an open-
source, multi-platform data analysis and visualization application, was implemented: see the documents in
the /utility/ParaView/ folder for more detail. Furthermore, a function to generate a Bitmap figure of
the 2-dimensional tally output was implemented. These improvements were introduced with the support of
Dr. Furutaka of the Research Group for Nuclear Sensing, JAEA, and V.I.C., Inc.
• A new mode for calculating the stopping power of all charged particles using ATIMA, ndedx=3, was added
and set as the default value.
• The name of the current batch information output file was changed from batch.now to batch.out. This
file name can be specified by setting file(22) in the [parameters] section.
• The RI-source function was implemented. Using this function, PHITS can generate photon sources with the
energy spectra of radioisotope (RI) decay by simply specifying the activity and name of the RIs. Nuclear
decay database DECDC 5 , which is equivalent to ICRP107, was used in this function: see Table 5.57 for
more detail. This improvement was performed under support of Dr. A. Endo of the Japan Atomic Energy
Agency (JAEA).
• A new parameter natural was introduced in the [parameters] section. When an element is defined
without specifying its mass number in the [material] section and natural is set to 1 or 2, PHITS assumes
that it has natural isotope composition. Note that natural isotopes whose nuclear data are not included in
JENDL-4.0 are ignored in the calculation. This improvement was performed under support of Center for
Computational Science & e-Systems, JAEA.
• A new section [Data Max] was introduced to specify the dmax parameter for each nucleus and material:
see Section 5.16 for more detail. This improvement was performed with the support of the Center for
Computational Science & e-Systems, JAEA.
4 T.Sato et al. Biological dose estimation for charged-particle therapy using an improved PHITS code coupled with a microdosimetric
1347 (2005).
1.1 Recent Improvements 9
• The muon nuclear reaction model was improved: see the reference 6 shown below for more detail.
• A new model for calculating deuteron-nucleus total reaction cross sections was introduced. This model can
be used by setting icrdm=1 in the [parameters] section. See the reference 7 shown below for more detail.
• The pion total reaction cross section model was improved and set as the default model. The improved model
reproduces experimental cross section data better than the old model, which used a geometrical formula.
The model used can be selected using the icxspi parameter.
• Several sumtally subsections can be defined in an input. Some bugs related to sumtally were fixed.
• The high-energy heavy ion reaction model, JAMQMD, which works above 3 GeV/u, was improved to
JAMQMD2 in the same manner as JQMD. The accuracy and stability of the calculation are improved,
particularly for cosmic-ray simulation.
• The ATIMA algorithm for stopping power calculation in PHITS was improved. Following this improvement,
PHITS simulation with high precision ATIMA is now possible in nearly the same calculation time as that of
SPAR. This improvement was implemented by Mr. Akio Wada of the Research Organization for Information
Science & Technology (RIST) and was supported by the Center for Computational Science & e-Systems,
Japan Atomic Energy Agency (JAEA).
• The unit of the esmin and esmax parameters was changed from MeV to MeV/u. These parameters define,
respectively, the minimum and maximum energies of charged particles treated in the simulation.
• A bug in the high-energy photon transport (at above approximately 10 MeV) under EGS5 was fixed.
• A bug in the capture reaction of negative muons when 1 H is included in the material was fixed.
• Neutron decay can be considered with a mean neutron life time of approximately 886.7 s. Correspondingly,
a very large value for tmax (default = 1.0e9 ns) must be used to consider neutron decay in a simulation.
• A bug in the treatment of the Doppler effect under EGS5 was fixed. Because of this bug, previous versions
of PHITS scored some energies for [t-deposit] using part=photon instead of the correct value of 0.
• A bug in [t-point] occurring when other tallies were written with mesh=reg behind a [t-point] tally,
which can corrupt the results of the other tallies, was fixed.
• A bug under which the sumtally function does not work in an input file that includes infl was fixed.
• A point estimator tally [t-point] to calculate the particle fluence at a specific point or ring (see section 7.3
as well as /utility/tpoint/ folder) was implemented.
• A new parameter elastic was added to the [t-yield] tally to output recoil nuclei from elastic scattering.
• A new output option transmut was added to the [t-star] tally to output star density in reactions that
induce transmutation of target nuclei.
• A new option fiss was added in the [counter] section to output information on secondary particles gen-
erated through fission reactions, particularly in each generation of sequential fission.
6 S. Abe and T. Sato, Implementation of muon interaction models in PHITS, J. Nucl. Sci. Tech. 54, 101-110 (2017).
7 K. Minomo, K. Washiyama, and K. Ogata, J. Nucl. Sci. Tech. 54, 127-130 (2017).
10 1 RECENT IMPROVEMENTS AND DEVELOPMENT MEMBERS
• A new function was implemented in the [source] section to generate neutron sources from spontaneous
fission. The multiplicity and energy spectra of neutrons under this function are taken from reference 8 shown
below: see section 5.3.2 for more detail. The PHITS development team is grateful to Dr. Liem Peng Hong
of NAIS, Co., Inc. for his support in developing this function.
• A new function was implemented in the [source] section to generate particles from a triangle prism: see
section 5.3.13 for more detail.
• A new function was implemented in [source] section to generate particles with arbitrary time information.
See section 5.3.21 in more detail.
• A new parameter NONU was added in the [parameters] section to control neutron multiplicity.
• A new function to calculate the particle fluence in sector prisms was implemented in the [t-track] tally
by introducing a θ-mesh in the case of mesh=r-z.
• A new function to consider the polarization of photons was implemented in the calculation of nuclear flores-
cence resonance (NRF).
• The sumtally function became applicable to all tallies except for [t-dchain]. (From ver. 2.88, this function
became applicable to all tallies.)
• The individual contribution of particles can be properly calculated using [t-deposit] with output=deposit
option.
• Several bugs in the muon- and photon-induced nuclear reaction models and in JQMD-2.0 were fixed.
• Instructions on how to use tetrahedral geometry (TetraGEOM), the point estimator tally [tpoint], and the
user-defined tally [usrtally] were added to the utility folder.
• The makefile was revised to consider the dependence of each source file. Owing to this improvement, the
“-j” option can be used to speed up the compilation of PHITS: please be careful to ensure that the target
(executable) file name is changed in the revised makefile. This revision was performed with the support of
Dr. Furutaka of the Research Group for Nuclear Sensing, JAEA.
• The limitation on the number of materials possible under EGS5 was eliminated. However, PHITS calculation
may still crash owing to insufficient memory when more than a few hundred materials are defined. In
addition, the maximum number of elements per material is still limited to 20.
• A bug in [t-dchain] was fixed to enable the proper consideration of successive lines. The maximum
number of regions that can be specified in [t-dchain] was extended to 500.
• A bug in [t-deposit], mesh=reg, output=deposit using the [delta-ray] section was fixed.
• The function to read tetrahedral geometry (a kind of polygonal geometry) was implemented (see section
5.6.5). This implementation was carried out under the support of HUREL, Hanyang University, Korea.
• A function to produce bremsstrahlung and electron-positron pairs via muon interactions was implemented.
8
J. M. Verbeke, C. Hagmnn, and D. Wright, “Simulation of Neutron and Gamma Ray Emission from Fission and Photofission”, UCRL-
AR-228518 (2014).
1.1 Recent Improvements 11
• A function for simulating nuclear resonance florescence (NRF) was implemented. This function enables
reproduction of the excitation of nuclei and the associate production of isomers via lower energy photons.
The nuclear resonance fluorescence model can be activated by setting ipnint=2 in the [parameters]
section.
• The sumtally function became applicable to all tallies except for [t-dpa] and [t-dchain].
• A function to read user defined cross sections was implemented (see Section 5.17).
• The algorithm to consider energy straggling of charged particles was revised to reproduce doses around the
Bragg peak more precisely.
• A new parameter idelt was introduced to reduce the computational time for particle transport simulation
in very large gas areas. When idelt=1, deltm and deltc are divided by the densities of each material.
• A function to properly calculate the uncertainty of tally results was implemented for use in conjunction with
the dump source (see Section 5.3.17).
• A new parameter pnimul was introduced to bias the photo-nuclear reaction cross section against the photo-
atomic interaction cross section.
• A bug in the calculation of the uncertainty of [t-yield] was fixed.
• Several improvements related to EGS5 were made:
– A new parameter ipegs was introduced to control PEGS5 execution before PHITS simulation.
– A new parameter imsegs was introduced to precisely simulate multiple electron scattering upon entry
of electrons into a new material. This option is original to PHITS and is not included in the original
EGS5.
– A bug in the electron transport algorithm in PHITS2.77 only (but not in PHITS 2.76 or earlier) was
fixed. The bug caused PHITS2.77 to calculate an insufficiently large range of electrons.
– The limitation on the number of materials used in PHITS, even when using EGS5, was eliminated.
• Bugs arising from the use of Intel Fortran 2015 were fixed.
From ver. 2.75, a bug in which the sumtally function does not work when using an input file that includes some
sections of tally was fixed; additionally, a bug occurring when setting e-mode=2 was corrected. (2015/02/09)
• Thread parallelization is now available even when using EGS5, i.e., negs=1. Some bugs related to EGS5
were also fixed. These improvements were performed by Mr. Masaaki Adachi of the Research Organization
for Information Science & Technology (RIST) and was supported by the Center for Computational Science
& e-Systems, Japan Atomic Energy Agency (JAEA).
• A new function to combine two (or more) tally results (“sumtally”), was implemented (from ver. 2.88, this
function became applicable to all tallies): see Sec. 6.8 for more detail. This function was developed by Mr.
Takamitsu Miura of RIST and was supported by the Center for Computational Science & e-Systems, JAEA.
• The Kurotama model was revised to enable calculation of cross sections over 5 GeV/u. See reference 9
• The gamma de-excitation data contained in trxcrd.dat were incorporated into the source files of PHITS.
Consequently, the parameter file(14) does not need to be specified in the PHITS input file even when
setting e-mode≥1 or |igamma|≥1.
From ver. 2.73, a bug producing abnormal nuclei such as di-neutrons in the calculation of nuclear reaction
models was fixed. An installed executable file of the OpenMP version of this fix is available for Windows platforms
(64-bit only); although PHITS can be executed via single processing on both 32-bit and 64-bit systems, it cannot
be executed on 32-bit OpenMP. (2014/11/05)
From ver. 2.72, a bug occurring in the setting igamma=2 was fixed and an error in which the GEM model
produces di-neutrons was repaired. Furthermore, an error in the definition of angular distribution using degree
was corrected for a-type in the [source] section. In the previous version, an incorrect interpolation caused
the use of a biased distribution in setting the a-type sub-section using degree. Finally, the definition of na and
nn in [source] using a-type was changed to prevent these parameters from being set to negative values.
(2014/10/21)
From ver. 2.71, a bug with respect to electron-positron annihilation under EGS5 was corrected. (2014/09/26)
From ver. 2.70, the following functions have been implemented. (2014/08/30)
• The transport algorithm incorporated in EGS5 (Electron Gamma Shower Version 5 10 ) for photon, electrons,
and positrons has been implemented in the PHITS code. This algorithm can be activated instead of the
original by setting negs=1 and in the [parameters] section and specifying file(20). Currently, its
OpenMP version is not available yet, and there is a limit of 100 materials that can be used at maximum when
negs=1. (From ver. 2.80, there is no such limitation.) See Sec. 5.2.20 for details. This improvement was
supported by Dr. Hirayama and Dr. Namito of KEK.
• High-energy photo-nuclear reactions of up to 1 TeV can be treated by implementing non-resonant the photo-
nuclear reaction mechanism in JAM.
• Muon-induced nuclear reactions of up to 1 TeV can be treated by considering the generation of virtual
photons from muons. This model can be activated by setting imuint=1 in the [parameters] section.
9 L. Sihver et al., Nucl. Instr. & Meth. B 334, 34-39 (2014).
10 H. Hirayama et al., SLAC-R-730 (2005) and KEK Report 2005-8 (2005).
1.1 Recent Improvements 13
• The event generator mode ver.2 was improved to precisely determine the charged particle spectra on the
basis of cross sectional data such as (n, p) and (n, α) contained in the evaluated nuclear data library. This
new event generator mode can be used by setting e-mode=2 in the [parameters] section.
• JQMD was improved to take relativistic effects into account, and an algorithm for stabilizing the initial states
of nuclei was implemented. The improved JQMD, called JQMD-2.0, can be activated by setting irqmd=1
in the [parameters] section. This improvement was performed in collaboration with Dr. D. Mancusi at
CEA/Saclay.
• Detector resolution can be considered in the event-by-event deposition energy calculation by using [t-deposit]
with output=deposit.
From ver. 2.67, the following functions were implemented. (2014/05/22)
• A geometry check function was implemented. This function applies when specifying a tally for generating
a two-dimensional view of the geometry; when double-defined or undefined regions are detected, they are
painted onto the two-dimensional view. See Sec. 10 for details.
• An extension of the event generator mode (ver.2) was implemented, resulting in an improvement of the
accuracy of event-by-event analysis for reactions induced by neutrons below 20 MeV. See Sec. 5.2.22 for
details.
• A new parameter infout was added to control the selectivity of output information in file(6) (D=phits.out).
• The current batch number appears on the console window in real time. Important error and warning messages
such as “input data file for cross section directory does not exist” are also shown in the window.
• A cone shape can be used to specify source locations by setting s-type=18, 19.
• The dumpall and dump functions for [t-cross], [t-time], and [t-product] tallies can now be used in
the restart calculation. To implement this revision, the rule for specifying file names was changed: results
written in a configuration file (.cfg) in the former version of PHITS (before 2.66) are now output in a file
specified by file=***, while dump data are output in another file named *** dmp.
• The total memory usage of PHITS (mdas) given in the param.inc file was increased to 120,000,000 (equiva-
lent to 1GB) and the maximum number of lattices in a cell was increased to 25,000,000. Using this extension
makes it possible to utilize detailed voxel phantoms such as ICRP phantom without recompiling the source
code.
From ver. 2.66, the following functions were implemented. (2014/02/21)
• An algorithm for including discrete spectra calculated using the Distorted Wave Born Approximation (DWBA)
was implemented. In several nuclear reactions induced by protons or deuterons, discrete peaks are added to
neutron and proton spectra obtained by nuclear reaction models.
• Pion production processes in photo-nuclear reactions were included by implementing ∆ and N ∗ resonances.
Thus, PHITS2.66 can treat photo-nuclear reactions up to 1 GeV(from ver. 2.70, this model is available up
to 1 TeV).
• Results in units of Gy can now be obtained in the [t-heat] tally. A bug in which “NaN” was detected in
void regions was corrected.
• A bug occurring when setting nm negative in the [source] section using e-type=2,3,5,6,7,12,15,16,
which specify the energy spectrum as a functional shape, was corrected. Additionally, a similar bug for nn
in the cases where a-type=5,6,15,16, which specify the angular distribution by shape, was also fixed.
From ver. 2.65, doses in units of Gy can be obtained in the [t-deposit] tally. Furthermore, a bug in
converting mass density to particle density in the [material] and [cell] sections was fixed. This bug caused
maximum errors of 0.6% in calculated results when neutron-rich nuclei were used. (2014/01/30)
From ver. 2.64, bugs in the photo-nuclear reaction model and in EBITEM, as well as other minor bugs, were
fixed. Furthermore, a bug in which “NaN” was detected in [t-heat] calculations because of negative values in
the probability table (p-table) was corrected. The Ace libraries were reproduced by neglecting the p-tables for the
following 130 nuclides:
14 1 RECENT IMPROVEMENTS AND DEVELOPMENT MEMBERS
As075 Ba130 Ba132 Ba134 Ba135 Ba136 Ba137 Ba140 Br079 Br081 Cd106 Cd108
Cd110 Cd111 Cd112 Cd113 Cd114 Cd116 Ce141 Ce142 Ce143 Ce144 Cf250 Fe059
Ga069 Ga071 Hf174 Hf176 Hf177 Hf178 Hf179 Hf180 Hf181 Hf182 I_127 I_129
I_130 I_131 I_135 In113 In115 Kr078 Kr080 Kr082 Kr083 Kr084 Kr085 La138
La139 La140 Mo092 Mo094 Mo095 Mo096 Mo097 Mo098 Mo099 Mo100 Nb094 Nb095
Ni059 Pr141 Pr143 Rb085 Rb086 Rb087 Rh103 Rh105 Ru096 Ru098 Ru099 Ru100
Ru101 Ru102 Ru103 Ru104 Ru105 Ru106 Sb121 Sb123 Sb124 Sb125 Sb126 Se074
Se076 Se077 Se078 Se079 Se080 Se082 Sr084 Sr086 Sr087 Sr088 Sr089 Sr090
Tc099 Te120 Te122 Te123 Te124 Te125 Te126 Te127m Te128 Te129m Te130 Te132
Xe124 Xe126 Xe128 Xe129 Xe130 Xe131 Xe132 Xe133 Xe134 Xe135 Y_089 Y_090
Y_091 Yb168 Yb170 Yb171 Yb172 Yb173 Yb174 Yb176 Zr093 Zr095
(2013/11/19)
• A new tally [t-dchain] was implemented to generate DCHAIN input files to calculate the time dependence
of activation during and after irradiation: please see Sec. 7.14 for more detail.
• Several macro bodies –Right Elliptical Cylinder (REC), Truncated Right-angle Cone (TRC), Ellipsoid (ELL),
and Wedge (WED)– were implemented.
From ver. 2.50, the following functions were implemented. (2012/9/25)
• The procedure for calculating statistical uncertainties was revised. A function to restart PHITS calculation
based on the tally results obtained by past PHITS simulations was implemented to increase the history
number when the number is not sufficient: please see Sec. 5.2.2 for more detail. This improvement was
performed by Mr. Daichi Obinata of Fujitsu Systems East Limited and was supported by the Center for
Computational Science & e-Systems, Japan Atomic Energy Agency (JAEA).
• Shared memory parallel computing using OpenMP architecture became available in PHITS, although some
restrictions remain (see Sec. 12.2). For this purpose, the source code of PHITS was drastically revised; as a
result, old Fortran compilers such as f77 and g77 can no longer be used for compiling PHITS. See Sec. 11
for details. This work was supported by Next-Generation Integrated Simulation of Living Matter, Strategic
Programs for R&D of RIKEN and by the RIKEN Special Postdoctoral Researchers (SPDR) Program. To
implement this improvement, we used K computer and the RIKEN Integrated Cluster of Clusters (RICC).
• The cross-section data for photo-nuclear reactions was revised based on JENDL Photonuclear Data File 2004
(JENDL/PD-2004). It should be noted that the current version of PHITS can handle only giant resonances
among the photo-nuclear reaction mechanisms and, therefore, it has low accuracy when calculating higher
energy photo-nuclear reactions above 20 MeV.
• The Statistical Multi-fragmentation Model (SMM) was implemented to handle the statistical decay of highly-
excited residual nuclei. SMM improves accuracy in calculating the production cross sections of light and
medium-heavy fragments in heavy ion collisions.
• Intra-Nuclear Cascade of Liège (INCL) was implemented as the default model for simulating nuclear reac-
tions induced by neutrons, protons, pions, deuterons, tritons, 3 He, and 4 He particles at intermediate energies.
This improvement was supported by Dr. Joseph Cugnon of the University of Liège and Dr. Davide Mancusi,
Dr. Alain Boudard, Dr. Jean-Christophe David, and Dr. Sylvie Leray of CEA/Saclay under a collaboration
between CEA/Saclay and JAEA.
• The KUROTAMA model, which gives nucleon-nucleus and nucleus-nucleus reaction cross sections, was
implemented. This improvement was supported by Dr. Akihisa Kohama of RIKEN, Dr. Kei Iida of Kochi
University, and Dr. Kazuhiro Oyamatsu of Aichi Shukutoku University.
• The Intra-Nuclear Cascade with Emission of Light Fragment (INC-ELF) tool was implemented based on the
work of the Uozumi research group under a collaboration between Kyushu University and JAEA.
• The user-defined [t-userdefined] tally was introduced to deduce user specific quantities from PHITS
simulations. PHITS must be recompiled to use this tally; see Sec. 7.18 for details.
• The neutron kerma factors for several nuclei, such as 35 Cl, were revised. The photo- and electro-atomic data
libraries were recreated based on JENDL-4.0 and the Livermore Evaluated Electron Data Library (EEDL),
respectively.
From ver. 2.30, the radiation damage model for calculating Displacement Per Atom (DPA) in PHITS was
improved through the application of screened Coulomb scattering. The [multiplier] section for use in the
[t-track] section was also added. (2011/8/18)
From ver. 2.28, it is possible to use the dumpall and dump options for [t-cross], [t-time], and [t-product]
tallies in MPI parallel computing. When these options are used in parallel computing, PHITS makes (PE−1) files
for writing the dump information from each node, where PE is the total number of used Processor Elements. PHITS
can also read the dump files under parallel computing.
From ver. 2.26, a function to generate knocked-out electrons (so-called δ-rays) produced along the trajectories
of charged particles was added. Setting the threshold energy for each region in the [delta ray] section enables
the explicit transport of δ-rays above the threshold energy.
16 1 RECENT IMPROVEMENTS AND DEVELOPMENT MEMBERS
Tatsuhiko Sato, Yosuke Iwamoto, Shintaro Hashimoto, Tatsuhiko Ogawa, Takuya Furuta, Shinichiro Abe,
Takeshi Kai, Pi-En Tsai, Norihiro Matsuda, Yusuke Matsuya, and Hunter Ratliff
Japan Atomic Energy Agency (JAEA).
Hiroshi Iwase,
High Energy Accelerator Research Organization (KEK).
Nobuhiro Shigyo,
Kyushu University.
Lembit Sihver,
Vienna University of Technology, Austria.
Hiroshi Takada, Shin-ichro Meigo, Makoto Teshigawara, Fujio Maekawa, Masahide Harada, Yujiro Ikeda,
Yukio Sakamoto, Hiroshi Nakashima, Tokio Fukahori, Keisuke Okumura, Tetsuya Kai, and Shusaku Noda,
Japan Atomic Energy Agency (JAEA).
Satoshi Chiba,
Tokyo Institute of Technology (TITech).
Takashi Nakamura,
Tohoku University.
Davide Mancusi,
Chalmers University, Sweden.
• T. Sato, Y. Iwamoto, S. Hashimoto, T. Ogawa, T. Furuta, S. Abe, T. Kai, P.-E. Tsai, N. Matsuda, H. Iwase, H.
Shigyo, L. Sihver, and K. Niita, Features of Particle and Heavy Ion Transport code System (PHITS) version
3.02, J. Nucl. Sci. Technol. 55, 684-690 (2018).
• H. Iwase, K. Niita, T.Nakamura, Development of general purpose particle and heavy ion transport Monte
Carlo code. J Nucl Sci Technol. 39, 1142-1151 (2002).
• K. Niita, T. Sato, H. Iwase, H. Nose, H. Nakashima and L. Sihver, Particle and Heavy Ion Transport Code
System; PHITS, Radiat. Meas. 41, 1080-1090 (2006).
• K. Niita, N. Matsuda, Y. Iwamoto, H. Iwase, T. Sato, H. Nakashima, Y. Sakamoto and L. Sihver, PHITS:
Particle and Heavy Ion Transport code System, Version 2.23, JAEA-Data/Code 2010-022 (2010).
• K. Niita, H. Iwase, T. Sato, Y. Iwamoto, N. Matsuda, Y. Sakamoto, H. Nakashima, D. Mancusi and L. Sihver,
Recent developments of the PHITS code, Prog. Nucl. Sci. Technol. 1, 1-6 (2011).
(6) To check whether PHITS has been installed properly, right click “\phits\lecture\basic\lec01\lec01.inp” and
select “send to” → “PHITS.”
(Note #1) The names of the installation files and folders and must contain no space characters; otherwise instal-
lation and execution will fail.
(Note #2) If you enter an incorrect password, please delete the “phits” folder first, and then run the installer again.
(3) It creates shortcuts for three batch files—“phits.bat” and “angel.bat” in the “\phits\bin\” folder and “dchain.bat”
in the \dchain-sp\bin\” folder— in the “sendto” folder.
(4) It revises the first line of the nuclear data list file “xsdir.jnd” in the “\phits \data\” folder as datapath=
‘the installation folder’+ ‘\phits\XS\’.
Right click the PHITS input file in a File Explorer, select “send to → PHITS” . As the shortcut for “phits.bat” in
the “\phits\bin\” folder has been created during installation, the PHITS code will be initiated and start simulations.
The shared-memory parallel computing using OpenMP can be executed by adding $OMP=N (N is the number
of CPU cores to be used) before the first section in the PHITS input file. If N = 0, all cores in the computer are
used. If N = 1, the parallel computing is not used. From version 2.73, the executable file of the OpenMP version
coming along with the PHITS package is available only for 64-bit Windows systems.
The MPI version of PHITS can be also executed by added $MPI=M in the same manner as OpenMP, but the
installation of a MPI protocol (MPICH2) is required. Please see Sec. 12.1.1 in more detail.
PHITS can be executed by command lines in Command Prompt (also known as cmd.exe or cmd), the command-
line interpreter on Windows operating systems as shown in Figure 2.1.
To execute PHITS, use the “cd” command to go to the directory of where the input is, and then type the
following commands in the terminal:
phits.bat your_input.inp
where “your input.inp” is your input file name (e.g., “lec01.inp”). As command histories can be retrieved by
pressing the ↑ key in the terminal, it is convenient to use the same input file name when you want to repeatedly
execute PHITS.
• Notepad++ (https://notepad-plus-plus.org/).
20 2 INSTALLATION AND EXECUTION OF PHITS
For details of the installation of Ghostscript and GSview, see the following web pages:
• Ghostscript (http://www.ghostscript.com/)
• GSview (http://pages.cs.wisc.edu/˜ghost/gsview/index.htm).
(2) Select “Automatic” for “select installation mode” (See Fig. 2.2). “Manual” should be selected only when
the “Automatic” mode fails. In that case, please refer to the “README-eng.pdf” file in the “/mac/” folder.
(3) Specify the folder to install PHITS in. It is recommended to select the folder with user’s account name (eg,
iwamoto). Then click the “choose” button (See Fig. 2.3).
(4) A “/phits/” folder will be created under the account name. All the code content, including the executable
files, source code, and documentation (manuals, lecture notes, input examples) will be copied to the specified
folder; the process may take several minutes.
(Note #1) If a wrong password is typed during the installation, the message of “installation is completed” will
immediately pop out, and the PHITS icon will appear on the Dock. However, no file is copied to the
hard disk, and PHITS cannot be executed. In that case, please go back to the procedure (1) and type
the correct password.
(Note #2) If the “/phits/” folder is moved to another folder after installation, PHITS will not work.
(Note #3) If a “/phits/” folder already exists in the specified folder, the old “/phits/” folder will be automatically
renamed from “/phits/” to “/phits[date.time]/” of that moment.
(Note #4) If the names of the files and folders to be installed contain a blank character, the PHITS installation
will fail.
Drag the icon of the PHITS input file and drop it on the blue PHITS icon on the Dock (See Fig. 2.4). For
test calculation, click the Finder icon on the Dock and open the folder of “/phits/lecture/basic/lec01/.” Then, drag
“lec01.inp” and drop it on the PHITS icon. A new terminal window will appear, and the calculation condition will
be outputted on it. The calculated results will be shown in the same folder as the input file. As command histories
can be retrieved by pressing the ↑ key in the terminal, it is convenient to use the same input file name when you
want to repeatedly execute PHITS.
The shared-memory parallel computing using OpenMP can be executed by adding $OMP=N (N is the number
of CPU cores to be used) before the first section in a PHITS input file. If N = 0, all cores in the computer are used.
If N = 1, the parallel computing is not used.
To execute ANGEL or DCHAIN, drag the icons of the output file generated by the PHITS tally and drop it
onto the red ANGEL or the green DCHAIN icon on the Dock. Note that the PHITS icon can identify whether the
input file is in PHITS, ANGEL, or DCHAIN format, so dragging an ANGEL or DCHAIN input to the PHITS icon
would also work.
After installing PHITS by using “PHITS Installer,”PHITS can be executed via terminal commands. To launch
terminal, select the following items:
To execute PHITS, use the “cd” command to go to the directory of where the input is, and then type the
following commands in the terminal:
phits.sh your_input.inp
where “your input.inp” is your input file name (e.g., “lec01.inp”). As command histories can be retrieved by
pressing the ↑ key in the terminal, it is convenient to use the same input file name when you want to repeatedly
execute PHITS.
ANGEL and DCHAIN can also be executed via the terminal. To execute ANGEL, type the following command
in the Terminal:
angel_mac.sh angel.inp
where “angel.inp” is the input file name (tally output of PHITS. e.g., “track xz.out”).
To execute DCHAIN, type the following command in the terminal:
dchain.sh dchain.out
where “dchain.out” is the name of the DCHAIN input file (the file name is designated in the [t-dchain] section
of the PHITS input).
where “/PATH-TO-PHITS” should be changed to the name of the folder of which PHITS is copied to (e.g.,
/Users/iwamoto/). If you do not know where the folder is, type in the following command in the Terminal:
2.3 Installation and Execution on Linux OS 23
Figure 2.6: Example of PHITS execution via Terminal with the initial setting.
To execute DCHAIN, it is necessary to set PATH to the folder with the DCHAIN execution file. The method
for setting the PATH for DCHAIN is the same as that for PHITS:
echo export PATH=/PATH-TO-PHITS/phits/dchain-sp/bin:${PATH} >> ˜/.bash_profile
source ˜/.bash_profile
where “/PATH-TO-PHITS” should be changed to the directory of which PHITS is copied to (e.g., /Users/iwamoto/).
Here “your input.inp” is the PHITS input file name (e.g., lec01.inp). As command histories can be retrieved
by pressing the ↑ key in the terminal, it is convenient to use the same input file name when you want to repeatedly
execute PHITS.
The shared-memory parallel computing using OpenMP can be executed by adding $OMP=N (N is the number
of CPU cores to be used) before the first section in a PHITS input file. If N = 0, all cores in the computer are used.
If N = 1, the parallel computing is not used.
The MPI version of PHITS can be also executed by added $MPI=M in the same manner as OpenMP, but it
is required to pre-install OpenMPI. Please see the OpenMPI website (https://www.open-mpi.org/) for more
detail.
The execution of ANGEL and DCHAN-SP can be done in a similar fashion. ANGEL can be executed by
angel.sh angel.inp
where “angel.inp” is the input file name (tally output of PHITS. e.g., “track xz.out”).
To execute DCHAIN, type the following command in the terminal:
dchain.sh dchain.out
where “dchain.out” is the name of the DCHAIN input file (the file name is designated in the [t-dchain] section
of the PHITS input).
Note that if errors, such as no permission, occur when executing PHITS, it might be because the execution
permission has not been added to the executable file. For such a situation, go to “phits/bin/” or where the executable
file is located in the terminal, and type the following command for authorization:
chmod +x XXX
Here “XXX” is the name of the executable file (e.g., phits309.exe).
The PHITS code can be executed on Linux without using a shell by the following command:
phitsXXX.exe < your_input.inp
where “phitsXXX.exe” is the PHITS executable file and XXX is the version number, and “your input.inp” is the
input file for PHITS calculation.
(Note #1) If additional files are used with the infl: parameter when PHITS is executed with this method. In
this case, the following text should be written in the first line of the main input file:
file = phits.inp
See Sec. 4.3 for further discussion of infl:.
(Note #2) To perform a PHITS calculation using distributed-memory parallel computing, the name of the input
file must be specified in the first line of the “phits.in” file, which locates in the same folder containing
the executable file, by the following manner:
file = input.inp
The name of “phits.in” is fixed and cannot be changed arbitrarily. See the example in Sec. 12.1.3 for
more detail.
25
(1) Check whether or not the file specified by resfile in each tally section exists. The default file name of the
resfile is that given by file parameter.
(2) If there is no resfile for a tally, it is regarded to be new. If no resfile can be found for any tally, a new
calculation is begun with istdev=|istdev|.
(3) If resfile exists, PHITS reads information from the file on the standard deviation mode istdev, to-
tal weight resc2, total history number resc3, history number per batch maxcas, the next random seed
rijklst, and the results and relative errors of the past calculation.
(4) The tally parameters given in the current and past PHITS input files are then checked for consistency. If they
are not consistent with each other, PHITS stops the calculation and outputs an error message. It should be
noted that not all tally parameters are checked for consistency in this process.
(5) (In batch standard deviation mode only) The consistency of istdev and maxcas among the resfiles is
checked. If they are consistent, the restart calculation is performed using these values. If an inconsistency is
found, the calculation is stopped.
(6) The initial random seed is changed to the value of rijklst obtained from the first resfiles. If rijklst
differs by resfile, a warning message is output.
(7) Upon finishing the restart calculation, the tally results are output to the file specified by file=. If resfile
is not specified, the past tally results are overwritten.
Important notice:
I. All past tally results should be calculated in the same standard deviation mode: i.e., istdev should be the
same in all resfile.
II. The maxcas written in the input file is not used in the restart calculation in batch standard deviation mode.
III. Except for those given in the tally sections, the consistencies of input parameters are not checked by the
PHITS program. If they are inconsistent with the previous setting, the tally results might be incorrect even
if no error messages show up.
Here, the value on the left is the number of remaining batches at the moment. The remaining batches can be reduced
by editing the value and saving batch.out. For example, when the value is changed to “3” the PHITS execution
will be terminated after the calculation of three batches is finished. Changing the value to “0” terminates the code
11 Until ver. 2.85, the name of this file had been named “batch.now.”
26 3 RESTART AND TERMINATE PHITS CALCULATIONS
execution right after the calculation of that batch is completed. This function can be useful in the way explained
below.
The parameter itall can be used together with “batch.out”. If itall=0(default) or itall=1 is set in the
[parameters] section, PHITS will update the calculation results (tally output) at the end of each batch. With
itall=1, the image (*.eps) files will also be updated (See Sec. 6.7.17). In parallel computing mode, the results
are updated every batch × ( PE −1 ). Using these functions enables terminating PHITS calculations at any time
with the latest results updated.
From ver. 2.86, the file name of batch.out can be modified by setting file(22) in the [parameters] section.
Changing the name of each input file enables multiple executions of PHITS in a common directory. Note that this
function is not available if [t-dchain] is set in the input files, because the same file name, “n.flux,” is used.
The value of rijk written in the batch.out file is the initial random number of the current batch. Thus, for
example, in cases of unsuccessful termination of PHITS, it is possible to reproduce the calculation of the specified
batch using the value of rijk.
1: anatally start
2: ix = 89 91
3: iz = 61 81 101
4: iy = 1
5: ipart = 1
6: anatally end
“anatally” subsection should be defined between the lines of anatally start and anatally end written in
the tally section. If anatally subsection has no content, meaning only these two lines are written, tally results at all
mesh points are output.
ix,iz,iy are parameters to specify mesh points defined by x-type, z-type, y-type subsections, respec-
tively. In this example, the 89th and 91st points of the x-mesh are specified. The specified points are given by the
combination of mesh points of each parameter: in the above case, the six points, the product of two (89, 91) and
three points (61, 81, 101), are specified. ipart=1 means the first particle set by part=. For example, only tally
results for proton are output in the case that part = proton neutoron is set.
There are the following ten kinds of parameters to specify the mesh point: ireg: region (cell), ix, iy, iz,
ir, ie, it, ia: x-, y-, z-, r-, e-, t-, a-type subsections, ipart: part parameter, and imul:
multiplier parameter. When a parameter is not specified, results at all mesh points about its parameter are
output. all can be used to output results at all points.
27
4 Input File
PHITS input consists of a number of sections that are listed in Tables 4.1 and 4.2. Each section begins with
a [Section Name]. A maximum of four blanks can be placed between the line head and the declaration of
[Section Name]; a configuration with (more than four blanks) [Section Name] will not be recognized as the
beginning of a section, and the following code will be regarded as part of the previous section.
4.1 Sections
Table 4.1 and 4.2 shows the sections used in PHITS.
name description
[title] Title
[parameters] Various types of parameters
[source] Source definition
[material] Material definition
[surface] Surface definition
[cell] Cell definition
[transform] Definition of the coordinate transform
[temperature] Cell temperature definition
[mat time change] Definition of time-dependent materials
[magnetic field] Magnetic field definition
[electro magnetic field] Electro-magnetic field definition
[delta ray] Definition of δ-ray production
[track structure] Definition for using the track-structure simulation mode.
[super mirror] Definition of super mirror for low-energy neutrons
[elastic option] Definition of elastic scattering options for low-energy neutrons
[data max] Definition of maximum energies (dmax) of each nucleus for using data libraries
[frag data] Definition of user defined cross sections
[importance] Definition of region’s importances
[weight window] Definition of region’s weight windows
[ww bias] Definition of values to bias in [weight window]
[forced collisions] Forced collision definition
[volume] Region volume definition
[multiplier] Multiplier definition
[mat name color] Material name and color definition for graphical plot
[reg name] Region name definition for graphical plot
[counter] Counter definition
[timer] Timer and clock definition
28 4 INPUT FILE
name description
[t-track] Particle fluence in a given region.
[t-cross] Particle fluence/current across a given surface.
[t-point] Particle fluence at a given point.
[t-deposit] Deposit energy in a given region.
[t-deposit2] Deposit energies in two given regions.
[t-heat] Heat generation in a given region. (Not recommended12 )
[t-yield] Residual nuclei yields in a given region.
[t-product] Reaction products in a given region.
[t-dpa] Displacement Per Atom (DPA) in a given region.
[t-let] LET distribution in a given region.
[t-sed] Microdosimetric quantity distribution in a given region.
[t-time] Time information of particle in a given region.
[t-interact] (former name [t-star]) Number of interactions occurred in a given region.
[t-dchain] Residual nuclide yields (for the use of DCHAIN).
[t-wwg] Output parameters for [weight window].
[t-wwbg] Output parameters for [ww bias].
[t-volume] Automatic calculation of the volume for a given region.
[t-userdefined] Any quantities defined by users.
[t-gshow] 2D geometry visualization.
[t-rshow] 2D geometry visualization with physical quantities.
[t-3dshow] 3D geometry visualization.
[end] End of input file.
Note that PHITS does not read any input information written below the [end] section.
Tab
A tab is replaced by eight blanks.
Line connecting
The maximum number of characters that can be written in a line is 200. If ‘\’ is added at the end of a line,
the next line is considered to be a continued line. Multiple lines can be used to write input data using this
method, but ‘\’ is not necessary in the [surface] and [cell] sections, in which lines are automatically
connected without the use of an additional symbol. Note that more than four blanks are required at the
beginning of a continued line.
Line dividing
Several short lines can be displayed in one line, and divided by ‘;’ as follows:
idbg = 0; ibod = 1; naz = 0
However, this function is not available when the format is defined in the mesh description.
Comment marks
The following comment marks can be used: #, %, !, $ (recommand). A comment out is effective starting
from the comment mark to the end of the line. Note that in the [surface] and [cell] sections, only ‘$’
12 Until ver. 3.04, the [t-heat] tally had been used to calculate deposit energy using the kerma approximation, because the [t-deposit]
tally did not have the option.
4.3 Inserting files 29
can be used as a comment mark. Also, ‘c ’cannot be used as comment marks in the [material] section
by the default setting13 . To use ‘c’ as comment marks in the [material] section, it is necessary to set set
icommat=1 in [parameters] section14 .
Blank lines
Blank lines and lines beginning with a comment mark are skipped.
Skip all
q: can be used as a terminator of an input file; this works the same way as using [end].
infl: { f ile.name } [ n1 − n2 ]
The name of the file to be inserted should be enclosed in curly brackets ‘{ },’ and the number of lines from n1 to n2
of the file should be enclosed in square brackets ‘[ ].’ If there is no ‘[ ],’ PHITS includes all lines of the specified
file.
The following style can be used to specify line numbers: [n1 -] and [-n2 ]. These expressions specify the range
from the n1 th line to the end, and from the initial line to the n2 th line, respectively. Inserted files can be nested
more than once. After reading the end of the including file, the reading process returns to its parent file.
Care should be taken in using the command-line interpreter (Command prompt) to execute PHITS. If infl:
is used, the following text should be written in the first line of the input file:
file = phits.inp
The set: definition can be written anywhere. Note that there should be no space between ci and [ in the format
ci[]. User-defined variables can be used as numerical values in input file, and the variables can be re-defined at
any time, with the values retained until they are re-defined. In the third case of the above example (c3), another
variable c1 is called in the definition; in this case, the value held by the variable c1 at that time is used. Therefore,
13 Prior to version 2.89, ‘c’ can be used as comment marks in the [material] section. If ‘c’ followed by a blank (⊔) is placed before
the 6th column, it is considered to be a comment line. Thus, if the natural isotope of carbon in the [material] section is defined as ‘C’, the
definition line may be treated as a comment line and be skipped; in such case, carbon should be defined by 6000.
14 Note that the [parameters] section with icommat=1 should be written above (before) the [material] section.
30 4 INPUT FILE
even if c1 is re-defined following the definition of c3, the value of c3 is not changed. Note that, by default, pi is
set to the value of π.
The set: definition is ignored in sumtally subsection.
File 1: param.inc
1: ************************************************************************
2: * *
3: * ’param.inc’ *
4: * *
5: ************************************************************************
6:
7: parameter ( mdas = 80000000 )
8: parameter ( kvlmax = 3000 )
9: parameter ( kvmmax = 1000000 )
10: parameter ( itlmax = 200 )
11: parameter ( inevt = 70 )
12: parameter ( isrc = 500 )
13: parameter ( latmax = 20000000 )
14: parameter ( nbchmax= 10000 )
15:
16: common /mdasa/ das( mdas )
17: common /mdasb/ mmmax
18:
19: *----------------------------------------------------------------------*
20: * *
21: * mdas : total memory * 8 = byte *
22: * mmmax : maximum number of total array *
23: * *
24: * kvlmax : maximum number of regions, cell and material *
25: * kvmmax : maximum number of id for regions, cel and material *
26: * *
27: * itlmax : number of maximum tally entry *
28: * inevt : number of collision type for summary *
29: * isrc : number of multi-source *
30: * latmax : maximum number of lattice in a cell + 1 *
31: * nbchmax: maximum number of batch assigned to parallel MPI node *
32: * *
33: *----------------------------------------------------------------------*
34 5 SECTIONS FORMAT
5 Sections format
5.1 [ Title ] section
In the [title] section, the titles of calculations can be defined. Any number of title lines is allowed. Blank
lines are skipped in this section.
[ Title ]
This is a test calculation of PHITS.
Any number of title lines is allowed.
..........
5.2 [ Parameters ] section 35
[ Parameters ]
para1 = number | file.name
para2 = number | file.name
..........
The order of parameters can be changed. As each parameter has a default value, undefined parameters use the
default values.
Parameters and default values are listed in the tables shown below. (D= ) indicates the default value.
The function of nuclear reaction calculation specified as icntl=1 is still under development.
By setting icntl=12, PHITS reads the previous event-by-event calculation result from a dumpall file created
when the dumpall=1 option was activated. All of the transport events are reproduced by the dumpall file without
being re-calculated again. Thus, maxcas and maxbch cannot be changed. This functionality is suitable for tallying
different physics quantanties with the same simulation setup, especially when such a simulation setup is computa-
tional time consuming. However, it should be noted that calculation with dumpall=1 may create a huge dumpall
file. Please refer to 5.2.21 for more details.
By setting icntl=13, two (or more) tally results can be summed: see Sec. 6.8 for further detail.
By setting icntl=14 with [t-volume], automatic calculations to obtain volumes of specified cells can be
performed. See Sec. 7.17 in more detail.
By setting icntl=15 with [t-wwbg], automatic calculations to obtain parameters of [ww bias]. See Sec.
7.16 for further detail.
36 5 SECTIONS FORMAT
In the distributed-memory parallel calculation, the number of batches should be an integer multiple of NPE − 1,
where NPE is the total number of Processing Element (PE). Otherwise, PHITS will automatically convert maxbch
to an integer multiple of NPE − 1, and adjust maxcas such that the total number of histories becomes close to or
the same as the given total number of histories. In this case, some comments will be output at the end of an input
echo.
Time limit of a PHITS calculation can be activated by assigning timeout a positive value. If the CPU time
reaches timeout in the middle of a batch, PHITS will finish the calculation of all histories in that batch, and then
terminates the code. In the distributed-memory parallel computing, timeout is ruled by the sum of all CPU time.
Note that the function of timeout can be used only when the computer’s CPU time is correctly retrieved.
The procedure for calculating statistical uncertainties was revised from version 2.50: a function to restart
PHITS calculation based on the tally results obtained by past PHITS simulations has been implemented to increase
the total history number and then decrease the statistical uncertainties of the results. In this mode, the initial random
seed is also read from the past tally file.
To calculate statistical uncertainties, two modes can be selected –“batch standard deviation mode” and “history
standard deviation mode”– which calculate standard deviations of tally results by batch and by history, respectively.
5.2 [ Parameters ] section 37
If values given by these parameters are referred to the upper boundaries of a range, then the given values are
not included in the range. If values given by the parameters are referred to the lower boundaries of a range, then
the given values are included in the range. For example, a proton right at the emin(1) energy is not cut-off as the
cut-off range is ⩾ 0 and < emin.
When the kinetic energy of a transport particle is less than emin, the energy cut-off is performed and then its
transport calculation is stopped. In this case, the residual kinetic energy is deposited locally at that place, and the
particle decays in accordance with decay modes shown in Table 4.5 except for neutrons. If the particle species is
positron, annihilation occurs instead of decay.
PHITS uses libraries in the energy region emin < energy < dmax. If emin > dmax is set, no libraries are
used. The upper energy limits for the use of data libraries are 20 MeV and 100 GeV, respectively for neutron and
photon. When EGS5 is not used, the upper energy limits for electrons and positrons are 10 GeV. The default setting
of emin(12-14) is automatically adjusted by the negs option; e.g., emin(14)=0.001 if negs=-1. The default
settings of emin(2) and dmax(2) are automatically adjusted by the nucdata option; e.g., emin(2)=1.0e-11 if
nucdata=1. See Table 5.5 for both settings in more details.
The range table of charged particles is set within esmin < energy < esmax. To use a significantly higher
energy, the user should set esmax.
The minimum cut-off energy for charged particles, emin, cannot be set lower than esmin. In such cases, emin
is automatically adjusted to esmin.
etsmin>1e-9 (1meV) can be set. But the setting below 1e-6 (1 eV) is not recommend because computational
time becomes extremely long.
etsmax>1e-3 (1keV) must be set. The setting this parameter below 0.1 (100 keV) is recommend, otherwise
the computational time becomes extremely long.
For the track structure mode, emin(12) and emin(13) should be set to 1.0e-3, and EGS5 should be activated
(negs=1).
Below eqmdmin, the nuclear reactions of d, t,3 He, 4 He, and nuclei are not treated by JQMD. As the applicability
of JQMD is restricted in the low energy region and the range of nuclei is very low in the normal material, it is not
necessary to consider the low energy reactions of nuclei for the usual case. As a default, high energy heavy
ion collisions are treated by JAMQMD above 3.0 GeV/u. This switching energy can be changed by changing e
5.2 [ Parameters ] section 39
jamqmd. It is possible to calculate even nucleon-induced collisions in JAMQMD by changing eqmdnu, ejamnu,
and ejamqmd.
INCL (Intra-Nuclear Cascade of Liège) is a nuclear reaction model for nucleon (proton and neutron), pion, and
light-ion (d, t,3 He, or 4 He) induced reactions. From version 2.50, INCL is used by default for these reactions if
the nuclear reaction model is not explicitly specified. Before using INCL results in a publication, please refer to a
document 15 in the footnotes.
Intra-Nuclear Cascade with Emission of Light Fragment (INC-ELF) is a nuclear reaction model for nucleon-
induced reactions. Before using results obtained by INC-ELF in a publication, please refer a document16 in the
footnotes.
JQMD and JQMD-2.0 are nuclear reaction models; in particular, they can be used to describe heavy-ion in-
duced reactions. In PHITS Ver. 2.7 and later, JQMD-2.0 can be used as an alternative to the conventional JQMD.
JQMD-2.017 describes reactions - particularly peripheral collisions - more reasonably than JQMD. Users should
note that JQMD-2.0 may take more than twice the CPU time required by JQMD.
15 A. Boudard, J. Cugnon, J.-C. David, S. Leray, and D. Mancusi, Phys. Rev C87, 014606 (2013).
16 Y. Sawada, Y. Uozumi, S. Nogamine, T. Yamada, Y. Iwamoto, T. Sato, and K. Niita, Nucl. Instr. & Meth. B 291, 38-44 (2012).
17 T. Ogawa, T. Sato, S. Hashimoto, D. Satoh, S. Tsuda, and K. Niita, Phys. Rev C92, 024614 (2015).
40 5 SECTIONS FORMAT
The cut-off time for each particle should be specified as tmax(i) (in units of [nsec]). After arrival at the cut-off
time, the particle is killed; although this is not effective in the context of high energy particle transport, it is useful
for low energy particle transport calculation.
A particle’s weight is affected by the importance, forced collisions, implicit captures, and weight window
functions. When the weight is lower than the user-defined weight cut off, a Russian roulette method is applied to
determine whether or not the particle is killed. This function is not available for particles defined in the weight
window.
Under the Russian roulette method, when the weight wgt is lower than the product, wc2× R, of wc2 and the
ratio R of the importances at the source and current points (i.e., when wgt < wc2 × R), the particle survives with a
probability wgt /(wc1×R), which is a function of the particle’s own weight, WGT. If the particle survives, its weight
is changed to wgt = wc1 × R. If wc1 and wc2 are negative, they are respectively set to |wc1| = swtm(i) and
|wc2| = swtm(i).
Any particles or regions for which the user has not set importances are given default importances of 1.
In this case of iwwbias=1, the products of the multiplication are output in the input echo of [weight window],
and [ww bias] with off is output. If an input file without [ww bias] is used, all values of [ww bias] in the
input echo are set to 1.
42 5 SECTIONS FORMAT
18 H. Koura, T. Tachibana, M. Uno, and M. Yamada, RIKEN Accel. Prog. Rep. 36 (2003) 9: H. Koura, TOURS Symposium on Nuclear
For the nuclear resonance fluorescence considered in ipnint=2, polarization of incident photons can be spec-
ified using sx,sy,sz in the [source] section. The angular distribution of the scattered photons is determined
with regard to the polarization.
If a particle with a decay channel (See Table 4.5) has an energy lower than the cut-off, the particle decays
completely. Negative-charged pions (π− ) with the setting of npidk=0 are forced to be absorbed by nucleus. If π−
is not able to be absorbed in the program, the particle decays (to prevent an infinite calculation loop).
The KUROTAMA model covers a wide energy range of projectiles in nucleon-nucleus and nucleus-nucleus
reaction cross sections. See the paper 24 for more details, and please cite the reference if your publication is based
on the KUROTAMA model.
In the icrdm=1 setting, the MWO formula reproduces reaction cross sections of deuteron-induced reactions
for incident energies below 1 GeV, and for target nuclei no lighter than C-12. See the reference 25 for more details;
please cite this document in published results based the MWO model.
For the icxspi setting, the Hashimoto’s formula has been used as the default model for calculating pion-
induced reaction cross sections since version 2.86. This is an empirical formula that reproduces cross section
experimental data better than the geometrical formula specified by icxspi=0.
If iidfs=1 is specified, the multiplicity ν and energy spectra of neutrons from neutron-induced fission taken
from reference 26 are used instead of the nuclear library data for the following 18 nuclei: U-238, Pu-238, Pu-
240, Pu-242, Cm-242, Cm-244, Cf-252, Th-232, U-232, U-233, U-234, U-235, U-236, Np-237, Pu-239, Pu-241,
Am-241, and Bk-249.
24 K. Iida, A. Kohama, and K. Oyamatsu, J. Phys. Soc. Japan 76, 044201 (2007), and L. Sihver et al., Nucl. Instr. & Meth. B 334, 34-39
(2014).
25 K. Minomo, K. Washiyama, and K. Ogata, J. Nucl. Sci. Technol. 54, 127-130 (2017).
26 J. M. Verbeke, C. Hagmnn, and D. Wright, UCRL-AR-228518 (2014).
5.2 [ Parameters ] section 45
With the idwba=1 setting, the discrete spectra calculated by the DWBA are added to the neutron and proton
spectra obtained using other nuclear reaction models for the following reactions:
7
Li(p, n)7 Be reactions at 30–400 MeV
9
Be(p, n)9 B reactions at 10–50 MeV
6,7
Li(d, n)7,8 Be and 6,7 Li(d, p)7,8 Li reactions at 10–50 MeV
9
Be(d, n)10 B and 9 Be(d, p)10 Be reactions at 5–25 MeV
12,13
C(d, n)13,14 and 12,13 C(d, p)13,14 C reactions at 10–50 MeV
See the reference 27 for more details.
28 The default was ndedx=0 until PHITS ver. 2.00, and ndedx=2 from ver. 2.01 to ver. 2.85.
29 T.M. Armstrong and K.C. Chandler, ORNL Report, ORNL-4869 (1973).
30 About ATIMA, see the web site: https://web-docs.gsi.de/˜weick/atima/
31 When describing a scattering process on thin films less than 1cm, delt0 should be set to 1/10 of its thickness.
√
X/X
32 σ = S 2 pβ 0 [1 + ϵ log10 (e) loge (X/X0 )]: Eq.(4) in G.R. Lynch and O.I. Dahl, Nucl. Instrum. Methods Phys. Res, B 58, 6-10 (1991).
33 About these models, see the web site: http://www.dnp.fmph.uniba.sk/cernlib/asdoc/geantold/H2GEANTPHYS332.html
5.2 [ Parameters ] section 47
From version 2.85, the algorithm for calculating stopping power with ATIMA in PHITS was improved and
speeded up. In the old algorithm, calculation of range and stopping power was always performed every time when
a new charged particle was produced or a transporting particle entered a new material. The new algorithm creates
a database for each combination of transporting particle and material when a new particle-material combination
appears, and look up the range and stopping power in the database the next time, instead of calling the high
computational-cost routine ATIMA. As such, PHITS simulation using ATIMA is compatible with SPAR in terms
of calculation time but with higher accuracy.
Starting from ver. 2.97, the setting of ndedx=3 can be used for nuclei with the atomic number of 93 ≤ Z ≤ 97
(from Np to Bk) 34 . Ionization potentials and density correction parameters needed in calculating nuclear stopping
powers for those nuclei are adopted from the literature 35 , and SPAR is used in the calculation of electronic
stopping power.
The setting of ifixchg = 1 is not appropriate in most circumstances. The charge state of ions changes along
their traveling paths in a material owing to attachment and disattachment of electrons. Thus, this setting only suits
calculations of energy losses in a thin foil or gas.
34 Prior to ver. 2.96, ATIMA cannot be used for nuclei with Z > 92 (U). For those cases, use SPAR by setting ndedx=2.
35 Table I of R.M.Sternheimer, Atomic data and nuclear data tables, 30, 261-271 (1984).
48 5 SECTIONS FORMAT
gravx, gravy, gravz represent the directions of gravity; the gravitational force is effective for neutrons at
energies below 1 eV. For example, if gravx=1, gravy=0, gravz=0, the direction of the gravitational force is
negative along the x-axis.
The event generator mode (e-mode=1,2) is essential for calculation of event-by-event quantities, such as
detector signals, residual recoiled nuclides, lineal energies, attributed to neutrons below 20 MeV. The simple
sampling mode (e-mode=0) reproduces secondary neutron spectra given by the nuclear data library better than
e-mode=1,2. Note that e-mode=0 does not consider the conservation of energy and momentum. See Sec. 5.2.22
for further discussion of the use.
By setting ntrnore = 1, following reactions are considered; 1 H(ν̄e , e+ )n, 2 H(ν̄e , ν̄e′ )np, 2 H(νe , e− )2p, 2 H(νe , νe′ )np,
and elastic scattering with electrons. Above 20 MeV, the cross sections of some reactions channels are extrapo-
lated. Note that, the reaction channels above 150 MeV (e.g. charge-current reactions of µ-neutrinos) are not
considered. Table 5.12 shows neutrino reaction systems considered in the current version of PHITS. In the case of
that considered reaction channel, ∞ or values are shown as an energy upper-limit.
Table 5.12: List of neutrino reaction systems considered and energies above which cross sections are extrapolated.
×: unimplemented, -: reaction is not existing.
The infout parameter controls output information in the summary file, file(6). Using infout, the output
information can be selected by the user. infout information is divided into the following six categories:
I Basic information – LOGO (excluding the information on PHITS developers), calculation process, source,
geometry error, random seed, and CPU summary.
II Input echo.
III Information on memory usage and batch.
IV Information on transport particles.
V Detailed information – variance reduction, number of scattered particles for each region, information for
each material.
(3) Information on memory usage and composition for geometry, material, tally, bank, etc. (Category III).
50 5 SECTIONS FORMAT
Note that when icput=0 by default, output information does include the computation time (except for ‘total
cpu time’), ‘transport’, nor ‘set data.’
When infout=8, information on the calculations by each nuclear reaction model is output in detail.
• count: number of runs using the models with each incident particle.
• real: number of successes for model calculation.
• %: probability of model calculation.
52 5 SECTIONS FORMAT
In the setting of inpara, igpara, ippara, idpara, “/wk/” and “/uname/” are the default directory name
and a user-name read in from the environment variable LOGNAME, respectively. In parallel computing, files cor-
responding to each processor element (PE) are created for writing the output or the dumped data. If inpara,
igpara, ippara, or idpara is set to 0 or 1, a file is made in the directory named by /wk/uname/ on each of
the nodes. If inpara, igpara, ippara, or idpara is set to 1 or 3, the PE number is added at the end of the
filename. Each PE writes down its calculation result only on its corresponding file.
5.2 [ Parameters ] section 53
When iMeVperu=1, the unit of nucleus energy is changed from [MeV] to [MeV/u] in outputs of [t-track],
[t-cross], [t-point], [t-product], [t-time], [t-interact]. For example, in the case of [t-track]
with unit = 2, quantities in units of [1/cm2 /MeV/source] are converted to those in [1/cm2 /(MeV/u)/source].
[t-track] uses deltm as the step length to describe particle trajectories in fields that continuouly change
particles’ momenta, such as a magnetic field. To describe the trajectory curve more smoothly, adjust the setting of
deltm.
When two (or more) cells are defined with the same material number but differing densities, with the default
setting of matadd=1, such an material will be given a new material number as it is redefined by the other density.
If matadd=0 is set, the cells will have the same material number. Note that this setting is invalid in the [mat
name color], in which other given material numbers are output as a warning message in the first part of file(6)
(D=phits.out).
To save calculation time, CPU time for each calculation process, such as transport, set data, analysis, etc., is
not recorded and output by default. To obtain such information, set icput=1.
Setting ipara=1 enables confirmation of all parameters in the PHITS code.
39 An error message occurs if such a natural element does not exist in the data library.
5.2 [ Parameters ] section 55
The ivoxel parameter can be used to accelerate calcutions with voxel geometry. When performing PHITS
calculation with ivoxel=2, voxel data are output in file(18) in binary format, and the calculation is then stopped
(until ver. 2.30, calculation was continued). In the next calculation with ivoxel=1, the necessary information is
read from file(18) created in the previous calculation with ivoxel=2, so the data output process is omitted and
the calculation time is shortened.
Using the option of itetvol=1, when the tetrahedron geometry is treated with LAT=3, the volume of the
universes appearing in tetrahedron geometry can be automatically computed. However, the volume is computed
by simply summing up the volumes of individual tetrahedrons, which might produce incorrect values in cases in
which tetrahedron geometry is clipped out through the use of nest structure of “universe”and “fill”. The computed
value with the option of itetvol=1 is given priority over values specified in the [volume] or other sections.
When tetrahedron geometry (LAT=3) is used in PHITS calculation, necessary information for transport calcu-
lation is generated by reading the tetrahedron geometry file prior to the actual transport calculation. This process
becomes computationally heavy as the number of elements in the tetrahedron geometry increases. In such case, the
itetra parameter can be used to reduce the computational time. Performing PHITS calculation with itetra=2
will have the processed tetrahedron geometry data recorded in the binary file (“Tetra.bin”) followed by the calcu-
lation being stopped. In the next calculation with itetra=1, the necessary information is read from the Tetra.bin
file, and the data generation process is omitted to reduce the calculation time.
The ntetsurf and ntetelem parameters are associated with the two algorithms sub-dividing the box con-
taining the tetrahedron geometry for PHITS calculations with (LAT=3), which reduce the computational time by
limiting the number of elements belonging to each sub-space. One algorithm finds a surface of the tetrahedron
geometry when a particle enters the geometry. The container box is sub-divided so that the number of outer sur-
faces at each sub-space is less than ntetsurf. The other algorithm finds an element of tetrahedron geometry when
a particle is initiated inside the geometry. The box containing all tetrahedron elements is subdivided so that the
number of elements belonging to each sub-space is less than ntetelem.
Using the option of itetauto=1, cells required by each tetrahedron with specfied universe in tetrahedron
geometry are created automatically. The cost manually creating the cells can be reduced with this option when
the number of universes contained in tetrahedron geometry increase. This option is especially helpful when the
tetrahedron geometry is imported with the NASTRAN bulk data format. See 5.6.5 for more details.
56 5 SECTIONS FORMAT
If igchk is set to 1, after a particle crosses the boundary of a region, the particle’s location is artificially moved
a short distance away from the boundary surface along the forward direction in the PHITS code, and this short
distance is defined as “flight mesh.”
The purpose of the use of flight mesh is to more accurately determine which region the particle belongs to, for
prevention of misjudments due to insufficient significant digits. This function is important in particular for large
scale simulations that use curved surfaces.
From ver. 2.80, idelt=1 has become the default setting of PHITS, which sets the quotients of deltm and
deltc divided by the region’s density (in units of g/cm3 ) as the flight mesh maxima. This setting is useful in for
shortening the particle transport calculation time in air with a spatial scale over several hundred meters.
5.2 [ Parameters ] section 57
file(7) must be written with the full pathname. From ver. 2.74, the file(14) parameter does not have to be
specified in the PHITS input file even when setting |igamma|≥1.
58 5 SECTIONS FORMAT
5.2.17 Others
The nuclear reaction calculation mode with inucr is corresponding to icntl=1, which is currently under
development.
From version 2.89, in the default setting, ‘c’ cannot be used as comment marks in [material] section. To
use ‘c’ as comment marks in the section, set icommat=1. Note that the [parameters] section with icommat=1
should be written above (before) the [material] section including ‘c.’
40 ides is automatically set to 0 when either emin(12) or emin(13) or both is defined in the input file from ver. 2.96.
60 5 SECTIONS FORMAT
PEGS is the prepocessor for EGS. It contains a set of fortran subprograms, which negerate material data for the
use of EGS5. It is needed to change the parameter ipegs in order to change the input file of PEGS5 (pegs5.inp).
Note that, to retain PEGS5-related files after executing PHITS, iegsout automatically becomes 1 (or greater)
when ipegs is set ≥ 1.
When using EGS5, the default values of the minimum and maximum energies for electron, positron, and photon
transports are changed to emin(12,13)=0.1, emin(14)=0.001, and dmax(12-14)=1,000.0, respectively.
These values can also be changed by explicitly setting the related parameters. Note that the default values of
several EGS5 parameters differ from those employed in the original EGS5 code.
From ver. 2.76, photo-nuclear reactions can be considered in EGS5. Thus, input files with negs=1 and
ipnint=1 produce results that differ from those calculated by the previous version of PHITS.
(1) NCOL
NCOL is an intrinsic variable in the program and denotes identification of processes.
NCOL
1 : start of calculation
2 : end of calculation
3 : end of a batch
4 : source
5 : detection of geometry error
6 : recovery of geometry error
7 : termination by geometry error
8 : termination by weight cut-off
9 : termination by time cut-off
10 : geometry boundary crossing
11 : termination by energy cut-off
12 : termination by escape or leakage
13 : (n,x) reaction
14 : (n,n’x) reaction
15 : sequential transport only for tally
When NCOL=1, 2, 3, the output is finished. The followings are for NCOL≥4.
(a) QS
This data is written only for ITYP=12, 13, namely electron and positron. QS is dE/dx for electrons.
64 5 SECTIONS FORMAT
(a) ILAT1
This is a variable of level structure of cell. The next data are written only for ILEV1>0 as
(b) ILAT2
This is a variable of level structure of cell. The next data are written only for ILEV2>0 as
(7) WT, U, V, W
These mean
(8) E, T, X, Y, Z
These mean
(11) NZST
This is the charge state of particles.
(12) NCLSTS
This variable is written only for NCOL=13, 14, collision case, and means the number of produced particle
and nucleus. The next data are written for NCLSTS>0 case.
(a) MATHZ, MATHN, JCOLL, KCOLL
These mean
JCOLL
0 : nothing happen
1 : Hydrogen collisions
2 : Particle Decays
3 : Elastic collisions
4 : High Energy Nuclear collisions
5 : Heavy Ion reactions
6 : Neutron reactions by data
7 : Photon reactions by data
8 : Electron reactions by data
9 : Proton reactions by data
10 : Neutron event mode
11 : delta ray production
13 : Photon reactions by EGS5
14 : Electron reactions by EGS5
KCOLL
0 : normal
1 : high energy fission
2 : high energy absorption
3 : low energy n elastic
4 : low energy n non-elastic
5 : low energy n fission
6 : low energy n absorption
(b) ICLUSTS, JCLUSTS, QCLUSTS, JCOUNT
These variables have an array and denote the information on the produced particle and nucleus.
do i = 1, NCLSTS
write(io) ICLUSTS(i)
write(io) ( JCLUSTS(j,i), j=0,7)
write(io) ( QCLUSTS(j,i), j=0,12)
write(io) ( JCOUNT(j,i), j=1,3)
end do
These mean
66 5 SECTIONS FORMAT
(1) The deposition energy distribution by the low-energy neutrons below dmax(2) without the kerma approx-
imation is available in the [t-deposit] tally by considering contributions from the secondary charged
particles. When e-mode=0, the deposition energy by the low-energy neutrons in [t-deposit] is calculated
with the kerma approximation 43 .
(2) In [t-yield] and [t-product], the yield and product quantities can be tallied below dmax(2).
(3) DPA values are obtained even for neutrons of energies below dmax(2).
42 Y. Iwamoto et al., International Conference on Nuclear Data for Science and Technology 2007, DOI: 10.1051/ndata:07417; K. Niita et
al., International Conference on Nuclear Data for Science and Technology 2007, DOI: 10.1051/ndata:07398; Y. Iwamoto et al., Prog. Nucl.
Sci. Technol. 2, 931-935 (2011).
43 After ver. 3.05. Before ver. 3.04, the [t-deposit] tally cannot calculate the deposition energy with the kerma approximation.
68 5 SECTIONS FORMAT
In Table 5.26, numbers in the brackets were used until ver. 2.94. If both e0 and e-type are defined from
ver. 2.95, the energy is decided according to the previous procedure of s-type. For example, e0 is used when
s-type=1, and the definition of e-type is used when s-type=4.
44 Until ver. 2.94, s-type had to be used depending on the definition of the energy, e.g., s-type=1 with e0 defined the cylinder source of
the mono-energy, or s-type=4 with e-type defined that of the energy spectrum.
5.3 [ Source ] section 69
Tally results in PHITS calculations are normalized to per source particle, or per unit weight in a more strict
sense. For the totfact setting, if it is given a positive value, number of source particles are generated based on
the intensity ratio of each source definition; if negative, same number of source particles are generated for each
source definition, but their weights are adjusted to match the intensity ratio of all source definitions. If one source
definition has a much lower intensity than the others, yet such source definition contributes significantly to the tally
results, it is recommended to set totfact<0 to improve calculation efficiency.
For iscorr = 1-3, the multiplicity of each source must be specified as an integer value representing its
<source> parameter, and the sum of the multiplicities must be specified as the totfact parameter. For example,
to simulate (X, 1p2n) reaction as an event, set <source>=1 and 2 for proton and neutron sources, respectively, and
totfact=3.
70 5 SECTIONS FORMAT
parameter explanation
proj = Projectile: see Table4.4 for specification.
sx = (D=0) x-component of spin.
sy = (D=0) y-component of spin.
sz = (D=0) z-component of spin.
reg = (D=all) The source region can be restricted to the overlap(s) between the regions defined by
s-type and those specified by this parameter. The format is reg = { 1 - 5 } 10 34. The
lattice and universe frame can be used as reg = ( 6 < 10[1 0 0] < u=3 ). See the section
of tally region specification for more details on the syntax.
Note that this parameter cannot be written in the line right above <source> = if multi-source
sub-sections are defined; otherwise it will cause a syntax error.
ntmax = (D=1000) Maximum number of re-sampling the source location from the region specified by
s-type when reg is specified.
trcl = (D=none) Transform number, or definition of transform.
wgt = (D=1.0) Weight of source particles.
factor = (D=1.0) Scaling factor fot tally results; all tally results are multiplied by the value of factor.
When factor and totfact are both defined, totfact × factor is the actual scaling factor.
However, when multi-source is defined, use totfact only; do not use this parameter for scaling.
izst = (D=charge of particle species specified by proj=)
Charge state of source particle. This value influences the particle motions only in the magnetic
and electro-magnetic fields defined in [magnetic field] and [electro magnetic field]
sections. In addition, ATIMA with the fixed charge mode (ifixchg=1) calculates the stopping
power based on this charge state.
The charge number defined with izst does not change while the particle travels. Note that this
parameter is only valid for source particles, i.e., secondary particles produced from nuclear reac-
tions carry the charges of their atomic numbers.
cnt(i)= (D=0) Initial value of counter i (i=1-3) of source particle. You can distinguish the contributions
from each multi-source definition by assigning different values to their initial counter values.
spin. In this case, the initial spin of the neutron is determined at the entrance
of the magnetic field by the direction of the magnetic field and the polarization factor. If the spin is defined in this
section, the neutron enters the magnetic field with the defined spin direction irrespective of the direction of the
magnetic field and polarization.
parameter explanation
ispfs = 0, 1, 2 (D=0) Neutron sources from spontaneous fission.
If ispfs=1 or 2 is specified in the [source] section and the following 18 nuclei are
chosen as proj, neutrons can be defined using spontaneous fission as a source. These
nuclei are assumed to be spontaneous fission nuclei:
U-238, Pu-238, Pu-240, Pu-242, Cm-242, Cm-244, Cf-252, Th-232, U-232, U-233, U-
234, U-235, U-236, Np-237, Pu-239, Pu-241, Am-241, Bk-249.
ispfs=1: Tally result is normalized by the number of spontaneous fissions.
ispfs=2: Tally result is normalized by the number of neutrons produced by spontaneous
fission.
In the case of ispfs = 1,2, e0 and e-type, dir, and a-type are neglected. Unlike the
case of RI source (e-type=28,29), particle type specified by proj is not used, namely,
neutrons are generated as source particles.
When ispfs=1,2 is specified, the multiplicity and energy spectrum of neutrons are taken from the reference 45 .
The PHITS development team is grateful to Dr. Liem Peng Hong of NAIS, Co., Inc. for his support in developing
this function to generate neutron sources.
In the next example, setting proj=240Pu and ispfs=1 selects neutrons from the spontaneous fission of Pu-240
as source particles. In this case, the value of e0 is invalid.
[ Source ]
s-type = 1
proj = 240Pu
e0 = 1.0
z0 = 0
z1 = 0
r0 = 0.0
dir = 1.0000
ispfs = 1
45J. M. Verbeke, C. Hagmnn, and D. Wright, “Simulation of Neutron and Gamma Ray Emission from Fission and Photofission”, UCRL-
AR-228518 (2014).
72 5 SECTIONS FORMAT
When using the source type s-type=9 for volume and area calculation, set dir=-all, r1=r2; dir=iso
gives the same result.
Inner radius, r1, should be smaller or equal to outer radius, r2, except for dir=iso, where r1 should be equal
to (or larger than) r2.
r2
r1
5.3.10 s-type = 11
This is a uniform distribution source in a phase space which is vertical with beam direction. Parameters for
this source type are shown below. The order of parameters is free. If a parameter has a default value (D=***), the
parameter can be omitted.
5.3.11 s-type = 12
In this source type, decay-turtle output is read as source. Parameters for this source type are shown below. The
order of parameters is free. If a parameter has a default value (D=***), the parameter can be omitted.
The input file is rewinded and re-used from the first particle again, if all of source in decay-turtle is read before
the calculation finishes.
The format of decay-turtle is double precision, and ascii, and each record is as
variable explanation
xp, yp Incoming position of beam particle[cm].
xq, yq Angle against vertical face with beam direction[mrad].
e0 Momentum of beam particle[GeV/c].
wt0 Weight of beam particle.
pz0 Polarizing of beam particle (be not in use).
5.3 [ Source ] section 77
When all of nx,ny,nz are positive, the order of the relative intensities Ii jk is given as
I111 , I211 , · · · , Inx 11 , I121 , I221 , · · · , Inx ny 1 , I112 , I212 , · · · , Inx ny nz , (2)
where n x =|nx|, ny =|ny|, nz =|nz|. When nx and ny are positive and nz is negative, the order is given as
I11nz , I21nz , · · · , Inx 1nz , I12nz , I22nz , · · · , Inx ny nz , I11nz −1 , I21nz −1 , · · · , Inx ny 1 . (3)
In the latter case, the data with k = nz =|nz| should be first put.
An example using s-type=22 is shown below.
18: zmax = 10
19: 1 2 3
20: 4 5 6
21: 7 8 9
22:
23: 1 0 3
24: 0 5 0
25: 7 0 9
In this case, the source region is [-10cm≤ x, y, z ≤10cm], and the ranges in x, y, and z-axes are divided by 3, 3, and 2
bins, respectively. Because ny and nz are negative, the relative intensities Ii jk should be written in descending order
for j and k. Therefore, in the 19th-21st lines of the example, Ii jk with k = 2, i.e. in the region of [0cm≤ z ≤10cm],
are given as
I132 I232 I332 1 2 3
I122 I222 I322 = 4 5 6 , (4)
I112 I212 I312 7 8 9
and Ii jk with k = 1, i.e. in the region of [−10cm≤ z ≤0cm], are given in the 23rd -25th lines as
I131 I231 I331 1 0 3
I121 I221 I321 = 0 5 0 . (5)
I111 I211 I311 7 0 9
Figure 5.5 shows the sources distribution of the example, which are obtained by [t-product] with output=source.
The left and right panels are results in the regions of [0cm≤ z ≤10cm] and [−10cm≤ z ≤0cm], respectively. In
the left panel, the regions of 1, 2, 3, 4, 5, 6, · · · correspond to I132 , I232 , I332 , I122 , I222 , I322 , · · · , respectively. As
the region number increases, the intensity in each region gradually increases. In the right panel, the sources don’t
generate in the regions of 2, 4, 6, and 8, which correspond to the elements of 0 in the right side of Eq. 5.
20 20
10 10
1 2 3 1 2 3
Number [1/source]
Number [1/source]
y [cm]
y [cm]
0 4 5 6 10−4 0 4 5 6 10−4
7 8 9 7 8 9
−10 −10
11 11
−20 −20
−20 −10 0 10 20 −20 −10 0 10 20
x [cm] x [cm]
Figure 5.5: Results of example 2 in the region of [0cm≤ z ≤10cm] (left panel) and [−10cm≤ z ≤0cm] (right
panel).
5.3 [ Source ] section 81
In this case, source particles are produced uniformly from the region of the cell number 201 specified by tetreg.
This specified cell number should belong the universe as the 13th line of the example 44.
82 5 SECTIONS FORMAT
46 The option idmpmode=1 and re-used calculation using the option dmpmulti were introduced by referring to the presentation “Estimation
of uncertainty in multi-step Monte Carlo calculation” (N50) by Dr. Y. Namito et al. at the 2015 annual meeting of AESJ (Hitachi, Japan).
84 5 SECTIONS FORMAT
To use idmpmode=1, the history number (nocas) and batch number (nobch) must be contained in the dump
data. Using the PHITS tally dump option, a dump file named “*** dmp” is created in addition to the normal tally
file with the file name “***” specified by file=***. Both files are required to use idmpmode=1 and must be
placed in the same folder. The total number of histories of the previous step is adopted from the values of maxcas
and maxbch written in this tally file and the history numbers, maxcas and maxbch, given in the PHITS input file
are neglected. The normalization factor totfact is ignored when idmpmode=1. To use the normalization factor,
totfact should be applied to the previous step for creating the dump file, at which point it will be reflected in
the weights of particles recorded in the dump file. The option idmpmode=1 is incompatible with multi-source
processing.
The option dmpmulti controls the number of re-uses of the dump file. For instance, in the case of dmpmulti=2.0,
the dump file will be reused twice, i.e., information for each particle recorded in the dump file is reproduced twice
and the particle is treated as two particles having half-weights based on a different random number. The digits after
the decimal point indicate the probability of creating another reproduction of the particle as stochastically deter-
mined by running the Russian roulette procedure for each particle. For example, in the case of dmpmulti=2.3, the
particle data are reproduced twice with probability 70 % and three times with probability 30 %. As a special mode,
setting dmpmulti=0.0 rewinds and re-uses the dump file until the total histories specified by (maxcas*maxbch)
in the PHITS input file are finished. This mode is valid only with idmpmode=0.
The restart calculation (istdev<0) is essentially not applicable for dump source calculation; it only allowed
with dmpmulti=0.0, in which case it should be noted that the calculation might give biased results unless the dump
file contains sufficiently large particle data. Thus, re-calculation using a larger dmpmulti factor is recommended
to achieve better statistics; if the particle data contained in the dump file are not statistically suffcient, the statistical
uncertainties may not satisfactorily diminish even if a large dmpmulti factor is selected. In this case, it will be
necessary to re-calculate from the previous step to create suffcient dump data.
5.3 [ Source ] section 85
The parameter dump specifies the number of dump data points per record. If this number is positive, the data are
read as binary data; setting dump as a negative value will cause the data to be read as ascii data. In the line following
the dump= assignment, the data sequence of the record is input. The respective dump file physical quantities are
encoded with the id numbers shown in Tables 5.47 and 5.48.
In the table, kf is the particle kf-code (see Table 4.4), x, y, and z are coordinates [cm], u, v, and w are the unit
vectors of particle coordinate system, e is the energy ([MeV], or [MeV/u] for nuclei), wt is the weight, time is
the initial time [ns], c1, c2, and c3 are the counter values, and sx, sy, and sz are the unit vectors of the respective
spin directions. In Table 4.43, which encodes history-related ids, name is the particle’s collision number, nocas is
the batch history number, nobch is the batch number, and no is the cascade id contained in the history. These are
assumed to in real*8 format for binary data and in n(1p1e24.15) data format for ascii data.
For an example, a record containing nine data points is given by
kf e wt x y z u v w
To read these data, the parameters are written as
dump = 9
1 8 9 2 3 4 5 6 7
86 5 SECTIONS FORMAT
User-defined variables c1-c99 by setting set can be used in “usrsors.f” as cval(1-99). Note that the last
setting of set is available if the same variable is defined several times.
5.3 [ Source ] section 87
A sample program of “usrsors.f” is shown as following. In the first comment part, there is a list of the variables
which is necessary to define the source. Next there is a list of kf-code which specifies the source particle. In the
last part of the comment, the random number functions, one is a uniform random number, the other is a Gaussian
random number, are shown. The first part of the program is an example of the initialization, which describes the
open and close the data file. The remaining part shows a list of the variables which user should define in this
subroutine.
File 2: usrsors.f
1: ************************************************************************
2: subroutine usrsors(x,y,z,u,v,w,e,wt,time,name,kf,nc1,nc2,nc3,
3: & sx,sy,sz)
4: * sample subroutine for user defined source. *
5: * variables : *
6: * x, y, z : position of the source. *
7: * u, v, w : unit vector of the particle direction. *
8: * e : kinetic energy of particle (MeV). *
9: * wt : weight of particle. *
10: * time : initial time of particle. (ns) *
11: * name : usually = 1, for Coulmb spread. *
12: * kf : kf code of the particle. *
13: * nc1 : initial value of counter 1 *
14: * nc2 : initial value of counter 2 *
15: * nc3 : initial value of counter 3 *
16: * sx,sy,sz : spin components *
17: *----------------------------------------------------------------------*
18: * kf code table *
19: * kf-code: ityp : description *
20: * 2212 : 1 : proton *
21: * 2112 : 2 : neutron *
22: * 211 : 3 : pion (+) *
23: * 111 : 4 : pion (0) *
24: * -211 : 5 : pion (-) *
25: * -13 : 6 : muon (+) *
26: * 13 : 7 : muon (-) *
27: * 321 : 8 : kaon (+) *
28: * 311 : 9 : kaon (0) *
29: * -321 : 10 : kaon (-) *
30: * kf-code of the other transport particles *
31: * 12 : nu_e *
32: * 14 : nu_mu *
33: * 221 : eta *
34: * 331 : eta’ *
35: * -311 : k0bar *
36: * -2112 : nbar *
37: * -2212 : pbar *
38: * 3122 : Lanbda0 *
39: * 3222 : Sigma+ *
40: * 3212 : Sigma0 *
41: * 3112 : Sigma- *
42: * 3322 : Xi0 *
43: * 3312 : Xi- *
44: * 3334 : Omega- *
45: *----------------------------------------------------------------------*
46: * available function for random number *
47: * unirn(dummy) : uniform random number from 0 to 1 *
48: * gaurn(dummy) : gaussian random number *
49: * for exp( - x**2 / 2 / sig**2 ) : sig = 1.0 *
50: ************************************************************************
51: implicit real*8 (a-h,o-z)
52: *-----------------------------------------------------------------------
53: parameter ( pi = 3.141592653589793d0 )
88 5 SECTIONS FORMAT
Table 5.50: Types of source energy distribution. There are two methods for generation of source particles; one is
to adjust statistically the number of particles in each energy bin with the constant weight value, while the other is
to change the weight value of the source particle in each bin with the constant number of particles. When setting
the numbers in the brackets to e-type, the energy can be given by wave length (Å).
Input formats and parameters in each e-type will be explained below. If a parameter has a default value
(D=***), the parameter can be omitted.
90 5 SECTIONS FORMAT
parameter explanation
e-type = 1, (11) Any energy distribution can be specified by providing the data set of energy bins e(i)
and the integrated values of the particle generation probabilities w(i) by hand. The
number of particles generated in a bin is proportional to w(i), and the specified energy
distribution is statistically described. For case 11, the energy is given by the wave
length (Å).
ne = Number of energy groups.
If this is a positive number, source particles are generated so that the energy differential
fluxes in units of [1/MeV] become constant in each bin. If negative, the fluxes in units
of [1/Lethargy] become constant for each bin. Data must be provided in the following
line using the format
(e(i), w(i), i=1, ne), e(ne+1).
The integrated numbers of particles generated in each energy bin is proportional to
w(i).
e-type = 4, (14) The same energy distribution as in the case of e-type = 1, (11) can be specified,
except with the energy bins e(i) and weights of the source particle w(i) entered by
hand. The number of source particles generated in each bin is the same for all energy
bins, but integrated values of the weights of source particles are adjusted to be pro-
portional to w(i). The number of source particles generated in each bin can also be
changed by specifying p(i). For case 14, the energy is given by wave length (Å).
ne = Number of energy groups.
If this is a positive number, source particles are generated so that the energy differential
fluxes in units of [1/MeV] become constant in each bin. If negative, the fluxes in units
of [1/Lethargy] become constant for each bin. Data must be provided in the following
line using the format
(e(i), w(i), i=1, ne), e(ne+1).
In the default (p-type = 0), equal numbers of particles are generated in each cell. The
integrated number of source particles generated in each bin is proportional to p(i).
p-type = 0, 1 (D = 0) generation option.
For 0, p(i) = 1 for all i is assumed without the following data.
For 1, p(i) must be given from the next line using the format
(p(i),i=1,ne).
An alternative option for neutron optics has been developed to specify the energy as a wavelength: if e-type
is set to = 11, 12, 14, the wavelength (Å) is used as the energy unit. In the other cases, the expression e0 =
8.180425e-8/13**2 is used, which corresponds to the energy of a neutron with a 13Å wavelength.
5.3 [ Source ] section 91
e-type = 1
ne = n
e(1) w(1)
e(2) w(2)
e(3) w(3)
.... ...
e(n-1) w(n-1)
e(n) w(n)
e(n+1)
e(1)-e(2) w(1)
e(2)-e(3) w(2)
e(3)-e(4) w(3)
....... ...
e(n-1)-e(n) w(n-1)
e(n)-e(n+1) w(n)
As an example, use the following code to set the strengths of three energy bins between 0-2 MeV, 2-4 MeV, and
4-6 MeV as 0.2, 0.6, and 0.2, respectively:
e-type = 1
ne = 3
0 0.2
2 0.6
4 0.2
6
92 5 SECTIONS FORMAT
parameter explanation
e-type = 21, (31) Any energy distribution can be specified by giving data set of energy bins
e(i) and differential probabilities of the particle generation dφ/dE(i) by hand.
The integrated number of the particle generation in the bin is proportional to
dφ/dE(i)*{e(i+1)-e(i)}, and the specified energy distribution is statistically de-
scribed.
For 31 case, energy is given by wave length (Å).
ne = Number of energy group.
If it is given by positive number, source particles are generated so that the energy dif-
ferential fluxes in the unit of [1/MeV] become constant in each bin. On the other hand,
if ne is negative, the fluxes in the unit of [1/Lethargy] become constant in each bin.
Data must be given from the next line by the format as (e(i),dφ/dE(i),i=1,ne),
e(ne+1). The integrated number of the particle generation in the each energy bin is
proportional to dφ/dE(i)*{e(i+1)-e(i)}.
e-type = 24, (34) The same energy distribution as in the case of e-type=21,(31) can be specified. Un-
like e-type=21,(31), the distribution is described by giving data set of energy bins
e(i) and weights of the source particle w(i) by hand. The number of source particles
generated in each bin is the same for all energy bin, but integrated values of the weight
of source particles are adjusted to be proportional to w(i)*{e(i+1)-e(i)}.
The number of source particles generated in each bin can also be changed by specify-
ing p(i).
For 34 case, energy is given by wave length (Å).
ne = Number of energy group.
If it is given by positive number, source particles are generated so that the energy
differential fluxes in the unit of [1/MeV] become constant in each bin. On the other
hand, if ne is negative, the fluxes in the unit of [1/Lethargy] become constant in each
bin. Data must be given from the next line by the format as (e(i),w(i),i=1,ne),
e(ne+1).
In default (p-type=0), equal number of particle is generated in each cell. The inte-
grated number of source particles generated in each bin is proportional to p(i).
p-type = 0, 1 (D=0) generation option.
For 0, p(i)=1 for all i is assumed without the following data.
For 1, p(i) must be given from the next line by the format as (p(i),i=1,ne).
5.3 [ Source ] section 93
parameter explanation
e-type = 8, (18) Any energy distribution can be specified by giving data set of energy points e(i) and
probabilities of the particle generation w(i) by hand. The number of the particle gen-
eration at the point is proportional to w(i), and the specified energy distribution is
statistically described.
For 18 case, energy is given by wave length (Å).
ne = Number of energy points.
Data must be given from the next line by the format as (e(i),w(i),i=1,ne). The
number of the particle generation at the each energy point is proportional to w(i).
e-type = 9, (19) The same energy distribution as in the case of e-type=8,(18) can be specified. Un-
like e-type=8,(18), the distribution is described by giving data set of energy points
e(i) and weights of the source particle w(i) by hand. The number of source parti-
cles generated in each point is the same for all energy point, but integrated values of
the weight of source particles are adjusted to be proportional to w(i). The number of
source particles generated in each bin can also be changed by specifying p(i).
For 19 case, energy is given by wave length (Å).
ne = Number of energy points.
Data must be given from the next line by the format below.
In default (p-type=0), equal number of particle is generated at each point.
(e(i),w(i),i=1,ne)
The number of source particles generated in each point is proportional to p(i).
p-type = 0, 1 (D=0) generation option.
For 0, p(i)=1 for all i is assumed without the following data.
For 1, p(i) must be given from the next line by the format as (p(i),i=1,ne).
94 5 SECTIONS FORMAT
parameter explanation
e-type = 22, (32) Any energy distribution can be specified by providing the data set of the minimum
emin(i) and maximum emax(i) of energy bins, and the integrated values of the
particle probabilities w(i) by hand. To define the same discrete distribution as
e-type=18, (28), set the maximum to the same value as the minimum. The num-
ber of particles generated in a bin is proportional to w(i), and the specified energy
distribution is statistically described.
For case 32, the energy is given by the wave length (Å).
ne = Number of energy groups. If this is a positive number, source particles are generated
so that the energy differential fluxes in units of [1/MeV] become constant in each bin.
If negative, the fluxes in units of [1/Lethargy] become constant for each
bin. Data must be provided in the following line using the format:
(emin(i),emax(i),w(i),i=1,|ne|). The integrated numbers of particles gen-
erated in each energy bin is proportional to w(i).
e-type = 23, (33) The same energy distribution as in the case of e-type=22,(32) can be specified,
except with the weights of the source particle w(i) entered by hand. The number of
source particles generated in each bin is the same for all energy bins, but integrated
values of the weights of source particles are adjusted to be proportional to w(i). The
number of source particles generated in each bin can also be changed by specifying
p(i).
For case 33, the energy is given by wave length (Å).
ne = Number of energy groups. If this is a positive number, source particles are generated
so that the energy differential fluxes in units of [1/MeV] become constant in each bin.
If negative, the fluxes in units of [1/Lethargy] become constant for each
bin. Data must be provided in the following line using the format:
(emin(i),emax(i),w(i),i=1,|ne|).
In the default (p-type=0), equal numbers of particles are generated in each cell. The
integrated number of source particles generated in each bin is proportional to p(i).
p-type = 0, 1 (D=0) generation option.
For 0, p(i)=1 for all i is assumed without the following data.
For 1, p(i) must be given from the next line by the format as (p(i),i=1,ne).
An alternative option for neutron optics has been developed to specify the energy as a wavelength: if e-type is
set to = 32, 33, the wavelength (Å) is used as the energy unit. In the other cases, the expression e0 = 8.180425e-
8/13**2 is used, which corresponds to the energy of a neutron with a 13Åwavelength.
5.3 [ Source ] section 95
e-type = 22
ne = n
emin(1) emax(1) w(1)
emin(2) emax(2) w(2)
emin(3) emax(3) w(3)
.... ...
emin(n-1) emax(n-1) w(n-1)
emin(n) emax(n) w(n)
As an example, use the following code to set the strengths of three energy bins between 0-2 MeV, 2-4 MeV,
and 4-6 MeV as 0.2, 0.6, and 0.2, respectively, and the discrete one of mono-energy of 5.6 MeV as 0.4:
e-type = 22
ne = 4
0 2 0.2
2 4 0.6
4 6 0.2
5.6 5.6 0.4
96 5 SECTIONS FORMAT
parameter explanation
e-type = 2, (12) Differential spectrum dφ/dE(i) is given by Gaussian distribution.
For 12 case, energy is given by wave length (Å).
eg0 = center of Gaussian distribution [MeV].
eg1 = FWHM of Gaussian distribution [MeV].
eg2 = minimum cut off for Gaussian distribution [MeV].
eg3 = maximum cut off for Gaussian distribution [MeV].
e-type = 3 Differential spectrum dφ/dE(i) is given by Maxwellian distribution: f (x) =
x exp(−x/T )
nm = (D=-200) number of energy group.
If it is given by positive number, linear interpolation is assumed in a bin. If negative,
logarithmic interpolation is assumed in a bin.
et0 = temperature parameter T [MeV].
et1 = minimum cut off for Maxwellian distribution [MeV].
et2 = maximum cut off for Maxwellian distribution [MeV].
e-type = 7 The same energy distribution as in the case of e-type=3 can be specified. Unlike
e-type=3, the number of source particles generated in each bin is the same for all
energy bin, but integrated values of the weight of source particles are adjusted to be
proportional to f (x) = x1.5 exp(−x/T ). The number of source particles generated in
each bin can also be changed by specifying p(i).
nm = (D=-200) Number of energy group.
If it is given by positive number, linear interpolation is assumed in a bin. If negative,
logarithmic interpolation is assumed in a bin.
In the default (p-type=0), equal numbers of particles are generated in each cell. The
integrated number of source particles generated in each bin is proportional to p(i).
et0 = temperature parameter T [MeV].
et1 = minimum cut off for Maxwellian distribution [MeV].
et2 = maximum cut off for Maxwellian distribution [MeV].
p-type = 0, 1 (D=0) generation option.
For 0, p(i)=1 for all i is assumed without the following data.
For 1, p(i) must be given from the next line by the format as (p(i),i=1,nm).
5.3 [ Source ] section 97
parameter explanation
e-type = 5, (15) Differential spectrum dφ/dE(i) is given by f (x).
For 15 case, energy is given by wave length (Å).
f(x) = Any analytical function of x, Fortran style. x denotes energy [MeV/u]. One can use
intrinsic functions and constants C, e.g., f(x) = exp(-c1*x**2).
nm = number of energy group.
If it is given by positive number, linear interpolation is assumed in a bin. If negative,
logarithmic interpolation is assumed in a bin. Integrated number of source particles
generated in each cell is proportional to f (x).
eg1 = minimum cut off for energy distribution [MeV].
eg2 = maximum cut off for energy distribution [MeV].
e-type = 6, (16) The same energy distribution as in the case of e-type=5,(15) can be specified. Unlike
e-type=5,(15), the number of source particle generated in each bin is the same for
all energy bin, but integrated values of the weight of source particles are adjusted to be
proportional to f (x). The number of source particles generated in each bin can also be
changed by specifying p(i).
For 16 case, energy is given by wave length (Å).
f(x) = Any analytical function of x, Fortran style. x denotes energy (MeV/u). One can use
intrinsic functions and constants C, e.g., f(x) = exp(-c1*x**2).
nm = number of energy group.
If it is given by positive number, linear interpolation is assumed in a bin. If negative,
logarithmic interpolation is assumed in a bin. In the default (p-type=0), equal num-
bers of particles are generated in each cell. The integrated number of source particles
generated in each bin is proportional to p(i).
eg1 = minimum cut off for energy distribution [MeV].
eg2 = maximum cut off for energy distribution [MeV].
p-type = 0, 1 (D=0) generation option.
For 0, p(i)=1 for all i is assumed without the following data.
For 1, p(i) must be given from the next line by the format as (p(i),i=1,nm).
98 5 SECTIONS FORMAT
parameter explanation
e-type= 28,29 The α, β (including Auger electrons), and γ-rays of radioisotope (RI) decay are generated
by simply specifying the activity (in Bq) and names of the RIs. The DECDC47 nuclear
decay database (equivalent to ICRP107) is used to obtain the energy spectra. To use this
function, the directory containing the DECDC data file “RIsource.datd” must be specified
by setting file(24) (D=c:\phits\data\) in the [parameters] section.
When e-type=28, spectra are expressed by changing the probabilities of generating parti-
cle energy spectra obtained from DECDC.
When e-type=29, spectra are expressed by changing the weights of the source particles
while maintaining constant probabilities for all source energy.
ni= Number of RIs. RI names and activity must be given in the next line using the format
(RI(i),A(i),i=1, ni).
RI(i) can be defined using one of two formats, e.g., as 137Cs or Cs-137.
A(i) is specified in units of Bq.
dtime= (D=−10.0) Option for time evolution [s].
dtime>0 (in s): The energy spectrum is determined based on the decays of specified RIs
including contributions from their daughter nuclides at the time at which dtime has passed;
this changes the activity of each RI from its specified value. For example, setting 100 Bq
for an RI with a half-life of 1 min and dtime=60 results in an RI activity of 50 Bq in the
PHITS calculation.
dtime=0: No time evolution is considered.
dtime<0: The energy spectrum is determined based on the decays of the specified RIs
including the contributions from their daughter nuclides at the time at which the half-
life×|dtime| has passed. Unlike the case of dtime>0, the activities of the respective RI
are unchanged from their specified values. For example, setting 100 Bq for an RI with a
half-life of 1 min and dtime=−1.0 results in an unchanged RI activity of 100 Bq in the
PHITS calculation. When no information on the time necessary to attain radioactive equi-
librium is present, a large negative value, e.g., dtime=−10.0, must be set. It is not possible
to specify both parent and daughter nuclides simultaneously for dtime<0.
To use this function with multi-sources, set <source>=1.0 and totfact as follows:
• when all sources are defined by e-type=28,29, set totfact as the number of <source>;
• when the multi-sources include sources defined by e-type,28,29, set each <source> as the absolute
intensity of each RI and set totfact as the sum of all values of <source>.
If the totfact is given as a negative value, the same particle is generated in each multi-source section with weights
adjusted according to the ratio of the activities.
47A. Endo, Y. Yamaguchi and K.F. Eckerman, Nuclear decay data for dosimetry calculation - Revised data of ICRP Publication 38, JAERI
1347 (2005).
5.3 [ Source ] section 99
[ Source ]
totfact = 2.0
<source> = 1.0
s-type = 1
proj = photon
dir = all
r0 = 0.
z0 = 0.
z1 = 0.
e-type = 28
ni = 1
Cs-137 100.
dtime = -10.0
actlow = 1.0
<source> = 1.0
s-type = 1
proj = photon
dir = all
r0 = 0.
z0 = 0.
z1 = 0.
e-type = 28
ni = 1
Cs-134 100.
dtime = -10.0
actlow = 1.0
In this case, Cs-137 and Cs-134 after reaching radioactive equilibrium at 100 Bq are both defined as photon
sources. Furthermore, setting actlow=1 ensures that activity smaller than 1 Bq is ignored.
Furthermore, for example, to consider both γ and β-rays by decay of Cs-137, make a multi-sources having
two <source> sections with proj=photon and proj=electron. Because both the production rates of the γ and
β-rays are the same, their ratios can be specified as 1.0 (<source>=1.0). In this case, totfact should be 2.0,
which is the sum of the <source> sections.
100 5 SECTIONS FORMAT
parameter explanation
e-type= 20 Results of tallies can be used as an energy distribution by specifying file. Only results of
[t-track], [t-cross], [t-point], [t-product], [t-time], and [t-interact]
tallies with axis=eng can be used. A file name (***.out), which was specified in the tally
section as an output file name, should be set in file. There are two kinds of tally results, en-
ergy differential and integrated values, in accordance with unit given in the tally section. The
energy distribution of the source particle is expressed on the basis of the kind. Note that time
(nsec) and angular (sr) derivatives are not taken into account. The distribution of the source is
normalized to the integrated value of the tally result.
file= Output file name of tallies.
The first result specified by part in the tally section is used as the distribution of the source particle. Note that
particles of its kind are not generated. The parameter proj should be set to specify the kind of the source particle.
An example using e-type=20 is as follows. This function can be used by setting only e-type=20 and file.
[ Source ]
s-type = 1 # axial source with energy spectrum
proj = neutron # kind of incident particle
dir = 1.0 # z-direction of beam [cosine]
r0 = 0. # radius [cm]
z0 = 0. # minimum position of z-axis [cm]
z1 = 0. # maximum position of z-axis [cm]
e-type = 20 # energy distribution given by tally output
file = cross.out # file name of tally output
5.3 [ Source ] section 101
parameter explanation
a-type = 1, (11) Any angular distribution can be specified by giving data set of angle bins a(i) and
integrated values of the particle generation probability w(i) by hand. The number of
the particle generation in the bin is proportional to w(i), and the specified angular
distribution is statistically described. For 1 case, angle is given by cosine, and for 11
case, given by degree.
na = Number of angular group.
Data must be given from the next line by the format as (a(i),w(i),i=1,na),
a(na+1).
a-type = 4, (14) The same angular distribution as in the case of a-type=1,(11) can be specified. Un-
like a-type=1,(11), the distribution is described by giving data set of angle bins a(i)
and weights of the source particle w(i) by hand. The number of source particles gen-
erated in each bin is the same for all angle bin, but integrated values of the weight of
source particles are adjusted to be proportional to w(i). The number of source parti-
cles generated in each bin can also be changed by specifying q(i). For 4 case, angle is
given by cosine, and for 14 case, given by degree.
na = Number of angular group.
Data must be given from the next line by the format as (a(i),w(i),i=1,na),
a(na+1).
In default (q-type=0), equal number of particle is generated in each cell. The inte-
grated number of source particles generated in each bin is proportional to q(i).
q-type = 0, 1 (D=0) generation option.
For 0, q(i)=1 for all i is assumed without the following data.
For 1, q(i) must be given from the next line by the format as (q(i),i=1,na).
102 5 SECTIONS FORMAT
parameter explanation
a-type = 5, (15) Angular distribution dφ/dΩ(i) is given by g(x). For 5 case, angle is given by cosine,
for 15 case, given by degree.
g(x) = Any analytical function of x, Fortran style. x denotes angle. One can use intrinsic
functions and constants C, e.g., g(x) = exp(-c1*x**2).
nn = Number of angular group.
ag1 = minimum cut off for angular distribution.
ag2 = maximum cut off for angular distribution.
a-type = 6, (16) The same angular distribution as in the case of a-type=5,(15) can be specified. Un-
like a-type=5,(15), the number of source particle generated in each bin is the same
for all angle bin, but integrated values of the weight of source particles are adjusted to
be proportional to g(x). The number of source particles generated in each bin can also
be changed by specifying q(i). For 6 case, angle is given by cosine, for 16 case, given
by degree.
g(x) = any analytical function of x, Fortran style. One can use intrinsic functions and constants
C.
nn = Number of angular group.
In default (q-type=0), equal number of particle is generated in each cell. The inte-
grated number of source particles generated in each bin is proportional to q(i).
q-type = 0, 1 (D=0) generation option.
For 0, q(i)=1 for all i is assumed without the following data.
For 1, q(i) must be given from the next line by the format as (q(i),i=1,nn).
5.3 [ Source ] section 103
parameter explanation
t-type = 0, 1, 2 (D=0) time distribution.
0: no time-distribution, t=0.0.
1: rectangle distribution.
2: Gaussian distribution.
t0 = (D=0.0) center of time when t-type = 1 [ns]. )
tw = width of time distribution [ns]. When t-type=1, it means full width. When t-type=2,
it means FWHM of Gaussian distribution.
tn = number of time distribution.
td = interval of time distribution [ns].
tc = (D=10×tw) cut off time when Gaussian distribution t-type=2 [ns]
t-type = 3 Any time distribution can be specified by giving data set of time bin t(i) and integrated
values of the particle generation probability w(i), and specified time distribution is
statistically described.
ntt = Number of time group.
Data must be given from the next line by the format as (t(i),w(i),i=1,ntt),
t(ntt+1). The integrated number of the particle generation in the each time bin is
proportional to w(i).
t-type = 4 The same time distribution as in the case of t-type=1 can be specified. Unlike
t-type=1, the distribution is described by giving data set of time bins t(i) and
weights of the source particle w(i) by hand. The number of source particles gen-
erated in each bin is the same for all time bin, but integrated values of the weight of
source particles are adjusted to be proportional to w(i). The number of source particles
generated in each bin can also be changed by specifying o(i).
ntt = Number of time group.
Data must be given from the next line by the format as (t(i),w(i),i=1,ntt),
t(ntt+1).
In default (o-type=0), equal number of particle is generated in each cell. The inte-
grated number of source particles generated in each time bin is proportional to o(i).
o-type = 0, 1 (D=0) generation option.
For 0, o(i)=1 for all i is assumed without the following data.
For 1, o(i) must be given from the next line by the format as (o(i),i=1,ntt).
104 5 SECTIONS FORMAT
parameter explanation
t-type = 5 Differential spectrum (dφ/dt) is given by h(t).
h(x) Any analytical function of x[ns], Fortran style. One can use intrinsic function and constants
C.
ll Number of time group.
If it is given by positive number, linear interpolation is assumed in a bin. If negative, loga-
rithmic interpolation is assumed in a bin. Integrated number of source particles generated
in each cell is proportional to h(x).
tg1 Minimum cut off for time distribution [ns].
tg2 Maximum cut off for time distribution [ns].
t-type = 6 The same time distribution as in the case of t-type=5 can be specified. Unlike t-type=5,
the number of source particle generated in each bin is the same for all time bin, but inte-
grated values of the weight of source particles are adjusted to be proportional to h(x). The
number of source particles generated in each bin can also be changed by specifying o(x).
h(x) Any analytical function of x[ns], Fortran style. One can use intrinsic function and constants
C.
ll Number of time group.
If it is given by positive number, linear interpolation is assumed in a bin. If negative,
logarithmic interpolation is assumed in a bin.
In default (o-type=0), equal number of particle is generated in each cell. The integrated
number of source particles generated in each time bin is proportional to o(i).
tg1 Minimum cut off for time distribution [ns].
tg2 Maximum cut off for time distribution [ns].
o-type = 0, 1 (D=0) generation option.
For 0, o(i)=1 for all i is assumed without the following data.
For 1, o(i) must be given from the next line by the format as (o(i),i=1,ntt).
When setting t-type=100, an original distribution can be used by defining its function in subroutine “tdis01”
of “sors.f,” which a source file of PHITS.
parameter explanation
t-type = 100 User define time distribution. User can write any type of time distribution in the source
program of “sors.f”.
tg1 Minimum cut off for time distribution [ns].
tg2 Maximum cut off for time distribution [ns].
5.3 [ Source ] section 105
1: [ Source ]
2: totfact = 3
3: <source> = 9.72
4: s-type = 1
5: proj = proton
6: z0 = 2
7: z1 = 29
8: r0 = 5
9: r1 = 4
10: dir = 0.0
11: e-type = 6
12: eg1 = 1.e-6
13: eg2 = 1.e-3
14: nm = -200
15: set: c10[1.e-4]
16: f(x) = x**(1.5)*exp(-x/c10)
17: <source> = 1
18: s-type = 1
19: proj = photon
20: z0 = 1
21: z1 = 2
22: r0 = 5
23: dir = -1
24: e-type = 5
25: eg1 = 1.e-3
26: eg2 = 5.e-1
27: nm = 200
28: set: c10[1.e-1]
29: set: c20[1.e-1/2.35482]
30: f(x) = exp(-(x-c10)**2/2/c20**2)
31: <source> = 1
32: s-type = 1
33: proj = neutron
34: z0 = 29
35: z1 = 30
36: r0 = 5
37: e-type = 6
38: eg1 = 1.e-2
39: eg2 = 1.e+3
40: nm = -200
41: set: c10[92.469]
42: set: c20[5.644e+10]
43: f(x) = c10/c20*exp(-sqrt(x*(x+1876))/c10)*(x+938)/sqrt(x*(x+1876))
44: dir = data
45: a-type = 5
46: ag1 = 0
47: ag2 = 1
48: nn = 200
49: g(x) = exp(-(x-1)**2/0.3**2)
106 5 SECTIONS FORMAT
In this example, there are three source subsections started from <source>. In the first source subsection, a
cylinder source from z =2 cm to z =29 cm with 5 cm radius is defined, and r1=4 is set. This r1=4 means that the
region inside the cylinder with radius 4 cm is not included. In the next source, it is also a cylinder source from z =1
cm to z =2 cm with 5 cm radius without r1. This is a normal thin cylinder. The last one is also a thin cylinder from
z =29 cm to z =30 cm with 5 cm radius. The numbers defined after each <source> denote the relative weight of
the multi-source. In this example, the relative weight is determined by the relative volume ratio of each source.
This means that the source particles are generated uniformly in each source volume. The coordinate distribution of
the generated source particles is shown in Fig. 5.6 using [t-product] tally with output=source, and icntl=6.
6
4
Number [1/cm3/source]
2
x [cm]
10−3
0
−2
−4
−6
0 10 20 30
z [cm]
6 z=1.5cm 6 z=15cm
4 4
Number [1/cm3/source]
Number [1/cm3/source]
2 2
10−3 10−3
y [cm]
y [cm]
0 0
−2 −2
−4 −4
−6 −6
−6 −4 −2 0 2 4 6 −6 −4 −2 0 2 4 6
x [cm] x [cm]
The source particles of the multi-source are proton, photon and neutron. In each subsection, the energy dis-
tribution of the source particle is defined as Maxwellian, Gaussian, and user defined analytical function by using
the expression of those function with Fortran style. The first Maxwellian distribution is just equivalent to the
expression by e-type=7 as
e-type = 7
et0 = 1.e-4
et1 = 1.e-6
et2 = 1.e-3
e-type = 2
eg0 = 1.e-1
eg1 = 1.e-1
eg2 = 1.e-4
eg3 = 5.e-1
These energy distributions are shown below by using [t-product] tally with output=source, and icntl=6.
The result of each particle is shown in Fig. 5.7 with different colors.
10−1
10−2
Number [1/source]
10−3 proton
photon
10−4 neutron
10−5
10−6
10−6 10−5 10−4 10−3 10−2 10−1 100 101 102 103
Energy [MeV]
Figure 5.7: Multi-source, energy distribution
108 5 SECTIONS FORMAT
The first source has an angular distribution defined by dir=0, which means 90 degrees direction with respect
to z-axis, the second one has dir=-1, 180 degrees direction, and the third one has an angular distribution defined
by a-type description in which an analytic function is used for an angular distribution. The angular distribution
of the third one is shown in Fig. 5.8 by using [t-cross] tally.
0.0015
Angular distribution
0.0010
0.0005
0.0000
0.0 0.2 0.4 0.6 0.8 1.0
cos(θ)
Figure 5.8: Multi-source, angular distribution
5.3 [ Source ] section 109
parameter explanation
dom = -10 specify the duct source
dl0 = starting z position of the beam-line from z0[cm].
dl1 = starting z position of the duct source from z0[cm].
dl2 = ending z position of the duct source from z0[cm].
dpf = portion of pass through particles at dl2
drd = radius of circle beam line for s-type = 1[cm].
dxw = x size of rectangle beam line for s-type = 2[cm].
dyw = y size of rectangle beam line for s-type = 2[cm].
A shape of the beam-line is assumed to be circle or rectangle for s-type=1 or 2, respectively. The setting of
z1=z0 and dir=1 is also assumed. The latter parameter dir means the direction of the beam-line. To change the
direction of the beam-line, use the transformation by setting trcl=number of transformation. The source particles
are generated within the circle or rectangle region at z0 defined by r0 or x0, x1, y0, y1, for s-type=1 or 2,
respectively. The direction of the particle is determined by the wall position where it reaches within dl1 and dl2
so as to equalize the wall current at any point within this region changing the importance of the particle. Overall
normalization factor is defined as a number of the source particles which pass the entrance of beam-line at dl0
originated within the same region at the source position z0 as that at dl0. If the source region at z0 can be seen
at all duct wall positions from dl0 to dl2, the normalization factor is set to be 1. If the source region at z0 is
larger than the area of the beam-line at dl0, the source particle from the outer region at z0 is not counted as the
normalization number at dl0. This means that the extra region at z0 increases the current in the beam-line without
changing the normalization factor. In the above argument, the angular distribution of the source particle is assumed
to be isotropic within the small solid angle which covers the whole beam-line.
dyw
dxw
False
In the first example, the rectangle source and beam-line, the same size of the source and beam-line dimensions,
are defined. The input for the duct source option is as follows:
1 [ Source ]
2:
3: set: c1[200] $dl0
4: set: c2[500] $dl1
5: set: c3[5000] $dl2
6: set: c4[5.0] $x*2 at z0
7: set: c5[5.0] $y*2 at z0
8: set: c10[5.0] $dxw
9: set: c20[5.0] $dyw
10: set: c30[0.001] $dpf
11:
12: s-type = 2
13: proj = neutron
14: e0 = 20.0
15: x0 = -c4/2
16: x1 = c4/2
17: y0 = -c5/2
18: y1 = c5/2
19: z0 = 0.0
20: z1 = 0.0
21: dir = 1.0
22: phi = 0.0
23:
24: dom = -10
25: dl0 = c1
26: dl1 = c2
27: dl2 = c3
28: dxw = c10
29: dyw = c20
30: dpf = c30
In the first part of above source section, some constants are set to define the duct source option, dl0, dl1, dl2,
and size of source, dxw, dyw, dpf. In the second part, the position and xy region of the source, direction of the
beam-line and the energy of source particle are defined. In the third part, the duct source options are defined. The
setting gives the calculaton of the particle transport in the beam-line from 5 m up to 50 m by this duct source and
the current, wall current by using the cross tally. The results are shown in Fig. 5.10 compared with an ideal case
in which the current and the wall current are proportional to 1/L2 and 1/L3 , respectively. The cross marker in the
figure indicates the position of dl0 and show that the current at this point is unit. The results of the duct source
option agree very well with the analytical results.
In the next example, only the size of the source is changed from the previous example.
1 [ Source ]
2:
3: set: c1[200] $dl0
4: set: c2[500] $dl1
5: set: c3[5000] $dl2
6: set: c4[10.0] $x*2 at z0
7: set: c5[10.0] $y*2 at z0
8: set: c10[5.0] $dxw
9: set: c20[5.0] $dyw
10: set: c30[0.001] $dpf
11:
12: s-type = 2
13: proj = neutron
14: e0 = 20.0
15: x0 = -c4/2
16: x1 = c4/2
5.3 [ Source ] section 111
101
1 / L2
100 1 / L3
Current, PHITS
Wall Current, PHITS
10−1
Current [n/source]
10−2
10−3
10−4
10−5
10−6
17: y0 = -c5/2
18: y1 = c5/2
19: z0 = 0.0
20: z1 = 0.0
21: dir = 1.0
22: phi = 0.0
23:
24: dom = -10
25: dl0 = c1
26: dl1 = c2
27: dl2 = c3
28: dxw = c10
29: dyw = c20
30: dpf = c30
Figure 5.11 shows how the extra region of the source increases the current and the wall current. By this function,
the margin area of the moderator to the size of the cross-section of beam-line can be automatically treated.
101
1 / L2
100 1 / L3
Current, PHITS
Wall Current, PHITS
10−1
Current [n/source]
10−2
10−3
10−4
10−5
10−6
[ Material ]
MAT[n] element ratio element ratio ... ...
Two formats to specify material numbers can be used as follows: MAT[n] and Mn, where n can be specified up to
a material number of 99,999 unless it is over-defined. Note that a blank space cannot be set between MAT and [ in
the format MAT[n].
The following comment marks can be used: #, %, !, $. Although version 2.88 or before, c can be also used
as comment marks, after version 2.89, it is not permitted in the default setting. To use c as comment marks in
this section, set icommat=1 in the [parameters] section. Note that the [parameters] section with icommat=1
should be written above (before) the [material] section including c.
MAT[1] H 2 O 1
or
5.4 [ Material ] section 113
MTn materialID
where n is the material number and materialID is the ID number, such as lwtr.20t, written in “xsdir”. For
example, the library for water at room temperature (at 296K) can be set as follows:
M1 H 2.0
O 1.0
MT1 lwtr.20t
5.4.6 Examples
Some examples using the materials parameter are shown below.
1: [ Material ]
2: MAT[ 1 ]
3: 1H 1.0000000E-04
4: 208Pb 1.7238000E-02
5: 204Pb 4.6801000E-04
6: 206Pb 7.9430000E-03
7: 207Pb 7.2838000E-03
8: MAT[ 2 ]
9: 1H 1.0000000E-09
10: 14N 4.6801000E-05
11: 16O 7.9430000E-06
By default, the order is element, then ratio; these can be specified in reverse by putting den and nuc as,
1: [ Material ]
2: den nuc <------
3: MAT[ 1 ]
4: 1.0000000E-04 1H
5: 1.7238000E-02 208Pb
6: 4.6801000E-04 204Pb
7: 7.9430000E-03 206Pb
8: 7.2838000E-03 207Pb
9: MAT[ 2 ]
10: 1.0000000E-09 1H
11: 4.6801000E-05 14N
12: 7.9430000E-06 16O
1: [ Material ]
2: m1 80196.49c 5.9595d-5
3: 80198.49c 3.9611d-3
4: 80199.49c 6.7025d-3
5: 80200.49c 9.1776d-3
6: 80201.49c 5.2364d-3
7: 80202.49c 1.1863d-2
8: 80204.49c 2.2795d-3
9: c ...Be...
10: m3 4009.37c 1.2362E-1
11: mt3 be.01
12: c ...h2o (25C)...
13: m4 1001.37c 6.6658d-2 8016.37c 3.3329d-2
14: mt4 lwtr.01
15: c ...b4c (natural boron; 25%-density)...
16: m5 6012.37c 6.8118d-3
17: 5011.37c 2.1825d-2
18: c ...liquid-h2 (20K)...
19: m6 1001.49c 3.1371d-2 1011.49c 1.0457d-2
20: mt6 orthoh.00 parah.00
5.5 [ Surface ] section 115
[ Surface ]
surface number transform number surface symbol surface definition
The surfaces expressed by the equations in Table 5.68 or the macro body in Table 5.68 can be referred to using
their surface symbols. In addition, mathematical expressions and user defined variables can be used for surface
definition. Reflective and white boundary conditions can be set by writing * and +, respectively, before the surface
number. For example, *10 indicates that surface 10 is a reflective boundary. The reflective boundary condition is
useful to develop an infinite repeated structure.
√x + z ∓ |t| (y − y0 ) = 0 y0 , |t|2 , k
KY on Y-axis 2 2
KZ on Z-axis x + y2 ∓ |t| (z − z0 ) = 0
2 z0 , |t|2 , k
k is ±1 or unspecified
SQ ellipse, parallel with A(x − x0 )2 + B(y − y0 )2 + C(z − z0 )2 A, B, C, D, E,
hyperboloid, X-, Y-, +2D(x − x0 ) + 2E(y − y0 ) + 2F(z − z0 ) F, G, x0 , y0 , z0
paraboloid or Z- axis +G = 0
GQ cylinder, non parallel with Ax2 + By2 + Cz2 + Dxy + Eyz+ A, B, C, D, E,
cone, X-, Y- and Fzx + Gx + Hy + Jz + K = 0 F, G, H, J, K
ellipse, Z-axis
hyperboloid,
paraboloid
TX ellipse torus parallel with √ (x − x0 )2 /B2 + x0 , y0 , z0 , A, B, C
torus X-, Y-, or ( (y − y0 + (z − z0 )2 − A)2 /C 2 − 1 = 0
)2
TY Z-axis √ (y − y0 )2 /B2 + x0 , y0 , z0 , A, B, C
( (x − x0 ) + (z − z0 )2 − A)2 /C 2 − 1 = 0
2
TZ √ (z − z0 )2 /B2 + x0 , y0 , z0 , A, B, C
( (x − x0 )2 + (y − y0 )2 − A)2 /C 2 − 1 = 0
When using the surfaces defined in the [surface] section in the [cell] section, the interior of the shape
should essentially be specified in a ‘negative sense,’ while the exterior should be specified in a ‘positive sense.’
Note that, in the case of unclosed shapes such as planes, it is necessary to distinguish which side of the plane is
‘positive’ and which is ‘negative’ by calculating a value of f (x, y, z) at a point (x0 , y0 , z0 ), where f (x, y, z) is the
equation of the unclosed shape. If f (x0 , y0 , z0 ) > 0, the side including the point is ‘positive’ ; if f (x0 , y0 , z0 ) < 0,
the side is ‘negative.’ For example, for shape symbol PY with D = 5, the side including the origin (0, 0, 0) is
‘negative’ because f (0, 0, 0) = −5 < 0.
A plane can be defined by assigning the symbol P to the x, y, z-coordinates of three points. In this case, the
region including the origin is a negative region.
A cone can be defined in terms of its vertex point x0 , y0 , and z0 and aligned with any of the x, y, or z axes. By
default, the cone will have two sheets extending from the vertex (see Example 14); If parameter k is set = 1, the
upper sheet is used, while the lower sheet is used when k = −1. If k is not specified, both sheets are used. Note
that if a region is defined in the [cell] section using only one cone sheet, the plane passing through the vertex
must be specified. In defining a cone, three surfaces —the vertex-crossing plane, the side sheet of the cone, and
5.5 [ Surface ] section 117
If R < 0, In this case, the ellipsoid formed by a rotation on the major axis.
The major axis can be set to be shorter than the minor axis.
x0 , y0 , z0 , Center coordinate of ellipsoid.
A x , Ay , Az , Major axis vector.
R Radius of minor axis.
WED Wedge x0 , y0 , z0 , Coordinate of top.
A x , Ay , Az , Vector to first side of triangle ( A).
Bx , By , Bz , Vector to second side of triangle (B).
H x , Hy , Hz Height vector (H).
Note that, in defining TRC, R2 cannot be set to 0. To define a typical cone, i.e., one that is not truncated, using
TRC, set R2 to a small value.
The bottom of a wedge defined by WED must be a right triangle. To make an arbitrary triangle, right triangles
of various sizes must be combined.
118 5 SECTIONS FORMAT
5.5.2 Examples
This section shows examples of the surface definitions listed in Tables 5.68 and 5.69.
1: [surface]
2: 1 PY 5
y=5
1: [surface]
2: 1 P 2 2 1 10
3: 2 P 5 0 0 0 5 0 0 0 10
the plane can be defined by setting A = s, B = t, C = u, D = sx0 + ty0 + uz0 . The surface number 1 shown in
Example 11 is defined as a plane having the normal vector (2, 2, 1) and containing the coordinate (5, 0, 0). This
surface corresponds to the plane denoted by the dashed line in Fig. 5.13. As an illustration of the latter method,
surface number 2 is defined as a plane passing through the three coordinates (5, 0, 0), (0, 5, 0), (0, 0, 10). This
surface coincides with surface 1 in Figure 5.13.
5.5 [ Surface ] section 119
1: [surface]
2: 1 SO 5
3: 2 SZ 10 3
4: 3 S 10 10 0 3
1: [surface]
2: 1 CY 5
3: 2 C/Y 15 0 3
1: [surface]
2: 1 KZ 0 1
3: 2 K/Z 0 20 0 1/3 1
A cone surface with a central axis along the x, y, z axes can be defined by specifying the symbols KX,KY,KZ,
respectively. Parameters defining the coordinate of the vertex, an angle parameter, |t|2 , and a sheet parameter, k
(omitted), must also be set. An example in which KZ is specified is shown in the second line of Example 14.
The first parameter is the z-coordinate of the vertex
of the cone, z0 = 0, and the second defines |t|2 = 1. z
The equation of KZ is
45o Surface Number 2
√ 30o
x2 + y2 ∓ |t| (z − z0 ) = 0. (8)
Surface Number 1
After substituting each of the parameters, the fol-
lowing equations are obtained: 20 y
x
√
x2 + y2 − z = 0, (z > 0) (9)
√ Figure 5.16: The cone surface defined in Example 14.
x2 + y2 + z = 0, (z < 0) (10)
This formulation corresponds to surface number 1, which is defined as the cone surface having a central axis on
the z axis with its vertex at (0, 0, 0). This surface is shown on the left side of Fig. 5.16. The cone in the region
z > 0 is represented by Eq. (9), while that in z < 0 is given by Eq. (10); these surfaces are specified by k = 1 and
k = 1, respectively. Note that, as k is not specified in the second line of the example, both surfaces are defined. The
parameter |t|2 is given by the relation |t|2 = tan2 θ, where θ is the angle between the central axis and the generating
line. In the case of surface number 1, tan θ = 1, and therefore θ = 45◦ . To define a cone surface with a central
axis parallel to either the x, y, z axes and a vertex at (x0 , y0 , z0 ), the symbols K/X,K/Y,K/Z, respectively, can be
used. The third line of Example 14 shows an example in which K/Z is specified. The coordinate of the vertex is
◦
√ the cone has a central axis parallel to the z axis. Its angle θ is = 30 , corresponding to |t| = 1/3, or
2
(0, 20, 0), and
tan θ = 1/ 3. In this case, only one cone surface in the region of z > 0 is defined by specifying k = 1.
1: [surface]
2: 1 SQ 1/9**2 1/6**2 1/3**2 0 0 0 -1 0 0 0
The symbol SQ can be specified to define hyperboloid surfaces, as shown in the center and right-hand side of
Fig. 5.18. The surface in the center of the figure is called the hyperboloid of one sheet; those on the right-hand side
are hyperboloids of two sheets. Equations of hyperboloids of one and two sheets are given as, respectively,
x2 y2 z2
+ − = 1, (12) z=0 z
a2 b2 c2
x2 y2 z2
− 2 − 2 + 2 = 1. (13) b=3
a b c
Here, the central axis is the z axis. y
a=6
If a = b, the shape is called a hy- (0,20,0)
perboloid of revolution. The surface x x
number 1 defined in the second line y
of Example 16 corresponds to the
hyperboloid of one sheet shown in
the center of Fig. 5.18. In the second
Figure 5.18: The hyperboloid surface defined in Example 16.
line, the first to the seventh parame-
ters of SQ are given as A = 1/62 , B = 1/32 , C = −1/52 , D = E = F = 0, and G = −1, respectively. The central
axis, which corresponds to the z axis, passes through the origin because the eighth to tenth parameters are set to
x0 = 0, y0 = 0, z0 = 0, respectively. The intersection of this hyperboloid with a plane vertical to the z axis is an
ellipse. The figure in the left side of Fig. 5.18 shows the intersection line of surface number 1 with the plane z = 0.
This ellipse has the major and minor radii of a = 6 cm and b = 3 cm, respectively. The surface defined in the
third line of Example 16 corresponds to the hyperboloid of two sheets shown in the right-hand side of Fig. 5.18.
In this case, the signs of a, b, c of surface number 1 are reversed, and D = E = F = 0 and G = −1 are specified to
define a hyperboloid of two sheets. Note that the central axis passes through the coordinate (0, 20, 0) as (x0 , y0 , z0 )
is set = (0, 20, 0) in the eighth, ninth, and tenth parameters, respectively. When a surface of a hyperboloid of two
sheets is used to define a cell in the [cell] section, one region of the coordinate system (x0 , y0 , z0 ) represents the
‘negative sense,’ while the remaining space represents the ‘positive sense.’ The interiors of the two sheets shown
in the right-hand side of Fig. 5.18 should be specified as ‘positive.’
To define a paraboloid surface as shown in Fig. 5.19, the symbol SQ can be specified as described in Example 17.
The equation of
a paraboloid sur- y=0 z
x=0
face with a cen- z z
tral axis coincid-
ing with the z axis
is given as
z=x2
z= 41 y 2
x2 y2 y
z= + . (14) x
a2 b2 x y
This surface can
be defined by spec- Figure 5.19: The paraboloid surface defined in Example 17.
ifying A = 1/a2 , B = 1/b2 , C = 0, D = E = 0, F = −1, and G = 0 as the first to seventh parameters, respectively,
of SQ. In the example, a paraboloid with a = 1, b = 2 is defined. The intersection of this paraboloid with a plane
including the z axis is a parabola. The intersection lines of the paraboloid with y = 0 and x = 0 are shown in the
left and right panels of Fig. 5.19, respectively. The coordinates of the vertex are specified by eighth through tenth
parameters; in this case, x0 = 0, y0 = 0, z0 = 0.
122 5 SECTIONS FORMAT
1: [surface]
2: set: c1[30]
3: set: c2[cos(c1/180*pi)]
4: set: c3[sin(c1/180*pi)]
5: 1 GQ c2**2 1/2**2 c3**2 0 0 -2*c2*c3 -c3 0 -c2 0 z
Arbitrary surfaces expressed by quadratic equations in x, y, z by can be de-
fined specifying the symbol GQ. Although there similar surfaces such as
CX,KX,SQ are also expressed by quadratic equations, GQ can be used to
represent quadratic surfaces with a central axis that is NOT parallel to the
x, y, z axes. Note that it is easier to use apply a coordinate transformation
in the [transform] section to CX,KX,SQ than it is to use GQ. Example 18 y
x
represents a paraboloid surface obtained by rotating the surface in Example
17 by an angle of 30◦ around the y axis. The result is shown in Fig. 5.20.
The parameters of this example were obtained by calculating the following Figure 5.20: The paraboloid sur-
transform defined by rotating the coordinate (x, y, z) by an angle of θ around face defined in Example 18.
y axis:
′
x cos θ 0 sin θ x
′
y = 0 1 0 y . (15)
z′ − sin θ 0 cos θ z
After substitution of this result into Eq. (14), the following equation of x′ , y′ , z′ is obtained:
1: [surface]
2: 1 TZ 0 0 0 10 3 5
A torus surface, as shown in the center of Fig. 5.21, can be obtained by rotating an ellipse around a rotational
axis outside of the ellipse. In PHITS, torus surfaces with rotational axes corresponding to the x, y, z axes can be
specifying the symbols TX,TY,TZ, respectively. The equation of a torus surface with z axis as the rotational axis
is given as
(√ )2
x2 + y2 − R z2
+ = 1. (18)
a2 b2
In this case, the ellipse has major and minor radii z and b, respectively, and a distance between the center of the
ellipse and the rotational axis given by R. The center of the torus surface in Example 19 is set at the origin by
setting the first, second, and third parameters of TZ to zero. The fourth, fifth, and sixth parameters are A = R = 10
cm, B = b = 3 cm, and C = a = 5 cm, respectively. The intersection line of the torus with the plane z = 0 is shown
in the left panel of Fig. 5.21. The distance between the z axis and the center of the ellipse is 10 cm and the width of
the ring is 5 · 2 = 10 cm. The intersection of the torus with the plane y = 0 is shown in the right panel of Fig. 5.21:
note that only the region x > 0 is shown. The major and minor radii of the ellipse are 5 and 3 cm, respectively.
z=0 y z y=0
z
a=5 x
R=10 x b=3
a=5 y R=10
x
1: [surface]
2: 1 BOX 5 5 0 9 0 0 0 6 0 0 0 3
1: [surface]
2: 1 RPP 5 14 5 11 0 3
1: [surface]
2: 1 SPH 5 5 5 5
1: [surface]
2: 1 RCC 5 5 0 0 0 10 5
The symbol RCC can be used to define an arbitrary cylinder sur- z H(Hx ,Hy,Hz )=(0,0,10)
face. The parameters of RCC are the coordinates of the center of R =5
the bottom of the cylinder, P(x0 , y0 , z0 ), a vector from the bottom
to the top, H(H x , Hy , Hz ), and the radius of the cylinder, R. The
y
relation between these parameters is shown in Fig. 5.25. In Exam-
ple 23, the coordinate P(5, 5, 0) is the center of the bottom circle,
the vector is H = (0, 0, 10), and the radius is 5 cm. Unlike sym-
x
bols such as CX and C/X, it is useful to define a cylinder surface
with a central axis NOT parallel to x, y, z axes. P(x0 ,y0 ,z0)=(5,5,0)
1: [surface]
2: 1 RHP 0 0 0 0 0 10 5 0 0 2 -5 0 -2 -5 0
The symbols RHP or HEX can be used to define hexagonal prism surfaces as shown in the right panel of Fig. 5.26.
As parameters, the center coordinate of the bottom of the prism, P(x0 , y0 , z0 ), a vector from the bottom to the
top, H(H x , Hy , Hz ), and three vectors, A(A x , Ay , Az ), B(Bx , By , Bz ), and C(C x , Cy , Cz ) must be specified. Vectors
A, B, C are required to define the hexagon comprising the bottom and top surfaces. The left panel of Fig. 5.26
shows the relation between point P and the three vectors; namely, the lengths and directions of the perpendicular
lines between P and the three contiguous sides of the hexagon determine the three vectors. In Example 24, the
origin is at the center of the bottom hexagon and the height along the z axis of the prism is 10 cm. The components
of the origin (0, 0, 0) are specified as the first, second, and third parameters of RHP, respectively, and those of the
vector H(H x , Hy , Hz ) = (0, 0, 10) are given as the fourth, fifth, and sixth parameters, respectively. The seventh
to fifteenth parameters are the x, y, z components of A, B, C, respectively. The defined hexagon shown in the left
panel of the figure is symmetric with respect to the y axis.
C(Cx,Cy,Cz )=(-2,-5,0)
z=0 H(Hx ,Hy ,Hz )=(0,0,10)
z
P
y
B(Bx ,By ,Bz ) y
x x
=(2,-5,0)
P(x0 ,y0 ,z0)=(0,0,0)
A(Ax ,Ay ,Az )=(5,0,0)
1: [surface]
2: 1 REC 0 0 0 0 0 10 5 0 0 0 2 0
1: [surface]
2: 1 TRC 0 0 0 0 0 10 5 2
The surfaces of a truncated right-angle cone, as shown in z H(Hx ,Hy ,Hz )=(0,0,10)
Fig. 5.28, can be defined by specifying the symbol TRC. As R2=2
parameters of TRC, each component of the center coordinate,
P(x0 , y0 , z0 ), of the cone bottom, the components of a vector
from the bottom to the top, H(H x , Hy , Hz ), and two radii of the
R1=5
bottom and top circles, R1 and R2 , must be specified. In Exam-
y
ple 26, the surfaces of the truncated right-angle cone of height x
10 cm along the z axis are defined. The center of the bot-
tom circle is the origin. The coordinates of the origin (0, 0, 0) P(x0 ,y0 ,z0)=(0,0,0)
are specified as the first, second, and third parameters, respec-
tively, and those of vector H(H x , Hy , Hz ) = (0, 0, 10) are given Figure 5.28: The cut cone surface defined in Ex-
as the fourth through sixth parameters. The radius of the bot- ample 26.
tom is R1 = 5 cm and that of the top is R2 = 2 cm with R1 and
R2 specified as the seventh and eighth parameters, respectively.
R2 cannot be set to zero when defining TRC. To set a typical cone, i.e., a non-truncated cone, using TRC, R2
should be set to a small value.
1: [surface]
2: 1 ELL 3 3 0 -3 -3 0 9
1: [surface]
2: 1 ELL 0 0 0 6 6 0 -6
1: [surface]
2: 1 WED 0 0 0 10 0 0 0 10 0 0 0 5
[ Cell ]
cell number mat. number mat. density cell def. cell parameter
In the LIKE n BUT format, the cell parameter format and repeated structures with lattices can be used: see
Sec. 5.6.5 for some examples showing how to use this format. The cell parameters are listed and explained in
Table 5.72.
When defining cells with the same material number but different densities, the cells assume material numbers
that differ from that of the first cell.
In operation of the cell definition, ⊔(blank) has a higher priority than :.
130 5 SECTIONS FORMAT
item explanation
VOL Volume [cm3 ] of the cell is given.
TMP Temperature [MeV] of the material in the cell is given.
TRCL Coordinate transform for position of the cell is performed using the defined coordinate transform
number defined in the [transform] section or the transform format.
U Universe number; using this, the number of the universe including the cell is defined. Any number
value can be used from 1 to 999,999. See Sec. 5.6.3 for details.
LAT Lattice number. Setting LAT=1 or 2 defines a quadratic or hexangular prism, respectively: see
Sec. 5.6.4 for details.
FILL Set universe numbers to fill the cell with the universe.
MAT This is used with the LIKE n BUT MAT=m format. Using MAT, a cell can be duplicated except with
its material number changed to m.
RHO This is used with the LIKE n BUT RHO=x format. Using RHO, a cell can be duplicated except with
its density changed to x.
1: [ Cell ]
2: 1 0 -10
3: 2 -1 10
4: [ Surface ]
5: 10 SZ 3 5
The tenth surface represents a sphere with a radius of 5 cm. Because the inside of this sphere is in the negative
sense, the first cell is defined using a negative number -10. The outer void is explicitly defined as the second cell.
This example produces the virtual space shown in Fig. 5.32.
10
5
x [cm]
0 1 void
−5
−10
−10 −5 0 5 10
z [cm]
In some cases, the treatment of a region in the cell definition involves the use of Boolean operators. The symbols
⊔(blank), :, and # denote the intersection (AND), union (OR), and complement (NOT), operators, respectively.
Parentheses, e.g., ( and ), can be used to combine some regions. The second example in this section uses ⊔(blank)
and #.
In the cell definition in the second line, the three numbers without minus signs correspond to the positive sense
regions of the eleventh, thirteenth, an fifteenth surfaces, while those with minus signs correspond to the negative
sense regions of the twelfth, fourteenth, and sixteenth surfaces. A region surrounded by these surfaces is defined
with ⊔(blank) as the first cell, which is the interior of a 12-cm cube. The outside of the cube is defined by the
complement operator # as the outer void. Figure 5.33 shows the result of this example.
10
5
x [cm]
0 1 void
−5
−10
−10 −5 0 5 10
z [cm]
The next example uses : and parentheses to combine the sphere in the first example and the cube in the second
example.
The numbers surrounded by the parentheses in the second line correspond to the region of the first cell in example
(2). In this example, a region combining the inside of the cube with the inside of the sphere in example (1) is
defined using the union operator : as the first cell. The result is shown in Fig. 5.34.
132 5 SECTIONS FORMAT
10
x [cm]
0 1 void
−5
−10
−10 −5 0 5 10
z [cm]
The next example shows the division of a cube into two regions by a spherical surface.
1: [ Material ]
2: mat[1] 1H 2 16O 1
3: [ Cell ]
4: 1 0 -10
5: 2 1 1.0 10 (11 -12 13 -14 15 -16)
6: 3 -1 #1 #2
7: [ Surface ]
8: 10 SZ 3 5
9: 11 PX -6
10: 12 PX 6
11: 13 PY -6
12: 14 PY 6
13: 15 PZ -6
14: 16 PZ 6
This [surface] section is the same as in example (3). In the fifth line, the second cell is defined with ⊔(blank) as
an overlap region between the outside of the sphere, which is the tenth surface, and the inside of the cube defined
by the parentheses. The cell is filled with water as defined in the [material] section and the result is shown in
Fig. 5.35. The interior of the sphere is the first cell, which is filled with void.
10
5
x [cm]
water
0 1
void
2
−5
−10
−10 −5 0 5 10
z [cm]
Figure 5.35: Result of [cell] section example (4). The first and second cells are filled with void and water,
respectively.
5.6 [ Cell ] section 133
5
x [cm]
0 1 2 void
−5
−10
−10 −5 0 5 10
z [cm]
(b) Universe 1 (c) Universe 2
10 10
5 5
x [cm]
x [cm]
void water
0 101 0 201
water iron
−5 −5
102 202
−10 −10
−10 −5 0 5 10 −10 −5 0 5 10
z [cm] z [cm]
Figure 5.36: (a) Two rectangular solids. (b) Cylinder filled with water. (c) Iron cylinder in water.
1: [ Material ]
2: mat[1] 1H 2 16O 1
3: mat[2] Fe 1
4: [ Cell ]
5: 1 0 11 -12 13 -14 15 -17 FILL=1
6: 2 0 11 -12 13 -14 17 -16 FILL=2
7: 101 1 1.0 -10 13 -14 U=1
8: 102 0 #101 U=1
9: 201 2 10.0 -10 13 -14 U=2
10: 202 1 1.0 #201 U=2
11: 9 -1 #1 #2
12: [ Surface ]
13: 10 CY 5
14: 11 PX -6
15: 12 PX 6
16: 13 PY -6
17: 14 PY 6
18: 15 PZ -6
19: 16 PZ 6
20: 17 PZ 0
134 5 SECTIONS FORMAT
Universes 1 and 2 are defined in the seventh and eighth lines and in the ninth and tenth lines, respectively, using
cell parameter U. These universes have similar structures in which a cylinder is placed at the origin of the coordinate
space, but their components inside and outside the cylinder differ, as shown in Fig. 5.36. In the fifth and sixth lines,
the first and second cells are defined respectively as regions filled with the corresponding part of each universe
using the cell parameter FILL. The result of this example is shown in Fig. 5.37, in which it can be seen that the
first cell comprises the 101st and 102nd cells in universe 1, while the second cell comprises the 201st and 202nd
cells in universe 2.
10
void
x [cm]
−5 102
202
−10
−10 −5 0 5 10
z [cm]
It is not possible to use an undefined region from one of the universes. If the 102nd cell is not defined in the
eighth line as a void region, the first cell cannot be filled with universe 1. Not also that all universes have the same
coordinate system definition, with the position of the origin, directions of x, y, and z-axes, and scale of the space in
any universe agreeing with those in any other universe. If a different value of PX is in the fourteenth and fifteenth
lines, the cube will not include some of the cylinder, as shown in Fig. 5.38.
10
5 102 202
void
x [cm]
101 201
0 water
iron
−5
−10
−10 −5 0 5 10
z [cm]
Figure 5.38: Result of [cell] section example (5) with the region is shifted in the x-direction.
or void. The numbering of each unit component in Fig. 5.39 corresponds to the surface number order written in
the cell definition; the lattice coordinate system, which will be explained below, depends on this order.
3 5 3
2 LAT=1 1 2 LAT=2 1
4 4 6
Figure 5.39: Unit structure of lattice.
An example using a quadratic prism (LAT=1) is shown below.
In the fifth line, a unit cell with LAT=1 is defined using four surface numbers. Setting U=1 defines as the repeated
structures of this unit, which is filled with universe 2 defined in the sixth line. Because the cross section of the unit
in the x-z plane is a square four cm per side, the first cell defined in the fourth line as a 12 cm cube has nine blocks,
as shown in Fig. 5.40. Note that the unit has an infinite length in the y direction of universe 1 because of only four
surfaces
20 are defined. To define a finite-length prism, -24 23 must be added to the cell definition in the fifth line.
10
15
5
(-1,1,0) (0,1,0) (1,1,0)
x [cm]
10
0 (-1,0,0) (0,0,0) (1,0,0) water
−10
−10 −5 0 5 10
0
0 5 10 15 20
z [cm]
Figure 5.40: Result of [cell] section example (6) in 3D (left) and 2D (right) images.
To distinguish cells in the repeated structure, each cell is placed at the lattice coordinate (s, t, u), as shown in
the right panel of Fig. 5.40. Note that the ordering this coordinate notation corresponds to the general coordinate
136 5 SECTIONS FORMAT
ordering (x, y, z) and are defined by the order of surface numbers written in the cell definition. To specify any cell
using mesh=reg in a tally section, the lattice and universe styles (201 < 101[-1 0 0] < 1) can be used, where
the lattice coordinate is represented by [s t u]: see Sec. 6.1.2 for more information on this format. The lattice
coordinates can be viewed using the [t-gshow] tally with output=7 or 8.
The following example involves a hexangular prism (LAT=2).
1: [ Material ]
2: mat[1] 1H 2 16O 1
3: [ Cell ]
4: 1 0 11 -12 13 -14 15 -16 FILL=1
5: 101 0 -31 32 -33 34 -35 36 -24 23 LAT=2 U=1 FILL=2
6: 201 1 1.0 -90 U=2
7: 2 -1 #1
8: [ Surface ]
9: 11 PX -6
10: 12 PX 6
11: 13 PY -6
12: 14 PY 6
13: 15 PZ -6
14: 16 PZ 6
15: 23 PY -2
16: 24 PY 2
17: set: c1[2]
18: 31 PZ [ c1*cos(pi/6)]
19: 32 PZ [-c1*cos(pi/6)]
20: 33 P 1 0 [ 1/tan(pi/3)] [ c1]
21: 34 P 1 0 [ 1/tan(pi/3)] [-c1]
22: 35 P 1 0 [-1/tan(pi/3)] [ c1]
23: 36 P 1 0 [-1/tan(pi/3)] [-c1]
24: 90 BOX -10 -10 -10 20 0 0 0 20 0 0 0 20
A hexagon with LAT=2 is defined in the fifth line using the six surfaces defined in the seventeenth through twenty
third lines. The hexagonal prism is restricted in the y-direction by -24 23 in the cell definition and is filled with the
universe 2, i.e., water, as specified in the sixth line. The first cell has the repeated structure defined in universe 1.
Figure 5.41 shows the result of this example. It can be seen that some prisms near the edges of the first cell, which
is defined as a 12 cm cube, are only partly used. The directions of the lattice coordinate shown in the right panel
depend on the order of the surface number written in the cell definition. To specify a cell using mesh=reg in a tally
section, the lattice and universe styles (201 < 101[-2 0 0] < 1), where the lattice coordinate is represented
by [s t u], can be used: see Sec. 6.1.2 for more information on this format. The lattice coordinates can be shown
using 20the [t-gshow] tally with output=7 or 8.
10
15
10
0 (-2,0,0) (-1,0,0) (0,0,0) (1,0,0) (2,0,0) water
−10
−10 −5 0 5 10
0
0 5 10 15 20
z [cm]
Figure 5.41: Result of [cell] section example (7) in 3D (left) and 2D (right) images.
5.6 [ Cell ] section 137
A 4 cm cube filled with water and placed at the origin of the coordinate system is defined in the sixth line. The
interior of this cube is the second cell, which is regarded as the original cell in this example. In the seventh
and eighth lines, respectively, the third and fourth cells are defined using the LIKE n BUT format with n = 2.
Figure 5.42 shows the result of this example. The coordinate system of the third cell is transformed using the cell
parameter TRCL=1, where the coordinate transform number 1 is defined in the nineteenth line of the [transform]
section. The coordinate system of the fourth cell is transformed using TRCL=2 and the interior material of the cell
is replaced with iron defined using the material number 2 in the third line.
10
5
3
void
x [cm]
0 2 4 iron
water
−5 1
−10
−10 −5 0 5 10
z [cm]
1: [ Material ]
2: mat[1] 1H 2 16O 1
3: mat[2] Fe 1
4: [ Cell ]
5: 1 0 11 -12 13 -14 15 -16 FILL=1
6: 101 0 -26 25 -22 21 LAT=1 U=1
7: FILL=-1:1 -1:1 0:0
8: 2 2 3 2 3 2 3 2 2
9: 201 1 1.0 -90 U=2
10: 301 2 10.0 -10 U=3
11: 302 0 10 U=3
12: 2 -1 #1
13: [ Surface ]
14: 10 CY 1.5
15: 11 PX -6
16: 12 PX 6
17: 13 PY -6
18: 14 PY 6
19: 15 PZ -6
20: 16 PZ 6
21: 21 PX -2
22: 22 PX 2
23: 25 PZ -2
24: 26 PZ 2
25: 90 BOX -10 -10 -10 20 0 0 0 20 0 0 0 20
The definition of the first cell in the fifth line and the lattice unit in the sixth line are the same as in the [cell]
section example (6). However, the format of the cell parameter FILL in the seventh and eighth differs: in the sev-
enth line, regions treated in this calculation are given in the lattice coordinate system. The numbers in the next line
correspond to the universe number filling each lattice at (s, t, u) following the order (−1, −1, 0), (0, −1, 0), (1, −1, 0),
(−1, 0, 0), . . . , (1, 1, 0); in other words, a lattice at (−1, −1, 0) is filled with universe 2 and one at (1, −1, 0) is filled
with universe 3. Universe 2 is defined in the ninth line as a space filled with water, while the universe 3 is defined
in the tenth and eleventh lines has an iron cylinder centered at the origin. The result of this example is shown
in Fig. 5.43, in which it can be seen that three lattices at (1, −1, 0), (0, 0, 0), and (−1, 1, 0) have an iron cylinder.
Specifying a cell using mesh=reg in the tally sections can be done using the lattice and universe styles as (302 <
101[0 0 0] < 1), where the lattice coordinate is represented by [s t u]: see Sec. 6.1.2 for more information
on this format.
10
5
(-1,1,0) (0,1,0) (1,1,0)
(-1,1,0)
water
x [cm]
−10
−10 −5 0 5 10
z [cm]
1: [ Material ]
2: mat[1] 1H 2 16O 1
3: mat[2] Fe 1
4: [ Cell ]
5: 1 0 11 -12 13 -14 15 -16 FILL=1
6: 101 0 -26 25 -22 21 LAT=1 U=1
7: FILL=-1:1 -1:1 0:0
8: 2 2 3(1 0 1) 2 3(1 0 1) 2 3(1 0 1) 2 2
9: 201 1 1.0 -90 U=2
10: 301 0 -36 35 -32 31 LAT=1 U=3
11: FILL=-1:0 -1:0 0:0
12: 4 2 2 4
13: 401 2 10.0 -10 U=4
14: 402 0 10 U=4
15: 2 -1 #1
16: [ Surface ]
17: 10 CY 0.5
18: 11 PX -6
19: 12 PX 6
20: 13 PY -6
21: 14 PY 6
22: 15 PZ -6
23: 16 PZ 6
24: 21 PX -2
25: 22 PX 2
26: 25 PZ -2
27: 26 PZ 2
28: 31 PX -1
29: 32 PX 1
30: 35 PZ -1
31: 36 PZ 1
32: 90 BOX -10 -10 -10 20 0 0 0 20 0 0 0 20
The virtual space formed by this input is shown in Fig. 5.44, in which there are nine square poles defined using the
lattice parameter. Three of the poles comprise four units of the other lattice. In the eighth line, (1 0 1) denotes
a transformation of the coordinate system in which the origin is shifted by 1 cm in both the x- and z-directions.
The lattice and universe styles (402 < 301[-1 -1 0] < 101[0 0 0] < 1), where the lattice coordinate is
represented as [s t u], can be used to specify any cell using mesh=reg in the tally sections: see Sec. 6.1.2 for
more information on this format.
10
water
x [cm]
0 void
iron
−5
−10
−10 −5 0 5 10
z [cm]
Voxel phantom
In PHITS, a virtual space can be created using voxel phantoms for calculation on complex structures such as the
human body or an organism. To define a voxel phantom, a small cube must first be defined as the unit of a lattice
with LAT=1. This unit is then repeated to define a large-size structure. Each unit can then be filled with a universe,
which itself is filled with biological matter, e.g., compounds of carbon and water.
In the example below, a 10-cm cube comprising 125 (5 × 5 × 5) 2 cm cubes (voxels) is described.
1: [ Material ]
2: mat[1] 1H 2 16O 1
3: mat[2] Fe 1
4: [ Cell ]
5: 1 0 11 -12 13 -14 15 -16 FILL=1
6: 101 0 -20 LAT=1 U=1
7: FILL=-2:2 -2:2 -2:2
8: 2 2 2 2 2 2 2 2 2 2 2 2 3 2 2 2 2 2 2 2 2 2 2 2 2
9: 2 2 2 2 2 2 3 3 2 2 2 3 4 3 2 2 3 3 2 2 2 2 2 2 2
10: 2 2 2 2 2 2 3 3 3 2 3 4 4 4 3 2 3 3 3 2 2 2 2 2 2
11: 2 2 2 2 2 2 2 3 3 2 2 3 4 3 2 2 2 3 3 2 2 2 2 2 2
12: 2 2 2 2 2 2 2 2 2 2 2 2 3 2 2 2 2 2 2 2 2 2 2 2 2
13: 201 0 -90 U=2
14: 301 2 10.0 -90 U=3
15: 401 1 1.0 -90 U=4
16: 2 -1 #1
17: [ Surface ]
18: 11 PX -5
19: 12 PX 5
20: 13 PY -5
21: 14 PY 5
22: 15 PZ -5
23: 16 PZ 5
24: 20 BOX -1 -1 -1 2 0 0 0 2 0 0 0 2
25: 90 BOX -10 -10 -10 20 0 0 0 20 0 0 0 20
As the voxel unit, the 2 cm cube is defined in the twenty fourth line. The first cell, which is located within a 10-cm
cube, has a repeated structure as defined in the fifth line. The region of the lattice coordinate space is determined in
the seventh line. The order of voxels in the eighth through twelfth lines is as follows: (−2, −2, −2), (−1, −2, −2), . . . ,
(2, 2, 2), which represent the lattice coordinates. In the eighth through twelfth lines, 2 means universe 2, which is
void, while 3 and 4 correspond to universes 3 and 4, which are of iron and water, respectively. Figure 5.45 shows
the results of this example —a distorted iron box with regions of water within. To specify any cell using mesh=reg
in tally sections, the lattice and universe styles (401 < 101[0 0 0] < 1), where the lattice coordinate is rep-
resented by [s t u], can be used: see Sec. 6.1.2 for more information. Note that formats such as, e.g., (301 <
101[-2:2 -2:2 20 -2:2] < 1) cannot be used because20 not all 101[-2:2 -2:2 -2:2] cells have a 301st cell.
15 15
10 10
5 5
0 0
Figure 5.45: Results
0 of the
5 [cell] section
10 example
15 (11) in0203D images.
5 The structure
10 in the
15 right panel
20 is equivalent
to that in the left panel with part of its iron surface removed.
5.6 [ Cell ] section 141
From the PHITS version 3.09, the array of universe numbers at the 8th through 12th lines of the example 40
can be expressed in a compressed format. For voxel phantoms, the universe array contains long ques of continuous
same universe numbers and the compressed format is designed to reduce the size of this array. Thus the redution of
the file size and computational time for read and write of the huge voxel data can be achieved. In the compressed
format, the array of the continous universe numbers are given by the number of the continuous same universe with
minus sign followed by the universe number. Following this rule, the array of universe number at the 8th through
12th lines of the example 40 can be rewritten as follows.
In the example 40 after the universe number 2 are aligned 12 times, the universe number 3 comes. On the other
hand in the example 41, the second number -11, which comes after the first number 2, specifies that the universe
number 2 given before was replicated 11 times afterword.
To enable save computational time, ivoxel can be specified in the [parameters] section. Performing PHITS
calculation with ivoxel set =2 causes voxel data to be output in binary to file(18) and then stops the calculation.
From the next calculation with ivoxel set =1, data output is omitted, which reduces the calculation time. If a very
large amount of voxel data is used, it may be more convenient to use infl.
The node file begins with the number of nodes and the number of dimensions (second line). PHITS operates only
in three-dimensional geometry, and the two last zeros in the second line are not used in PHITS. The following lines
(below the third line) represent a list of nodes and their xyz space coordinates in the order
[node no.] [x] [y] [z]
The element file begins with the number of elements, the number of nodes comprising a tetrahedron (= 4 in
PHITS), and the number of information points tagged to the element (=1 in PHITS) [second line]. The following
lines (below the third line) give a list of 4-node IDs, each corresponding to a tetrahedron, in the order
[element no.] [node 1] [node 2] [node 3] [node4] [element universe no.]
The element no. represents the ID of the tetrahedron element. The node no. specifies the list of 4-node IDs in the
node file. The element universe no. specifies the universe used to fill the tetrahedron element; the definition of this
universe should be given in the PHITS input file (See Example 44). Arbitrary comment lines starting with # can
be inserted into any line of the node or element file.
The node and element files can be created using the Tetrahedral Mesh Generator (TetGen) software, which
can convert general polygon mesh data to tetrahedron geometry with some effort. TetGen can be obtained free of
charge from the following source:
http://wias-berlin.de/software/tetgen/
For details on TetGen, please refer to the manual in the link above.
PHITS adopts another format, which is the bulk data format of NASTRAN. This format is a generally accepted
in many software of structural analysis and computational fluid dynamics (CFD). PHITS uses the bulk data format
defined using GRID and CTETRA and assumes those are written in a file with .bdf extention. The explantion of
the buld data format is omitted here because the file will be deduced automatically from some software which is
used to create the tetrahedron geometry. By adopting the same format for the tetrahedral geometry in PHITS as
structural analysis or CFD, seamless coupled analysis between those studies and radiation transport calculation
becomes possible. For the details, a document will be uploaded in the PHITS homepage
http://phits.jaea.go.jp/
which explains how to conduct such a coupled analysis.
The method for using tetrahedron geometry in a PHITS input file is explained below.
To use tetrahedron geometry, a region must be defined as a rectangular shape (using the surface symbol RPP).
This region should contain all of the nodes of the tetrahedrons that will be created but should not be so large that it
incurs unnecessary computational costs. At the tenth line in the example code, a region with cell no. 101 is defined
as a rectangular shape specified by surface number 20 as a 14 cm × 10 cm × 14 cm rectangular box. Setting the LAT
option =3 declares the use of a tetrahedron geometry defined by the node and element files with names specified by
5.6 [ Cell ] section 143
Node 4
Element 1
Node 5 Node 2
Node 3
Element 2
Node 1
TFILE. For a file of the NASTRAN bulk data format, the name should be specified accompanied by file NFILE as
in the example 45. The file of the name with the suffix .bdf will be imported. Note that the upper and lower cases
of the file name differ between Mac and Linux. Using the TSFAC factor allows the size of the tetrahedron geometry
to be scaled up or down by multiplying the coordinates of the nodes by the value of the factor. The material given
in cell 101 is used to fill all of region 101 aside from the tetrahedron interiors. In the eleventh line the region with
cell no. 1 is defined as a rectangular box of dimensions 10 cm × 6 cm × 10 cm. Using the FILL option, this
region is filled by the tetrahedron geometry of cell no. 101. The Tetrahedron Geometry setting (LAT=3) should be
used together with the universe and fill nest structures in the same manner as in lattice structure specification; the
universes included in the element file should be defined in the same manner as in the lattice structure (this is done
in lines 13 and 14 in this example, where element no. 1 is filled by material 2 (water), while element no. 2 is filled
by material 3 (iron).
When the number of universes used in the tetrahedron geometry increases, the cost manually creating the cells
done in lines 13 and 14 in the example 44 becomes heavy. By specifying the option itetauto=1 in the parameter
section, the cells corresponding to the universes for tetrahedron geometry will be automatically created. With this
option, extreamly large surface no. 5000 and cells from no. 5001 to no. 5000+n are added to those given in the
PHITS input file and thus use of those no. should be avoided to use this option, where n is number of universes
used in the tetrahedron geometry. Density of the added cells are automatically defined by reading PSOLID and
MAT tabs when a file with the NASTRAN bulk data format is used. For a TetGen format file, density information
should be provided by an external file. The file name needs to be a common but with .txt suffix. The universe no.
and its density should be specified for each line as 46. The addional cells will be provied with the same material no.
as the cell. Error messages as shown in 47 will be displayed by executing PHITS without specifying the materials
corresponding to the universes in the tetrahedron geometry. The materials from 5001 to 5000+n should be defined
according to these messages. This automatic process can be verified by cheking the input echo lines in the phits.out
file, where the additional surface and cells will be inserted.
[ Transform ]
TRn O1 O2 O3 B1 B2 B3 B4 B5 B6 B7 B8 B9 M
The format with ∗, ∗TRn, is also used. When ∗TRn, components of a rotation matrix Bi can be given by angles
in the unit of [degree].
item explanation
n Transform number. Use any number from 1 to 999,999.
O1 , O2 , O3 x, y, z components for translation.
B1 ∼ B9 Components of rotation matrix. Please see Eqs. (19)∼(22) in more detail. The determinant of the
matrix is automatically adjusted to 1.
M Option for equation of coordinate transformation.
= 1: translation is performed after rotation.
= −1: rotation is performed after translation.
= ±2: these options need only B1 , B2 , B3 to define rotation angles around z, y, x axes, respectively.
The order of the rotations is z, y, x. The unit of the angles is radian when TRn, and that is degree
when ∗TRn (the format with ∗). The mathematical definition of the transformation of M = 2 and
−2 is the same as M = 1 and −1, respectively.
TRn 0 0 0 1 0 0 0 1 0 0 0 1 1
When M = ±2, the parameters should be set like the following example:
TRn x0 y0 z0 θz θy θx 0 0 0 0 0 0 2
where, x0 , y0 , z0 are ,respectively, x, y, z-components for the translation, and θz , θy , θ x are rotation angles around
z, y, x-axes, respectively. For B4 -B9 , any values, such as zero, should be set.
for M = 1,
′
x B1 B4 B7 x O1
′ y + O2 ,
y = B2 B5 B8 (19)
z′ B3 B6 B9 z O3
for M = −1,
′
x B1 B4 B7 x − O1
′
y = B2 B5 B8 y − O2 . (20)
z′ B3 B6 B9 z − O3
In the case of M = 1, the object using this transform function is rotated and then translated. On the other hand, in
the case of M = −1, the rotation is performed after the translation. The rotation is performed about the origin of
the xyz coordinate system. Note that the direction of the translation setting M = 1 and −1 is opposite each other.
For the case of tallies, the mathematical definition of M = 1 is given as,
′
x B1 B2 B3 x − O1
y′ = B4 B5 B6 y − O2 , (21)
′
z B7 B8 B9 z − O3
and that of M = −1 is given as,
′
x B1 B2 B3 x O1
′
y = B4 B5 B6 y + O2 . (22)
z′ B7 B8 B9 z O3
Because tally results are output in the coordinates system after the transformation, the relation between (x, y, z) and
(x′ , y′ , z′ ) in the equations in the case of tally is opposite to that in the other case.
When M = ±2, the input format is simplified. The mathematical definition of M = 2 and −2 are the same as
M = 1 and −1, respectively.
In this example, tr1 rotates the coordinate by c10 degrees around z axis, c20 degrees around y axis and finally
c30 degrees around x axis. By setting c10, c20, c30, the rotation can be defined.
These are examples of M = 2, which gives the same definition of the rotation as the above example. The rotation
angles of ∗TR1 are given in units of degree, and those of TR2 are given in radian.
146 5 SECTIONS FORMAT
[ Temperature ]
reg tmp
1 1.0*1.e-8
11 5.0*1.e-8
( { 2 - 5 } 8 9 ) 2.0*1.e-8
( 11 12 15 ) 3.0*1.e-8
16 6.0*1.e-8
.... ........
.... ........
The format ( { 2 - 5 } 8 9 ) can be used. However, any value that is not single numeric must be enclosed
value by ( ) .
The lattice and universe style can be used as ( 6 < 10[1 0 0] < u=3 ).
To change the order of region number (reg) and temperature (tmp), set as tmp reg. The skip operator non
can be used.
5.9 [ Mat Time Change ] section 147
In the above example, the material 1 is changed to material 11 at t = 50.0 nsec, 2 to 12 at 100 nsec and 3 to
void at 1000 nsec. If you want to replace the order of the initial material (mat), time (time) and the final material
(change), set as mat change time. You can use the skip operator non. These three columns are always necessary
to define the mat time change function.
148 5 SECTIONS FORMAT
[ Magnetic Field ]
reg typ gap mgf trcl time
1 4 10.00000 -5.956540 3 non
2 4 10.00000 6.416140 1 non
3 2 10.00000 -7.611980 0 0.0
4 2 10.00000 3.516000 0 pi/2
( 150 < 61 ) 4 13.00000 7.880140 2 non
( 150 < 62 ) 4 13.00000 -7.440800 2 non
( 150 < 63 ) 4 13.00000 9.441010 2 non
( 150 < 64 ) 4 13.00000 -8.295220 2 non
( 150 < 65 ) 4 13.00000 3.694830 2 non
( 150 < 66 ) 4 13.00000 -2.099350 2 non
... ... ........ ........ ... ...
... ... ........ ........ ... ...
The column of trcl is omitted. The zero for trcl means no transformation. The time is a parameter of user defined
time dependent magnetic field. The column of time is also omitted. The non for time means no time dependence.
Two subroutines, “usrmgt1.f” and “usrmgt2.f” are included in the source as user defined subroutines for the time
dependent magnetic field. The former is for Wobbler magnet, and the latter is for pulse magnet for neutron optics.
These two subroutine are chosen by setting usrmgt=1, 2 in the [parameters] section. For the Wobbler magnet
and pulse magnet, time means phase of the magnet and starting time, respectively.
In the above expression, reg is region number, typ can take 2 or 4 for dipole electromagnet, or quadrupole
electromagnet, respectively. mgf denotes the strength of the magnetic field [kG], and trcl is the coordinate
transformation number defined in the [transform] section.
The format ( { 2 - 5 } 8 9 ) can be used. However, any value that is not single numeric must be enclosed
value by ( ) . The lattice and universe style can be used as ( 6 < 10[1 0 0] < u=3 ).
By using this format, the different magnetic field can be set for each lattice. If a cell is re-defined, the value,
which is defined at first, is used.
In the case of dipole magnet, the distances gap make no sense, but set any numeric. The magnetic field is
available not only in the void region, but also in the material where the normal reaction can be occurred.
z-axis is assumed to be the center of the magnetic field. The direction of the magnetic field is positive direction
of y-axis for dipole, i.e., the positive charge particle is bent to positive direction of x-axis when it goes to positive
direction of z-axis. For quadrupole, the positive particle is converged in x-axis, diverged in y-axis when it goes to
positive direction of z-axis. The coordinate transformation by trcl is needed for different geometrical situation.
When specifying charge number of the projectile particle with izst in [source] section, the motion of the
particle with the number in the magnetic field is described. Using izst, PH I TS can simulate the motion of the
particle with charge states. The charge number defined with izst doesn’t change while the particle moves. It
should be noted that particles produced from nuclear reactions are not affected by the value of izst; the charge of
the produced particle is given as its atomic number.
[t-track] uses deltm as a step length to describe particle trajectories in a magnetic field that continuouly
changes particles’ momenta. Please adjust deltm to describe the trajectory curve more smoothly.
5.10 [ Magnetic Field ] section 149
5.10.2 Neutron
The definition of the magnetic field for neutron is almost the same as for charged particles. Here we describe
the detail of the magnetic field for neutron.
[ Magnetic Field ]
reg typ gap mgf trcl polar time
1 60 0.00000 35000.0 3 non non
2 61 0.00000 35000.0 1 1 non
3 106 5.00000 7130.0 0 0 non
4 104 0.00000 3.5 0 non 5.0
5 102 0.00000 0.20 0 non non
6 101 3.00000 7130.0 2 1 non
7 103 0.00000 35000.0 0 -1 non
... ... ........ ........ ... ... ...
... ... ........ ........ ... ... ...
We cannot take into account of the gravity nor additional dipole magnet. For 60 case, it is assumed that the spin
always keeps parallel or anti-parallel to the magnet field. For 61 case, we solve the coupled equation of motion
between the spin and the magnetic field. Then the spin flip can be occurred in the region with weak magnetic field.
The strength of the magnetic field is specified in the unit of [T/m2 ] in mgf column.
For the types above 100, we consider the coupled equations of the spin and the magnetic field. In addition, the
effects of the gravity and additional dipole field can be taken into account. 106 is sextupole, 104 quadrupole, and
102 dipole, respectively. The strength of additional quadrupole magnet (z-direction) is give by the column of gap
in the unit of [T].
For 101 type, the magnetic field is defined by the user program file, “usrmgf1.f.” In this user program, the data
measured by the neutron optics group in JAERI are read from the file and used the calculation. The strength of this
field is renormalized by the value of mgf.
For 101 type, the magnetic field is also defined by the user program file, “usrmgf3.f.” In this user program,
there is a simple sextupole magnet field as same as in 106 type.
The neutron goes into the magnetic field with the initial spin if it is defined in the source section. If not, the
initial spin is defined at the moment when the neutron goes into the magnetic field. The ratio of the number of
parallel and anti-parallel spin to the magnetic field is determined by the polarization defined by the polar column.
non in polar column means 0 polarization. The polarization is defined as
ϕ+ − ϕ−
P= ,
ϕ+ + ϕ−
here, ϕ+ and ϕ− are the number of the parallel and anti-parallel particles.
150 5 SECTIONS FORMAT
[ Magnetic Field ]
reg typ gap mgf trcl file
101 -1 10.0 0.5 0 xyzlist.dat
102 -2 100.0 3.0 0 rzlist.dat
103 -3 10.0 10.0 0 xyzmap.dat
104 -4 1.0 1.0 1 rzmap.dat
Four types of magnetic field maps can be read by PHITS, which are specified by typ=−1, · · · , −4 for charged
particles, and typ=−101, · · · , −104 for neutrons. Only one magnetic field map can be defined for each type in an
input file. The meanings of each type are shown in Table 5.74. (see Sec. 5.10.4 in more detail):
typ explanation
−1 or −101 xyz grid, data list type
−2 or −102 r-z grid, data list type
−3 or −103 xyz grid, data map type
−4 or −104 r-z grid, data map type
The meanings of gap and mgf are different from those for the case of the conventional magnetic fields, where
gap is inversely proportional to the step size for calculating particle trajectory, i.e. setting the higher value for gap
results in the smoother trajectory but longer computational time, while mgf indicates the normalization factor of
the field strength for the magnetic field map cases. For example, you have to set mgf=10 when your magnetic field
map is written in the unit of T because the unit of magnetic field in PHITS is kG. Note that electron and positron
step sizes in the magnetic field are automatically determined irrelevant to gap. Name of the magnetic field map
file is specified by file parameter.
5.10 [ Magnetic Field ] section 151
Header format
In the header part, discrimination between lowercase and uppercase characters is not performed, and blank
is ignored in the same as PHITS input. Only one parameter can be specified in one line. Table 5.75 shows the
parameter list to be specified in the header part:
parameter explanation
nx number of x grid (only for typ=-1 & -3, not omissible)
ny number of y grid (only for typ=-1 & -3, not omissible)
nz number of z grid (only for typ=-1 & -3, not omissible)
nr number of r grid (only for typ=-2 & -4, not omissible)
xmin minimum value of x grid in cm (only for typ=-3,D=0)
xmax maximum value of x grid in cm (only for typ=-3, not omissible)
ymin minimum value of y grid in cm (only for typ=-3,D=0)
ymax maximum value of y grid in cm (only for typ=-3, not omissible)
zmin minimum value of z grid in cm (only for typ=-3 & -4,D=0)
zmax maximum value of z grid in cm (only for typ=-3 & -4, not omissible)
rmin minimum value of r grid in cm (only for typ=-4,D=0)
rmax maximum value of r grid in cm (only for typ=-4, not omissible)
ibxmap existence of the Bx map (yes=1, no=0) (only for typ=-3, D=1)
ibymap existence of the By map (yes=1, no=0) (only for typ=-3, D=1)
ibzmap existence of the Bz map (yes=1, no=0) (only for typ=-3 & -4, D=1)
ibrmap existence of the Br map (yes=1, no=0) (only for typ=-4, D=1)
extendx extend the field to negative x (only for typ=-1 & -3, omissible)
extendy extend the field to negative y (only for typ=-1 & -3, omissible)
extendz extend the field to negative z (for all typ, omissible)
data End of header.
Data format
In the data part, only numerical values with separation of comma, tab, or blank can be written. Comments
cannot be inserted except for columns behind the last numerical data of each line. The units of the grid coordinate
and the magnetic field are cm and kG, respectively. Note that the magnetic field strength at the point of each grid
should be given instead of that at the center of each grid-mesh. The followings are the format of each field type:
r1 z1 Br1,1 Bz1,1
r1 z2 Br1,2 Bz1,2
.. .. ..
. . .
r1 znz Br1,nz Bz1,nz
r2 z1 Br2,1 Bz2,1
.. .. ..
. . .
rnr znz Brnr,nz Bznr,nz
The order of the data cannot be changed. However, you can omit to define the field strength for certain
directions by specifying ibxmap, ibymap, ibzmap, ibrmap for typ=-3 & -4. In that case, the field strength
for the omitted direction are assumed to be 0. For typ=-1 & -2, the grid coordinates should be given in the
ascending order. The computational time for the data map types are generally shorter than that for the data list
type, but they are nearly equivalent when the interval of each grid coordinate is constant.
154 5 SECTIONS FORMAT
When specifying charge number of the projectile particle with izst in [source] section, the motion of the
particle with the number in the electro-magnetic field is described. Using izst, PHITS can simulate the motion of
the particle with charge states. The charge number defined with izst doesn’t change while the particle moves. It
should be noted that particles produced from nuclear reactions are not affected by the value of izst; the charge of
the produced particle is given as its atomic number.
[t-track] uses deltm as a step length to describe particle trajectories in an electro-magnetic field that con-
tinuouly changes particles’ momenta. Please adjust deltm to describe the trajectory curve more smoothly.
5.12 [ Delta Ray ] section 155
[ delta ray ]
reg del
1 0.1
11 1.0
.... ....
.... ....
You can use the format ( { 2 - 5 } 8 9 ). But you need to close a value by ( ) if it is not a single numeric
value. You cannot use the lattice and universe style as ( 6 < 10[1 0 0] < u=3 ). If you want to replace the
order of region number (reg) and the threshold energy (del), set as del reg. You can use the skip operator non.
Even if you use GG, use the symbol not cell but reg here.
48 J. J. Butts and R. Katz, “Theory of RBE for Heavy Ion Bombardment of Dry Enzymes and Viruses”, Radiation Research 30, 855-871
(1967).
156 5 SECTIONS FORMAT
[track structure]
reg mID
1 1
2 0
You can use the format ( 2 - 5 89 ). But you need to close a value by ( ) if it is not a single numeric
value. You cannot use the lattice and universe style as ( 6 < 10[100] < u=3 ). If you want to replace the
order of region number (reg) and index of the cross section database (mID), set as mID reg. You can use the skip
operator non.
The followings are the important parameters for this mode. The parameters of etsmax and etsmin in [parameters]
section are maximum and minimum energies of particles simulated by track-structure mode. In case of the use
of the track-structure mode, the parameters of emin(12) and emin(13) should be set concurrently to 1.0e-3, and
EGS5 should be activated (negs=1).
[ Parameters ]
emin(12) = 1.E-03
emin(13) = 1.E-03
negs = 1
etsmax = 1.E-2
etsmin = 1.E-6
49T. Kai et al., “Thermal equilibrium and prehydration processes of electrons injected into liquid water calculated by dynamic Monte Carlo
method,” Radiat. Phys. Chem., 115, 1-5 (2015).
5.14 [ Super Mirror ] section 157
4π sin θ
Q = |ki − k f | = .
λ
The value of m is a parameter determined by the mirror material, the bilayer sequence and the number of bilayers.
Qc is the critical scattering wave vector for a single layer of the mirror material. At higher values of Q, the
reflectivity starts falling linearly with a slope α until a cutoff at Q = mQc . The width of the cutoff is denoted W.
These parameters are defined as
[ Super Mirror ]
r-in r-out mm r0 qc am wm
{2001-2020} 3001 3 0.99 0.0217 3.0 0.003
2500 3500 3 0.99 0.0217 3.0 0.003
2600 3600 3 0.99 0.0217 3.0 0.003
.... .... .. ... .... ... ...
.... .... .. ... .... ... ...
.... .... .. ... .... ... ...
The reflection surface is defined by the surface between r-in and r-out. You can use the format ( { 2 - 5 }
8 9 ), and you can use the lattice and universe style as ( 6 < 10[1 0 0] < u=3 ) in these definitions. The
remaining parameters in above expression denote m by mm, R0 by r0, Qc by qc in Å−1 , α by am in Å, and W by wm
in Å−1 .
We restrict this function only to neutrons for the case that its energy is less than 10 eV or sinθ is greater than
0.001, the latter is due to roughness of the surface.
158 5 SECTIONS FORMAT
[ Elastic Option ]
reg c1 c2 c3 c4
1 5 1 3.3 0.4
2 1 1 1.1 0.7
3 3 1 0.3 0.8
.... ... ... ... ...
.... ... ... ... ...
If you want to replace the order of region number (reg), (c1 c2 c3 c4), set as reg c3 c2 c1 c4. You can use
the skip operator non. You can use the format { 4 - 7 }, but the ( { 4 - 7 } 9 10 ) format cannot be used.
The sample routine of “usrelst1.f” is for Bragg scattering based on the data base, and “usrelst2.f” for any type
of angular distribution described by an analytic formula.
5.16 [ Data Max ] section 159
[Data Max]
part = neutron proton
mat nucleus dmax
all Fe 20
5 all 50
3 56Fe 150
Particle is defined in the first line as part=. Only neutron and proton can be define in PHITS ver. 2.86.
Three columns, mat, nucleus, and dmax, can be used. If you want to change the order of (mat) (nucleus), set
as nucleus mat. You can use the skip operator non. In the mat column, material numbers can be specified and
all means all materials. In the nucleus column, you can specify nucleus as 56Fe and 26056 type. You can use Fe
or 26000, which specifies all isotopes of Fe. You can also use all. By the number (MeV) in the dmax column, you
define the maximum energy of library use for the nucleus.
If the same nucleus is defined in the [data max] sections, the latest definition has priority in an input file.
The values of dmax(1) and dmax(2) defined by [parameters] section should be the maximum value in
[data max] section.
If kmout=1 is specified in [parameters] section, the values of dmax for each nucleus in the materials are
shown in the output file, file(6) (D=phits.out).
160 5 SECTIONS FORMAT
[ Frag Data ]
opt proj targ file
0 12C 16O DDX_12C-16O.dat
1 proton 63Cu DDX_p-63Cu.dat
.... ... ... ... ...
.... ... ... ... ...
The user defined cross sections are not used when opt=0. In the case of opt=1, PHITS reproduces the cross
section of the reaction between an incident particle and target, which are specified by proj and targ, respectively,
using the data. Options when opt=2,3 are under construction. When opt=4, PHITS simply extrapolates the given
data for incident energies, emission angles, and emission energies. Note that you can use this option only in the
case of neo>0 and nag,0, which will be explained below.
Format of the data of the user defined cross sections is as follows.
projectile
target
nei
ein(1) ein(2) ein(3) ...... ein(nei+1)
totxs(1) totxs(2) totxs(3) ...... totxs(nei+1)
neo
eout(1) eout(2) eout(3) ...... eout(neo+1)
nag
angle(1) angle(2) angle(3) ...... angle(nag+1)
nfrg
frag(1) frag(2) frag(3) ...... frag(nfrg)
.........
.........
5.17 [ Frag Data ] section 161
(continued)
.........
.........
.........
.........
.........
.........
In the beginning, you specify incident particle and target in this file. nei is the number of points of the energy
mesh. In the next line, you set nei+1 points of incident energies (ein in the unit of MeV/u). neo is the number of
energy mesh points of the outgoing particles. In the next line, you set neo+1 points of the energy (eout in the unit
of MeV/u), and then in the next next line you set neo+1 data of total reaction cross sections (totxs in the unit of
mb). Note that when totxs=0, total reaction cross sections obtained by models, which are specified by icxsni or
icrhi, are used. nag is the number of angular mesh points for the outgoing particles. You set nag+1 data of the
angles in the next line. If nag>0 the data should be given in the unit of radian, and if nag<0 those are in the unit is
degree. When nag=0, isotropic is assumed. nfrg is the number of the outgoing particles. In the next line, you write
nfrg names of the particles. proxs (in the unit of mb) is the production cross sections of the particles at an incident
energy, and then you set neo×nag data of the double differential cross sections (ddx in the unit of mb/MeV/sr).
You have to specify nei+1 groups of the proxs and ddxs per an outgoing particle.
If you write model in the line where you should write neo, nuclear reaction models are used for simulating
nuclear reaction events. In this case, you do not have to write the data below neo.
10: 1
11: neutron
12: 300.0
13: 10.0 10.0 10.0 10.0 10.0 10.0
14: 15.0 13.0 12.0 11.0 10.0 10.0
15: 10.0 11.0 10.0 11.0 10.0 10.0
16: 0.0
17: 5.0 5.0 5.0 5.0 5.0 5.0
18: 10.0 8.0 7.0 6.0 5.0 5.0
19: 5.0 6.0 5.0 6.0 5.0 5.0
An example of the data file of the user defined cross sections is shown in Example 50. In first and second lines,
proton and 63 Cu are defined as incident particle and target, respectively. In third line, nei=1 is set. Tow data of
incident energies and total reaction cross sections are given in fourth and fifthe lines, respectively. In sixth line
neo=3 is set, and then 4 values of 1.0, 10.0, 50.0, and 100.0MeV are given as energies of the outgoing particles.
The number of angular mesh points nag=-6 is set in eighth line. In this case, the angles are given in the unit of
degree. In tenth and eleventh lines, the number of particles and its kind (neutron) are specified, respectively. In
twelfth line, a production cross section of neutron at the 10.0MeV proton is given. The double differential cross
sections of the neutron are set in thirteenth, fourteenth, and fifteenth lines. Each lines correspond to the energy
bins defined in seventh line, and each columns correspond to the angular bins defined in ninth line. The production
cross section is used as a normalization factor. When proxs=0 (mb), the integrated values of the ddxs are used as
proxs.
When neo is negative, you can set the intensity of the cross section discretely. In this case, the number of eout
should be neo.
If neo is 0, the energy spectra of the outgoing particle can be given by Gaussian distribution. In the places of
ddxs, you set mean value and FWHM of the Gaussian in the unit of MeV.
5.18 [ Importance ] section 163
[ Importance ]
part = proton neutron
reg imp
1 1.000000
11 5.000000
( { 2 - 5 } 8 9 ) 2.000000
( 11 12 15 ) 3.000000
( 6<10[1 0 0]<u=3 ) 6.000000
.... ........
.... ........
Particle is defined as part= at the first line. If the part is not defined, default value is defined as part=all. The
format to describe particles is the same as in tally definition. However, it can distinguish ityp only, each nucleus is
not specified.
If you want to change the order of region number (reg) and (imp), set as imp reg. You can use the skip
operator non. Even if you use the GG, you should write not cell but reg here.
You can use the format like ( { 2 - 5 } 8 9 ), and you can use the lattice and universe style as
( 6 < 10[1 0 0] < u=3 ). But you need to close a value by ( ) if it is not a single numeric value. The
importance of bottom level is a product by each importance at each level. In PHITS, importance of a specific cell
at bottom level can be defined by above format. By using the format, we can define different importance into each
lattice. If the importance is double-defined, the first defined importance is valid.
If you set large importance to particles which have strong penetration through matter such as neutrino, PHITS
calculation takes time too much. If you define part=all, neutrino is included. You must give attention about it.
Some rules can be used to define an importance of a cell in a repeated structures and lattices. For example,
cells 5, 6, and 7 on a bottom level are included by cells 11, 12, and 13 on upper level, we can define the importance
as
1: [ Importance ]
2: reg imp
3: ( 5 6 7 < 11 ) 2.0
4: ( 5 6 7 < 12 ) 4.0
5: ( 5 6 7 < 13 ) 8.0
6: ( 11 12 13 ) 1.0
or
1: [ Importance ]
2: reg imp
3: ( 5 6 7 ) 1.0
4: 11 2.0
5: 12 4.0
6: 13 8.0
Above two definitions give same results, but in the latter case, the importance for cells 5, 6, and 7 are displayed as
1.0 at the importance summary.
164 5 SECTIONS FORMAT
[ Weight Window ]
mesh = reg
part = proton neutron
eng = 5
( tim = 5 )
6.00e-7 3.98e-1 1.00e+0 7.00e+0 5.00e+4
reg ww1 ww2 ww3
1 0.010000 0.100000 0.001000
11 0.005000 0.050000 0.000300
( { 2 - 5 } 8 9 ) 0.001000 0.010000 0.000100
( 11 12 15 ) 0.000500 0.005000 0.000030
( 6<10[1 0 0]<u=3 ) 0.000010 0.001000 0.000010
.... ........ ........ ........
ww4 ww5
0.010000 0.100000
0.005000 0.050000
0.001000 0.010000
0.000500 0.005000
0.000010 0.001000
........ ........
Mesh type should be defined in the 1st line, i.e. mesh=reg or xyz. When mesh is not defined, the default setting
mesh=reg is set. For mesh=xyz, x-type, y-type, and z-type must be defined in subsequent lines (see Sec. 6.
Geometrical mesh in detail). Particle type should be defined as part=. part=all means all particles. The format
to describe particles part= is the same format as in tally definition. However, it can distinguish ityp only, each
nucleus is not specified.
Next you define the energy mesh or time mesh. First, you define the number of mesh by eng= or tim= and,
in next line, the values of each mesh (e1 , e2 , e3 , ....). Minimum value of weight window for each mesh should be
defined in the followings. Each minimum values are like ww1, ww2, ww3, .... where wwi is a window minimum
value for a mesh ei−1 < E < ei . e0 = 0 and t0 = −∞ is assumed. If there exists no eng= / tim= definitions, energy
/ time mesh are not prepared. In this case, you should set only ww1.
Region (ref or xyz) must be written at the first column. As above example, you can make another table for
wwi definitions. From second table, the region definition can be skipped as the example. You can use the skip
operator non in this section.
You can use the format ( { 2 - 5 } 8 9 ), and you can use the lattice and universe style as ( 6 < 10[1 0
0] < u=3 ). But you need to close a value by ( ) if it is not a single numeric value. For mesh = xyz, the
position of each data should be defined as (ix iy iz).
If you set large weight window to particles which has strong penetration through matter such as neutrino,
PHITS calculation takes time too much. If you define part=all, neutrino is included. You must give attention
about it.
5.20 [ WW Bias ] section 165
Figure 5.48: The flowchart of the connection calculation between [weight window] and [ww bias].
The format of [ww bias] is as follows: (Note that set the same particle, energy-mesh, and cell numbers as
[weight window].)
[ WW Bias ]
part = neutron
eng = 2
1e-3 1.0
reg wwb1 wwb2
1 0.25 0.25
2 0.50 0.50
3 1.00 1.00
4 2.00 2.00
.... ........ ........
In the first line, part= defines which particle is to be considered. When it is omitted, part=all is set. The
expression of part= is the same as that in the tally format. Note that only the expression as ityp can be set. Each
nuclides cannot be specified. Next, the energy mesh should be defined. The line starting with eng= specifies the
number of mesh. In the next line, energies (e1 , e2 , e3 , ...) are defined. Furthermore, names of columns are gives
as reg, wwb1, wwb2, .... In the reg column, the cell numbers are written. The bias values are given in the
columns of wwbi. The skip operator non can be used. Each wwbi column corresponds to energies of ei−1 < E < ei .
166 5 SECTIONS FORMAT
Here, e0 = 0. The format ( { 2 - 5 } 8 9 ) can be used, as can the lattice and universe style ( 6 < 10[1 0
0] < u=3 ). However, any value that is not single numeric must be enclosed value by ( ) .
By setting iwwbias=1 in [parameters], the [weight window] parameters multiplied by inverse of the
defined biases in [ww bias] are used. In this case, the products of the multiplication are output in the input echo
of [weight window], and [ww bias] with off is output. If an input file without [ww bias] is used, all values
of [ww bias] in the input echo are set to 1.
An example of [ww bias] is as follows.
Here, neutron is considered as part. One energy region of 100 GeV below is specified. Regions between 1 and
12 are gradually biased. The region of the large number is biased stronger than that of the small number.
5.20 [ WW Bias ] section 167
Figure 5.49(a) shows the xz cross-section view of a geometry; a concrete cylinder with a central axis on the z
axis with a radius of 100cm. Two results of the neutron fluence obtained by the transport calculation without and
with [ww bias] were shown in Figs. (b) and (c), respectively. Source particles of 14MeV-neutrons were generated
at x = 0, y = 0, z = 90cm as an isotropic source. After generating a [weight window] section by [t-wwg], the
result shown in Fig. (b) was obtained by performing the calculation with only the [weight window] section. The
result of the calculation with both the [weight window] section and the [ww bias] section of the example 51
was shown in Fig. (c). The neutron fluence in Fig. (b) was distributed in both regions of the small and large cell
numbers. On the other hand, the fluence in Fig. (c) was distributed in only the large cell numbers, which were
Date = 13:14 16-Aug-2017
[t-track] in xyz mesh
File = D:\home\hashimoto\STUDY\houkoku\phits\manual\tex\old-file\WWBG\WWBias\geometry\weight-dose-xz-g.out
biased by [ww bias] of the example 51. As seen in this example, to focus on a certain region, the calculation can
be efficiently performed by [ww bias]. emin = 1.0000E-10 [MeV]
(a) Geometry emax = 1.0000E+03 [MeV]
ymin = -2.0000E+01 [cm]
100 ymax = 2.0000E+01 [cm]
part. = neutron
mset = 1
50
x [cm]
void
0 1 2 3 4 5 6 7 8 9 10 11 12
1
−50
−100
Date = 13:17 16-Aug-2017 Date = 13:17 16-Aug-2017
[t-track] in xyz 0mesh
File = D:\home\hashimoto\STUDY\houkoku\phits\manual\tex\old-file\WWBG\WWBias\without-bias\weight-dose-xz-n.out [t-track] in xyz mesh
File = D:\home\hashimoto\STUDY\houkoku\phits\manual\tex\old-file\WWBG\WWBias\with-bias\weight-dose-xz-n.out
50 100 150
z [cm]
emin = 1.0000E-10 [MeV] emin = 1.0000E-10 [MeV]
(b) Without [WW
calculated by PHITSBias]
2.95
emax = 1.0000E+03 [MeV] (c) With [WW Bias] plotted by ANGEL 4.35
emax = 1.0000E+03 [MeV]
ymin = -2.0000E+01 [cm] ymin = -2.0000E+01 [cm]
100 ymax =100 2.0000E+01 [cm] ymax = 2.0000E+01 [cm]
part. = neutron part. = neutron
10−3 mset = 1 10−3 mset = 1
10−4 10−4
50 50
10−5
10−5
(µSv/h)/(source/sec)
(µSv/h)/(source/sec)
x [cm]
x [cm]
10−6
10−6
0 1 2 3 4 5 6 7 8 9 10 11 12 0 1 2 3 4 5 6 7 8 9 10 11 12
10−7
10−7
10−8
10−8
−50 −50
10−9
10−9
10−10
10−10
−100 −100
0 50 100 150 0 50 100 150
z [cm] z [cm]
calculated by PHITS 2.95 calculated by PHITS 2.95 plotted by ANGEL 4.35 plotted by ANGEL 4.35
Figure 5.49: (a) xz cross-section view of the geometry. (b) Result without [ww bias]. (c) Result with [ww
bias] of Example 51.
168 5 SECTIONS FORMAT
[ Forced Collisions ]
part = proton neutron
reg fcl
1 1.000000
11 0.500000
( { 2 - 5 } 8 9 ) 0.200000
( 11 12 15 ) 0.300000
( 6<10[1 0 0]<u=3 ) -0.500000
.... ........
.... ........
You set particle as part= in the first line. The default is part=all. part= is the same format as in tally definition.
If you want to replace the order of region number (reg) and (fcl), you can set as fcl reg. You can use the
skip operator non. Even if you use GG, you should write the symbol not cell but reg here.
You can use the format ( { 2 - 5 } 8 9 ), and you can use the lattice and universe style as
( 6 < 10[1 0 0] < u=3 ). But you need to close a value by ( ) if it is not a single numeric value. By
using this format you can set different forced collision factor for each lattice. If the same cell is re-defined, the
value, which is defined at first, is used.
The forced collision factor fcl means, 0: no forced collision, | f cl| > 1: is an error, and | f cl| ≤ 1 : multiply
forced collision probability by f cl, instead the weight is reduced by 1/ f cl times.
We have two options to control the particle transport and multiple scattering with the weight cut off in the
forced collisions region. When f cl < 0, secondary particles produced by forced collisions are treated by the
normal process. In this case, weight cut off is not performed. When f cl > 0, the forced collision is also applied
to secondary particles. In this case, weight cut off is performed. Even if a particle is killed by this weight cut off,
of course the particle is tallied before killed. There is a possibility that all particles are killed by this weight cut
off, if you set the weight cut off and the forced collisions without consideration. For example, it corresponds to
tallying tracks of secondary particles and information of particles at a distance from the forced collisions region.
When you want to transport secondary particles produced by forced collisions, you should decrease the value of
the cutoff weight parameter wc1(i) in the [parameters] section.
5.22 [ Volume ] section 169
[ Volume ]
reg vol
1 1.000000
11 5.000000
( { 2 - 5 } 8 9 ) 2.000000
( 11 12 15 ) 3.000000
16 6.000000
.... ........
.... ........
You can use the format ( { 2 - 5 } 8 9 ) for a group. In this case, you need to close a value by ( ) , if it
is not a single numeric value.
You cannot use the lattice and universe style as ( 6 < 10[1 0 0] < u=3 ). If you want to set cell volume
in detail, use the volume definition in the tally section.
If you want to change the order of region number (reg) and volume (vol), you can set as vol reg. You can
use the skip operator non. Even if you use GG, you should write the symbol not cell but reg here.
170 5 SECTIONS FORMAT
[ Multiplier ]
number = -201
interpolation = log
part = all
ne = 10
20.0 2.678
30.0 7.020
50.0 18.50
100.0 24.26
200.0 16.13
500.0 10.51
1000.0 10.55
2000.0 10.98
5000.0 12.10
10000.0 12.45
The ID number of each [multiplier] section can be set by negative integer between -200 and -299. Particle
type can be specified by part parameter. part = all indicates that the data are applicable to all particle. For
the data interpolation method, you can select from lin, log, glow, and ghigh, which indicate the linear-linear
interpolation, the log-log interpolation, and group data by specifying lower and higher boundary of each energy
group, respectively. The number of the energy point or group is given by ne, and the data of each energy and factor
should be defined in the subsequent lines. Note that the data should be listed in ascending order of energy.
From ver. 3.03, the conversion coefficients for several types of radiation doses and soft error rate (SER)
on semiconductor devices are pre-defined. Table 5.76 shows the multiplier ID of pre-defined data. Those data
are included in phits/data/multiplier directory with the file name of “m+|ID|+.inp” (e.g., m200.inp for
k = −200). The unit of conversion coefficients for radiation dose is pSv·cm2 , and that for soft error rate is
(FIT/Mbit)/(/cm2 /s). You can add your own [multiplier] section in this folder. If you specify [multiplier]
section with the same ID number in your input file, the pre-defined data are overwritten by the specified data.
The conversion coefficients for SER are derived from the neutron-induced SEU cross section for a virtual semi-
conductor device calculated by PHITS and device simulator 50 . The background SER51 is about 400 (FIT/Mbit).
Here, 1 (FIT) = 1e-9 (error/hour). Generally, SEU cross sections depend on the device. Therefore, the conversion
coefficients are not used to estimate the exact SER. Please utilize them to estimate SER roughly or to compare SER
in the radiation field and background SER.
50 The critical charge is assumed to be 0.6 fC. The neutron energies from 1 MeV to 1 GeV are considered. For details, please refer to “S.
Abe and Y. Watanabe, IEEE Trans. Nucl. Sci. 61, 3519-3526 (2014).”
51 The background means on the ground at Tokyo. The cosmic-ray neutron flux is calculated by PARMA model. The PARMA model can be
The line starting with multiplier= specifies the number of materials for which multiplication is considered; all
can be used instead of a number, in which case all should be used for the following mat column. In the second line,
part= defines which particle is to be considered. A maximum of six particles can be entered here; all, which is
the default, can be also used. Only those particles listed will be multiplied. In the third line, emax= defines the
maximum energy of multiplication. If emax is omitted, it is automatically defined as the maximum energy given in
the [multiplier] section. The numbers of the respective mat columns give the material numbers considered for
multiplication. The columns mset1 and mset2 define the multiplier sets up to a maximum of six sets. The result
of each set is printed out. Although several multiplier subsections can be defined in one tally section, the number
of multiplier sets should be constant across subsections.
PHITS has some built-in coefficients available for the [multiplier] section. If you set k = −1, a value
of 1/weight is used as the multiplication factor to obtain tally results of a Monte Carlo particle, i.e., particles
always having their weights as 1. For k = −2, a value of 1/velocity is used. For k = −120, material density is
used. Therefore, you can obtain mass in the region setting icntl=5. You can also set the ID number included in
52 Taken from EXPACS (http://phits.jaea.go.jp/expacs/)
53 Y. Sakamoto, O. Sato, S. Tsuda, N. Yoshizawa, S. Iwai, S. Tanaka, and Y. Yamaguchi, “Dose conversion coefficients for high-energy
photons, electrons, neutrons and protons”, JAERI-1345, (2003) etc.
54 ICRP Publication 116, Ann. ICRP 40(2-5), 2010.
55 ICRP Publication 123, Ann. ICRP 42(4), 2013.
56 S. Abe and Y. Watanabe, IEEE Trans. Nucl. Sci. 61, 3519-3526 (2014).
172 5 SECTIONS FORMAT
/phits/data/multiplier/ directory without specifying the [multiplier] section in the input file. Currently,
the databases of the conversion coefficients for several types of radiation doses are included in the directory (see
Table 5.76 in detail). The unit of the dose conversion coefficients is pSv.cm2 , and thus, the doses in the unit of
pSv/sec can be directly calculated when the calculated fluence is normalized to the unit of /cm2 /sec. Note that the
energy unit of the dose conversion coefficients for heavy ions is MeV/u, and you have to set iMeVperu = 1 in the
[parameters] section when you use the heavy ion data in your simulation.
In addition to them, the effective doses based on ICRP60 for the AP irradiation from proton, neutron, electron,
and photon can be separately calculated by specifying k = −101, −102, −112, and −114, respectively, though this
method is not recommended anymore because the corresponding doses can be calculated by k = −201. Note that
the unit of these dose conversion coefficients is (µSv/h)/(n/sec/cm2 ), i.e. the doses in the unit of µSv/h can be
directly calculated when the calculated fluence is normalized to the unit of /cm2 /sec. It should be noted that the
interpolation method of conversion factor has been changed in PHITS ver. 2.00 from linear-linear to log-log.
You can also use the following format.
In above example, the mset1 is for heat and the mset2 is zero for proton, attenuator set for neutron.
5.24 [ Mat Name Color ] section 173
To replace the order of material number (mat), (name), (size), and (color), set as mat color size name.
The skip operator non can be used. At least one parameter in name and color must be defined. If no definition,
the default values are used.
The format { 4 - 7 } can be used, but the format ( { 4 - 7 } 9 10 ) cannot be used. To use blanks in
name definition, the name must be closed by { } as the example. To use ( ), the format \( \) should be used. In
the name, { } cannot be used. Note that a superscript or subscript in the LaTeX format can be used by writing
\{ \}. For example, in the case of writing ˆ\{ 208 \}Pb, 208 Pb is output. The maximum number of characters to
define a name is 80.
When defining two (or more) cells of different densities from each other with the same material number in
[cell] section, the cells except the first one are given other material numbers in matadd=1 (the default setting).
The given numbers are written in the first part of file(6) (D=phits.out) as a warning message. Therefore, set
the numbers have to be set in the mat column of this section. Even if setting matadd=0 in [parameters] section,
the function unifying the material number is invalid in this section.
The color definition is based on the format in ANGEL. Set color by symbol ( r bbb yy), name ( red orange
blue), or HSB numeric H(hue) S (chroma) B(brightness). In the case HSB numeric definition, close each numeric
by { }. If only one HSB numeric is defined, chroma and brightness are set 1.
Color symbols, names, and HSB numerics are shown from next page.
174 5 SECTIONS FORMAT
[ Reg Name ]
reg name size
1 cover 1
2 body 0.5
3 {cell 2} 2
4 {cell 3} 2
{ 5 - 8 } tube 3
.... ........
.... ........
If you want to replace the order of region number (reg), region name (name), and font size (size), set as reg
size name. You can use the skip operator non. At least one of name and size must be defined. If nothing is
defined, it is assumed to be default. You can use the format { 4 - 7 }, but the ( { 4 - 7 } 9 10 ) format
cannot be used. If you need to use blanks in the name definition, the name must be closed by { } as the example.
If you want to use ( and ), you should write \( and \), respectively. Brackets { and } cannot be used in the name
definition. Note that a superscript or subscript in the LaTeX format can be used by writing \{ \}. For example,
in the case of writing ˆ\{ 208 \}Pb, 208 Pb is output. The maximum number of characters of a name that you can
define is 80. You can specify a font size as a relative value to the default size.
176 5 SECTIONS FORMAT
[ Counter ]
counter = 1
part = neutron proton
reg in out coll ref
1 1 10000 0 0
11 1 10000 0 0
counter = 2
*part = proton deuteron triton 3he alpha nucleus
reg in out coll
( { 2 - 5 } 8 9 ) -1 0 1
counter = 3
part = 208Pb
reg coll
( 11 12 15 ) 5
( 6<10[1 0 0]<u=3 ) 100
.... ........
.... ........
If you want to change the order of region number (reg), (in), (out), (coll), and (ref), set as reg coll in
out ref. You can use the skip operator non. At least one must be defined in the in out coll ref. If nothing
is defined, it is assumed no counter. Numeric gives one progress value of the counter. 10000 means zero set. The
initial counter value of source particle is zero.
You can use the format ( { 2 - 5 } 8 9 ), and you can use the lattice and universe style as
( 6 < 10[1 0 0] < u=3 ). But you need to close a value by ( ) if it is not a single numeric value.
In the definition of part=, you can specify particles up to 20 particles. For nucleus, you can use the expression
like 208Pb and Pb. The latter case, Pb, denotes all isotopes of Pb.
5.26 [ Counter ] section 177
From ver. 2.90, by detailed classification for coll, the opportunities shown in Table 5.80 are available as
keywords so that the counter counts. nucl, atom, and dcay, which are particular interactions, belong to coll.
Furthermore, nucl and atom are classified into three and ten kinds, respectively. When you want to analyze the
PHITS simulation in detail, set these keywords. Note that if you set coll and nucl at the same time, the counting
is duplicated when a nuclear reaction event occurs.
When (fiss) is specified, the counter is called when fission channels of the nuclear data library and the statis-
tical decay model (GEM) are chosen.
[ Timer ]
reg in out coll ref
1 0 -1 0 0
11 1 0 0 0
.... .... .... .... ....
.... .... .... .... ....
.... .... .... .... ....
If you want to replace the order of region number (reg), (in), (out), (coll), and (ref), set as reg coll in out
ref. You can use the skip operator non. At least one must be defined in the in out coll ref. If nothing is
defined, it is assumed no action.
You can use the format ( { 2 - 5 } 8 9 ), and you can use the lattice and universe style as
( 6 < 10[1 0 0] < u=3 ). But you need to close a value by ( ) if it is not a single numeric value.
179
name explanation
[t-track] Particle fluence in a certain region.
[t-cross] Particle fluence crossing at a certain surface.
[t-point] Particle fluence at a certain point.
[t-deposit] Deposit energy in a certain region.
[t-deposit2] Deposit energies in certain two regions.
[t-heat] Heat generation in a certain region. (Not recommended57 )
[t-yield] Residual nuclei yield in a certain region.
[t-product] Produced particle in a certain region.
[t-dpa] Displacement Per Atom (DPA) in a certain region.
[t-let] LET distribution in a certain region.
[t-sed] Microdosimetric quantity distribution in a certain region.
[t-time] Time information of particle in a certain region.
[t-interact] (formerly named [t-star]) Number of interactions occurred in specified regions.
[t-dchain] Residual nuclide yields (in combination with DCHAIN).
[t-wwg] Output parameters for [weight window].
[t-wwbg] Output parameters for [ww bias].
[t-volume] Automatic calculation of region volume.
[t-userdefined] Any quantities that user defined.
[t-gshow] 2D geometry visualization.
[t-rshow] 2D geometry visualization with physical quantities.
[t-3dshow] 3D geometry visualization.
57
Before ver. 3.04, the [t-heat] tally was used to calculate deposit energy using the kerma approximation, because the [t-deposit] tally
did not have the option.
180 6 COMMON PARAMETERS FOR TALLIES
mesh = reg
reg = 1 2 3 4 5 ( 10 11 ) 50
Each cell number should be separated by blank. Some regions can be combined by using ( ). The following
format can be used for defining sequential region numbers.
mesh = reg
reg = { 1 - 5 } ( 10 11 ) ( 6 < 10[1 0 0] < u=3 )
In the format {n1 - n2} (n1 is smaller than n2), you can specify regions from n1 to n2. You cannot specify like
( n1 - n2 ). Styles ( { } ) and ( all ) can be used, but { ( ) } cannot be used. You can use
the lattice and universe style as ( 6 < 10[1 0 0] < u=3 ). By using above format, you can tally from each
lattice individually. Furthermore, you set region as reg = all, all regions become tallying region. However, cells
which do not belong to bottom level, are not included.
6.1.2 Definition of the region and volume for repeated structures and lat-
tices
When you define regions including repeated structures and lattices, you must close your definition by ( ).
A level structure is indicated by <. In the case an intermediate level has the lattice structure, you can specify lattices
using [ ] represented by the lattice coordinate (s, t, u), after the cell number as 160[1:2 3:6 1:1]. In this
example, lattices, which from 1 to 2 in s direction, 3 to 6 in t direction, and 1 in u direction, are defined. You can
also specify individually as 160[1 3 4, 2 3 4, 3 3 4]. The style ( ) in one level can be used to combine
some regions. See next example.
1: mesh = reg
2: reg = (all)
3: ({ 201 - 205 })
4: ( 161 < 160[1:2 3:6 1:1] )
5: ( (201 202 203 204) < (161 162 163 ) )
6: ( ( 90 100 ) 120 < 61 ( 62 63 ) )
In the input, it looks only 5 regions defined, but in the input echo, you can see 15 regions are defined for tally. In
this input echo, region numbers are defined automatically starting from 10001, and the volume of each cell is set 1
because of no [volume] definition.
We explain the detail of 15 regions appears in the volume description of this input echo.
First for ( all ), 81 cells are defined in the bottom level, so the volume of ( all ) is set 81. If the volume
of the cell is defined correctly in the [volume] section, you don’t need to define the volume here again.
Next for ({ 201 - 205 }), this combined region has volume 5 in the echo, since this combined regions have
5 cells of bottom level. This is also not required to re-define here if the volume is set in the [volume] section.
For ( 161 < 160[1:2 3:6 1:1] ), the region 161 is included as a lattice in region 160. In this expression
in the lattice coordinate system, 8 lattices of the region 160 from 1 to 2 in s direction, 3 to 6 in t direction, and 1 in
u direction, are used for the tally. In the echo, the number of regions in bottom level is echoed 1. In the case, you
have to specify the volume by yourself by the volume definition below.
For ( (201 202 203 204) < (161 162 163 ) ), some regions are defined in each level, but these are all
closed by ( ), so it means one region as a whole. In this case, given volume by the echo is not correct, so set
volume manually by the volume definition below.
For ( ( 90 100 ) 120 < 61 ( 62 63 ) ), there are two independent regions in each level, so 4 regions
are defined here. In this case given volume by the echo is not correct too, so set volume manually in the [volume]
section.
You can set volume as below.
mesh = reg
reg = 1 2 3 4 ( 5 < 12 ) ( {13 - 17} )
volume
reg vol
1 1.0000
2 5.0000
3 6.0000
4 1.0000
10001 6.0000
10002 5.0000
In above example, region numbers from 1 to 4 are set normally as you can see, but regions ( 5 < 12 ) and (
{13 - 17} ) have numbers 10001 and 10002. These big values are given in an input echo automatically. You can
see and paste this settings from the input echo.
If you want to change the order of region number (reg) and volume (vol), set as vol reg. You can use the
skip operator non.
In the input echo, numbered entry is given in non column. When axis=reg, the numbered entry is used as a
value of x-axis.
When you define regions in the bottom level, set same region twice as ( 3000 < 3000[1:2 3:61:1] ).
mesh = r-z
x0 = 1.0
y0 = 2.0
mesh = r-z
r-type = [1-5]
..........
..........
z-type = [1-5]
..........
..........
mesh = xyz
x-type = [1-5]
..........
..........
y-type = [1-5]
..........
..........
z-type = [1-5]
..........
..........
mesh = xyz
reg = 100
The physical quantities specfied in the tally will be scored in all the tetrahedrons separatelly. Extraction of
some tetrahedrons or summation of tetrahedrons is not possible with this mesh. Such quantities may be extracted
by using the region mesh (mesh=reg) with selecting the cell corresponding to the universe of the tetrahedron
geometry. It should be noticed also the volume of tetrahedron is simply computed from the coordinates of the
nodes and thus incorrect qunatities may be obtained when the tetrahedron geometry is clipped out through the use
of nest structure of “universe”and “fill”. In such a case, the region mesh (mesh=reg) should be used instead.
e-type = [1-5]
..........
..........
e1-type and e2-type are also used in DEPOSIT2 tally. Mesh definition is described later.
l-type = [1-5]
..........
..........
t-type = [1-5]
..........
..........
If a-type is defined by positive number, this mesh denotes cosine mesh. If a-type is defined by negative
number, the mesh denotes angle mesh. Mesh definition is described later.
It is noted that you can use only 1, 2 (-1, -2) mesh types in a-type definition.
Only when [t-cross] and z-type=1, nz=0 can be set with only one data. This setting provides only one
tally surface of z = (data).
Each mesh type format is shown in followings.
6.6.2 e-type=1
When you use e-type=1, set number of group, then numerical data as
6.6 Mesh definition 185
e-type = 1
ne = number of group
data(1) data(2) data(3) data(4)
data(5) data(6) data(7) data(8)
.........
.........
data(ne+1)
You can use multi lines without any symbols for line connection.
186 6 COMMON PARAMETERS FOR TALLIES
6.6.3 e-type=2,3
When you use e-type=2,3, set number of group, minimum value, and maximum value as
e-type = 2, 3
ne = number of group
emin = minimum value
emax = maximum value
6.6.4 e-type=4
When you use e-type=4, set mesh width, minimum value, and maximum value as
e-type = 4
edel = width of mesh
emin = minimum value
emax = maximum value
6.6.5 e-type=5
When you use e-type=5, set mesh width, minimum value, and maximum value as
e-type = 5
edel = log( width of mesh )
emin = minimum value
emax = maximum value
In the case, mesh width is for log scale, i.e., edel= log(Mi+1 /Mi ).
or
6.7 Other tally definitions 187
part = proton
part = neutron
part = pion+
part = 3112
part = 208Pb
See Table 4.4 for particle identification. You can also use the kf code number.
part = all
Maximum 6 particles can be define in a tally. If you want to tally more particles, use another tally sections of
the same kind of tally.
If you want to tally some particles as a group, you can use ( ) as the following. The maximum number inside
the ( ) is 6.
In this case, as the first group, the sum of proton and neutron contribution is tallied, the second is the sum of all. 5
groups of the particle are printed out in this tally.
For nucleus, you can use the expression like 208Pb and Pb. The later case, Pb, denotes all isotopes of Pb.
axis = eng
axis = eng x y
or
188 6 COMMON PARAMETERS FOR TALLIES
axis = eng
axis = x
axis = y
If you define multiple axes, output results are written in different files. So you need to specify multiple output files
as shown in the next subsection when multiple axes are defined.
It should be noted that you can define only one axis in a [t-yield] section from ver. 2.50. This restriction
was implemented to calculate statistical uncertainties correctly. If you want to define several axes in the [t-yield]
tally, you have to set the corresponding number of [t-yield] sections in a input file.
Note that the file name should not have the extension of ‘.eps’ or ‘.vtk.’ As described before, when you set
multiple axis, set output files for each axis like following example.
file = file.001
file = file.002
file = file.003
resfile = file.001
where the file name must be written with full pathname. Even if several resfile parameters are set in a tally
section, only the earliest one is used. resfile is set to file by default. In this case, results of the past tally are
overwritten.
unit = number
The unit number and its meanings are described in each tally explanation.
6.7 Other tally definitions 189
factor = number
This value is multiplied to output values. When you use the [t-gshow] tally, this factor defines line thickness
instead.
info = 0, 1
p: xmin(1.0) ymin(1.3e-8)
190 6 COMMON PARAMETERS FOR TALLIES
These parameters change the minimum of the horizontal and vertical axes, respectively. The main ANGEL param-
eters are shown in Table 6.3. Please see the ANGEL manual in more detail.
From ver. 2.89, the default size was changed from A4 to US letter. ANGEL parameters, a4us(US letter),
a3pp(A3), a4pp(A4), a5pp(A5), b3pp(B3), b4pp(B4), and b5pp(B5) can be used to change an output size of an
eps file. The characters given in parentheses represent each output size.
2d-type = 1, 2, 3, 4, 5, 6, 7
• 2d-type = 1, 2, 3, 6, 7
Data are written by below format (the example is written by Fortran style.
( ( data(ix,iy), ix = 1, nx ), iy = ny, 1, -1 )
6.7 Other tally definitions 191
10 data are written in a line. Also a header for the ANGEL input is inserted. The ANGEL header is inserted
by 2d-type=1 for contour plot, 2d-type=2 for cluster plot, 2d-type=3 for color plot, 2d-type=6 for
cluster and contour plot, 2d-type=7 for color and contour plot.
• 2d-type=4
Data are written by below format
do iy = ny, 1, -1
do ix = 1, nx
( x(ix), y(iy), data(ix,iy) )
end do
end do
• 2d-type = 5
Data are written by below format
y/x ( x(ix), ix = 1, nx )
do iy = ny, 1, -1
( y(iy), data(ix,iy), ix = 1, nx )
end do
nx+1 data are written in a line, and total ny+1 lines. It is useful to use in the tabular soft like Excel.
gshow = 0, 1, 2, 3, 4
In above example, 0 means no gshow option, 1 means gshow with region boundary, 2 means gshow with region
boundary and material name, 3 means gshow with region boundary and region name, 4 means gshow with region
boundary and lattice numbers. When you increase the resolution of the plot by resol parameter, the indication
of region name, material name and lattice number on the graph are sometimes disturbed. In this case, you should
increase the mesh points instead of resol.
You can see your geometry plot on a graph without transport calculation by setting icntl=8 in the [parameters]
section, and this gshow option. You should check whether regions are correct, and a xyz mesh resolution is good
or not, before long time calculation.
rshow = 1, 2, 3
x-type = [2,4]
..........
..........
y-type = [2,4]
..........
..........
z-type = [2,4]
..........
..........
rshow=0 means no rshow option, 1 means rshow with region boundary, 2 means rshow with region boundary
and material name, 3 means rshow with region boundary and region name numbers. If rshow=0, xyz mesh
definition is not required, comment out it. When you increase the resolution of the plot by resol parameter, the
indication of region name, material name and lattice number on the graph are sometimes disturbed. In this case,
you should increase the mesh points instead of resol.
If you use the rshow option with reg mesh, there is no output for the values of each region. In this case, you
cannot re-plot the figure because of no original data. When this rshow option is used, usually axis is set as xy,
yz, and zx. But you should use in addition axis=reg in order to save results into another file, for re-plotting. You
can re-plot figures from saved data and [t-rshow] tally function.
You can execute this option without transport calculation by using icntl=10 in the [parameters] section.
For icntl=10, PH I TS makes a two dimensional plot for the tallies with reg mesh, xy, yz, zx axis and rshow = 1, 2,
3. In the figure, different colors are used for different materials. You should check whether regions are correct and
a xyz mesh resolution is good or not, before long time calculation.
trcl = number
trcl = O1 O2 O3 B1 B2 B3 B4 B5 B6 B7 B8 B9 M
The first definition is to specify the transformation number defined in [transform] section. The next one is to
define the transformation directly here with 13 parameters as same as in [transform] section. If the data are not
written in a line, you can write them in multiple lines without the line sequential mark. But you need to put more
than 11 blanks before data on the top of the sequential lines.
In the 3dshow tally, trcl can be used to transform the box. This will be explained in the [t-3dshow] tally
section.
Here kf means the kf-code of the particles (see Table 4.4), x, y, z are coordinates [cm], u, v, w denote the unit
vectors of the direction of the particle, e is the energy [MeV, or MeV/u for nucleus], wt is the weight, time is the
initial time [ns], c1, c2, c3 are the values of counters, and sx, sy, sz are the unit vectors of the direction of spin,
respectively. name is a collision number of the particle, nocas is a current history number of this batch, nobch
is a current batch number, no is a cascade id in this history. These are assumed as real*8 for the binary data,
n(1p1e24.15) data format for the ascii data.
For an example, one record has 9 data as
kf e wt x y z u v w
“sumtally” subsection is ignored when icntl parameter is not set to 13 in [parameters] section. 60 Please see the
ppt slides or sample input file in \phits\utility\sumtally\ for details.
“sumtally” subsection should be defined between the lines of sumtally start and sumtally end written
in the tally section that outputs one of the summing up tallies. The set: definition is ignored in the sumtally
subsection.
The parameters used in “sumtally” subsection are summarized in Table 6.6.
Users can use isumtally=1 to manually obtain the parallel calculation results. For example, if you have
one tally result “result-1.out” obtained with maxbch=10 and maxcas=100, and another tally result “result-2.out”
obtained with maxbch=20 and maxcas=100, and if you would like to sum up the results to have same statistics as
of maxbch=30 and maxcas=100, you have to write:
1: sumtally start
2: isumtally = 1 $(D=1) sumtally option, 1:integration, 2:weighted sum
3: nfile = 2 $ number of tally files
4: result-1.out 1.0
5: result-2.out 1.0
6: sfile = result-s.out $ file name of output by sumtally option
7: sumfactor = 1.0 $ (D=1.0) normalization factor
8: sumtally end
Using this sumtally subsection, you can obtain the results for maxcas=100 and maxbch=30. Please be sure
that the initial random seeds for calculating “result-1.out” and “result-2.out” should be different from each other,
58 Before ver. 2.81, this function is available even if file parameter is not defined in the tally section. However, after ver. 2.82, PHITS
otherwise you would get biased results for certain random numbers. The most recommended method for changing
the initial random seed is to use irskip parameter. The weighted value for each tally outputs are generally set to
1 for isumtally=1, unless you would like to change the weight of source particles. The output file obtained from
this sumtally section, “result-s.out,” can be used for restart calculation by setting istdev<0. Note that the initial
random seed in the last file of the summing up files is used.
For isumtally=2, the weighted summation of the tally results, X̄, is calculated by the following equation:
∑
N
rj
X̄ = F X̄ j (23)
j=1
r
where F is the normalization factor defined by sumfactor, N is the number of summing up files defined by
∑
nfile, X̄ j is the j-th tally results, r j is the weighted value of j-th tally, and r is the sum of r j , i.e. r = Nj=1 r j . The
uncertainty of the summation value, σX , can be calculated by
v
u
t N ( )
∑ rj 2
σX = F σ2X j (24)
j=1
r
1: sumtally start
2: isumtally = 2 $(D=1) sumtally option, 1:integration, 2:weighted sum
3: nfile = 2 $ number of tally files
4: result-l.out 2.0
5: result-r.out 3.0
6: sfile = result-s.out $ file name of output by sumtally option
7: sumfactor = 5.0 $ (D=1.0) normalization factor
8: sumtally end
You can obtain the same results by using multi-source function, but it is more convenient to use sumtally
subsection when you would like to change the weighted values for several cases. It should be mentioned that the
sum of the weighted values is automatically normalized to sumfactor for isumtally=2. The output file obtained
from this sumtally section, “result-s.out,” cannot be used for restart calculation.
197
track length
As an example, information on the detector response in a specified region can be obtained by utilizing this tally.
Multiplying the fluence by the cross section (in units of cm2 ) of the detector enables estimation of the number of
counts in the response.
‘Lethargy’ in unit=3 or 13 is the natural logarithmic unit of energy defined by ln(Eref /E) using a reference
energy Eref and the particle energy E. Setting these units enables obtaining results in units of Lethargy, which are
given as Lethargy widths, ln(Ehigh /Elow ), for each energy bin in the energy mesh subsection. Here Ehigh and Elow
are the maximum and minimum values of the energy bins, respectively.
Setting unit=1,2,3,11,12 or 13 produces the mean particle fluence in a specified region calculated from the
sum of the track lengths per source divided by the volume of the region. Note that, for reg mesh the volume in
the [volume] section must be set; if this is not done, the particle fluence for volume=1 [cm3 ], i.e., the sum of the
track lengths per source, is obtained. For r-z and xyz meshes, the volume is automatically calculated. Setting
unit=4 or 14 produces the sum of the track lengths per source.
θ degrees of freedom can be set in r-z mesh of this tally. The a-type mesh definition used to specify θ follows
the same format as in the other angle mesh cases. The θ dependence of results can be obtained by setting axis=rad
or axis=deg, where rad and deg represent θ in radians and degrees, respectively.
7.1 [ T-Track ] section 199
When specifying stdcut, PHITS automatically stop the calculation depending on values of STD (standard
deviation). This function is available when stdcut is positive and itall=0,1 is set in [parameters] section.
When all relative values of STD of the tally result are smaller than stdcut at the last of one batch, PHITS finishes
its calculation. If stdcut in two (or more) tally sections is set, all the results of the tally sections have to satisfy
the conditions in order to work the function.
When using function to display transition of tally results and errors, mesh points to output tally results and these
statistical errors can be specified by setting “anatally” subsection. This subsection should be defined between the
lines of anatally start and anatally end written in the tally section. See Sec. 3.3 for more detail.
7.2 [ T-Cross ] section 201
direction of
Scosθ particle trajectory
S
θ
As the flux in this tally is evaluated by weighting by 1/ cos θ, the result is equivalent to that obtained from the
[t-track] tally for an extremely thin region. Consequently, information on the detector response in the specified
surface can be obtained from the [t-cross] tally. Multiplying the flux by a cross section (in the unit of cm2 ) of
the detector enables estimation of the number of counts in the response.
202 7 TALLY INPUT FORMAT
There may be cases in which results of a tally are incorrect when r-z or xyz mesh surface agrees with that of
the defined cell.
The current for a specified angle can be obtained using the angle mesh shown in Fig. 7.3. In cases where
unit=4,5 6,14,15,16, the output is given as a quantity per solid angle (in steradians) calculated using the mesh
size of the angle-bin defined in the angle mesh subsection.
‘Lethargy’ in unit=3,6,13,16 is the natural logarithmic unit of energy defined by ln(Eref /E) using a refer-
ence energy Eref and the particle energy E. Setting these units enables obtaining results in units of Lethargy, which
are given as Lethargy widths, ln(Ehigh /Elow ), for each energy bin in the energy mesh subsection. Here Ehigh and
Elow are the maximum and minimum values of the energy bins, respectively.
In unit=4,5,6,14,15,16, ‘sr’ denotes steradians as the solid angle unit.
7.2 [ T-Cross ] section 203
The output options output=f-curr, b-curr, of-curr, ob-curr can be used in either xyz or r-z meshes.
Note that in xyz meshes these options are available only for the z-direction.
In the [t-cross] tally, the dump option can only be used with reg meshes and only on axis=reg. If the
dump option is set, the e-type, a-type and t-type meshes take on only the maximum and minimum values.
The output option can be set as current, a-curr, or oa-curr. In using this dump parameter, axis and file
are restricted to one axis and one file apiece and unit is always 1. The dumped data are written onto a file named
“*** dmp”, where “***” indicates the file name specified by file=***. The normal output of the tally is written
on “***.” From this file, information on the total normalization factor can be obtained; doing so requires setting
one mesh each for e-type, a-type and t-type (in the versions of PHITS before 2.66, the normal output was
written on a configuration file (.cfg) and the dumped data were written on “***”). The history information (nocas
and nobch) is necessary to use idmpmode=1 for continuous calculation using the dump file; in addition, both the
dump file with “ dmp” and the normal output file specified by file= are required to use idmpmode=1. The option
dumpall is not compatible with this dump tally option when shared memory parallelization is active.
When specifying stdcut, PHITS automatically stop the calculation depending on values of STD (standard
deviation). This function is available when stdcut is positive and itall=0,1 is set in [parameters] section.
When all relative values of STD of the tally result are smaller than stdcut at the last of one batch, PHITS finishes
its calculation. If stdcut in two (or more) tally sections is set, all the results of the tally sections have to satisfy
the conditions in order to work the function.
From ver. 3.10, crossing surfaces are defined by closed surface separated by each mesh when enclos=1 is
set with mesh=xyz or mesh=r-z. In this case, the forward direction is defined as the incoming direction, and the
backward direction is defined as the outgoing direction. The total area of closed surface is used to calculate per
unit area.
Setting mesh=reg for the geometry mesh in this section requires defining the crossing surface by outgoing
(r-from) and incoming (r-to) region number, and the area of the surface (area in units of cm2 ), as shown in the
example below 63 .
mesh = reg
reg = number of crossing surfaces
r-from r-to area
2 8 10.0
3 8 5.0
( 4 5 ) ( 4 5 ) 2.0
(13<5) (14<5) 7.0
(13<6) (14<6) 7.0
(13<7) (14<7) 7.0
... ... ....
... ... ....
In the next line of mesh=reg, give the number of crossing surfaces to tally by reg=. Furthermore, from the next
line, the values of r-in r-out, and area should be written as a matrix format. The default order for this definition
is r-in r-out area. The line of these column headers can be omitted. However, to change the order, rearrange
and explicitly write the column headers as r-in r-out area. The skip operator non can be also used. When
specifying the region number, the format ( 2 -5 8 9 ) can be used, as can the lattice and universe style ( 6 <
10[1 0 0] < u=3 ). However, any value that is not single numeric must be enclosed by ( ) .
If mesh=reg is set, the obtained current or flux is unidirectional from r-from to r-to; a bidirectional flux can
be set in the third line of the above definition.
Setting the mesh=r-z defines the numbers of two crossing surface types: the number of “nz+1” crossing
surfaces for z defined by ri − ri+1 and the number of “nr+1” crossing surfaces for r defined by zi − zi+1 . If an
r-surface coincides with the surface of the outer void, the flux on this surface is not tallied.
If mesh=xyz is set, the number of “nz+1” crossing surfaces on z are defined by xi − xi+1 , and y j − y j+1 . In this
case, x and y crossing surfaces are not defined.
Setting mesh=r-z or xyz causes crossing particles to be detected in both directions on the defined surface.
The forward direction is defined as the positive direction on a z surface and from the center to the exterior on an r
surface. From ver. 3.05, specification of z-type=1 and nz=0 is allowed to calculate fluences of particles passing
through a certain surface.
63Before ver. 2.96, r-in and r-out were used instead of r-from and r-to, respectively. These old parameters can be used after ver. 2.97.
Note that ‘in’ and ‘out’ are reversed in this definition.
206 7 TALLY INPUT FORMAT
(2) only the fluence of neutrons and photons can be calculated by [t-point];
(3) neither event generator mode nor EGS5 should be used (e-mode=0, negs=0);
(4) the material should be uniform within a certain proximity to the point detector to avoid singularity;
(5) reflection or white boundary surface should not be used.
Please see the read-me file or the sample input file in “\phits\utility\tpoint\” for more details.
‘Lethargy’ in unit=3 or 13 is the natural logarithmic unit of energy defined by ln(Eref /E) using a reference
energy Eref and the particle energy E. Setting these units enables obtaining results in units of Lethargy, which are
given as Lethargy widths, ln(Ehigh /Elow ), for each energy bin in the energy mesh subsection. Here Ehigh and Elow
are the maximum and minimum values of the energy bins, respectively.
7.3 [ T-Point ] section 207
In [t-point], the number of points or rings (instead of the mesh, as in other tallies) must be defined. For
example, point=3 should be specified to define 3 point detectors. The maximum number of points or rings per
[t-point] is 20; to set more detectors, another [t-point] tally must be defined. Point and ring detectors cannot
be combined in one [t-point] tally. The information on a point or ring must be defined in t successive lines
following the definition of the point or ring parameter. The point detector definition is described as follows.
[ T-point ]
point = 1 # number of point detectors
non x y z r0
1 10.0 0.0 50.0 1.0
where x, y, and z indicate the coordinates of the point detector and r0 is the radius of the fictitious sphere (for
more information on the fictitious sphere, see the read-me file in “\phits\utility\tpoint\” ). These parameters are
given in units of cm.
The ring detector is defined as follows:
[ T-point ]
ring = 1 # number of ring detectors
non axis ar rr r0
1 z 50.0 10.0 1.0
where axis indicates the direction of the ring axis specified as x, y, or z, ar is the distance from the origin to the
center of the ring, rr is the ring radius, and r0 is the radius of the fictitious sphere. The order of these parameters
can be changed by changing the order of notation, e.g., x y z r0 can be changed to z y x r0. Aside from these
factors, the parameters defined in [t-point] are the same as those in [t-track], including the multiplier option.
Thus, the radiation dose at a specific point can be estimated using [t-point]. However, material, two-dimensional
plot options, and transforms cannot be specified in [t-point].
When specifying stdcut, PHITS automatically stop the calculation depending on values of STD (standard
deviation). This function is available when stdcut is positive and itall=0,1 is set in [parameters] section.
When all relative values of STD of the tally result are smaller than stdcut at the last of one batch, PHITS finishes
its calculation. If stdcut in two (or more) tally sections is set, all the results of the tally sections have to satisfy
the conditions in order to work the function.
When using function to display transition of tally results and errors, mesh points to output tally results and these
statistical errors can be specified by setting “anatally” subsection. This subsection should be defined between the
lines of anatally start and anatally end written in the tally section. See Sec. 3.3 for more detail.
208 7 TALLY INPUT FORMAT
64 T.Sato et al., “Biological dose estimation for charged-particle therapy using an improved PHITS code coupled with a microdosimetric
kinetic model,” Radiat. Res. 171, 107-117 (2009).
7.4 [ T-Deposit ] section 209
Note that deposition energies calculated by kerma approximation are not included in this mode. It should be
also noted that this mode cannot be used when weights of particles depositing energy change within a history, such
as the cases that [weight window] or [importance] section is defined.
When unit is set =0 with output=dose, results can be obtained in units of [Gy/source]. When mesh=reg, the
volumes of each cell should be defined in the [volume] section or set as volume parameters of the [t-deposit]
section. Because absorbed dose is an intensive variable, PHITS does not output a ‘sum over’ in output files for
unit=0. Note that, in a region including more than two materials the dose in the region does not equal the average
value of the region. For example, when there are two materials with masses M1 and M2 , and absorption energies
E1 and E2 , respectively, PHITS gives M E1 V1
1 V1 +V2
+M
E2 V1
2 V1 +V2
in this tally, even though its average dose is ME11 +E
+M2 . Here,
2
set in part can be obtained. Thus, the sum of results obtained by setting part=individual particle does not equal
to the distribution of energies deposited by all particles.
In the case of output=deposit and deposit=0, the statistical uncertainties of all results except for the values
of part=all calculated independent of istdev as standard deviations using history variance mode.
Table 7.12: [t-deposit] parameters (3)
Although the fano factor is generally defined as a dimensionless quantity, the dfano parameter is defined as a
quantity with the dimension of energy.
When specifying stdcut, PHITS automatically stop the calculation depending on values of STD (standard
deviation). This function is available when stdcut is positive and itall=0,1 is set in [parameters] section.
When all relative values of STD of the tally result are smaller than stdcut at the last of one batch, PHITS finishes
its calculation. If stdcut in two (or more) tally sections is set, all the results of the tally sections have to satisfy
the conditions in order to have the function work.
As an extension of sum up the deposit energies such as reg = (100 200 300 · · · ), weighted summation
option is added. Using this option in this tally, energies deposited in specified i-th regions for each history, Ehistory,i
are multiplied by specified coefficients, αi (Nlist ), and then summed up as written by:
∑
Ehistory = αi (Nlist ) × Ehistory,i . (25)
i
This option weights depending on deposited energies in each history, and it can be applied to simulation, for
example soft errors in semiconductor devices. If you want to weight depending on the condition for each particle,
please use user defined subroutine (“usrdfn1.f” or “usrdfn2.f”) and set dedxfnc=1 or 2. This option can be
used only mesh=reg, and it can be executed when you specify reg convolution. Formats and examples are shown
below;
212 7 TALLY INPUT FORMAT
mesh = reg
reg = weightsum
ncond = 4
no cell operator ethres list
1 100 ge 0.1 1
2 100 gt 0.2 1
3 100 eq 0.0 2
and 200 lt 0.4 2
4 100 le 0.5 3
ncell = 5
cell list01 list02 list03 list00
100 0.0 0.5 1.0 1.0
200 0.1 0.6 2.0 1.0
300 0.2 0.7 3.0 1.0
400 0.3 0.8 4.0 1.0
500 0.4 0.9 5.0 1.0
First, you define the number of condition. The next line defines the order of data, i.e., condition number (no),
cell number (cell), operator (operator), threshold energy (ethres), and list number (list). In next lines,
conditions are described as many as ncond value. These lines means that ‘list number is used when the energy
deposited in the specified cell satisfies large/small relation with threshold energy.’ The condition written in first is
preferred when the history satisfies some conditions. If the history does not satisfy all the condition, coefficients
of list00 are used. You can set several conditions by writing and in no column. In the cell column, you can use
the format ( 2 - 5 8 9 ) and the lattice and universe style as ( 6 < 10[1 0 0] < u=3 ). But you need
to close a value by ( ) if it is not a single numeric value. In the operator column, you can use greater than gt,
greater equal ge, equal eq, less equal le, and less than lt. The unit of ethres is MeV.
Next, you define the number of convoluted cell. The next column defines the order of data, i.e., cell number
(cell), and list number (listxxxx). In next lines, convoluted cell number and coefficients are described. In the
cell column, you can use the format ( 2 - 5 8 9 ) and the lattice and universe style as ( 6 < 10[1 0 0]
< u=3 ). But you need to close a value by ( ) if it is not a single numeric value. It should be noted that same
deposited energy is added up many times when you set same cell number many times. If you do not define list00,
coefficients of list00 are set to zero.
7.5 [ T-Deposit2 ] section 213
To tally the energy loss for each projectile particle entering the tally region, the counter should be defined using
part in the [counter] section and ctmin, ctmax in this tally section.
When specifying stdcut, PHITS automatically stop the calculation depending on values of STD (standard
deviation). This function is available when stdcut is positive and itall=0,1 is set in [parameters] section.
When all relative values of STD of the tally result are smaller than stdcut at the last of one batch, PHITS finishes
its calculation. If stdcut in two (or more) tally sections is set, all the results of the tally sections have to satisfy
the conditions in order to work the function.
7.6 [ T-Heat ] section 215
Neutrons, photons, and protons below the cut-off energy are not tallied in the ncut, gcut, and pcut compo-
nents but are tallied as stopped particles if, respectively, incut=0, igcut=0, or ipcut=0 in the [parameters]
section. Values of incut>0, igcut>0, and ipcut>0 are tallied in the respective ncut, gcut, and pcut parts.
216 7 TALLY INPUT FORMAT
Generally speaking, heat is energy produced by the ionization of charged particles. However, in the transport
simulation, transport is stopped below the set particle cut-off energy. In this case, additional components of heat,
including recoil, stopped particle, and others, will be output to the heat tally. These components may change as the
parameters of the transport are changed.
When unit is set =0 with output=dose, results can be obtained in units of [Gy/source]. When mesh=reg, the
volumes of each cell should be defined in the [volume] section or set as volume parameters of the [t-deposit]
section. Because absorbed dose is an intensive variable, PHITS does not output a ‘sum over’ in output files for
unit=0. Note that, in a region including more than two materials the dose in the region does not equal the average
value of the region. For example, when there are two materials with masses of M1 and M2 , and absorption energies
+E2
of E1 and E2 , respectively, PHITS gives M E1 V1
1 V1 +V2
+ M
E2 V1
2 V1 +V2
in this tally, even though its average dose is ME11 +M 2
.
Here, V1 and V2 are volumes of the two materials.
When specifying stdcut, PHITS automatically stop the calculation depending on values of STD (standard
deviation). This function is available when stdcut is positive and itall=0,1 is set in [parameters] section.
When all relative values of STD of the tally result are smaller than stdcut at the last of one batch, PHITS finishes
its calculation. If stdcut in two (or more) tally sections is set, all the results of the tally sections have to satisfy
the conditions in order to work the function.
218 7 TALLY INPUT FORMAT
In the [t-yield] section, projectiles to tally can be specified by part, but the output is the sum of their
contributions. To obtain each contribution separately, set multiple [t-yield] sections.
7.7 [ T-Yield ] section 219
For the use of ctmin and/or ctmax in this tally, it should be noted that a progress value defined in the
[counter] section will be given to the nuclear reaction products after a nuclear reaction if coll is set in the
[counter] section.
When specifying stdcut, PHITS automatically stop the calculation depending on values of STD (standard
deviation). This function is available when stdcut is positive and itall=0,1 is set in [parameters] section.
When all relative values of STD of the tally result are smaller than stdcut at the last of one batch, PHITS finishes
its calculation. If stdcut in two (or more) tally sections is set, all the results of the tally sections have to satisfy
the conditions in order to work the function.
7.7 [ T-Yield ] section 221
The following nuclear reactions are included in the available nuclear data for ndata=1:
4
He(n, x)3 H 14
N(n, x)3 H 14
N(n, x)7 Be 14
N(n, x)11 Be 14
N(n, x)10 C 14
N(n, x)11 C
14
N(n, x)14 C 14
N(n, x)13 N 16
O(n, x)3 H 16
O(n, x)7 Be 16
O(n, x)11 Be 16
O(n, x)10 C
16
O(n, x)11 C 16
O(n, x)14 C 16
O(n, x)15 C 16
O(n, x)13 N 16
O(n, x)16 N 16
O(n, x)14 O
16
O(n, x)15 O 4
He(p, x)3 H 14
N(p, x)7 Be 14
N(p, x)11 Be 14
N(p, x)10 C 14
N(p, x)11 C
14
N(p, x)13 N 14
N(p, x)14 O 16
O(p, x)3 H 16
O(p, x)7 Be 16
O(p, x)11 Be 16
O(p, x)10 C
16
O(p, x)11 C 16
O(p, x)14 C 16
O(p, x)13 N 16
O(p, x)14 O 16
O(p, x)15 O
For ndata=2,3, a file name of the production cross section data should be given as “[element symbol]+[mass
number(three digits)]+[-y-]+[incident particle(p or n)]+[.dat],” e.g., “O 016-y-n.dat” or “Pd107-y-n.dat.” Here, p
and n mean proton- and neutron-induced reactions, respectively. Note that if the element has only one character in
its symbol, an underline “ ” must be added after the element symbol. An example of the production cross section
data is as follows.
# ZAP = 48113 LIP = 1 INT = 2
# Elab (MeV) sigma (b)
1.000000e-11 0.000000e+00
2.530000e-08 0.000000e+00
2.000000e+01 0.000000e+00
2.100000e+01 0.000000e+00
・・
・・・
・・
where ZAP, LIP, and INT are produced nuclei, its isomer state, and interpolation method, respectively. The
produced nuclei are specified as 1000Z + A, where Z is atomic number and A(three digits) is mass number. The
isomer state is specified by LIP: =0; the ground state, =1; the first metastable state, =2; the second metastable
state. The interpolation method INT = (1,2,3,4,5) are as follows.
INT = 1 : Histogram
2 : Linear - Linear
3 : Log - Linear
4 : Linear - Log
5 : Log - Log
The second line should be written as,
‘Lethargy’ in unit=5, 6, 15, 16, 25, 26, 35 or 36 is the natural logarithmic unit of energy defined by
ln(Eref /E) using a reference energy Eref and the particle energy E. Setting these units enables obtaining results
in units of Lethargy, which are given as Lethargy widths, ln(Ehigh /Elow ), for each energy bin in the energy mesh
subsection. Here Ehigh and Elow are the maximum and minimum values of the energy bins, respectively.
In unit=21 - 26 or 31 - 36, ‘sr’ denotes steradians as the solid angle unit.
224 7 TALLY INPUT FORMAT
When specifying stdcut, PHITS automatically stop the calculation depending on values of STD (standard
deviation). This function is available when stdcut is positive and itall=0,1 is set in [parameters] section.
When all relative values of STD of the tally result are smaller than stdcut at the last of one batch, PHITS finishes
its calculation. If stdcut in two (or more) tally sections is set, all the results of the tally sections have to satisfy
the conditions in order to work the function.
7.10 [ T-LET ] section 229
From version 3.02, new options (unit=13 and 14) were implemented. Using them, the frequency and dose
probability densities of LET L, f (L) and d(L), respectively, can be easily calculated. The results obtained from
unit=13 and 14 are proportional to those obtained from unit=2 and 4, respectively, but their absolute values
are different because the integral of the probability densities are normalized to 1 for the new options. Note that
unit=13 and 14 can be set only when axis=let.
7.10 [ T-LET ] section 231
When specifying stdcut, PHITS automatically stop the calculation depending on values of STD (standard
deviation). This function is available when stdcut is positive and itall=0,1 is set in [parameters] section.
When all relative values of STD of the tally result are smaller than stdcut at the last of one batch, PHITS finishes
its calculation. If stdcut in two (or more) tally sections is set, all the results of the tally sections have to satisfy
the conditions in order to work the function.
232 7 TALLY INPUT FORMAT
Using this tally, information on the probability densities of y and z in water can be obtained. It is also possible
to calculate probability densities in different materials, although the accuracy of doing so has no yet been checked.
Similar to [t-let], the dose is only counted from the energy loss of charged particles and nuclei, and therefore
the event generator mode (e-mode≥1) must be used to transport low-energy neutrons. The deposition energy in
microscopic sites can be expressed as the deposit energy ε in MeV, the lineal energy y in keV/µm, or the specific
energy z in Gy. The definitions of these quantities are given in ICRU Report 36. Usage of [t-sed] is similar to
that of [t-let].
Table 7.33: [t-sed] parameters (1)
65 T. Sato, R. Watanabe and K. Niita, “Development of a calculation method for estimating the specific energy distribution in complex
code coupled with a microdosimetric kinetic model,” Radiat. Res. 171, 107-117 (2009).
7.11 [ T-SED ] section 233
From version 3.02, new options (unit=7 and 8) were implemented. Using them, the frequency and dose
probability densities of y, f (y) and d(y), respectively, can be easily calculated. The results obtained from unit=7
and 8 are proportional to those obtained from unit=2 and 4, respectively, but their absolute values are different
because the integral of the probability densities are normalized to 1 in the cases of the new options. Note that
unit=13 and 14 can be set only when axis=sed.
234 7 TALLY INPUT FORMAT
When specifying stdcut, PHITS automatically stop the calculation depending on values of STD (standard
deviation). This function is available when stdcut is positive and itall=0,1 is set in [parameters] section.
When all relative values of STD of the tally result are smaller than stdcut at the last of one batch, PHITS finishes
its calculation. If stdcut in two (or more) tally sections is set, all the results of the tally sections have to satisfy
the conditions in order to work the function.
7.12 [ T-Time ] section 235
In the [t-time] tally, the dump option can only be used only with output=cutoff. If the dump option is set,
the e-type and t-type meshes take on only the maximum and minimum values. In using this dump parameter,
axis and file are restricted to one axis and one file apiece and unit is always 1. The dumped data are written
onto a file named “*** dmp,” where “***” indicates the file name specified by file=***. The normal output of
the tally is written on “***.” From this file, information on the total normalization factor can be obtained; doing so
requires setting one mesh each for e-type and t-type (in the versions of PHITS before 2.66, the normal output
was written on a configuration file (.cfg) and the dumped data were written on “***”). The history information
(nocas and nobch) is necessary to use idmpmode=1 for continuous calculation using the dump file; in addition,
both the dump file with “ dmp” and the normal output file specified by file= are required to use idmpmode=1.
The option dumpall is not compatible with this dump tally option when shared memory parallelization is active.
By the dump option, similar files to ncut, gcut and pcut files can be created for the sequential calculations
of another transport code.
When specifying stdcut, PHITS automatically stop the calculation depending on values of STD (standard
deviation). This function is available when stdcut is positive and itall=0,1 is set in [parameters] section.
When all relative values of STD of the tally result are smaller than stdcut at the last of one batch, PHITS finishes
its calculation. If stdcut in two (or more) tally sections is set, all the results of the tally sections have to satisfy
the conditions in order to work the function.
238 7 TALLY INPUT FORMAT
When specifying stdcut, PHITS automatically stop the calculation depending on values of STD (standard
deviation). This function is available when stdcut is positive and itall=0,1 is set in [parameters] section.
When all relative values of STD of the tally result are smaller than stdcut at the last of one batch, PHITS finishes
its calculation. If stdcut in two (or more) tally sections is set, all the results of the tally sections have to satisfy
the conditions in order to work the function.
7.14 [ T-Dchain ] section 241
W,/d^ ,/E
EƵĐůĞĂƌƌĞĂĐƚŝŽŶĂŶĚ ,/EĚĂƚĂůŝďƌĂƌLJ
ƚƌĂŶƐƉŽƌƚĐĂůĐƵůĂƚŝŽŶƐ •EĞƵƚƌŽŶĂĐƚŝǀĂƚŝŽŶĐƌŽƐƐƐĞĐƚŝŽŶƐ
ǁŝƚŚϭϵϲϴŐƌŽƵƉĞŶĞƌŐLJƐƚƌƵĐƚƵƌĞ
•ĞĐĂLJĚĂƚĂůŝďƌĂƌLJŝŶĐůƵĚŝŶŐ
ŐĂŵŵĂͲƌĂLJƐƉĞĐƚƌƵŵ
&ŝůĞƐƉƌŽĚƵĐĞĚďLJdͲĚĐŚĂŝŶ •ĂƚĂůŝďƌĂƌLJĂďŽƵƚƌĂƚŝŽŽĨĞůĞĐƚƌŽŶ
ĐĂƉƚƵƌĞĂŶĚďĞƚĂнĚĞĐĂLJ
ŶƵĐůĞĂƌƉƌŽĚƵĐƚŝŽŶLJŝĞůĚ
ŶĞƵƚƌŽŶĞŶĞƌŐLJƐƉĞĐƚƌƵŵǁŝƚŚϭϵϲϴ
ŐƌŽƵƉĞŶĞƌŐLJƐƚƌƵĐƚƵƌĞďĞůŽǁϮϬDĞs
ĂůĐƵůĂƚĞĚƌĞƐƵůƚƐ
,/E ƚĂƌďŝƚƌĂƌLJƚŝŵĞ
ĂůĐƵůĂƚŝŽŶŽĨ WƌŽĚƵĐƚŝŽŶLJŝĞůĚ
ďĂƐŝĐŝŶƉƵƚĨŝůĞŽĨ,/E ƉƌŽĚƵĐƚŝŽŶLJŝĞůĚ ZĂĚŝŽĂĐƚŝǀŝƚLJ;ƋͿ
ĞĐĂLJŚĞĂƚ;tͿ
ŝŶĨŽƌŵĂƚŝŽŶĂďŽƵƚůŝŶŬƚŽƚŚĞĨŽůĚĞƌ
ŚĂǀŝŶŐ,/EĚĂƚĂůŝďƌĂƌLJ džĞĐƵƚŝŽŶƵƐŝŶŐ
'ĂŵŵĂͲƌĂLJƐƉĞĐƚƌƵŵ
ƐŚĞůůƐĐƌŝƉƚ
Figure 7.4: Concept of the connection calculation between PHITS and DCHAIN.
In the PHITS calculation, [t-dchain] automatically creates [t-track] and [t-yield] as well as the input
file of DCHAIN. The [t-track] tally calculates the neutron energy spectra below 20 MeV with a 1968-energy-
group structure. The [t-yield] tally calculates the nuclear production yields by protons, heavy-ions, mesons,
and neutrons with energies above 20 MeV.
In the DCHAIN calculation, the neutron energy spectra are multiplied by the activation cross section contained
in the DCHAIN data library. Then, the total activations are estimated by adding these results and those directly
calculated by PHITS using the [t-yield] tally. After that, DCHAIN evaluates radioactivity, nuclide, decay heat,
and the gamma energy spectrum at irradiation and cooling time.
Note that the time variation in particle transport simulation or that given by time distribution defined in the
[source] section is independent of the time variation in the DCHAIN calculation.
Setting e-mode≥1 in the [parameters] section enables calculation of the yields of radioactive nuclides pro-
duced by low-energy neutron reactions below 20 MeV using PHITS instead of the activation cross sections con-
tained in the DCHAIN data library. However, the accuracy of the event generator mode relative to that of the
DCHAIN data library in terms of calculating the residual-nuclide yields has not been verified, and it is there-
fore recommended that the use set e-mode=0 (default) in the PHITS calculation using [t-dchain]. Note that
activations from the originally activated target are not included in the DCHAIN calculation.
From ver. 3.00, the natural isotope expansion defined in [material] was effective in input files of DCHAIN
generated by [t-dchain]. Note that in the case that one nucleus is defined two (or more) times in a material, only
the latter one is effective. For example, if a material is defined as follows:
MAT[1] Fe 1 56Fe 1
67 Tetsuya Kai, et al., “DCHAIN-SP 2001: High Energy Particle Induced Radioactivity Calculation Code”, JAERI-Data/Code-2001-016
(2001) in Japanese
242 7 TALLY INPUT FORMAT
Time should be calculated from the end of the last step and not from the
start of the first irradiation. The allowable units are seconds (s), minutes
(m), hours (h), days (d), and years (y). One (or more) blank character must
be placed between the number indicating the time and the unit.
*See example of input for [t-dchain] tally in Example 56.
outtime= number Number of output timings in the DCHAIN calculation.
(next line) time Output timing.
When specifying stdcut, PHITS automatically stop the calculation depending on values of STD (standard
deviation). This function is available when stdcut is positive and itall=0,1 is set in [parameters] section.
When all relative values of STD of the tally result are smaller than stdcut at the last of one batch, PHITS finishes
its calculation. If stdcut in two (or more) tally sections is set, all the results of the tally sections have to satisfy
the conditions in order to work the function.
See Sec. 7.7 for ndata.
7.14 [ T-Dchain ] section 243
In addition to the above parameters, the DCHAIN parameters can also be specified in [t-dchain] section.
The specifiable parameters are:
imode, jmode, idivs, iregon, inmtcf, ichain, itdecs, itdecn, isomtr, ifisyd, ifisye, iyild, iggrp, ibetap,
acmin, istabl, igsdef, igsorg, ebeam, prodnp, hnxslib, hdcylib, iwrtchn, chrlvth, iwrchdt, iwrchss
The respective meanings of these parameters are given in the DCHAIN manual, where you can find in the
“\phits\dchain-sp\manual\” folder.
244 7 TALLY INPUT FORMAT
Figure 7.5: Relation between steps for irradiation and cooling and output times.
Example 57: Example for the setting of target material compositions and volumes for target=1
.......
: target = 1 <-target material composition ON
: non reg vol <-omissible
: 1 1 8000.0 <-serial number, cell number, volume
: tg-list = 2 <-number of the nuclides
: H-1 6.689E-02 <-Element ID, Atomic Number,
: O-16 3.345E-02 and Density of the atom (10ˆ24/cmˆ3)
: 2 2 2000.0 <-serial number, cell number, volume
: tg-list = 1 <-Number of the nuclides
: Fe-56 8.385E-02
To indicate an isotope, the symbol of the chemical element must be connected with its atomic number using
the character ‘-.’
Important notices for using [t-dchain]:
• Only one [t-dchain] tally per PHITS input file is allowed.
• The following parameters must be defined in the [parameters] section:
– jmout=1: display the atomic number density of materials.
– file(21): set the placement of the data folder for DCHAIN.
• The volume of each tally region must be defined in the [volume] section.
Files generated by [t-dchain] are listed below.
• The basic input file of DCHAIN: file name is set in the [t-dchain] tally.
7.14 [ T-Dchain ] section 245
• Neutron energy spectra with 1968 energy groups below 20 MeV : ***.dtrk
• Nuclear production yields: ***.dyld
• Information on the link to the folder containing the DCHAIN data library is in “dch link.dat.”
Note that when DCHAIN is executed, files of names shown below are deleted.
“yield.out, out-gsdef, out-gamsporg, out-allreg, spd-act.out, angel-data.ang, out-phits, out-dcychains”
246 7 TALLY INPUT FORMAT
To perform restart calculation, set two (or more) axis parameters, and
then set the first axis to reg, eng, or t.
file = file name Define file names. This is required by each setting of axis.
resfile = (omitted, D=file) Define a file name of the past tally in the restart calculation: even if
several axis parameters were defined, specify only one resfile.
factor = (omitted, D=1.0) Normalization factor.
title = (omitted) Title.
angel = (omitted) ANGEL parameters.
rshow = 0 (default), 1, 2, 3 When mesh=xyz and axis=xy,yz,xz, region border (1), material
name (2), and region name (3) are plotted using this option. A xyz
mesh section must be added below this option.
Only reg and xyz can be set as mesh in this tally, because the parameters in [Weight Window] are defined
only for these mesh types. In short, axis should be set wwg to obtain the parameters for [Weight Window].
Although eng, reg, xy, yz, xz, and t can also be set, their results are not related with [Weight Window].
axis= xy, yz, or xz are valid only with rshow=1.
68 To be precise, it is determined by the fluence of a Monte Carlo particle, i.e., a particle always having weight= 1.
7.15 [ T-WWG ] section 247
When specifying stdcut, PHITS automatically stop the calculation depending on values of STD (standard
deviation). This function is available when stdcut is positive and itall=0,1 is set in [parameters] section.
When all relative values of STD of the tally result are smaller than stdcut at the last of one batch, PHITS finishes
its calculation. If stdcut in two (or more) tally sections is set, all the results of the tally sections have to satisfy
the conditions in order to work the function.
An example output of this tally is as follows.
[ Weight Window ]
mesh = reg
part = neutron
eng = 2
1.00000E-03 1.00000E+03
In this sample, the [Weight Window] parameters for neutrons with two energy bins are output. In principle,
it is not necessary to change these parameters, but c71 or c74 should be specified when adding a constant value
for each Weight Window.
248 7 TALLY INPUT FORMAT
Figure 7.6: The flowchart of the connection calculation between [weight window] and [ww bias].
[t-wwbg] determines the bias values in stages of some cylindrical regions, which are with a central axis on a
vector defined by two points (x0,y0,z0) and (x1,y1,z1), shown in Fig. 7.7. Figure 7.7 shows a cross-section
view of three different size cylinders. To define the cylindrical regions, the parameters n-mesh, r-mesh, z-mesh,
and f-mesh are also required. n-mesh is the number of the cylinders. The differences of radii and heights of
the cylinders are given by r-mesh, z-mesh, respectively. In these parameters, the same number of values as the
n-mesh must be given. The bias values can be set from the inside of the cylindrical regions in f-mesh. f-mesh
must be set of (n-mesh)+1. The last value of f-mesh is the bias value in the outside of the cylinders. The
fm4
rm3 fm3
rm2 fm2
(x0,y0,z0) (x1,y1,z1)
cylindrical regions can be defined regardless of the geometry to calculation of the particle transport simulation.
Note that if the defined cylindrical regions overlap the outer void given in [cell], the outer void region can be
extended by the r-out parameter.
The [t-wwbg] parameters are formatted as follows.
In this example, the initial and terminal points are (0, -20, 50) and (0, 20, 150), respectively. The three cylindrical
regions are defined with the central axis on the vector defined the two points. Figure 7.8 shows a spatial distribution
of the bias values given by File
the example input. The radii of the three cylinders are defined by Date
= wwbyz01.dat
r-mesh, the differences
= 09:30 08-Aug-2017
of them are 10cm. The heights of the cylinders increase by 20cm, which is two times of 10cm given by z-mesh.
Bias values are given as 1.0, 0.5, 0.1, and 0.05 from the inside of the cylindrical regions. The change of the biases
is shown in Fig. 7.8.
x = 0.0000E+00 [cm]
no. = 1, ix = 1
0
10
50
WWB [WWB]
y [cm]
10−1
−50
The source type in the volume calculation is specified by s-type. In s-type=1, the source generates on a
sphere of the center coordinates (x0,y0,z0) and the radius r0 with the inward direction. This is the same condition
as dir=-all in s-type=9 of [source] section. In s-type=2, the source uniformly generates on surfaces of a
rectangular solid which are defined by 6 planes, x=x0, x1, y=y0, y1, and z=z0, z1. Its direction is inward.
In either case, you have to set the source region to be large so as to cover the all specified cells.
When specifying stdcut, PHITS automatically stop the calculation depending on values of STD (standard
deviation). This function is available when stdcut is positive and itall=0,1 is set in [parameters] section.
When all relative values of STD of the tally result are smaller than stdcut at the last of one batch, PHITS finishes
its calculation. If stdcut in two (or more) tally sections is set, all the results of the tally sections have to satisfy
the conditions in order to work the function.
When executing PHITS using [t-volume], the information on the source used in the volume calculation is
output in [source] of the summary file file(6) (D=phits.out). [source] written in the input file of PHITS
is not output in the summary file.
252 7 TALLY INPUT FORMAT
[t-volume] section should have the setting of mesh=reg. The cell numbers should be specified after reg=. By
setting s-type and the related parameters such as x0, you can define the special source region for the volume
calculation. Note that the source region should be set to cover all cells specified in reg=, otherwise the calculated
volumes would be wrong. On the contrary, if you set an extremely large source region, the statistical uncertainties
of the calculated results would be large. The obtained volumes are outputted in a file named by file=. The format
of the output file is as follows.
[ T - V o l u m e ] off
mesh = reg # mesh type is region-wise
.... .... .... ....
.... .... .... ....
[ V o l u m e ]
non reg vol non
1 101 5.0370E+02 0.2909
2 102 2.4727E+03 0.1634
.... .... .... ....
.... .... .... ....
Because the volumes are outputted in the format of [volume] section, the results can be used in the main calcu-
lation with icntl=0 by infl command. Here, values of the last column in [volume] are statistical uncertainties
(relative values). If the uncertainties are large, you can perform the restart calculation by adding istdev=-1 or
-2 in [parameters] section, because the output file of [t-volume] has information for the restart mode.
7.18 [ T-Userdefined ] section 253
(1) NCOL:
This is an intrinsic variable in the program and denotes identification of process.
NCOL
1 : start of calculation
2 : end of calculation
3 : end of a batch
4 : source
5 : detection of geometry error
6 : recovery of geometry error
7 : termination by geometry error
8 : termination by weight cut-off
9 : termination by time cut-off
10 : geometry boundary crossing
11 : termination by energy cut-off
12 : termination by escape or leakage
13 : (n,x) reaction
14 : (n,n’x) reaction
15 : sequential transport only for tally
69 This parameter plays the same role as udtparai (i = 0 − 9) before ver. 3.01. udtparai can be also set after ver. 3.02.
254 7 TALLY INPUT FORMAT
(4) iusrtally:
This is a parameter to control whether subroutine usrtally is used or not. If [t-userdefined] is
defined in an input file, this parameter is set to be 1.
(5) iudtf(50):
These are device numbers of output files defined with file=. For example, if there is the earliest file defined
in [t-userdefined], its device number is iudtf(1)=151.
(6) nudtvar:
The number of available udtvar(i). This is given as nudtvar in the input file.
(7) udtvar(i):
These are numerical values defined as udtvar(i) in the input file. udtvar(i) upto i=nudtvar can be used.
If udtvar(i) is not defined in the input file, it is set to 0.
(10) QS:
This is dE/dx for electrons at (x,y,z).
(a) ILAT1:
This is a variable of level structure of cell.
(b) ILAT2:
This is a variable of level structure of cell.
7.18 [ T-Userdefined ] section 255
(14) WT, U, V, W:
(15) E, T, X, Y, Z:
(18) NZST:
This is charge state of the particle.
(19) NCLSTS:
This variable means the number of produced particle and nucleus.
JCOLL
0 : nothing happen
1 : Hydrogen collisions
2 : Particle Decays
3 : Elastic collisions
4 : High Energy Nuclear collisions
5 : Heavy Ion reactions
6 : Neutron reactions by data
7 : Photon reactions by data
8 : Electron reactions by data
9 : Proton reactions by data
10 : Neutron event mode
11 : delta ray production
13 : Photon reactions by EGS5
14 : Electron reactions by EGS5
KCOLL
0 : normal
1 : high energy fission
2 : high energy absorption
3 : low energy n elastic
4 : low energy n non-elastic
5 : low energy n fission
6 : low energy n absorption
JCLUSTS(i)
i=0 : angular momentum
=1 : proton number
=2 : neutron number
=3 : ityp
=4 : status of the particle 0: real, <0 : dead
=5 : charge number
=6 : baryon number
=7 : kf code
7.18 [ T-Userdefined ] section 257
QCLUSTS(i)
i=0 : impact parameter
=1 : x-component of unit vector of momentum
=2 : y-component of unit vector of momentum
=3 : z-component
√ of unit vector of momentum
=4 : etot = p2 + m2 (GeV)
=5 : rest mass (GeV)
=6 : excitation energy (MeV)
=7 : kinetic energy (MeV)
=8 : weight
=9 : time (nsec)
= 10 : x coordinate (cm)
= 11 : y coordinate (cm)
= 12 : z coordinate (cm)
258 7 TALLY INPUT FORMAT
output=7,8 can be used only when the cells in bottom level are themselves in the lattice; the output then gives
lattice numbers in the format (4,1,2). For example, Fig. 5.40 in Sec. 5.6.4 is generated by the input shown below.
For example, Figure 7.9 can be obtained by the [t-rshow] tally shown below from the example (6) shown in
Sec. 5.6.4.
10
5
x [cm]
Values
−5
−10 100
−10 −5 0 5 10
z [cm]
w-dst
w-hgt
(w-mnh)
Figure 7.10: 3dshow tally: origin (x0,y0,z0), eye point (e-the,e-phi,e-dst), light source
(l-the,l-phi,l-dst), and picture flame (w-wdt,w-hgt,w-dst).
264 7 TALLY INPUT FORMAT
The definitions of the rules for reg= and reginbox= are the same as that for the region mesh in Sec. 6.1.1.
To saving calculation time, an outer void defined by the radius r-out has been introduced. A larger r-out
value must be used when using a large geometry or when placing the light source and view point at long distances.
As this new outer void definition can be seen in input echo, input echo cannot be used by icntl=11 as an input
for the next calculation.
No shadow is created if the view point and light source are set in the same position.
7.21 [ T-3Dshow ] section 265
box = 2
box x0 y0 z0
x1 y1 z1
x2 y2 z2 L
box trcl = 2
x0 y0 z0
x1 y1 z1
x2 y2 z2 L
box *trcl = (0 0 0 0 90 90 90 60 150 90 30 60 -1)
0.0 0.0 0.0
-5.0 0.0 0.0
0.0 0.0 5.0 5.0
( x1 , y1 , z1 )
( x3 , y3 , z3 )
L
( x0 , y0 , z0 ) ( x2 , y2 , z2 )
In the above geometry, the overall body is a rectangular solid with rectangular solid lattices including cylinders
on the interior. A graphical plot for the geometry can be created using 3dshow as follows.
A region boundary can be added using option line=1 to produce the following box, which shows how the
lattices are set up:
the regions defined by reg = (3 < 6[0 0 0] ) become transparent and material number 6 becomes visible:
Any number of complex structure types can be created by combining the above options.
269
File 3: dump-a.f
1: ************************************************************************
2: * *
3: * This program exchanges the binary data and the ascii data *
4: * of dump file. *
5: * *
6: * modified by K.Niita on 2005/08/15 *
7: * *
8: * *
9: * *
10: * *
11: ************************************************************************
12: implicit real*8 (a-h,o-z)
13: *-----------------------------------------------------------------------
14: dimension isdmp(0:30)
15: dimension jsdmp(0:30)
16: data isdmp / 31*0 /
17: data jsdmp / 31*0 /
18: character chin*80
19: character chot*80
20: logical exex
21: character dmpc(30)*4
22: data dmpc / ’ kf’,’ x’,’ y’,’ z’,’ u’,’ v’,’ w’,
23: & ’ e’,’ wt’,’ tm’,’ c1’,’ c2’,’ c3’,
24: & ’ sx’,’ sy’,’ sz’,’ n0’,’ nc’,’ nb’,’ no’,
25: & ’ ’,’ ’,’ ’,’ ’,’ ’,’ ’,
26: & ’ ’,’ ’,’ ’,’ ’/
27: dimension dmpd(30)
28: dimension dmpp(30)
29: data dmpp / 2112., 0.0, 0.0, 0.0, 0.0, 0.0, 1.0,
30: & 100., 1.0, 0.0, 0.0, 0.0, 0.0,
31: & 0.0, 0.0, 0.0, 0.0, 1.0, 1.0, 1.0,
32: & 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0,
33: & 0.0, 0.0, 0.0/
34: *-----------------------------------------------------------------------
35: in = 5
36: io = 6
37: id = 20
38: ia = 21
39: iserr = 0
40: *-----------------------------------------------------------------------
41: * user program frag : 0 => no, 1 => with user program
42: *-----------------------------------------------------------------------
43: iuser = 0
44: *-----------------------------------------------------------------------
45: * read ascii or binary frag
46: *-----------------------------------------------------------------------
47: write(io,*) ’ ** 0 => read binary to ascii’
48: write(io,*) ’ ** 1 => read ascii to binary’
49: read(in,*,end=993) iasb
50: *-----------------------------------------------------------------------
51: * read the name of input dump file
52: *-----------------------------------------------------------------------
53: write(io,*)
54: write(io,*) ’ ** put the file name of input dump file’
270 8 PROCESSING DUMP FILE
The input parameters are read from normal input, i.e., from console, in an interactive way. When you execute
the program, it asks you as,
You put 0 for binary, 1 for ascii. Next it asks you the name of target dump file.
The program ask you the number of data in a record. You put positive number for both ascii and binary.
You put ID for the data. See kind of dump data and ID, in Tables 6.4 6.5.
You put the file name of output. If the file already exists, the program asks you whether the file can be overwritten
or not.
Next, the program asks you how many records are processed.
If this number is larger than total record number, the program turns back to the top of the data. Finally, the number
of records actually processed is shown.
When you make a program based on this program, you should change iuser to 1 at 35 line in File 3. Then the
program does not write the converted data on file. In this case, the output is written by ascii.
In 150-169 lines, there are variables kf, x, y, z, u, v, w, e, wt, t, n1, n2, n3, sx, sy, sz,
n0, nc, nb, no. Here kf means the kf-code of the particles (see Table 4.4), x, y, z are coordinate [cm], u, v, w
denote the unit vector of the direction of the particle, e is the energy [MeV, or MeV/u for nucleus], wt is the weight,
time is the initial time [ns], c1, c2, c3 are the values of counters, and sx, sy, sz are the unit vector of the direction
of spin, respectively. By using these variables, you can make a program to obtain desired quantities.
273
where n = nint(rn), x, y, z is a coordinate [cm], e(i) is an energy [MeV], u(i), v(i), w(i) is an unit
vector of momentum, wt(i) is an weight, and t(i) is time [ns]. In the case igcut=3, the particle identifier p(i)
is written instead of t(i) in the case of incut=2.
p(i)=3.0 is photon, p(i)=4.0 is electron, and p(i)=5.0 is positron.
274 10 REGION ERROR CHECK
When ginfo=2 and PHITS detects a geometry error, a geometry error file named “***.err” is output (***
indicates the original tally output file name without the extension). In this file, the (x, y, z) coordinates together
with the overlapping cell numbers are written as follows:
The first line indicates that cell numbers 100 and 102 overlap at the point x=-4.847761E+00, y=1.234568E-11,
z=-1.211940E+00. The second line indicates that an undefined region is detected at the point x=-4.241791E+00,
y=-2.500000E+00, z=-8.079602E-01.
Geometry errors can easily be found using this geometry check function. Note that the function can detect
geometry error only when an error occurs on the grid points of the xyz mesh of the tally, while geometry errors
outside the tally region cannot be detected. Even in the tally region, a small error region might also remain
undetected if the region does not contain a grid point.
275
11 Compilation of PHITS
PHITS must be re-compiled by yourself for some circumstances; e.g. you need to extend the maximum mem-
ory allowed to be used by PHITS, or you would like to use your own source generation or tally programs. Our
recommended Fortran compilers are Intel Fortran 11.1 (or later) and gfortran (4.8, 7.0 or later). 70 Table 11.1
summarizes the combination of the Fortran compiler and OS by which we have succeeded in compiling PHITS for
four different parallel options: single mode, MPI, OpenMP, and hybrid of MPI and OpenMP.
written in the 2nd line of “mingw-w64.bat,” . Then set “PHITS EXE” to the PHITS executable file compiled
by gfortran, i.e., “phits WinGfort.exe.”
(3) Run PHITS via Windows explorer using “sendto → PHITS” command.
(4) After finishing the PHITS calculation, some warnings, such as “Note: The following floating-point excep-
tions are signaling: IEEE DENORMAL.” , may show up, but can be be ignored.
phits LinIfort OMP.exe. The compiler options given in “makefile” are simply examples, and users may need to
change the setting to fit their own computer environment.
The attached “makefile” can be used for GNU make. If an error is encountered with the “make” command,
try the “gmake” command instead.
278 12 ADDITIONAL EXPLANATION FOR PARALLEL COMPUTING
$MPI = 4
if you want to run PHITS as fast as possible in your computer with 4 CPU cores. Note that the actual number of
processing elements (PEs) is M + 1, where the additional element is used for controlling each process.
Then, you have to right-click the input file, and send to “phits” in the same manner as executing the single
version of PHITS. You have to input your username and password when you first-time run the MPI version of
PHITS. If you write both $OMP and $MPI in your input file, the command written behind is superseded.
12.1 Distributed memory parallel computing 279
where “mpirun” is the executable file name of your MPI protocol, “phits LinIfort MPI.exe” indicates the PHITS-
executable file name and the number of processing elements (PEs) is set following “-np.” This command can be
sent using a parallel computing submission protocol such as “qsub,” in which case the name of the PHITS input
file should be written in a text file named phits.in with the first line given as
file = input_file_name
where “input file name” is the name of the PHITS input file. This rule is only effective for distributed memory
parallel computing. file=phits.in can also be written in the first line, with the contents of the PHITS input file
added following the second line of phits.in: please see Sec. 2.3.2 for further details.
file(12) = temp/ncut.dat
In 1 PE calculation, the specified ncut.dat is written normally; in multi PE calculation, however, ncut.dat is
written separately in each node as
/wk/j9999/temp/ncut.dat
where “j9999” is the user-name, which is read-in automatically from the environmental variable “LOGNAME.”
By default, the user-name is placed in the “LOGNAME” in a UNIX system.
Before parallel calculation, a “j9999” directory should be created under the “/wk” directory for each node.
To create an ncut file in a directory not named using the user-name, the environmental variable “LOGNAME”
should be changed before parallel calculation. In the case, the user should confirm the existence of the directory
that they specified under “/wk.”
inpara, igpara, and ippara are used as writing options. By default, they each have values of zero: re-
setting the value= 1 gives the output files IP numbers as follows:
inpara, igpara, and ippara are prepared for writing options. By default, they have zero value. If you give
value 1, output files are given IP numbers as
/wk/j9999/temp/ncut.dat.005
280 12 ADDITIONAL EXPLANATION FOR PARALLEL COMPUTING
13 FAQ
13.1 Questions related to parameter setting
Q1.1 Input file that works before ver. 2.88 does not work after that version.
A1.1 Several revisions were made in terms of the input file format after ver. 2.89 to avoid frequently-occurring
mistakes. In general, it is not necessary to change input file when PHITS is updated, but in some cases, it is
necessary. If you encounter an error after the update, please check the following points.
(1) After ver. 2.89, ‘c’ cannot be used as a comment remark in [material] section in the default set-
ting. You have to change the comment remarks c in [material] to $ or #, or set icommat=1 in
[parameters].
(2) After ver. 2.93, low energy neutrons are transported using nuclear data library in the default setting.
Thus, you may encounter an error “There is no cross section table(s) in xsdir” even when you want
to transport only photon and electrons. In that case, you have to set nucdata=0 in [parameter] to
disable the use of nuclear data library.
(3) After ver. 2.96, it is not allowed to define two or more [parameter] sections in an input file.
(4) After ver. 2.96, unnecessary tallies are automatically disabled, depending on the icntl parameter.
Consequently, set: and infl: commands are ignored when they are written in the disabled sections.
When set: or infl: commands are ignored, PHITS outputs warning.
Q1.3 What nuclear reaction model settings gives the most accurate result?
A1.3 In general, the default models give the best results in most cases. However, it is desirable to activate JQMD-
2.0 (irqmd=1) for precisely simulating nucleon-nucleon interactions, and SMM (ismm=1) for precisely es-
timating the residual nuclide yields after high-energy nuclear reactions, though they are time consumptive.
Q1.5 When should the mode for statistical uncertainty (the setting of istdev) be changed?
A1.5 We generally recommend using the history variance mode (istdev=-2 or 2), in which the statistical uncer-
tainty depends on the total history number (maxcas*maxbch), except in the case of shared-memory parallel
computing, in which only the batch variance mode (istdev=-1 or 1) can be selected. However, the compu-
tational time occasionally becomes extremely long in history variance mode, especially in for tallies using
a large number of memories, e.g., an xyz mesh tally with very fine structure. When performing a PHITS
calculation under such conditions, please switch to batch variance mode and set maxbch to be greater than
10.
(1) using a text editor, open the “xsdir” file contained in the package of the new nuclear data library and
copy all nuclear data addresses (e.g., 1001.80c 0.999167 xdata/endf71x/H/1001.710nc 0 1 4 17969 0 0
2.5301E-08);
282 13 FAQ
(2) using a text editor, open the file “xsdir.jnd” included in the PHITS “data” folder and paste the copied
addresses at the end of the file;
(3) create a new folder with the appropriate name written in the address file in the PHITS “XS” folder and
copy the data files from the new nuclear data library to the created folder;
(4) explicitly specify the library ID in the [material] section of your PHITS input file (e.g., 1H.80c
or 1001.80c for the above example). If you do not specify the library ID, PHITS automatically finds
the data library of the previously written nucleus in “xsdir.jnd” and, therefore, JENDL-4.0 is selected
when the data for the nucleus is available.
Q1.7 How can neutron fluxes emitted from photo-nuclear reactions with low statistical uncertainty be found?
A1.7 The photonuclear cross section can be biased using the pnimul parameter. For example, the probability of
photo-nuclear reaction is doubled when pnimul is set =2.0 and the weights of secondary particles emitted
from the photo-nuclear reaction are 0.5. If a very high value of pnimul, e.g., above 100.0, is selected, the
photon fluxes might be altered; therefore, it should be confirmed that the photon fluxes are not significantly
altered as a result of changing this parameter.
Q1.8 I cannot restart PHITS simulation as a result of an error related to the inconsistency of a tally. Why is this?
A1.8 This occurs as the result of the loss of significant digits in the PHITS input file. In this case, set ireschk=1
to induce PHITS to skip the consistency check.
Q2.3 An error occurred when I tried to use infl: in my PHITS input file.
A2.3 When the infl: command is used in the PHITS input file (e.g., “phits.inp”), it is necessary to type
file=phits.inp in the first line of “phits.inp” file. Otherwise, another input file (e.g., “phits.in”) can
be created with the first line file=phits.inp and used as the PHITS input file. For example:
Q2.4 An error occurred when I tries to execute PHITS on a Linux console, but I can execute it on Windows using
the same input file.
A2.4 There are many possible causes of this error, but the most probable is a difference in the ‘return code’ used
in Linux and Windows. If the input file is prepared in a Windows computer and transferred to a Linux system
using FTP software, the status of the transfer mode must be checked, i.e., ‘ASCII mode’ must be selected in
the FTP software.
A2.6 We generally recommend using the Intel Fortran compiler because it can make PHITS executable files that
are faster than those made using gfortran. When using gfortran, it is vital that you set ‘-O0’ instead of
using optimization options because of the possibility that an executable file with optimization will not work
correctly. Thus, an executable file compiled using Intel Fortran is on average 3–5 times faster than one
compiled using gfortran. Furthermore, the latest version of gfortran cannot compile PHITS (see A2.1). Note
that the Intel Fortran compiler is not freeware (this is true for the Linux version as well).
Q2.7 How should the distributed memory parallel computing (MPI) or shared memory parallel computing (OpenMP)
be set depending on the situation?
A2.7 Calculation using MPI is generally faster than calculation using OpenMP if the MPI protocol is installed in
the computer. However, because the protocol is not generally pre-installed in Windows or Mac OS systems
as a default setting, we recommend the use of OpenMP for executable files. To perform PHITS calculation
on huge memories such as high energy nuclear data files or voxel phantoms, the hybrid MPI-OpenMP setting
must be used to avoid the possible memory shortages that could occur if only MPI were to be used. In the
hybrid setting, the number of MPI processes should be increased, but only up to the point at which the used
memory does not overflow the capacity of the computer. Note that PHITS uses a number of CPU cores
appropriate to the number of OpenMP processes to control the MPI processes. For example, to set the
number of OpenMP processes to eight on a computer with 128 CPU cores, the maximum number of MPI
processes can be specified as 128/8 − 1 = 15.
Q2.8 I got so many lost particles when I rotate a lattice structure by [transform].
A2.8 The size of outer frame surface should be smaller than the lattice structure inside it, otherwise you may
observe many lost particle. Please see “\phits\lecture\advanced\voxel\” in more detail.
Q3.2 The track length or fluence of heavy ions calculated by [t-track] or [t-cross] is strange.
A3.2 This might be caused by a mis-definition of the energy mesh in the tally section. The energies of heavy ions
should be defined in MeV in the tally section but should be written in MeV/u in the [parameters] section.
Q3.4 How can the statistical uncertainty be estimated from the tally output?
A3.4 In Version 2.50 and later the standard deviations or standard errors are correctly output in the tally results.
See section “5.2.2 Number of history and bank” for details.
Q3.5 Can the dump function be used when executing PHITS in distributed memory parallel computing?
A3.5 This is possible from version 2.30 onward. Please ask the PHITS offce for more information on its detailed
usage.
Q3.6 Tally results in boxes obtained using mesh=reg and mesh=xyz are inconsistent with each other.
A3.6 PHITS automatically calculates the volume of tally regions only in the cases of mesh=xyz or r-z. Thus, if
mesh=reg is set and the [volume] section is not specified, the volume of the tally region is assumed to be
1 cm3 .
Q3.7 Why do some events deposit energies greater than the incident energy when using [t-deposit] with the
output=deposit option.
284 13 FAQ
A3.7 When exothermic nuclear reactions occur, the total energy of secondary particles becomes greater than the
incident energy. Such events are also observed when mesh=xyz or r-z and nedisp=t0 based on the output
of the algorithm for considering the energy straggling of charged particles in PHITS. In such case, it is
necessary to set mesh=reg in [t-deposit] and define cells corresponding to each xyz or r-z mesh in the
[cell] section.
APPENDIX
A List of physical processes that cannot be handled by PHITS
• Criticality calculation
• Interaction between two (or more) moving particles (e.g. Simulation for particle collision experiments)
• Effect of electric fields generated by radiation (e.g. Laser acceleration of particles, plasma)
• Electron-induced nuclear reactions via virtual photon production
• Transport and generation of photons below 1 keV (e.g. Cherenkov light, synchrotron radiation, lumines-
cence)
• Polarization effect 73
• Chemical reactions (e.g. Transport and generation of radicals)
• Consideration of the status of a material 74 (e.g. crystal & molecular structure, temperature)
• Nuclear reactions originated from fine structure of nuclear shell 74 (e.g. Li(p,n) reaction)
286
INDEX 287
emumin, 43 file(11), 57
enclos, 203 file(12), 57, 272
ENDF/B-VIII.0, 242 file(13), 57, 272
energy mesh, 183, 196, 201, 205, 221, 234, 237, 245, file(14), 57
248 file(15), 52, 57
energy straggling, 46 file(18), 55, 57, 141
eng, 11, 164, 165, 186, 197, 201, 205, 208, 224, 234, file(20), 12, 40, 57
237, 245 file(21), 57, 242
eng-t, 186, 208 file(22), 8, 26, 57
eng1, 212 file(23), 57
eng2, 212 file(24), 57, 98
ENSDF, 14, 242 file(25), 57
enum, 59 file(26), 57
eps, 187, 191, 198, 202, 205, 209, 213, 216, 219, 224, file(27), 57
227, 230, 233, 236, 239, 246, 248, 257, 259, file(28), 57
263 file(4), 57
epsout, 7, 190, 191, 198, 202, 205, 209, 213, 216, 219, file(6), 13, 33, 49, 54, 57, 112, 159, 173, 250
224, 227, 230, 233, 236, 239, 246, 248, 257, file(7), 40, 57, 112
259, 263 FILL, 55, 129, 134–136, 138–140, 142, 143
epstfl, 62 fiss, 9, 177
eqmdnu, 38 fission, 224, 239
escape, 234 flight mesh, 56
esmax, 9, 38 fluence, 196, 200
esmin, 9, 38 fluo, 177
ESTEP, 113 flux, 200, 202
et0, 96 foamout, 1
et1, 96 forced collisions, 41
et2, 96 Fortran, 30, 97, 102, 104, 107, 189, 275
ets dea, 239
ets e-exc, 239 gap, 148
ets elast, 239 GAS, 113
ets ioniz, 239 gcut, 52, 214, 236, 278
ets ioniz e-exc, 239 GEM, 42, 177
ets p-exc, 239 geometry check, 273
ets r-exc, 239 geometry check function, 13
ets v-exc, 239 gfortran, 274
etsmax, 38, 156 GG, 52, 54, 163, 168, 169, 179
etsmin, 38, 156 GG(General Geometry), 129
evaporation, 42 ghigh, 170
event generator mode, 48, 67, 280 Ghostscript, 20
exa, 78 ghostview, 191
Excel, 190 giant-dipole resonance, 6
execution, 18 ginfo, 197, 202, 209, 216, 218, 224, 227, 230, 233, 236,
239, 246, 248, 257, 259, 273
f-curr, 202 glow, 170
f-mesh, 248 gmake, 274–276
factor, 70, 84, 188, 197, 202, 205, 208, 213, 216, 224, GQ, 116
227, 229, 232, 234, 239, 245 gravity, 48
FAQ, 280 gravx, 48
fcl, 168 gravy, 48
FENDL/A-2.0, 242 gravz, 48
FENDL/D-1, 242 groups, 184
file, 37, 83, 160, 187, 193, 197, 202, 205, 208, 213, 214, gshow, 3, 35, 175, 190, 192, 197, 202, 209, 216, 224,
224, 225, 229, 232, 234, 239, 241, 245, 248, 227, 230, 233, 236, 239, 273
250–252, 257, 259, 263 gslat, 198, 203, 209, 216, 219, 224, 227, 230, 233, 236,
file(1), 6, 40, 57 239, 246, 257, 259
file(10), 57, 272 GSview, 20
290 INDEX
xlog, 189
xmax, 189
xmin, 188
xnum, 59
xp, 76
xq, 76
xsdir, 57, 112, 281
xsdir.jnd, 6
XY, 116
xy, 5, 37, 186, 189–191, 197, 201, 208, 214, 218, 224,
229, 232, 234, 237, 245, 248, 257, 259, 273
xyz, 2, 4, 14, 35, 37, 79, 144, 164, 179, 182, 190, 196,
201, 204, 207, 214, 217, 221, 225, 228, 231,
234, 237, 245, 257, 259, 273, 280, 282, 283
xz, 197, 208, 214, 218, 224, 229, 232, 234, 237, 245,
248, 257, 259, 273
y, 186, 187, 197, 201, 208, 214, 218, 224, 229, 232, 234,
237
y-txt, 191, 197, 202, 208, 213, 216, 224, 227, 229, 232,
234, 239, 248, 257, 259, 263
y-type, 79, 164, 182, 184, 191
y0, 72–78, 83, 86, 182, 248, 250, 261
y1, 72, 73, 76–78, 83, 86, 248, 250
y2, 78
y3, 78
ylin, 189
ylog, 189
ymax, 189
ymin, 188
yp, 76
yq, 76
yz, 186, 190, 191, 197, 208, 214, 218, 224, 229, 232,
234, 237, 245, 248, 257, 259, 273
z, 4, 186, 197, 201, 208, 214, 218, 224, 229, 232, 234,
237
z-mesh, 248
z-txt, 191, 197, 202, 208, 213, 216, 224, 227, 229, 232,
234, 239, 248, 259, 263
z-type, 4, 79, 164, 182, 184, 191, 204
z0, 72–78, 83, 86, 248, 250, 261
z1, 72–74, 76–78, 83, 86, 248, 250
z2, 78
z3, 78
zlin, 259
zlog, 259
ZP, 116
zx, 186, 191
PHITS Ver. 3.17 User’s Manual
Ver.2.52 2012/12/27
Ver.2.64 2013/11/19
Ver.2.89 2017/01/11
Ver.2.90 2017/02/09
Ver.2.91 2017/02/20
Ver.2.92 2017/04/18
Ver.2.93 2017/06/16
Ver.2.94 2017/06/30
Ver.2.95 2017/07/21
Ver.2.96 2017/08/28
Ver.2.97 2017/09/21
Ver.3.00 2017/10/04
Ver.3.01 2017/10/31
Ver.3.02 2017/12/01
Ver.3.03 2018/02/01
Ver.3.04 2018/02/16
Ver.3.05 2018/03/14
Ver.3.06 2018/05/29
Ver.3.07 2018/07/05
Ver.3.08 2018/08/20
Ver.3.10 2019/04/03
Ver.3.11 2019/05/16
Ver.3.12 2019/06/20
Ver.3.13 2019/08/02
Ver.3.14 2019/08/19
Ver.3.15 2019/09/12
Ver.3.16 2019/09/26
Ver.3.17 2019/10/29