PHITS
Ver. 3.10
User’s Manual
English version

Preface
This manual is the Particle and Heavy Ion Transport code System (PHITS) user’s guide. PHITS is a generalpurpose 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 implemented 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
oﬃce (phits-oﬃce@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 Recent Improvements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 Development members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3 Reference of PHITS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1
1
14
15

2

Installation and execution of PHITS
2.1 Installation and execution on Windows OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.1 Installation on Windows OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.2 Execution on Windows OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.3 Recommended software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2 Installation and Execution on Mac OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.1 Installation on Mac OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.2 Execution on Mac OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3 Installation and Execution on Linux OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.1 Installation on Linux OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.2 Execution on Linux OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4 Restart and terminate PHITS calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4.1 Restart PHITS calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4.2 Terminate the PHITS code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

16
16
16
16
17
18
18
19
21
21
22
23
23
23

3

Input File
3.1 Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2 Reading control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3 Inserting files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4 User-defined variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5 Using mathematical expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.6 Particle identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.7 Array sizes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

25
25
26
27
27
28
29
31

4

Sections format
4.1 [ Title ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2 [ Parameters ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.1 Calculation mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.2 Number of history and Bank . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.3 Cut-oﬀ energy and switching energy . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.4 Cut-oﬀ time, cut-oﬀ weight, and weight window . . . . . . . . . . . . . . . . . . . . . .
4.2.5 Model options (1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.6 Model options (2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.7 Model options (3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.8 Model options (4) - stopping power . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.9 Model options (5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.10 Output options (1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.11 Output options (2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.12 Output options (3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.13 Output options (4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.14 Voxel and tetrahedron geometry options . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.15 About geometrical errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.16 Input-output file name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.17 Others . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.18 Physical parameters for low energy neutrons . . . . . . . . . . . . . . . . . . . . . . . .
4.2.19 Physical parameters for photon and electron transport based on the PHITS original model
4.2.20 Parameters for EGS5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.21 Dumpall option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.22 Event Generator Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3 [ Source ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

32
32
33
33
34
36
39
40
41
42
44
46
47
50
51
52
53
54
55
56
56
57
58
61
65
66

ii

4.3.1 <Source> : Multi-source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.2 Common parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.3 Cylinder distribution source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.4 Rectangular solid distribution source . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.5 Gaussian distribution source (x,y,z independent) . . . . . . . . . . . . . . . . . . . . . .
4.3.6 Generic parabola distribution source (x,y,z independent) . . . . . . . . . . . . . . . . . .
4.3.7 Gaussian distribution source (x-y plane) . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.8 Generic parabola distribution source (x-y plane) . . . . . . . . . . . . . . . . . . . . . . .
4.3.9 Sphere and spherical shell distribution source . . . . . . . . . . . . . . . . . . . . . . . .
4.3.10 s-type = 11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.11 s-type = 12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.12 Cone shape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.13 Triangle prism shape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.14 xyz-mesh distribution source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.15 Tetra-mesh source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.16 Reading dump file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.17 User definition source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.18 Definitions for energy distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.19 Definition for angular distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.20 Definition for time distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.21 Example of multi-source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.22 Duct source option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4 [ Material ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.1 Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.2 Element (nuclide) definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.3 Composition ratio definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.4 Material parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.5 S (α, β) settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.6 Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5 [ Surface ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5.1 Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5.2 Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5.3 Surface definition by macro body . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6 [ Cell ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.1 Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.2 Description of cell definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.3 Universe frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.4 Lattice definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.5 Repeated structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.7 [ Transform ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.7.1 Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.7.2 Mathematical definition of the transform . . . . . . . . . . . . . . . . . . . . . . . . . .
4.7.3 Examples (1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.7.4 Examples (2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.8 [ Temperature ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.9 [ Mat Time Change ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.10 [ Magnetic Field ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.10.1 Charged particle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.10.2 Neutron . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.10.3 Implementation of the magnetic field map . . . . . . . . . . . . . . . . . . . . . . . . .
4.10.4 Format of magnetic field map file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.11 [ Electro Magnetic Field ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.12 [ Delta Ray ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.13 [ Track Structure ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.14 [ Super Mirror ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.15 [ Elastic Option ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.16 [ Data Max ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
iii

67
68
70
70
71
71
72
72
73
74
74
75
76
77
79
80
83
86
98
100
102
106
109
109
109
109
110
110
111
112
112
115
125
126
126
127
130
131
134
141
141
141
142
142
144
145
146
146
147
148
149
152
153
154
155
156
157

5

4.17 [ Frag Data ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.18 [ Importance ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.19 [ Weight Window ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.20 [ WW Bias ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.21 [ Forced Collisions ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.22 [ Volume ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.23 [ Multiplier ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.23.1 Multiplier subsection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.24 [ Mat Name Color ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.25 [ Reg Name ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.26 [ Counter ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.27 [ Timer ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

158
161
162
163
166
167
168
169
171
173
174
176

Common parameters for tallies
5.1 Geometrical mesh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1.1 Region mesh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1.2 Definition of the region and volume for repeated structures and lattices . . . . . . . . . .
5.1.3 r-z mesh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1.4 xyz mesh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1.5 tet mesh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2 Energy mesh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3 LET mesh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4 Time mesh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5 Angle mesh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.6 Mesh definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.6.1 Mesh type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.6.2 e-type=1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.6.3 e-type=2,3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.6.4 e-type=4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.6.5 e-type=5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.7 Other tally definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.7.1 Particle definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.7.2 axis definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.7.3 file definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.7.4 resfile definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.7.5 unit definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.7.6 factor definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.7.7 output definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.7.8 info definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.7.9 title definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.7.10 ANGEL parameter definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.7.11 Sangel parameter definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.7.12 2d-type definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.7.13 gshow definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.7.14 rshow definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.7.15 x-txt, y-txt, z-txt definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.7.16 volmat definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.7.17 epsout definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.7.18 counter definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.7.19 resolution and line thickness definitions . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.7.20 trcl coordinate transformation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.7.21 dump definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.8 Function to sum up two (or more) tally results . . . . . . . . . . . . . . . . . . . . . . . . . . . .

177
177
177
178
179
180
180
181
181
181
182
183
183
183
184
184
184
184
184
185
186
186
186
187
187
187
187
187
188
188
189
189
190
190
190
191
191
191
191
193

iv

6

Tally input format
6.1 [ T-Track ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2 [ T-Cross ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3 [ T-Point ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.4 [ T-Deposit ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.5 [ T-Deposit2 ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.6 [ T-Heat ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.7 [ T-Yield ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.8 [ T-Product ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.9 [ T-DPA ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.10 [ T-LET ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.11 [ T-SED ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.12 [ T-Time ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.13 [T-Interact] section (formerly named [T-Star]) . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.14 [ T-Dchain ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.15 [ T-WWG ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.16 [ T-WWBG ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.17 [ T-Volume ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.18 [ T-Userdefined ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.19 [ T-Gshow ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.20 [ T-Rshow ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.21 [ T-3Dshow ] section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.21.1 Box definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.21.2 3dshow example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

195
195
198
203
205
211
213
216
220
224
227
230
233
236
239
243
245
248
250
255
257
259
262
263

7

Processing dump file266

8

Output cutoﬀ data format

270

9Region error check271

10 Compilation of PHITS
10.1 Compilation on Windows OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.1.1 Compilation using makefile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.1.2 Compilation using Microsoft Visual Studio with Intel Fortran . . . . . . . . . . . . . . .
10.2 Compilation on Mac OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.3 Compilation on Linux OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

272
272
272
273
273
273

11 Additional explanation for parallel computing
11.1 Distributed memory parallel computing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.1 Installation of MPI protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.2 Execution of MPI version of PHITS on Windows . . . . . . . . . . . . . . . . . . . . . .
11.1.3 Execution of MPI version of PHITS using command line . . . . . . . . . . . . . . . . .
11.1.4 Adjustment of maxcas and maxbch . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.5 Treatment of abnormal ending . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.6 ncut, gcut, pcut, and dumpall file definition in PHITS . . . . . . . . . . . . . . . . . . . .
11.1.7 Read-in file definition in PHITS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.2 Shared-memory parallel computing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.2.1 Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.2.2 Important notices for shared-memory parallel computing . . . . . . . . . . . . . . . . . .

275
275
275
275
276
276
276
276
277
277
277
277

12 FAQ12.1 Questions related to parameter setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.2 Questions related to errors occurred in compiling or executing PHITS . . . . . . . . . . . . . . .
12.3 Questions related to Tallies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.4 Questions related to source generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.5 Other questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

279
279
280
281
282
282

v

APPENDIX
A
List of physical processes that cannot be handled by PHITS
index

283
. . . . . . . . . . . . . . . . . . . . 283
284

vi

1

1

Recent Improvements and Development Members

1.1 Recent Improvements
Essential improvements after version 2.24 are described below.
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 introduced 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-SP is also updated. Note that the function to visualize the induced activities in xyz mesh has not been developed yet.
• Error and warning ID numbers are introduced for some messages.
Please see \phits\manual\supplementE-ErrID.pdf in more detail.
• 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.
• Electron track-structure mode is improved to consider the production of Auger electrons.
• User-defined energy resolution function has been implemented to [T-deposit] in order to reproduce energy resolution which cannot be realized by dresol and dfano. Users can define the functional forms ofenergy 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 peaksof 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 andtetrahedral phantoms.
• Time for reading lattice structure is reduced by introducing compressed format• 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.
• Remaining batch number has become adjustable using “batch.out.”• 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 diﬀerent lattice coordinates can be separately
analyzed in the case of [t-deposit] with output=deposit.

2

1 RECENT IMPROVEMENTS AND DEVELOPMENT MEMBERS• 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 acertain 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 6.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”).
• The high-speed mode of ANGEL, which does not check numerical data while plotting the results, has become 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 coeﬃcients 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 eﬀect 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 bysetting 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. Thisdevelopment 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 theenergy 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.

1.1 Recent Improvements

3• 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 outputtedfrom [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 4.3.15
in more detail.
• mesh = xyz became available in [weight window] and [t-wwg] sections.
• Coeﬃcients 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.
• [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 thisversion.
• 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 introducedin 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.

4

1 RECENT IMPROVEMENTS AND DEVELOPMENT MEMBERS• 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 crosssections, and the natural isotope expansion was eﬀective in input files of DCHAIN-SP 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 unitof 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 parameters 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 4.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 executedby drag and drop on the Dock. Note that these function are not available when to run PHITS on the commandline on Linux and so on.
• 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] toobtain better statistics for a certain direction. See Section 4.20 and 6.16 in more detail.
• The numerical data of tally results are outputted after each batch is finished even for itall=0 (default).
Thus, the diﬀerence 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 wheninfl 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 5.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 sections, 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 waschanged. The mono-energetic and energy-distributed sources can be defined by setting e0 and e-type, respectively, 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 andpositrons passing through vacuum is slightly diﬀerent from the real value when EGS5 mode is used. Note that thisrevision 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)

1.1 Recent Improvements

5• 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, and25) unless you have changed the folder structure of PHITS.
• A new parameter nucdata was introduced to automatically adjust emin(2) and dmax(2) parameters suitable 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 4.56 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 4.13 in more detail.
• A new method for calculating the energy loss of charged particles with explicitly generating δ-rays wasdeveloped, 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 toconsider the relativistic eﬀect.
• [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 wherethe 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 aﬀected calculations in whichelectrons or positrons were scored with [t-cross] using EGS5.
From version 2.90, following functions were implemented. (2017/02/09)• A new function to analyze the motion of electrons and positrons in the electro-magnetic fields was implemented. 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 canreproduce sources having a complex spatial distribution. See Section 4.3.14 in more detail.
3 G.R. Lynch and O.I. Dahl, Nucl. Instrum. Methods Phys. Res, B 58, 6-10 (1991).

1 RECENT IMPROVEMENTS AND DEVELOPMENT MEMBERS

6• A new tally named [t-volume] was developed in order to automatically calculate the volume of each cell.
See Sections 6.17 in more detail.
• A new parameter timeout was introduced in the [parameters] section. When CPU time exceeds thisvalue, 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 6.8, 6.13, 4.26 for more detail.
From version 2.89, following functions were implemented. (2017/01/11)• In the default setting, c became unusable as comment marks in [material] section in order to avoid anerror 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 definedconditions. This option can be applied to simulation, for example soft errors in semiconductor devices.
• 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 biologicaldose 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 datafor incident energies, emission angles, and emission energies; and a function that is eﬀective in cases inwhich no diﬀerential 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 onlyin 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 appropriate setting for the [Weight Window] section. See Section 6.15 for more detail.
• A function to output the tally results in the xyz-mesh in the input format of ParaView, which is an opensource, 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 ofDr. Furutaka of the Research Group for Nuclear Sensing, JAEA, and V.I.C., Inc.
4 T.Sato et al.

Biological dose estimation for charged-particle therapy using an improved PHITS code coupled with a microdosimetrickinetic model, Radiat. Res. 171, 107-117 (2009).

1.1 Recent Improvements

7• 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 theenergy 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 4.56 formore 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 definedwithout 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 4.16 for more detail. This improvement was performed with the support of the Center for
Computational Science & e-Systems, JAEA.
• 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 canbe 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.
From version 2.85, the following functions were implemented. (2016/05/16)• 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 the EGS5 mode was
fixed.
• A bug in the capture reaction of negative muons when 1 H is included in the material was fixed.
Some bugs in ver. 2.84 were fixed. (2016/03/16)
From version 2.83, the following functions were implemented. (2016/03/03)
5 A. Endo, Y. Yamaguchi and K.F. Eckerman, Nuclear decay data for dosimetry calculation - Revised data of ICRP Publication 38, JAERI
1347 (2005).
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).

1 RECENT IMPROVEMENTS AND DEVELOPMENT MEMBERS

8• 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 eﬀect under the EGS5 mode was fixed. Because of this bug, previous
versions of PHITS scored some energies for [t-deposit] using part=photon instead of the correct valueof 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.
From version 2.82, the following functions were implemented. (2015/12/16)• A point estimator tally [t-point] to calculate the particle fluence at a specific point or ring (see section 6.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 thatinduce transmutation of target nuclei.
• A new option fiss was added in the [counter] section to output information on secondary particles generated through fission reactions, particularly in each generation of sequential fission.
• 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 4.3.2 for more detail. The PHITS development team is grateful to Dr. Liem Peng Hongof 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: seesection 4.3.13 for more detail.
• A new function was implemented in [source] section to generate particles with arbitrary time information.
See section 4.3.20 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] tallyby introducing a θ-mesh in the case of mesh=r-z.
• Some bugs in the EGS5 algorithm were fixed.
• A new function to consider the polarization of photons was implemented in the calculation of nuclear florescence resonance (NRF).
• Restart calculation using the [t-dpa] tally became feasible.
• 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 theuser-defined tally [usrtally] were added to the utility folder.
From version 2.81, the following functions were implemented. (2015/10/15)
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

9• 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 ofDr. 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 insuﬃcient memory when more than a few hundred materials are defined. In
addition, the maximum number of elements per material is still limited to 20.
• Bugs in [t-track] and [t-deposit] occurring under EGS5 were fixed.
• 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.
• A bug in [t-heat] with mesh=r-z was fixed.
From version 2.80, the following functions were implemented. (2015/09/02)• The function to read tetrahedral geometry (a kind of polygonal geometry) was implemented (see section
4.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.
• 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 4.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 simulationin 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 withthe dump source (see Section 4.3.16).
• A new parameter pnimul was introduced to bias the photo-nuclear reaction cross section against the photoatomic interaction cross section.
• A bug in the calculation of the uncertainty of [t-yield] was fixed.
• Several improvements related to the EGS5 mode 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 entryof 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 insuﬃciently large range of electrons.
– The limitation on the number of materials used in PHITS, even when using EGS5, was eliminated.
From version 2.77, the following functions were implemented. (2015/05/19)• A bug in which an unnatural energy distribution is tallied was fixed by setting axis=eng when EGS5 is
used.

10

1 RECENT IMPROVEMENTS AND DEVELOPMENT MEMBERS• The muon-nuclear interaction model used to implement muon capture reactions was revised.
• The default setting of the nuclear reaction model when light ions are targets was fixed. When such a reaction
occurs, PHITS calculates it by assuming that the light ions are projectiles on the basis of inverse kinematics.
For example, in the default setting INCL is used even for heavy ion induced reactions when the deuteron isas the target nucleus.
From version 2.76, the following functions were implemented. (2015/03/23)• A muon-nuclear interaction model based on virtual photon production theory was implemented. Characteristic X-ray production from muonic atoms as well as associated muon capture reactions can be also modeledin this new version.
• Adjustment parameters for determining the magnitude of angular straggling for nspred=2 were introduced.
• 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)
From version 2.74, the following functions were implemented. (2015/01/30)• The version of DCHAIN-SP included in the PHITS package was changed from DCHAIN-SP2001 (dchain264.exe)
to DCHAIN-SP2014 (dchain274.exe). DCHAIN-SP2014 was improved relative to DCHAIN-SP2001 as follows:(1) The input format was changed.
(2) The number of energy groups of neutron activation cross section libraries was increased from 175 to
1968.
(3) A new function was implemented to output the [source] section of PHITS from the activities calculatedby DCHAIN-SP.
(4) In the input format of ANGEL, a new function was implemented to output the time dependence ofradioactivities in each region.
• 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, thisfunction became applicable to all tallies): see Sec. 5.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
shown below for more detail.
• 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 whensetting e-mode≥1 or |igamma|≥1.
• Some bugs related to JAM and JAMQMD, etc., were revised.
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)
9 L. Sihver et al., Nucl. Instr. & Meth. B 334, 34-39 (2014).

1.1 Recent Improvements

11

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 andnn 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 theoriginal 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 whennegs=1. (From ver. 2.80, there is no such limitation.) See Sec. 4.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 photonuclear reaction mechanism in JAM.
• Muon-induced nuclear reactions of up to 1 TeV can be treated by considering the generation of virtualphotons from muons. This model can be activated by setting imuint=1 in the [parameters] section.
• The event generator mode ver.2 was improved to precisely determine the charged particle spectra on thebasis 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 eﬀects into account, and an algorithm for stabilizing the initial statesof 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 generatinga two-dimensional view of the geometry; when double-defined or undefined regions are detected, they are
painted onto the two-dimensional view. See Sec. 9 for details.
• An extension of the event generator mode (ver.2) was implemented, resulting in an improvement of theaccuracy of event-by-event analysis for reactions induced by neutrons below 20 MeV. See Sec. 4.2.22 fordetails.
• 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 filespecified by file=***, while dump data are output in another file named *** dmp.
10 H. Hirayama et al., SLAC-R-730 (2005) and KEK Report 2005-8 (2005).

1 RECENT IMPROVEMENTS AND DEVELOPMENT MEMBERS

12• The total memory usage of PHITS (mdas) given in the param.inc file was increased to 120,000,000 (equivalent 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 toneutron 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 inconverting 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 thefollowing 130 nuclides:
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)
From ver. 2.60, the following functions were implemented. (2013/08/22)• The algorithm for the de-excitation of nuclei after the evaporation process was improved by implementing
the ENSDF-Based Isomeric Transition and isomEr production Model (EBITEM). Prompt gamma spectra
including discrete peaks can now be precisely estimated, and isomer production rates can also be properly
estimated.
• Quasi-deuteron disintegration, which is the dominant photo-nuclear mechanism from 25 to 140 MeV, wasimplemented in JQMD. Thus, PHITS2.60 can treat photo-nuclear reactions up to 140 MeV. (From ver. 2.70,
this model is available up to 1 TeV.) The evaporation process after the giant resonances of 6 Li, 12 C, 14 N, and16
O was improved by considering the isospins of excited nuclei, allowing alpha emission to be suppressedand neutron and proton emission to be enhanced via these giant resonances.
• Particle transport simulation in combined electro-magnetic fields became available: see section 4.11 fordetails.

1.1 Recent Improvements

13• In the [source] section, several new energy mesh functions for directly defining diﬀerential energy spectra(in /MeV) and discrete energy spectra were implemented.
• Several algorithms were optimized to reduce the computational time, especially for the xyz mesh tally withistdev=2. Furthermore, use of memory for tally and ANGEL was improved. These improvements were
performed by Mr. Daichi Obinata of Fujitsu Systems East Limited, and were supported by the Center for
Computational Science & e-Systems, Japan Atomic Energy Agency (JAEA).
• Minor revision and bug fix.
– The number of cells acceptable in [t-dchain] was increased.
– The references of PHITS and INCL were changed.
– 7-digit cell IDs became acceptable.
– The maximum dmax for electrons and positrons was increased from 1 to 10 GeV.
– Restart calculation became available even when PHITS does not stop properly.
– Lattice cells became acceptable in [t-dchain].
– Termination of PHITS as a result of strange errors in JAM is now averted.
– A new multiplier function k=-120 was added to weight the density.
– Several minor bug were fixed in SMM involving the user defined tally, range calculation, transform,
lost electron particles, random number generation for MPI, and δ-ray production.
– Nuclear data for some nuclei were revised by the following the revision of JENDL-4.0.
– A bug in reading the proton data library was fixed.
From ver. 2.52, the following functions were implemented. (2012/12/27)• The electron, positron, and photon transport algorithms were revised. In the new version, the eﬀective
stopping powers of electrons and positions vary with their cut-oﬀ energies. Energy is conserved in events,
such as the photo-electric eﬀect, induced by photon-atomic interactions.
• A new tally [t-dchain] was implemented to generate DCHAIN-SP input files to calculate the time dependence of activation during and after irradiation: please see Sec. 6.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 suﬃcient: please see Sec. 4.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. 11.2). For this purpose, the source code of PHITS was drastically revised; as aresult, old Fortran compilers such as f77 and g77 can no longer be used for compiling PHITS. See Sec. 10
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 resonancesamong 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 highlyexcited residual nuclei. SMM improves accuracy in calculating the production cross sections of light andmedium-heavy fragments in heavy ion collisions.

1 RECENT IMPROVEMENTS AND DEVELOPMENT MEMBERS

14• Intra-Nuclear Cascade of Liège (INCL) was implemented as the default model for simulating nuclear reactions 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 Liè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, wasimplemented. 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 thework 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. 6.18 for details.
• The neutron kerma factors for several nuclei, such as 35 Cl, were revised. The photo- and electro-atomic datalibraries 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 trajectoriesof 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.

1.2 Development members
Koji Niita,
Research Organization for Information Science & Technology (RIST).
Tatsuhiko Sato, Yosuke Iwamoto, Shintaro Hashimoto, Tatsuhiko Ogawa, Takuya Furuta, Shinichiro Abe,
Takeshi Kai, Pi-En Tsai, and Norihiro Matsuda,
Japan Atomic Energy Agency (JAEA).
Hiroshi Iwase,High Energy Accelerator Research Organization (KEK).
Nobuhiro Shigyo,
Kyushu University.
Lembit Sihver,
Vienna University of Technology, Austria.
The following members also contributed to the development of PHITS.
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).

1.3 Reference of PHITS

15

Satoshi Chiba,
Tokyo Institute of Technology (TITech).
Takashi Nakamura,Tohoku University.
Davide Mancusi,
Chalmers University, Sweden.

1.3 Reference of PHITS
Please refer the following document in context of using any version of PHITS.
• 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).
This is an open access article can be downloaded from https://www.tandfonline.com/doi/full/10.1080/
00223131.2017.1419890
Other articles that describe the features of PHITS are:• 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).
• L. Sihver, D. Mancusi, T. Sato, K. Niita, H. Iwase, Y. Iwamoto, N. Matsuda, H. Nakashima, Y. Sakamoto,
Recent developments and benchmarking of the PHITS code, Adv. Space Res. 40, 1320-1331 (2007).
• L. Sihver, T. Sato, K. Gustafsson, D. Mancusi, H. Iwase, K. Niita, H. Nakashima, Y. Sakamoto, Y. Iwamoto
and N. Matsuda, An update about recent developments of the PHITS code, Adv. Space Res. 45, 892-899(2010).
• 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).
• T. Sato, K. Niita, N. Matsuda, S. Hashimoto, Y. Iwamoto, S. Noda, T. Ogawa, H. Iwase, H. Nakashima, T.
Fukahori, K. Okumura, T. Kai, S. Chiba, T. Furuta and L. Sihver, Particle and Heavy Ion Transport Code
System PHITS, Version 2.52, J. Nucl. Sci. Technol. 50:9, 913-923 (2013).

2 INSTALLATION AND EXECUTION OF PHITS

16

2

Installation and execution of PHITS

PHITS is a fortran-based code; it can be executed on Windows (7 or later), Mac (OS X v10.6 or later), Linux,
and Unix operating systems. The installers are prepared for each environment. The execution environment can beeasily setup through the use of installer. Note that an administrator account is required to use PHITS on Windows
and Mac operating systems.
The recommended system requirements for PHITS are 2 GB of RAM and 6 GB (with at least 4 GB required)of available space on the hard disk.
The installation and execution methods for Windows, Mac, and Linux OS are respectively described in Sections
2.1, 2.2, 2.3. In addition, Section 2.4 describes how to resume PHITS calculations, and how to terminate the PHITS
code during calculations.

2.1 Installation and execution on Windows OS
2.1.1 Installation on Windows OS(1) If a previous version of PHITS has been installed, rename the existing folder to “phits-old” or somethingsimilar.
(2) Double click “setup-eng.vbs.”(3) Specify the installation folder (“c:\” is recommended).
(4) Enter the password.
(5) Installation is finished.
(6) To check whether PHITS has been installed properly, right click “\phits\lecture\basic\lec01\lec01.inp” andselect “send to” → “PHITS.”(7) Check whether “xz track all.eps” is created or not.
(Note #1) The names of the installation files and folders and must contain no space characters; otherwise installation and execution will fail.
(Note #2) If you enter an incorrect password, please delete the “phits” folder first, and then run the installer again.
The installer “setup-eng.vbs” performs the following processes:(1) It extracts “phits.zip” into the specified installation folder.
(2) It adds “\phits\bin\” in the environment variable “PATH.”(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\’.

2.1.2 Execution on Windows OS
The PHITS code can be executed either via File Explorer (previously known as Windows Explorer) using“sendto → PHITS” command, or via Command Prompt.

2.1 Installation and execution on Windows OS

17

Execute using “send to → PHITS”
Right click the PHITS input file in a File Explorer, select “send to → PHITS” . As the shortcut for “phits.bat” inthe “\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 numberof CPU cores to be used) before the first section in the PHITS input file. If N = 0, all cores in the computer areused. 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. 11.1.1 in more detail.
Execute via Command Prompt
PHITS can be executed by command lines in Command Prompt (also known as cmd.exe or cmd), the commandline interpreter on Windows operating systems as shown in Figure 2.1.

Figure 2.1: Example of how to execute PHITS via Command Prompt

To execute PHITS, use the “cd” command to go to the directory of where the input is, and then type thefollowing 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 bypressing the ↑ key in the terminal, it is convenient to use the same input file name when you want to repeatedly
execute PHITS.

2.1.3 Recommended software
There is no software that needs to be pre-installed before using PHITS. Nevertheless, it is recommended to
install a text editor that can display line numbers, as the line number is specified when an error occurs in the
PHITS input file. Furthermore, installation of Ghostscript and GSview (ver. 5 is preferable), which are written in
the EPS format, is necessary to display image files created by PHITS.
Free text editors for Windows:• Crimson Editor (http://www.crimsoneditor.com/).
• Notepad++ (https://notepad-plus-plus.org/).
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 INSTALLATION AND EXECUTION OF PHITS

18

2.2 Installation and Execution on Mac OS
2.2.1 Installation on Mac OS(1) Double-click “phits installer” included in the “/mac/” folder of the PHITS package.
(2) Select “Automatic” for “select installation mode” (See Fig. 2.2). “Manual” should be selected only whenthe “Automatic” mode fails. In that case, please refer to the “README-eng.pdf” file in the “/mac/” folder.

Figure 2.2: Selection of installation mode.

(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).

Figure 2.3: Screenshot of what folder is recommended for PHITS installation.

2.2 Installation and Execution on Mac OS

19(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 thehard disk, and PHITS cannot be executed. In that case, please go back to the procedure (1) and typethe 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 automaticallyrenamed 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.

2.2.2 Execution on Mac OS
PHITS can be executed by dragging and dropping or through the use of Terminal.
Execute by drag and drop
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.

Figure 2.4: Execution by drag and drop.

The shared-memory parallel computing using OpenMP can be executed by adding $OMP=N (N is the numberof 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-SP, 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-SP format, so dragging an ANGEL or DCHAIN-SP input to the
PHITS icon would also work.
Execute via Terminal
After installing PHITS by using “PHITS Installer,”PHITS can be executed via terminal commands. To launchterminal, select the following items:
Finder → Applications → Utilities → Terminal
To execute PHITS, use the “cd” command to go to the directory of where the input is, and then type thefollowing commands in the terminal:
phits.sh your_input.inp

2 INSTALLATION AND EXECUTION OF PHITS

20

Figure 2.5: How to launch Terminal: Finder → Applications → Utilities → Terminal.

where “your input.inp” is your input file name (e.g., “lec01.inp”). As command histories can be retrieved bypressing 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-SP 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-SP, type the following command in the terminal:
dchain.sh dchain.out
where “dchain.out” is the name of the DCHAIN-SP input file (the file name is designated in the [t-dchain]
section of the PHITS input).

If the PHITS installation fails
In such case, PHITS can still be executed via Terminal after some proper settings, even though it is not installed.
Before executing PHITS via the Terminal for the first time, it is necessary to set PATH to the folder with the PHITS
execution file. To do this, type the following commands in the Terminal:
echo export PATH=/PATH-TO-PHITS/phits/bin:${PATH} >> ˜/.bash_profile
source ˜/.bash_profile
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:
find $HOME -name phitsXXX_mac.exe
where XXX is the version of PHITS. (e.g., 309. XXX is in the name of the PHITS package such as “PHITSXXX”).
Note that there is no need to set PATH repeatly after executing PHITS the first time. PHITSver=252 at the 8th

2.3 Installation and Execution on Linux OS

21line of the file “phits.sh” in the directory “/phits/bin/” should be changed to the version of PHITS that you would
like to use. Hereafter, PHITS can be executed via terminal as shown the previous section of Execute via Terminal.
Figure 2.6 shows an example of the initial setting for PHITS used in Terminal without installation, followed by a
PHITS execution of a test input “lec01.inp.”

Figure 2.6: Example of PHITS execution via Terminal with the initial setting.

To execute DCHAIN-SP, it is necessary to set PATH to the folder with the DCHAIN-SP execution file. The
method for setting the PATH for DCHAIN-SP 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/).

2.3 Installation and Execution on Linux OS
2.3.1 Installation on Linux OS
Copy “phits.zip” from the PHITS installation package to a directory where you would like to install. Copy
also the installer for Linux “PHITS-Installer lin.sh” from the “linux” folder in the PHITS installation package
to the same folder. Open a terminal and move to the installing folder. Then type the following command to add
executable property to the installer:
chmod +x PHITS-Installer_lin.sh
Then execute the installer by the following command:./PHITS-Installer_lin.sh
Installation will proceed in unzipping the ZIP file, modifying the installation PATH in files, and setting theexecution PATH. Input of passward will be required during the unzip. PATH setting will be done in “.profile” withthe assumption of the use of Bash. If you are using other shells, please change the setting accordingly. Installation
is successfully finished if you do not see any error message.
Type the following command to activate the PATH setting:source ˜/.profile
This command is not necessary anymore from the next login, since “.profile” will be automatically read whenlogging in.

2 INSTALLATION AND EXECUTION OF PHITS

22

2.3.2 Execution on Linux OS
In Linux environment, PHITS is executed via terminal. Open a terminal and move to the directory whichcontains the input file by the “cd” command. Then PHITS can be executed in the following fashion.
phits.sh your_input.inp
Here “your input.inp” is the PHITS input file name (e.g., lec01.inp). As command histories can be retrievedby 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 numberof 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 moredetail.
The execution of ANGEL and DCHAN-SP can be done in a similar fashion. ANGEL can be executed byangel.sh angel.inp
where “angel.inp” is the input file name (tally output of PHITS. e.g., “track xz.out”).
To execute DCHAIN-SP, type the following command in the terminal:
dchain.sh dchain.out
where “dchain.out” is the name of the DCHAIN-SP 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).
Execute by specifying an executable file without using a shell
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. 3.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. 11.1.3 formore detail.

2.4 Restart and terminate PHITS calculations

23

2.4 Restart and terminate PHITS calculations
2.4.1 Restart PHITS calculations
If tally results of PHITS calculations are not statistically significant enough, PHITS is able to read the previous
tally results and resume the calculations (restart calculation mode). In the [parameters] section, restart calculation mode can be activated by setting istdev < 0, and the statistics of the restart calculation will be counted
together with the previous tally results. It is allowed to add new tally sections for the input file with the restartcalculation, even if there is no past tally result. Please refer to Table 4.2 for the setting of istdev.
The procedure of restart calculation is described as follows:(1) Check whether or not the file specified by resfile in each tally section exists. The default file name of theresfile 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, total weight resc2, total history number resc3, history number per batch maxcas, the next random seedrijklst, 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 ischecked. If they are consistent, the restart calculation is performed using these values. If an inconsistency isfound, the calculation is stopped.
(6) The initial random seed is changed to the value of rijklst obtained from the first resfiles. If rijklst
diﬀers 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 thesame 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.

2.4.2 Terminate the PHITS code
Once PHITS is executed, it creates a “batch.out” 11 file following every batch that contains elapse information.
In parallel calculation, batch.out also contains each processor element (PE) status. The occurrence of a PE abort
can be determined by examining batch.out.
The first line of batch.out is written as follows:
10 <--- number of remaining batches
Here, the value on the left is the number of remaining batches at the moment. The remaining batches can be reducedby 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.”

24

2 INSTALLATION AND EXECUTION OF PHITS

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. 5.7.17). In parallel computing mode, the results
are updated every batch × ( PE −1 ). Using these functions enables terminating PHITS calculations at any timewith 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 thisfunction 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, forexample, in cases of unsuccessful termination of PHITS, it is possible to reproduce the calculation of the specified
batch using the value of rijk.

25

3

Input FilePHITS input consists of a number of sections that are listed in Tables 3.1 and 3.2. Each section begins witha [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.

3.1 Sections
Table 3.1 and 3.2 shows the sections used in PHITS.
Table 3.1: Sections (1)name[title][parameters][source][material][surface][cell][transform][temperature][mat time change][magnetic field][electro magnetic field][delta ray][track structure][super mirror][elastic option][data max]
[frag data][importance][weight window][ww bias][forced collisions][volume][multiplier][mat name color][reg name][counter][timer]description
Title
Various types of parameters
Source definition
Material definition
Surface definition
Cell definition
Definition of the coordinate transform
Cell temperature definition
Definition of time-dependent materials
Magnetic field definition
Electro-magnetic field definition
Definition of δ-ray production
Definition for using the track-structure simulation mode.
Definition of super mirror for low-energy neutrons
Definition of elastic scattering options for low-energy neutrons
Definition of maximum energies (dmax) of each nucleus for using data libraries
Definition of user defined cross sections
Definition of region’s importances
Definition of region’s weight windows
Definition of values to bias in [weight window]
Forced collision definition
Region volume definition
Multiplier definition
Material name and color definition for graphical plot
Region name definition for graphical plot
Counter definition
Timer and clock definition

3 INPUT FILE

26

Table 3.2: Sections (2)name[t-track][t-cross][t-point][t-deposit][t-deposit2][t-heat][t-yield][t-product][t-dpa][t-let][t-sed][t-time][t-interact] (former name [t-star])[t-dchain][t-wwg][t-wwbg][t-volume][t-userdefined][t-gshow][t-rshow][t-3dshow][end]

description
Particle fluence in a given region.
Particle fluence/current across a given surface.
Particle fluence at a given point.
Deposit energy in a given region.
Deposit energies in two given regions.
Heat generation in a given region. (Not recommended12 )Residual nuclei yields in a given region.
Reaction products in a given region.
Displacement Per Atom (DPA) in a given region.
LET distribution in a given region.
Microdosimetric quantity distribution in a given region.
Time information of particle in a given region.
Number of interactions occurred in a given region.
Residual nuclide yields (for the use of DCHAIN-SP).
Output parameters for [weight window].
Output parameters for [ww bias].
Automatic calculation of the volume for a given region.
Any quantities defined by users.
2D geometry visualization.
2D geometry visualization with physical quantities.
3D geometry visualization.
End of input file.

Note that PHITS does not read any input information written below the [end] section.

3.2 Reading control
Uppercase, lowercase, blank(⊔)
Discrimination between lowercase and uppercase characters is not performed in PHITS input except in filenames. Blanks at the beginning and the end of a line are ignored except for the declaration of the [SectionName] as described above.
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 thismethod, but ‘\’ is not necessary in the [surface] and [cell] sections, in which lines are automaticallyconnected 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 eﬀective startingfrom 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.

3.3 Inserting files

27

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.
Section reading skip
Adding off after a section name (e.g., [Section Name] off) disables all the definitions in that given
section (i.e., the section is being skipped). Note that infl: or set: written in the skipped section is alsoskipped.
Skipping lines within a section
To skip from any place in a section, put qp: at the line head. Lines from qp: to the end of the section areskipped.
Skip allq: can be used as a terminator of an input file; this works the same way as using [end].

3.3 Inserting files
Files can be placed in any location using: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 n2of 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
Here, “phits.inp” is the input file name.

3.4 User-defined variables
User-defined variables can be set as follows:set:

c1[ 52.3 ] c2[ 2 * pi ] c3[ c1 * 1.e-8 ]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), anothervariable 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’, thedefinition 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.

3 INPUT FILE

28

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.

3.5 Using mathematical expressions
Mathematical expressions can be used in an input file following Fortran style guidelines. Available functions
are shown in Table 3.3.
Table 3.3: Intrinsic Functions.

FLOAT
MOD
COS

INT
NINT
COSH

ABS
SIGN
SIN

Intrinsic
EXP
SQRT
SINH

Function
LOG
ACOS
TAN

LOG10
ASIN
TANH

MAX
ATAN

MIN
ATAN2

As an example of the use of standard mathematical expressions:parameter= c1 * 3.5 * sin( 55 * pi / 180 )In the above example, because a single numerical value is expected after parameter=, blanks can be used in theexpression. However, in some sections multiple numerical values cannot be accommodated; in such cases, an
expression can be closed using ‘{ }’, for example, { c1 * 2 / pi }.

3.6 Particle identification

29

3.6 Particle identification
The particle species that can be handled by PHITS are listed in Table 3.4. These particle species can be specified
by their respective symbols or kf-codes. Particle species that are not assigned a symbol in Table 3.4 (itype=11) are
specified only by their kf-codes. Table 3.5 lists the particles’ decay-channels and their life-times.
Simulation of nuclei can be handled in PHITS with the use of physical models, such as JQMD. The isotope
notation is in the format of the mass number followed by the chemical symbol of the element, e.g., 208Pb, 56Fe,
etc.. When the mass number of an element is not specified (e.g., Pb and Fe), it refers to all naturally occurringisotopes of the respective element, and thus cannot be assigned as projectiles. Another way of describing nuclei isusing the kf-code: kf= Z ∗ 1000000 + A.

Table 3.4: List of transport particles.
ityp
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20

symbolprotonneutron
pion+
pion0
pion−
muon+
muon−
kaon+
kaon0
kaon−
other
electronpositronphotonadeuterontriton3he
alphanucleusallkf-code
2212
2112
211
111
−211
−13
13
321
311
−321
below
11
−11
22
1000002
100000320000032000004
Z*1000000+A−

particle nameprotonneutron
π+
π0
π−
µ+
µ−
K+
K0
K−
other particlee−e+γ
deuterontriton3Heαnucleusall particles

a In the previous version of PHITS, photon was coded as gamma;in the new version, this is changed to photon.

ityp
11
11
11
11
11
11
11
11
11
11
11
11
11
11

symbol
−
−
−
−
−
−
−
−
−
−
−
−
−
−

kf-code+ − 12+ − 14
−2212
−2112
−311
+ − 221331+ − 3122+ − 3222+ − 3212+ − 3112+ − 3322+ − 3312+ − 3334

particle name
νe νe
νµ νµ
p
n
K0
ηη
η′
0 0
Λ Λ
Σ+ Σ+
Σ0 Σ0
Σ− Σ−
Ξ0 Ξ0
Ξ− Ξ−
Ω− Ω−

3 INPUT FILE

30

Table 3.5: Decay channels and life times.

n
π0
π+
π−
µ+
µ−
K0
K+
K−
η

η′

Λ0
Σ+
Σ0
Σ−
Ξ0
Ξ−
Ω−

→
→
→
→
→
→
→
→
→
→
→
→
→
→
→
→
→
→
→
→
→
→
→
→
→
→
→
→
→
→
→
→

p
γ
µ+
µ−
e+
e−
π+
π0
γ
µ+
π+
µ−
π+
γ
π0
π+
π+
π+
π0
π+
γ
p
n
p
n
Λ0
n
Λ0
Λ0
Λ0
Ξ0
Ξ−

+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+

e−
γ
νµ
νµ
νe
νe
π−
π0
γ
νµ
π−
νµ
π−
γ
π0
π−
π−
π−
π0
π−
γ
π−
π0
π0
π+
γ
π−
π0
π−
K−
π−
π0

+

νe

+
+

νµ
νµ

+
+
+
+
+
+

π0
π0
γ
η
η
γ

branching ratio
100%
100%
100%
100%
100%
100%
68.61%
31.39%
other63.51%
other63.51%
other
38.9%
31.9%
23.7%
other
44.1%
20.5%
30.1%
other
64.1%
other
51.57%
other
100%
100%
100%
100%
67.8%
23.6%
other

life time (sec)
8.867e+202.6029e−82.6029e−82.19703e−6
2.19703e−6
8.922e−11

1.2371e−8
1.2371e−8002.631e−10
7.99e−1101.479e−10
2.90e−10
1.639e−10
8.22e−11

3.7 Array sizes

31

3.7 Array sizes
The array sizes described in the “param.inc” file may need to be checked and modified. The most importantvariable is mdas, which specifies the total size of arrays for geometry, tally output, nuclear data, and bank. To lookup the current usage of the array, run an input echo (corresponding to file(6)=“phits.out”).
The bank size can be specified in the [parameters] section. When the bank runs out, an extra array of mdas
is automatically used. The default param.inc is shown below.
File 1: param.inc
1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:
28:
29:
30:
31:
32:
33:

***************************************************************************’param.inc’***************************************************************************
parameter ( mdas
= 80000000 )parameter ( kvlmax =3000 )
parameter ( kvmmax = 1000000 )parameter ( itlmax =200 )parameter ( inevt =70 )parameter ( isrc=
200 )parameter ( latmax = 20000000 )parameter ( nbchmax=
10000 )
common /mdasa/ das( mdas )common /mdasb/ mmmax*----------------------------------------------------------------------*
*
*
*
mdas
: total memory * 8 = byte**
mmmax : maximum number of total array****kvlmax : maximum number of regions, cell and material**
kvmmax : maximum number of id for regions, cel and material****
itlmax : number of maximum tally entry**
inevt : number of collision type for summary**
isrc: number of multi-source**
latmax : maximum number of lattice in a cell + 1**
nbchmax: maximum number of batch assigned to parallel MPI node ****----------------------------------------------------------------------*

4 SECTIONS FORMAT

32

4

Sections format

4.1 [ Title ] section
In the [title] section, the titles of calculations can be defined. Any number of title lines is allowed. Blanklines are skipped in this section.

[ Title ]This is a test calculation of PHITS.
Any number of title lines is allowed.
..........

4.2 [ Parameters ] section

33

4.2 [ Parameters ] section
The various parameters of PHITS can be defined in [Parameters] using the following format:[ Parameters ]para1 = number | file.namepara2 = number | file.name..........

The order of parameters can be changed. As each parameter has a default value, undefined parameters use thedefault values.
Parameters and default values are listed in the tables shown below. (D= ) indicates the default value.

4.2.1 Calculation mode
Table 4.1: Parameters (1)Parameter
icntl

Value
(D = 0)
= 0
= 1
= 3
= 5
= 6
= 7
= 8
= 9
= 10
= 11
= 12
= 13
= 14
= 15

Explanation
Basic control option.
Normal PHITS calculation.
Nuclear reaction calculation, (under development).
Output only input echo for checking memory usage, libraries, and file links.
Calculation assuming all regions are void (no reaction, no ionization) for geometry
check, and volume and area calculations.
Source check. Source positions can be tallied by [t-product].
Execute [t-gshow] for graphical output.
Geometry output of xyz mesh tally with gshow option for graphical output.
Execute [t-rshow] for graphical output.
Geometry output of reg mesh tally with rshow option for graphical output.
Execute [t-3dshow] for graphical output.
Re-calculate using dumpall file. Dumpall file is specified by file(15).
Use of function to sum up tally results (Sumtally function).
Use of automatic calculation of region volume.
Execute [t-wwbg] to obtain [ww bias] parameters.

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
diﬀerent physics quantanties with the same simulation setup, especially when such a simulation setup is computational time consuming. However, it should be noted that calculation with dumpall=1 may create a huge dumpall
file. Please refer to 4.2.21 for more details.
By setting icntl=13, two (or more) tally results can be summed: see Sec. 5.8 for further detail.
By setting icntl=14 with [t-volume], automatic calculations to obtain volumes of specified cells can be
performed. See Sec. 6.17 in more detail.
By setting icntl=15 with [t-wwbg], automatic calculations to obtain parameters of [ww bias]. See Sec.
6.16 for further detail.

4 SECTIONS FORMAT

34

4.2.2 Number of history and Bank

Table 4.2: Parameters (2)Parameter
irskipValue(D = 0)irskip > 0
irskip < 0

rseedmaxcasmaxbchmaxbnktimeout
istdev(D = 0.0)
rseed < 0
rseed = 0
rseed > 0
(D = 10)(D = 10)(D = 10000)(D = -1.0)(D = 0)
= -2
= -1
= 0
= 1
= 2

ireschk(D = 0)= 0= 1

Explanation
Random number control.
Skip the first irskip number of histories and the random number seeds fordebugging. (The total number of history is reduced by irskip.)
Begin calculation with the No. irskip+1 random number seeds for executing
parallel computing manually. (The total number of history is unchanged.)
Initial random number option.
Get an initial random number from starting time.
6647299061401 (default).
Use rseed as initial seed of random number.
Number of histories per batch. The upper limit is 2147483647.
Number of batches. The upper limit is 2147483647.
Number of particle temporary saved in a memory.
Cut-oﬀ CPU time for PHITS calculation (in units of second).
Control parameter for statistical uncertainty calculation type and restart mode.
Restart calculation mode is activated; if there is no past tally result, a new calculation is started with istdev=2.
Restart calculation mode is activated; if there is no past tally result, a new calculation is started with istdev=1.
istdev is automatically set to 1 for shared-memory parallel computing, and 2
for the other cases.
A new calculation is begun. Statistical uncertainties are estimated from the standard deviation of each batch result.
A new calculation is begun. Statistical uncertainties are estimated from the standard deviation of each history result. This option cannot be selected in sharedmemory parallel mode.
Control parameter for tally consistency check.
Check consistency between new and old tally settings.
No check. This option is useful when setting a very complex tally whose settings
are not fully written in the tally output file.

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 timereaches timeout in the middle of a batch, PHITS will finish the calculation of all histories in that batch, and thenterminates 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.

4.2 [ Parameters ] section

35

In both modes, standard deviation σ is calculated as
v
u
u
u
N
u
u
u∑
t
(xi wi /w̄)2 − N X̄ 2
σ=i=1

N(N − 1)

(1)where N is the total batch number (istdev=1) or the total history number (istdev=2),
xi is the tally results,
wi is the source weight of each sample,
X̄ is the mean value of the tally results, andw̄ is the source weight of N samples.
The ratio of σ to X̄ is written as relative error in the tally output file. In shared-memory parallel computing
mode, only the batch standard deviation mode can be selected as it is impossible to calculate tallied quantities
history-by-history using shared-memory parallel computing. The standard deviations calculated by the batch standard deviation mode vary by combination of maxcas and maxbch, even for the same total history number. In
principle, a larger maxbch provides more reliable statistical uncertainties in batch standard deviation mode but
may require a longer computational time. Setting the value of maxbch greater than 10 is recommended to obtain reliable results. By contrast, in history standard deviation mode, the standard deviation depends only on the
total history number and is independent of the combination of maxcas and maxbch. Thus, it is recommended
to select the history standard deviation mode (istdev=2) when memory-shared parallel computing is not in use.
Note, however, that computational time occasionally becomes extremely long in history standard deviation mode,
especially in cases in which there are tallies using many memories, e.g., xyz mesh tally with its very fine structure.
In tallies for calculating the standard deviation of deposition energies by individual history, such as [t-deposit]
with output=deposit and [t-deposit2], the standard errors√instead of the standard deviations are output as relative errors. The relative standard errors can be estimated as 1/ K where K is the number of histories contributing
to the tally result. This calculation procedure is independent of the istdev parameter.
Relative errors are generally output in the r.err column, which is the rightmost column of tally results. In
the case of 2D-plots, such as tallies with axis=xy or rz, errors are output into another file, ‘* err’ where ‘*’indicates the file name specified in the tally. For example, when file=tally.out, the name of the error file is“tally err.out.” This error file has the same format of the conventional tally output file; hence, a graph for the error
in the 2D-plot can be obtained by ANGEL through a conversion process.
Note that as what PHITS calculates is the standard deviation or the standard error, it means the true value has
a 68% of chance falling within the ±1σ confidence interval. Furthermore, PHITS does not estimate systematic
uncertainties contributed by the nuclear reaction models.
When istdev < 0, the restart calculation mode is activated; however, if there is no past tally result, a new
calculation is started with istdev=|istdev|; in other words, the batch and history standard deviation modes are
selected for istdev = -1 and -2, respectively. When restarting a calculation, the standard deviation mode is
automatically determined from the past PHITS calculation. The tally parameters in the restart calculation must be
consistent with the original tally parameters (i.e., parameters that already exist in the previous tally results mustremain unchanged); however, new tally sections can be added in the restart calculation.

4 SECTIONS FORMAT

36

4.2.3 Cut-oﬀ energy and switching energy
Table 4.3: Parameters (3)Parameteremin(1)emin(2)emin(i)Value(D = 1.0)(D = 1.0)(D = 1.0)

emin(11)emin(i)(D = 2.0)(D = 1.e+9)

emin(i)(D = 1.0)

esmin
esmax

(D = 0.001)(D = 300000)

cmin(i)(D = emin(i))

dmax(i)i= 15 – 19
(D = emin(i))

etsminetsmax(D = 1e-6)(D = 1e-2)

Explanation
Proton cut-oﬀ energy [MeV].
Neutron cut-oﬀ energy [MeV].
(i=3–10) Cut-oﬀ energy for pions, muons, and kaons [MeV]. (i=particle id;
see Table 3.4)
Cut-oﬀ energy for particle species with itype = 11 in Table 3.4 (MeV).
Cut-oﬀ energy for electrons (i=12), positrons (i=13), and photons (i=14)[MeV].
Cut-oﬀ energy for deuterons (i=15), tritons (i=16), 3 He (i=17), 4 He
(i=18), and nuclei (i=19)[MeV/u].
Lower energy limit for range calculation of charged particles [MeV/u].
Upper energy limit for range calculation of charged particles [MeV/u].
Note that these parameters are not applicable for electrons and positrons.
Nuclear reaction cut-oﬀ energy for i-th particle [MeV]. Any nuclear reactions
at energies below cmin(i) are not treated.
For these nuclei, energy unit is [MeV/u].
Upper energy limit of library use for i-th particle [MeV]. Note that the user
has to prepare the data library except for dmax(i=2,12,13,14), which areincluded in the PHITS package.
Lower energy limit of particles simulated by track structure mode [MeV].
Upper energy limit of particles simulated by track structure mode [MeV].

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, thenthe given values are included in the range. For example, a proton right at the emin(1) energy is not cut-oﬀ as the
cut-oﬀ range is ⩾ 0 and < emin.
When the kinetic energy of a transport particle is less than emin, the energy cut-oﬀ is performed and then its
transport calculation is stopped. In this case, the residual kinetic energy is deposited locally at that place, and theparticle decays in accordance with decay modes shown in Table 3.5 except for neutrons. If the particle species ispositron, annihilation occurs instead of decay.
PHITS uses libraries in the energy region emin < energy < dmax. If emin > dmax is set, no libraries areused. The upper energy limits for the use of data libraries are 20 MeV and 100 GeV, respectively for neutron andphoton. When EGS5 is not used, the upper energy limits for electrons and positrons are 10 GeV. The default settingof 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 4.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-oﬀ 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 computationaltime 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 applicabilityof JQMD is restricted in the low energy region and the range of nuclei is very low in the normal material, it is notnecessary 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4.2 [ Parameters ] section

37

Table 4.4: Parameters (4)Parameter
ejamnuValue(D=20.)

ejampi(D=20.)

eisobar(D=0.0)eqmdnu(D=20.)

eqmdminejamqmd
inclg(D=10.0)(D=3000.0)
(D=1)
=0
=1
=2
(D=1.0)(D=3000.0)
(D=0)
=0
=1
(D=1.0)(D=3500.0)
(D=0)
=0
=1
(D=0)
=0
=1

einclmineinclmaxincelfeielfmineielfmax
irqmd

kerma

Explanation
Switching energy of nucleon-nucleus reaction calculation from Bertini (orJQMD) to JAM model [MeV].
Switching energy of pion-nucleus reaction calculation from Bertini to JAM model[MeV].
Maximum energy [MeV] of isobar calculation when isobar is defined(isobar=1).
Switching energy of nucleon-nucleus reaction calculation from Bertini to JQMD
model [MeV/u].
Minimum energy of JQMD calculation [MeV/u].
Switching energy from JQMD to JAMQMD [MeV/u].
Control parameter for use of INCL.
INCL is not used.
Use of INCL in a proton, neutron, pion, d, t,3 He, or 4 He induced reaction.
Use of INCL in a proton, neutron, or pion induced reaction.
Minimum energy of INCL calculation [MeV/u].
Maximum energy of INCL calculation [MeV/u].
Control parameter for use of INC-ELF.
INC-ELF is not used.
Use of INC-ELF in a proton or neutron induced reaction.
Minimum energy of INC-ELF calculation [MeV].
Maximum energy of INC-ELF calculation [MeV].
Control parameter for use of JQMD or JQMD-2.0.
Use of JQMD in nuclear reactions.
Use of JQMD-2.0 in nuclear reactions.
Option for kerma mode.
This option is not used.
When neutron or proton nuclear data library of is used, PHITS produces nocharged particles except for protons.

jamqmd. It is possible to calculate even nucleon-induced collisions in JAMQMD by changing eqmdnu, ejamnu,
and ejamqmd.
INCL (Intra-Nuclear Cascade of Liège) is a nuclear reaction model for nucleon (proton and neutron), pion, andlight-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 nucleoninduced reactions. Before using results obtained by INC-ELF in a publication, please refer a document16 in thefootnotes.
JQMD and JQMD-2.0 are nuclear reaction models; in particular, they can be used to describe heavy-ion induced 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 shouldnote 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).

4 SECTIONS FORMAT

38(1MeV)(=emin)(3.0GeV)emin(i)dmax(i)einclmax

NucleonLibrary

INCL (inclg=1)

JAM(1MeV)(3.0GeV)emin(i)einclmax

Pion

JAM

INCL (inclg=1)(10MeV/u)(3.0GeV/u)

eqmdminejamqmd

Nucleus(d, t, 3He, α)Kaon, Hyperon

JQMD
INCL (inclg=1)

JAMQMD
JAM

Figure 4.1: Map of Nuclear Reaction Models.

Table 4.5: Parameters (5)Parameter
negs

Value
(D=-1)
=-1

= 0
= 1

nucdata

(D=1)
= 0
= 1

Explanation
Option for electron, positron, and photon transport.
Transport only photons based on the PHITS original algorithm. By selecting this option, emin(14) and dmax(14) are automatically set to 0.001 and 1000.0, respectively.
If these parameters are directly specified in the input file, the specified parameters overwrite the setting.
Ignore electron, positron, and photon transport.
Transport electrons, positrons, and photons based on the EGS5 algorithm. By setting this option, emin(12,13) and emin(14) are automatically set to 0.1 and 0.001,
respectively, while dmax(12-14) are set to 1000.0. If these parameters are directly
specified in the input file, the specified parameters overwrite the setting. file(1) orfile(20) must be specified in this option.
Option for automatic setting of emin(2) and dmax(2) for the usage of nuclear datalibrary.
No adjustment (nuclear data are not used).
Change the parameters suitable for JENDL-4.0, i.e.
emin(2)=1.0e-11 anddmax(2)=20.0. If these parameters are directly specified in the input file, the specified parameters overwrite the setting. file(1) or file(7) must be specified in thisoption.

4.2 [ Parameters ] section

39

4.2.4 Cut-oﬀ time, cut-oﬀ weight, and weight window
Table 4.6: Parameters (6)Parametertmax(i)
wc1(i)
wc2(i)
swtm(i)wupn

Value(D=1.e+9)i = 1-20(D=-0.5)(D=wc1/2)(D=1.0)(D=5)

wsurvnmxspln(0.6*wupn)(D=5)

mwhere(D=0)

iwwbias

(D=0)
= 0
= 1

Explanation
Cut-oﬀ time for i-th particle [nsec].
(i; particle id, see Table 3.4).
Minimum weight for i-th particle.
Cut-oﬀ weight for i-th particle.
Minimum source weight for i-th particle.
Maximum value of weight window is given by the product of wupn × (minimum
value in [Weight Window] section). Here, wupn ≥ 2 should be set.
Survival weight value. Here, 1 < wsurvn < wupn should be set.
Maximum number of split and maximum multiple number of survival. Here,mxspln > 1 should be set.
Where the weight window takes place.
-1: at nuclear reaction, 0: both, 1: at region crossing.
Option for [ww bias].
Values defined in [ww bias] are not used.
Values defined in [ww bias] are used. The [weight window] parameters multiplied by inverse of the defined biases in [ww bias] are used.

The cut-oﬀ time for each particle should be specified as tmax(i) (in units of [nsec]). After arrival at the cut-oﬀ
time, the particle is killed; although this is not eﬀective in the context of high energy particle transport, it is usefulfor low energy particle transport calculation.
A particle’s weight is aﬀected by the importance, forced collisions, implicit captures, and weight windowfunctions. When the weight is lower than the user-defined weight cut oﬀ, a Russian roulette method is applied todetermine whether or not the particle is killed. This function is not available for particles defined in the weightwindow.
Under the Russian roulette method, when the weight wgt is lower than the product, wc2× R, of wc2 and theratio R of the importances at the source and current points (i.e., when wgt < wc2 × R), the particle survives with aprobability wgt /(wc1×R), which is a function of the particle’s own weight, WGT. If the particle survives, its weightis 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.

4 SECTIONS FORMAT

40

4.2.5 Model options (1)Table 4.7: Parameters (7)Parameter
ielas

ielms
inmed

nevap

ismm

Value
(D=2)
= 0
= 1
= 2
(D=100)
(D=1)
= 0
= 1
= 2
(D=3)
= 0
= 1
= 2
= 3
(D=0)
= 0
= 1

ngem

(D=1)
= 0
= 1
= 2

igamma

(D=2)
= 0
= 1
= 2
= 3
=-1,-2,-3

isobar

(D=0)
= 0
= 1
(D=0)
= 0
= 1
(D=3)
= 1
= 2
= 3

ipreeqlevel

Explanation
Elastic scattering option.
Exclude elastic scattering.
Include neutron elastic scattering.
Include neutron and proton elastic scattering.
Number of angle groups for elastic scattering.
Nucleon-nucleon cross section options for Bertini model.
Free (nmtclb25.dat).
Cugnon old (nmtclb95.dat); the in-medium eﬀect for nucleon-nucleon cross sections is included.
Cugnon new (nmtclb30.dat).
Options for evaporation model.
Without evaporation model.
Using DRES model.
Using SDM model.
Using GEM model.
Control parameter of Statistical Multi-fragmentation Model (SMM).
SMM is not used.
SMM is used. When a JQMD calculation is performed, switching time from JQMD
to GEM changes from the default value of 100 fm/c to 75 fm/c.
Options for the version of the GEM model.
Use the default version (currently ver.1).
Use Ver.1.
Use Ver.2 (including nucleon-gamma emission competition、KTUY data18 forshell correction).
γ decay options for residual nuclei19 .
Without γ decay.
With γ decay.
With γ decay based on the EBITEM model.
With γ decay and isomer production based on the EBITEM model.
Same as 1, 2, 3, except that Doppler eﬀect owing to the motion of excited nuclei isdisregarded. Do not use unless necessary, as it distorts physical reaction processes.
Options for the isobar model.
Without isobar.
With isobar.
Options for the pre-equilibrium model when nevap=1.
Without the pre-equilibrium model.
With the pre-equilibrium model.
Level density options when nevap=1.
8/A.
With Baba’s parameters.
With Ignatyuk’s parameters.

With the Statistical Multi-fragmentation Model (SMM), PHITS improves the accuracy of calculating the production cross sections of light and medium-heavy fragments for collisions of heavy ions such as Pb or Hg or forincident energies over 100 MeV/u. It should be noted that the computational time becomes long when using thismodel: see the references 20 21 for details.
Setting igamma=3 enables obtaining of information on isomer production using [t-yield] with axis=chartor dchain: see reference 22 in the footnotes for details.
18 H. Koura, T. Tachibana, M. Uno, and M. Yamada, RIKEN Accel. Prog. Rep. 36 (2003) 9: H. Koura, TOURS Symposium on Nuclear
Physics V, AIP Proceedings 704 (2004) 60.
19 Prior to ver. 2.73, file(14)=trxcrd.dat is required for igamma=1-3.
20 T. Ogawa, T. Sato, S. Hashimoto, and K. Niita, Nuclear Instruments and Methods in Physics Research A 723 (2013) 36-46.
21 J.P. Bondorf, A.S. Botvina, A.S. Iljinov, I.N. Mishustin, and K. Sneppen, Physics Reports 257 (1995) 133-221.
22 T. Ogawa, S. Hashimoto, T. Sato, and K. Niita, Nuclear Instruments and Methods in Physics Research B 325 (2014) 35-42.

4.2 [ Parameters ] section

41

4.2.6 Model options (2)Table 4.8: Parameters (8)Parameter
ieleh

Value
(D=0)
= 0
= 1

ipnint

(D=0)
= 0
= 1
= 2

pnimulimucap(D=1.0)
(D=1)
= 0
= 1
= 2

imuintemumin

(D=1)
= 0
= 1
(D=1)
= 0
= 1
(D=1)
= 0
= 1
(D=200.0)

emumaxnpidk(D=1.0e+6)(D=0)

imubrmimuppd= 0= 1

Explanation
Options for electron and positron transport.
No slowing down and no reaction in the energy region above dmax(12).
When the energy, e, is above dmax(12), the weight value, wgt, is changed to
wgt= e/dmax(12), and then the transport calculation is performed with the energy of dmax(12).
Options for photo-nuclear reaction. 23
This reaction mechanism is not considered.
This reaction mechanism is considered, except for nuclear resonance fluorescence.
This reaction mechanism is considered, including nuclear resonance fluorescence.
(See notes below this table for polarization of incident photons.)
Multiplying factor to increase sampling probability of photo-nuclear reaction.
Options for capture reactions of negative-muons considering characteristic X-ray
production from muonic atoms and nuclear absorption.
This reaction mechanism is not considered.
This reaction mechanism is considered with default parameters used for calculation of characteristic X-ray production.
This reaction mechanism is considered with user defined parameters written infile(28) used for calculation of characteristic X-ray production.
Options for muon-induced nuclear reaction based on the virtual photon theory.
This reaction mechanism is not considered.
This reaction mechanism is considered.
Options for muon-induced bremsstrahlung.
This reaction mechanism is not considered.
This reaction mechanism is considered.
Options for muon-induced electron-positron pair production.
This reaction mechanism is not considered.
This reaction mechanism is considered.
Minimum energy of muon-induced nuclear reaction [MeV]. The change of
emumin also changes the reaction cross sections over the entire energy range.
Maximum energy of muon-induced nuclear reaction [MeV].
Treatment of negative-charged particles listed in Table 3.5 when they are below
cut-oﬀ energies.
Force to be absorbed by nucleus.
Sets to decay.

For the nuclear resonance fluorescence considered in ipnint=2, polarization of incident photons can be specified using sx,sy,sz in the [source] section. The angular distribution of the scattered photons is determinedwith regard to the polarization.
If a particle with a decay channel (See Table 3.5) has an energy lower than the cut-oﬀ, 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).

23 Until ver. 2.30, this parameter was named ipngdr.

4 SECTIONS FORMAT

42

4.2.7 Model options (3)Table 4.9: Parameters (9)Parameter
imagnf

Value
(D=0)
= 0
= 1

ielctf

(D=0)
= 0
= 1

andit

(D=0)
= 0
= 1
= 2
(D=0)

icxsni

icrhi

icrdm

icxspi

iidfs

idwba

= 0
= 1
= 2
(D=2)
= 0
= 1
= 2
(D=0)
= 0
= 1
(D=1)
= 0
= 1
(D=0)
= 0
= 1
(D=0)
= 0
= 1

Explanation
Options for magnetic field.
Without Magnetic field.
With Magnetic field. Note that, to correctly describe the trajectory as a curve by tally,
adjust the step length for the field by deltm.
Options for electromagnetic field.
Without electromagnetic field.
With electromagnetic field. Note that, to correctly describe the trajectory as a curve bytally, adjust the step length for the field by deltm.
∆ angular distribution for Bertini.
50 % isotropic, 50 % forward.
All isotropic.
All forward.
Options for inelastic scattering, elastic scattering, and total cross sections for nucleonnucleus collisions.
Pearlstein-Niita’s formula.
KUROTAMA model.
Sato’s formula.
Options for total cross section of nucleus-nucleus collisions.
Shen formula.
NASA formula.
KUROTAMA model.
Options for total reaction cross sections for deuteron-induced reactions.
Same as icrhi.
MWO formula.
Options for total reaction cross sections for pion-induced reactions.
Geometrical formula.
Hashimoto’s formula.
Options for neutron-induced fission.
Use the nuclear data library.
Neutron multiplicity ν and neutron energy spectrum are taken from the literature.
Options for the Distorted Wave Born Approximation (DWBA) spectra.
Without discrete DWBA spectra.
With discrete DWBA spectra.

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 basedon 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 pioninduced 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 takenfrom reference 26 are used instead of the nuclear library data for the following 18 nuclei: U-238, Pu-238, Pu240, 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).

4.2 [ Parameters ] section

43

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
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
9Be(d, n)10 B and 9 Be(d, p)10 Be reactions at 5–25 MeV
12,13C(d, n)13,14 and 12,13 C(d, p)13,14 C reactions at 10–50 MeV
9See the reference 27 for more details.

27 S. Hashimoto et al., Nucl. Instr. & Meth. B 333, 27-41 (2014).

4 SECTIONS FORMAT

44

4.2.8 Model options (4) - stopping power
Table 4.10: Parameters (10)Parameter
ndedx

Value
(D=3)28

mdbatima
dbcutoff
ih2o

= 0
= 1
= 2
= 3
(D=500)(D=0.0)(D=-1)

ifixchg

< 0
> 0
(D=0)
= 0
= 1

irlet

(D=1)
= 0
= 1

nspred

(D=0)
= 0
= 1
= 2

ascat1
ascat2
nedisp= 10(D=13.6)(D=0.038)
(D=0)
= 0
= 1
= 10

Explanation
Options for dE/dx of charged particle and nucleus. Note that this option is notapplicable for electrons and positrons.
SPAR29 for nucleus, NMTC for the rest of particle species.
ATIMA30 for nucleus and proton, NMTC for the rest of particle species.
SPAR for nucleus, proton, pion, and muon, NMTC for the rest of particle species.
ATIMA for all charged particles.
Maximum database size of ATIMA.
Cut-oﬀ energy of ATIMA database [MeV/u].
Setting for the ionization potential of water in ATIMA. This setting is applicablefor H2 O only.
Use of the default 75 eV.
User-defined value [eV].
Option for the charge number of source particles in ATIMA calculations.
Eﬀective charge. The charge number is equal to the Z number at high energies, andgradually decreases with decreasing energies.
Fixed charge. The charge number is equal to the Z number as a constant, unless it
is specified by the izst parameter in the [source] section.
Options for the method of considering δ-ray energy in calculating dE/dx for
charged particle and nuclei.
Conventional method (subtract the energy of sampled δ-ray from the unrestricted
stopping power).
Restricted LET. The cut-oﬀ energy of the delta rays is set in the [Delta Ray]section.
Options for Coulomb diﬀusion (angle straggling)31 . Note that this option is notapplicable for electrons and positrons.
Without Coulomb diﬀusion.
With Coulomb diﬀusion by the original NMTC model.
(Recommended) With Coulomb diﬀusion by the Lynch’s formula based on the
Moliere theory32 .
With Coulomb diﬀusion by ATIMA.
S 2 parameter in the Lynch’s formula for nspred=2.
ϵ parameter in the Lynch’s formula for nspred=2.
Energy straggling option for charged particle and nuclei. Note that this option is
not applicable for electrons and positrons.
Without energy straggling.
(Recommended) With Landau Vavilov energy straggling33 .
With energy straggling for ATIMA.

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/X0
2 pβ [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

32 σ = S

4.2 [ Parameters ] section

45

From version 2.85, the algorithm for calculating stopping power with ATIMA in PHITS was improved andspeeded up. In the old algorithm, calculation of range and stopping power was always performed every time whena new charged particle was produced or a transporting particle entered a new material. The new algorithm createsa 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 highcomputational-cost routine ATIMA. As such, PHITS simulation using ATIMA is compatible with SPAR in termsof 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).

4 SECTIONS FORMAT

46

4.2.9 Model options (5)Table 4.11: Parameters (11)Parameter
gravx
gravy
gravz
usrmgtusrelste-mode36

em-emode
ikermanikermap

ntrnore

Value
(D=0)
(D=0)
(D=0)
(D=1)
= 1
= 2
(D=1)
= 1
= 2
(D=0)
= 0
= 1
= 2
(D=20)
(D=0)
= 0
= 1
= 2
(D=0)
= 0
= 1
= 2
(D=0)
= 0
= 1

Explanation
x-component of gravity direction.
y-component of gravity direction.
z-component of gravity direction.
Options for user subroutine of time dependent magnetic field.
usrmgt1.f, which includes Wobbler magnet, is used.
usrmgt2.f, which includes Pulse magnet, is used.
Options for [elastic option].
usrelst1.f, for Bragg scattering, is used.
usrelst2.f, a sample program, is used.
Options for event generator mode for neutrons below 20 MeV.
Simple sampling mode (non event generator mode).
Event generator mode Ver.1 (simple sampling + evaporation model).
Event generator mode Ver.2 (Ver.1 + accurate charged particle yields + accurate neutron energy distribution).
Maximum energy for e-mode [MeV].
Control parameters for the use of kerma approximation for neutrons in [t-deposit].
Automatic selection. Kerma approximation is not used when event generator mode isactivated (e-mode ≥ 1).
Kerma approximation for neutrons is not used.
Kerma approximation for neutrons is used.
Control parameters for the use of kerma approximation for photons in [t-deposit].
Automatic selection. Kerma approximation is not used when EGS5 mode is activated(negs = 1), or when emin(12) and emin(13) are set below 10 MeV.
Kerma approximation for photons is not used.
Kerma approximation for photons is used.
Options for neutrino-induced reactions.
This reaction mechanism is not taken into account.
This reaction mechanism is taken into account.

gravx, gravy, gravz represent the directions of gravity; the gravitational force is eﬀective for neutrons atenergies below 1 eV. For example, if gravx=1, gravy=0, gravz=0, the direction of the gravitational force isnegative along the x-axis.
The event generator mode (e-mode=1,2) is essential for calculation of event-by-event quantities, such asdetector 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 thane-mode=1,2. Note that e-mode=0 does not consider the conservation of energy and momentum. See Sec. 4.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 extrapolated. Note that, the reaction channels above 150 MeV (e.g. charge-current reactions of µ-neutrinos) are notconsidered. Table 4.12 shows neutrino reaction systems considered in the current version of PHITS. In the case ofthat considered reaction channel, ∞ or values are shown as an energy upper-limit.

36 Until ver. 2.73, file(14)=trxcrd.dat is required for e-mode=1,2.

4.2 [ Parameters ] section

47

Table 4.12: List of neutrino reaction systems considered and energies above which cross sections are extrapolated.
×: unimplemented, -: reaction is not existing.
Charge current
e− 1 H 2 H
νe ∞
20
ν̄e
150 20
νµ ×
×
ν̄µ
×
×
ντ ×
×
ν̄τ
×
×

Neutral current
e− 1 H 2 H
νe ∞ ×20
ν̄e ∞ ×20
νµ ∞ ×20
ν̄µ ∞ ×20
ντ ∞ ×20ν̄τ ∞ ×20

4.2.10 Output options (1)Table 4.13: Parameters (12)Parameter
infout

Value
(D=7)

nrecover

= 0
= 1
= 2
= 3
= 4
= 5
= 6
= 7
= 8
(D=0)

Explanation
Options to specify output information in file(6). The notes followed by this table givethe meanings of the category codes.
I
I, II
I, III
I, IV
I, II, III
I, II, IV
I, III, IV
I, II, III, IV, VI
I, II, III, IV, V, VI
Number of warning messages output when the recovery of lost particles succeeds.

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 foreach material.
VI Information on PHITS developers.
The information is output in the following order:(1) LOGO (Category I). Version of PHITS, developers information (Category VI), job title, and starting time.
(2) Echo of input file (Category II).
(3) Information on memory usage and composition for geometry, material, tally, bank, etc. (Category III).

4 SECTIONS FORMAT

48(4) Information on batch (Category III)
Number of histories by batch and CPU time.
(5) Information on calculation process (ncol) (Category I).
Number of geometry boundary crossings, reactions, terminations by energy cut-oﬀ, etc.
(6) Information on variance reduction (Category V).
Particle weights changed by importance, weight window, and forced collision options.
(7) Number of scattered particles for each region (Category V).
(8) Number of scattered particles for each material (Category V).
(9) Number of transport, produced, stop, and leakage particles (Category IV).
(10) Number of source particles and their weights (Category I).
(11) Geometry error (Category I).
Number of lost particles and their types.
(12) Random seed (Category I).
Initial random seed and next initial random seed.
(13) CPU summary (Category I).
Total computation time and number of calls for each calculation process. The meanings of each term are
explained as follows:• total cpu time: total computation time.
• transport: time for particle transport.
• set data: time for setting input parameters.
• analysis: number of data processing events.
• nevap: number of evaporations.
• dexgam: number of de-excitations.
• nreac: number of atomic and nuclear reactions.
• dklos: number of particle decays.
• hydro: number of nucleon-nucleon scatterings.
• n-data: number of runs using neutron data library.
• h-data: number of runs using proton data library.
• p-data: number of runs using photon data library.
• e-data: number of runs using electron data library.
• p-egs5: number of photon interactions with EGS5.
• e-egs5: number of electron interactions with EGS5.
• photonucl: number of photo-nuclear reactions.
• muon: number of muon-induced nuclear reactions.
• elast: number of elastic scatterings.
• ncasc: number of runs using nuclear reaction models.
• bertini: number of runs using Bertini model.
• isobar: number of runs using isobar model.
• JAM: number of runs using JAM model.
• QMD: number of runs using JQMD or JQMD-2.0 models.
• JAMQMD: number of runs using JAMQMD model.
• INCL: number of runs using INCL model.
• INCELF: number of runs using INC-ELF model.

4.2 [ Parameters ] section

49

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.

4 SECTIONS FORMAT

50

4.2.11 Output options (2)Table 4.14: Parameters (13)Parameter
incut

igcut

ipcut

inparaigparaipparadumpall

idpara

Value
(D=0)
= 0
= 1
= 2
(D=0)
= 0
= 1
= 2
= 3
(D=0)
= 0
= 1
= 2
(D=0)
= 0
= 1
= 3
(D=0)
= 0
= 1
= 3
(D=0)
= 0
= 1
= 3
(D=0)
= 0
= 1
= -1
(D=3)
= 0
= 1
= 3

Explanation
Neutron output options below the cut-oﬀ energy.
No output.
Output in the ncut file specified as file(12).
Output in file(12) with time information.
γ-ray and electron output options below the cut-oﬀ energy.
No output.
Output γ-ray data in the gcut file specified as file(13).
Output γ-ray in file(13) with time information.
Output γ-ray, electron, and positron data in file(13).
Proton output options below the cut-oﬀ energy.
No output.
Output in the pcut file specified as file(10).
Output in file(10) with time information.
ncut file name options in the parallel calculation.
/wk/uname/file-name of file(12).
/wk/uname/file-name of file(12)+(PE number).
File-name of file(12)+(PE number).
gcut file name options in the parallel calculation.
/wk/uname/file-name of file(13).
/wk/uname/file-name of file(13)+(PE number).
File-name of file(13)+(PE number).
pcut file name options.
/wk/uname/file-name of file(10).
/wk/uname/file-name of file(10)+(PE number).
File-name of file(10)+(PE number).
dumpall option. Activate and use with icntl=12. See 4.2.21 for more details.
No dump.
Write down all information on file(15) as binary data.
Write down all information on file(15) as ASCII data.
dumpall file name option in the parallel calculation.
/wk/uname/file-name of file(15).
/wk/uname/file-name of file(15)+(PE number).
File-name of file(15)+(PE number).

In the setting of inpara, igpara, ippara, idpara, “/wk/” and “/uname/” are the default directory nameand a user-name read in from the environment variable LOGNAME, respectively. In parallel computing, files corresponding 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 thefilename. Each PE writes down its calculation result only on its corresponding file.

4.2 [ Parameters ] section

51

4.2.12 Output options (3)Table 4.15: Parameters (14)Parameter
itall

iMeVperu

itstep

imout

jmout

kmout

Value
(D=0)
= -1
= 0
= 1
= 2
(D=0)
=0
=1
(D=1)
= 0
= 1
(D=0)
= 0
= 1
= 2
(D=0)
= 0
= 1
= 2
(D=0)
= 0
= 1

Explanation
Options for tally output after every batch.
No output.
Output only numerical data files.
Output both numerical data and image (*.eps) files37 .
Output to diﬀerent files. (file name = specified file name + batch number))
Options for the unit of energy in tally output.
Output in MeV.
Output in MeV/u (MeV per nucleons) for nuclei. The unit automatically changes to
MeV for the rest of the particle species.
Options for the tallying timing when the tracking particle is in a field, which constantly
changes the particle’s momentum, such as a magnetic, electromagnetic, or gravity field.
Tally at reaction or surface cross (normal).
Tally at each step of the transport.
Options for the output format of the [material] section.
e.g., mat[12], 208Pb.33c.
e.g., mat[12], Pb-208.33c.
e.g., m12, 82208.33c (MCNP style).
Options for the output format of material density in [material].
No conversion.
Conversion into particle density.
Conversion into mass ratio (%).
Options of nuclear data information.
No display.
Writing in input echo.38

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 ofdeltm.

37 Note that vtk files are output with both itall=0,1.
38 From Ver. 2.86, the dmax of each nucleus is also output.

4 SECTIONS FORMAT

52

4.2.13 Output options (4)Table 4.16: Parameters (15)Parameter
matadd

Value
(D=1)

natural

= 0
= 1
(D=1)

= 0
= 1
= 2
iggcm

icput

ipara

nwsors

(D=0)
= 0
= 1
(D=0)
= 0
= 1
(D=0)
= 0
= 1
(D=0)

Explanation
Options when diﬀerent densities are defined for a given material number in the [cell]
section.
Use the same material number.
Use a new material number.
Options for using the naturally occurring isotopes for nuclear cross section data, and forwriting their ratios in the input echo, when a given element is defined without the mass
number in [material].
Use nuclear cross section data for natural elements, such as nat Fe and nat Pb, in the nuclear data library.39 Isotopes are not output in file(6).
Assign all the naturally occurring isotopes to the given element. Isotopes are not output
in file(6).
Assign all the naturally occurring isotopes to the given element. Isotopes are output infile(6).
Option of GG warnings.
No echo.
In input echo.
Options for recording and outputting CPU time for each calculation process.
Not recorded nor output.
Recorded and output.
Parameter display options.
Only described parameters.
All parameters.
Write down the information on nwsors source particles in file(6).

When two (or more) cells are defined with the same material number but diﬀering 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 [matname 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.

4.2 [ Parameters ] section

53

4.2.14 Voxel and tetrahedron geometry options
Table 4.17: Parameters (16)Parameter
ivoxelitetra

Value
(D=0)
= 0
= 1
= 2
(D=0)
= 0
= 1
(D=0)

ntetsurf

= 0
= 1
= 2
(D=100)ntetelem(D=200)itetauto(D=0)

itetvol= 0= 1

Explanation
Read and write voxel data in binary.
Not using file(18).
Read from voxel data in binary file(18).
Write down voxel data in binary on file(18).
Options to compute volume of tetrahedron geometry for LAT=3.
The volume will not be computed.
The volume will be automatically computed and used in tallies, etc.
Read and write tetrahedron geometry data in binary. Binary file must be reconstructed by setting itetra=2 when ntetsurf and/or ntetelem are changed.
Not using the data file.
Read from tetrahedron geometry data in binary “Tetra.bin” (fixed name).
Write down tetrahedron geometry data in binary “Tetra.bin” (fixed name).
Number of outer surfaces of tetrahedron geometry allowed for each sub-space of thecontainer box.
Number of elements of tetrahedron geometry allowed for each sub-space of the container box.
Options to automatically create cells corresponding to universes of tetrahedron geometry.
No cell is automatically created.
The cells will be automatically created. The text file (.txt) is required for the TetGen
format.

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 isread from file(18) created in the previous calculation with ivoxel=2, so the data output process is omitted andthe calculation time is shortened.
Using the option of itetvol=1, when the tetrahedron geometry is treated with LAT=3, the volume of theuniverses appearing in tetrahedron geometry can be automatically computed. However, the volume is computedby simply summing up the volumes of individual tetrahedrons, which might produce incorrect values in cases inwhich 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 calculation 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, theitetra 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 calculation 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 containing the tetrahedron geometry for PHITS calculations with (LAT=3), which reduce the computational time bylimiting the number of elements belonging to each sub-space. One algorithm finds a surface of the tetrahedrongeometry when a particle enters the geometry. The container box is sub-divided so that the number of outer surfaces at each sub-space is less than ntetsurf. The other algorithm finds an element of tetrahedron geometry whena 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 tetrahedrongeometry 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 thetetrahedron geometry is imported with the NASTRAN bulk data format. See 4.6.5 for more details.

4 SECTIONS FORMAT

54

4.2.15 About geometrical errors
Table 4.18: Parameters (17)Parameter
nlost
igerr
igchk

deltb

idelt

Value
(D=10)
(D=0)
(D=0)
= 0
= 1
(D=1.e-9)

deltm
deltc

(D=1)
= 0
= 1
(D=20.12345)(D=2.012345)

delt0(D=0.1)deltg(D=1.012345)

deltt(D=1.0)Explanation
Acceptable value against lost particle (per 1 PE).
Number of recoveries from region error.
Options for region check.
No region check.
Set the flight mesh to deltb after region-crossing, and check region.
Distance of flight mesh [cm] after region-crossing if igchk=1. (deltb
is also the distance from the region boundary to where theparticle is created by importance and forced collision.)
Options for minimum flight mesh.
Use values of deltm and deltc as flight mesh maxima.
Maximum flight mesh is deltm and deltc divided by the density in the region.
Maximum flight mesh [cm]. This parameter is linked with idelt.
Maximum flight mesh [cm] for charged particles if nedisp=1,10 (not applicable for electrons and positrons). This parameter is linked with idelt.
Minimum flight mesh [cm] if nspred=1,2,10. Note that, when describing ascattering process on thin films less than 1 cm, delt0 should be set to 1/10 of
its thickness.
Maximum flight mesh [cm] in a magnetic field for charged particles (excluding
electrons and positrons).
Maximum flight time [msec] in a time-dependent magnetic field.

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 shortdistance is defined as “flight mesh.”
The purpose of the use of flight mesh is to more accurately determine which region the particle belongs to, forprevention of misjudments due to insuﬃcient 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 anddeltc 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.

4.2 [ Parameters ] section

55

4.2.16 Input-output file name
Table 4.19: Parameters (18)Parameterfile(1)Value(D=c:/phits)

file(6)file(7)
file(11)file(12)file(13)
file(10)file(15)
file(18)
file(20)
file(21)file(22)
file(23)
file(24)
file(25)(D=phits.out)(D=file(1)/data/xsdir.jnd)(D=nuclcal.out)(D=fort.12)(D=fort.13)(D=fort.10)(D=dumpall.dat)(D=voxel.bin)(D=file(1)/XS/egs/)(D=file(1)/dchain-sp/data/)(D=batch.out)(D=pegs5)(D=file(1)/data)(D=file(1)/XS/tra)file(26)(D=file(1)/data/multiplier)file(27)(D=file(1)/XS/yield/)

file(28)(D=file(1)/data/aama.dat)

Explanation
PHITS installation folder name. If this parameter is set
properly, there is no need to specify the names of other input files, i.e. file(7, 20, 21, 24, 25, and 26), unless the folder structure of PHITS have not been changed.
If these parameters are directly specified in the input file,the specified parameters overwrite the setting.
Summary output file name.
Cross section directory file name.
Nuclear reaction output file name.
Cut-oﬀ neutron output file name.
Cut-oﬀ γ-ray output file name.
Cut-oﬀ proton output file name.
dump file name for dumpall=1 option.
File name when using ivoxel=1, 2.
Directory containing the library data for EGS5.
Directory containing the library data for DCHAIN-SP.
Name of the file to output information on current batch.
Output file name for PEGS5.
Directory containing RIsource.dat (DECDC database).
Directory containing cross section database used for trackstructure simulation.
Directory containing the pre-defined [multiplier] sections.
Directory containing the user-defined activation cross section data. The last “/” of the path is needed.
Input file name for the MUONIC ATOM CASCADE program to use the user-defined parameters.

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.

4 SECTIONS FORMAT

56

4.2.17 Others
Table 4.20: Parameters (19)Parameterinucr

idam(i)rdam(i)

icommat

Value
(D=1)
= 1
= 2
= 3
= 4
= 5
= 6
integer
real*8i = 1-100
(D=0)
= 0
= 1

Explanation
Nuclear reaction calculation options.
Double diﬀerential cross section calculation.
Total, elastic, non-elastic cross section calculation.
Non-elastic cross section calculation.
Angular distribution of elastic scattering.
pp, np, πp cross section output.
pp, np, πp cross section calculation.
User-defined integer variable.
User-defined real variable.
These values can be used in the PHITS code bycommon /userp/ idam(100), rdam(100)Option for comment marks in [material] section.
c cannot be used as comment marks.
c can be used as comment marks.

The nuclear reaction calculation mode with inucr is corresponding to icntl=1, which is currently underdevelopment.
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.’

4.2.18 Physical parameters for low energy neutrons
The following parameters are used for neutrons with energies less than 20 MeV.
Table 4.21: Parameters (20)
Parameter
emcnf

Value
(D=0.0)dnb(D=-1)
=-1
= 0
> 0
(D=1)
=0
=1
(D=0)
= 0
= 1

nonu

isaba

Explanation
Threshold energy for neutron capture [MeV]:
implicit capture is considered above this energy; analog capture is considered below
this energy.
Number of delayed neutron produced by fission.
Natural sampling.
No delayed neutrons.
Specify number of delayed neutrons.
Options for fission neutrons
Turn oﬀ fission: fission is treated as simple capture.
Normal fission producing neutrons.
Option for S (α, β).
No interpolation.
Perform interpolation of the data of S (α, β), which should be specified for calculations
with thin targets in which particle scattering rarely occurs.

4.2 [ Parameters ] section

57

4.2.19 Physical parameters for photon and electron transport based on
the PHITS original model
Table 4.22: Parameters (21)Parameter
emcpf
ides

nocoh

iphot

ibad

istrg

bnum

xnum

enum

numb

rnok

Value
(D=100)
(D=1)
= 0
= 1
(D=0)
= 0
= 1
(D=0)
= 0
= 1
(D=0)
= 0
= 1
(D=0)
= 0
= 1
(D=1)
= 0
> 0
(D=1)
= 0
> 0
(D=1)
= 0
> 0
(D=0)
= 0
> 0
(D=1)
= 0
> 0

Explanation
Maximum energy in the detailed photon model [MeV].
Electron creation options by photon.40
Create electron or bremsstrahlung photon.
Do not create electron.
Photon coherent scattering options.
With coherent scattering.
Without coherent scattering.
Photon creation options by electron.
Create photon.
Do not create photon.
Angular distribution option for bremsstrahlung.
Full bremsstrahlung tabular angular distribution.
Simple bremsstrahlung angular distribution approximation.
Energy straggling options for electrons.
Sampled straggling for electron energy loss.
Expected value straggling for electron energy loss.
Options for bremsstrahlung photon.
Do not create bremsstrahlung photon.
Number of analog bremsstrahlung photons.
Options for X-ray photon.
Not create X-ray photon.
Number of analog X-ray photons.
Options for secondary electron.
Do not create secondary electrons.
Number of analog secondary electrons.
Options for bremsstrahlung production process.
Nominal bremsstrahlung production.
Produce bremsstrahlung at each substep.
Options for knock-on electron.
Do not create knock-on electrons.
Number of knock-on electrons.

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.

4 SECTIONS FORMAT

58

4.2.20 Parameters for EGS5
Table 4.23: Parameters (22)Parameter
ipegs

imsegs

Value
(D=0)
= -1
= 0
= 1
= 2
(D=1)
= 0

= 1

iegsout

iegsrand

(D=0)
= 0
= 1
= 2
(D=-1)< 0= 0> 0

Explanation
Options for controlling PEGS5 (invalid when negs, 1).
Output PEGS5.inp: Yes, Execute PEGS5: Yes, Execute PHITS: No.
Output PEGS5.inp: Yes, Execute PEGS5: Yes, Execute PHITS: Yes.
Output PEGS5.inp: No, Execute PEGS5: Yes, Execute PHITS: Yes.
Output PEGS5.inp: No, Execute PEGS5: No, Execute PHITS: Yes.
Options for treating multiple scatterings in EGS5.
Original EGS5 method. With this option, the starting scattering strength is used only
when the electron is generated as a source particle. After several steps, the maximum
scattering strength is used.
Original PHITS-EGS5 method. Use starting scattering strength whenever an electron
enters a new material. This option enables transporting electrons in thin foils withoutchanging the chard parameter; the computational time becomes slightly longer.
Options for controlling EGS5 output files.
Delete all EGS5 output files when PHITS calculation is finished. Some files remain
when the user self-terminates the PHITS calculation.
Keep egs5.inp, pegs5.dat and pegs5.msfit and delete the others.
Keep all EGS5 output files. See EGS5 manual41 for details on each file.
Options for random number used in EGS5. Setting parameter to 0 or to a positive value
hides the MPI parallelization and the restart-calculation function.
Use random number generated by PHITS.
Use random number generated by EGS5 with the default initial random seed
(314159265).
Use random number generated by EGS5 with the initial random seed = iegsrand.

PEGS is the prepocessor for EGS. It contains a set of fortran subprograms, which negerate material data for theuse 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 photontransports 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 ofseveral EGS5 parameters diﬀer 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 andipnint=1 produce results that diﬀer from those calculated by the previous version of PHITS.

41 H. Hirayama et al., SLAC-R-730 (2005) and KEK Report 2005-8 (2005).

4.2 [ Parameters ] section

59

Table 4.24: Parameters (23)Parameter
iedgfllpolar

Value
(D=1)
= 0
= 1
(D=1)
= 0
= 1
(D=1)
= 0
= 1
(D=0)

iunrst

= 0
= 1
(D=0)

chard

= 1
= 2
= 3
= 4
= 5
= 6
= 7
(D=0.1)

iaugeriraylrepstfl

(D=0)
= 0
= 1

Explanation
Option for K and L-edge fluorescent photons.
Do not explicitly treat K and L-edge fluorescent photons.
Explicitly treat K and L-edge fluorescent photons.
Option for K and L-edge Auger electrons.
Do not explicitly treat K and L-edge Auger electrons.
Explicitly treat K and L-edge Auger electrons.
Option for coherent (Rayleigh) scattering.
Do not consider coherent scattering.
Consider coherent scattering.
Option for linearly polarized photon scattering (not available in the PHITS code at
this moment).
Do not consider linearly polarized photon scattering.
Consider linearly polarized photon scattering.
Option for outputting stopping powers by PEGS5. When this parameter is changed,
ipegs must be set to −1 to not to execute PHITS calculations, and to prevent obtaining
incorrect results.
Unrestricted collisional stopping power only.
Unrestricted collisional and radiative stopping power.
Unrestricted collisional and restricted radiative stopping power.
Restricted collisional and unrestricted radiative stopping power.
Unrestricted radiative stopping power only.
Restricted radiative stopping power only.
Restricted collisional stopping power only.
Array of ‘characteristic dimensions,’ or representative size (in units of cm) of eachmaterial. This parameter controls the electron step-size in each material. The
value must be decreased when simulating electron scattering in thin foils by setting
imsegs=0. When a negative value is set for this parameter, the actual chard values
used in EGS5 are adjusted to their absolute values divided by the material density ing/cm3 . This option is useful for simulating electrons in huge objects (of km order).
Option for using density correction factors contained in EPSTAR.
Do not use EPSTAR for density correction.
Use EPSTAR for density correction.
If this option is selected, a text file named “epstar.dat” must be created in
the same folder containing the PHITS input file.
The data contained in“\XS\density corrections” must be copied and pasted in the order of materials specified in the [material] section. This can be directly changed for each material byediting “pegs5.inp.”

4 SECTIONS FORMAT

60

Table 4.25: Parameters (24)
Parameter
incohr

Value
(D=1)
= 0
= 1

iprofr

(D=1)
= 0
= 1
(D=1)
= 0
= 1
(D=0)
= 0
= 1
(D=0)
(D=1)
= 0
= 1
(D=1)
= 0
= 1
(D=1)
= 0
= 1
(D=1)
= 0
= 1
(D=1)
= 0
= 1
= 2

impacrieisplneisplibrdstiprdstiphteriboundiaprimExplanation
Option for incoherent scattering function.
Do not use incoherent scattering function for Compton scattering.
Use incoherent scattering function for Compton scattering (ibound is automatically setto 1).
Option for Doppler broadening of Compton scattering energies.
Do not consider Doppler broadening.
Consider Doppler broadening (incohr and ibound are both automatically set to 1).
Option for electron-impact ionization (EII).
Do not consider EII.
Consider EII.
Option for split of X-rays generated by electron-impact ionization.
No splitting.
Splitting.
Number of electron-impact ionization X-rays for splitting when ieispl=1.
Option for determination of bremsstrahlung polar angle.
Angle given by m/E.
Sampling.
Option for determination of polar angles of pair electrons.
Angle given by m/k.
Sampling.
Option for determining angular distributions of photoelectrons.
Emission in the direction of incident photon.
Sampling.
Option for Compton cross section.
Use free Compton cross section.
Use bound total Compton cross section.
Option for correcting bremsstrahlung cross section.
Use Motz et al. empirical.
Normalize integrated cross section to ICRU-37 radiative stopping power.
No correction.

4.2 [ Parameters ] section

61

4.2.21 Dumpall option
With the setting of icntl=12, PHITS reads the detailed information of a completed transport calculation froma dumpall file created beforehand by using the dumpall option, and reproduces all of the transport result event by
event. As such, the input file except the tally sections must be identical as used in the previous calculation when
the dumpall option is activated. maxcas and maxbch cannot be changed either, because they are read from thedump file.
This can be a very useful function in order to calculate diﬀerent tallies which were not used in the previous
calculation. However, please be careful that the calculation with the dumpall option may create a huge dump file.
The dumped data written in ascii can be used on the computers, but the data written in binary cannot. The data
sequence and meaning are given in the following.
(1) NCOL
NCOL is an intrinsic variable in the program and denotes identification of processes.
NCOL
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15

:
:
:
:
:
:
:
:
:
:
:
:
:
:
:

start of calculation
end of calculation
end of a batchsourcedetection of geometry error
recovery of geometry error
termination by geometry error
termination by weight cut-oﬀ
termination by time cut-oﬀ
geometry boundary crossing
termination by energy cut-oﬀ
termination by escape or leakage(n,x) reaction(n,n’x) reaction
sequential transport only for tally

When NCOL=1, 2, 3, the output is finished. The followings are for NCOL≥4.
(2) NOCAS, NOBCH, RCASC, RSOUIN
These four data are written only for NCOL=4 and their meaning are,
NOCAS
NOBCH
RCASC
RSOUIN::::current history number in this batchcurrent batch number
real number of NOCAS+maxcas*(NOBCH-1)
sum of the weight of source particle(3) NO, MAT, ITYP, KTYP, JTYP, MTYP, RTYP, OLDWT
These mean
NO
MAT
ITYP
KTYP
JTYP
MTYP
RTYP
OLDWT

:
:
:
:
:
:
:
:

cascade id in this history
material id
particle typeparticle kf-code
charge number of the particle
baryon number of the particle
rest mass of the particle (MeV)
weight of the particle at (x,y,z)(a) QSThis data is written only for ITYP=12, 13, namely electron and positron. QS is dE/dx for electrons.

4 SECTIONS FORMAT

62

QS

:

dE/dx of electron at (x,y,z)(4) IBLZ1, IBLZ2, ILEV1, ILEV2
These mean
IBLZ1
IBLZ2
ILEV1
ILEV2

:
:
:
:

cell id at (x,y,z)cell id after crossing
level structure id of the cell at (x,y,z)level structure id of the cell after crossing(a) ILAT1
This is a variable of level structure of cell. The next data are written only for ILEV1>0 as
write(io) ( ( ILAT1(i,j), i=1,5 ), j=1,ILEV1 )(b) ILAT2This is a variable of level structure of cell. The next data are written only for ILEV2>0 as
write(io) ( ( ILAT2(i,j), i=1,5 ), j=1,ILEV2 )(5) COSTH, UANG(1), UANG(2), UANG(3), NSURF
These variables mean as follows. These had come to be output from ver. 2.30.
COSTH
UANG(1,2,3)
NSURF

:
:
:

cosine of an angle of incidence in a surface crossing
x,y,z component of a normal vector of its surface, respectively
internal number of the surface
Note that this is diﬀerent from the surface number defined in the [surface] section(6) NAME, NCNT(1), NCNT(2), NCNT(3)These mean
NAME
NCNT(1,2,3)::

collision number of the particle
values of counter 1, 2, and 3(7) WT, U, V, W
These mean
WTU, V, W::

weight of the particle at (xc,yc,zc)
unit vector of momentum of the particle(8) E, T, X, Y, Z
These meanE
T
X, Y, Z:::

energy of the particle at (x,y,z) (MeV)time of the particle at (x,y,z) (nsec)
position coordinate of the preceding event point (cm)(9) EC, TC, XC, YC, ZC
These meanEC
TC
XC, YC, ZC:::

energy of the particle at (xc,yc,zc) (MeV)time of the particle at (xc,yc,zc) (nsec)
position coordinate of the particle (cm)

4.2 [ Parameters ] section

63(10) SPX, SPY, SPZ
These mean
SPX, SPY, SPZ:

unit vector of spin direction of the particle(11) NZSTThis is the charge state of particles.
(12) NCLSTSThis 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
MATHZ
MATHN
JCOLL
KCOLL

:
:
:
:

Z number of the mother nucleus
N number of the mother nucleus
reaction type id1
reaction type id2

JCOLL and KCOLL indicate the following meaning.
JCOLL
0
1
2
3
4
5
6
7
8
9
10
11
13
14
KCOLL
0
1
2
3
4
5
6

:
:
:
:
:
:
:
:
:
:
:
:
:
:

nothing happen
Hydrogen collisions
Particle Decays
Elastic collisions
High Energy Nuclear collisions
Heavy Ion reactions
Neutron reactions by data
Photon reactions by data
Electron reactions by data
Proton reactions by data
Neutron event modedelta ray production
Photon reactions by EGS5
Electron reactions by EGS5
:
:
:
:
:
:
:

normalhigh energy fission
high energy absorption
low energy n elastic
low energy n non-elastic
low energy n fission
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 doThese mean

4 SECTIONS FORMAT64

ICLUSTS
0
1
2
3
4
5
6
7

kind of particle
nucleus
protonneutronpion
photonkaon
muon
others

:
:
:
:
:
:
:
:

JCLUSTS(i)
i=0
=1
=2
=3
=4
=5
=6
=7
QCLUSTS(i)
i=0
=1
=2
=3
=4
=5
=6
=7
=8
=9
= 10
= 11
= 12

:
:
:
:
:
:
:
:

angular momentum
proton number
neutron number
itypstatus of the particle 0: real, <0 : deadcharge number
baryon number
kf code
:
:
:
:
:
:
:
:
:
:
:
:
:

impact parameter
x-component of unit vector of momentum
y-component of unit vector of momentum
z-componentof unit vector of momentum√
2
etot = p + m2 (GeV)
rest mass (GeV)
excitation energy (MeV)
kinetic energy (MeV)
weighttime (nsec)
x coordinate (cm)y coordinate (cm)z coordinate (cm)

4.2 [ Parameters ] section

65

4.2.22 Event Generator ModeFor Event Generator mode 42 , dmax(2) should be defined appropriately using information from the nuclear
data library. In the special statistical decay model, detailed information on the level structure near the ground statefor particle and photon emission is used, which requires setting igamma=1-3. The special statistical decay model
has been developed based on GEM; to use it, the operator should specify nevap=3. In this mode, the eﬀect of thethermal motion of materials is not considered, namely, it is assumed that T always = 0 in this mode. The relatedparameters are automatically set by specifying e-mode=1 or 2 (unless explicitly specified, igamma=2 is selected).
For consistency reason, the combination igamma=1 and e-mode=1 is also supported.
Event generator mode Ver.2 is the improved version of the legacy version (i.e., event generator mode Ver.1).
In reactions emitting multiple neutrons, the previous event generator mode sampled the first ejectile neutron fromthe cross-section data and emission of the subsequent particles was simulated using the statistical decay model.
By contrast, ver.2 samples all ejectile neutrons from the cross-section data and the statistical decay model isused merely to simulate prompt gamma-ray production. For capture reactions, the previous event generator mode
assumed that the target nucleus absorbs incident neutrons, and particle emission was simulated by the statistical
decay model. In this updated version, ejectile particle species are fully determined by the statistical decay model.
While ver.2 selects the ejectile particle species depending on the reaction channel (i.e., in the (n, α) reaction,
emission of only one alpha particle and gamma-rays is allowed).
Under Event Generator mode, the following new observables, which cannot be detected otherwise, are obtained:(1) The deposition energy distribution by the low-energy neutrons below dmax(2) without the kerma approximation 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 calculatedwith 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 etal., 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.

4 SECTIONS FORMAT

66

4.3 [ Source ] section
The source information can be set in this section. The source type is specified by the number s-type=N as in
Table 4.26.
The energy of the source particle can be given by e0 for mono-energy or e-type for energy spectrum 44 .
Table 4.26: Source typesource types-type = 1, (4)s-type = 2, (5)s-type = 3, (6)s-type = 7, (8)s-type = 9, (10)s-type = 11s-type = 12
s-type = 13, (14)s-type = 15, (16)s-type = 17s-type = 18, (19)s-type = 20, (21)s-type = 22, (23)s-type = 24
s-type = 100

explanation
Cylinder (or circle, pencil).
Rectangular solid (or rectangle).
Gaussian (x, y, z independent).
Generic parabola (x, y, z independent).
Sphere or spherical shell.
Uniform distribution in a phase space vertical with beam direction.
Reading the data from decay-turtle output.
Gaussian (xyx plane).
Generic parabola (xy plane).
Reading dump file.
Cone.
Triangle prism.
xyz-mesh distribution.
Tetra-mesh source.
User definition source. Edit the usrsors.f and compile PHITS.

Numbers in the brackets in Table 4.26 were used until ver. 2.94. If both e0 and e-type are defined fromver. 2.95, the energy is decided according to the previous procedure of s-type. For example, e0 is used whens-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 ofthe mono-energy, or s-type=4 with e-type defined that of the energy spectrum.

4.3 [ Source ] section

4.3.1

67

<Source> : Multi-source

Using this multi-source function, plural sources specified by s-type can be defined. Each source begins
with <source>=number, which defines the relative weights of the multi-sources. totfact= defines the global
normalization. Note that <source> should not be written in the line following the line in which reg parameter iswritten.
Table 4.27: Multi-source
parameter<source> =totfact =iscorr =explanation
Defines a multi-source; the relative weight is defined by this number.
(D=1) Global normalization factor.
If this is given by a positive number, the source particle is generated according to this ratio;
if negative, the same particle is generated in each multi-source section with weights adjusted
according to the ratio.
(D=0) Multi-source correlation option.
0: Normal multi-source.
1: Correlated multi-source. In this case, sources from each multi-source group are generated
as an event. This option is useful for estimating detector response by nuclear reactions producing several secondary particles. Note that the locations of all sources generated in an eventare not the same, unlike the case of iscorr = 2,3.
2: Correlated multi-source. In this case, the locations of all sources generated in an event
are the same. This mode is useful for simulating a nuclear reaction occurring at an arbitrary
location.
3: Correlated multi-source. In this case, the locations of all sources generated in an event are
the same, and the direction of the second source is opposite to that of the first. This mode isuseful for simulating a particle decaying into two particles at an arbitrary location.
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 forproton and neutron sources, respectively, and totfact=3.

4 SECTIONS FORMAT

68

4.3.2 Common parameters
Common parameters for each source type are shown below. The order of the parameters in the source section isfree. If a parameter has a default value (D=***), it can be omitted. The energies of d, t, α, and nuclei are specified
by [MeV/nucleon].
Table 4.28: Common source parameters (1)parameter
proj =
sx =
sy =
sz =
reg =

ntmax =
trcl =
wgt =factor =izst =

explanation
Projectile: see Table3.4 for specification.
(D=0) x-component of spin.
(D=0) y-component of spin.
(D=0) z-component of spin.
(D=all) The source region can be restricted within overlaps between regions defined by eachs-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 section ontally region specification for more detail.
(D=1000) Maximum re-try number when reg is specified.
(D=none) Transform number, or definition of transform.
(D=1.0) Weight of source particle.
(D=1.0) Normalization factor of source particle. PHITS multiplies all results of tally by factor.
When using multi-source, totfact should be used instead of factor; when not using multisource, totfact * factor is an actual normalization factor.
(D=charge of particle specified with proj=) Charge state of source particle.
This value influences the particle motions only in the magnetic and electro-magnetic fields definedin [magnetic field] and [electro magnetic field] sections. In addition, ATIMA withthe fixed charge mode (ifixchg=1) calculates the stopping power based on this charge state.
The charge number defined with izst doesn’t change while the particle moves. Note that particles
produced from nuclear reactions are not aﬀected by the value of izst; the charge of the produced
particle is given as its atomic number.

The projectile direction is specified by three parameters: dir,phi, and dom. The relation between these is shown in Fig. 4.2, inzwhich the direction is noted as a thick arrow. dir is the directioncosθ=dir ψ=dom
cosine relative to the z axis. phi is the azimuthal angle from thex axis and is given in degrees; if not set by the user, the value ofthe azimuthal cosine is selected randomly. Using the parameter dom
θspreads the direction determined by dir and phi by the solid angle
2π(1 − cos ψ), where ψ = dom (in degrees). In the PHITS calculation,
the angle is selected randomly within the solid angle.
By setting dir=all, the direction of the source beam becomesisotropic. To use a specific angular distribution, a subsection in theydistribution based on numerical data or an analytic function starting x
from a-type is required.
φ=phi
In s-type=9, the definition of dir diﬀers. In s-type=11 and
12, dir can only bet set = −1 or 1.
Figure 4.2: Source direction and parameTo transform coordinates, the trcl parameter, which specifies
ters dir, phi, dom.
the transform number or the definition of the transformation itself,
can be used. The relation of wgt and factor is reciprocal.
If its spin is not defined or zero, a neutron enters a magnetic field without spin. In this case, the initial spinof the neutron is determined at the entrance of the magnetic field by the direction of the magnetic field and thepolarization 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.

4.3 [ Source ] section

69

Table 4.29: Common source parameters (2)parameter
ispfs = 0, 1, 2

explanation(D=0) Neutron sources from spontaneous fission.
If ispfs=1 or 2 is specified in the [source] section and the following 18 nuclei arechosen 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, U234, 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 thecase 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

45 J. M. Verbeke, C. Hagmnn, and D. Wright, “Simulation of Neutron and Gamma Ray Emission from Fission and Photofission”, UCRL-

AR-228518 (2014).

4 SECTIONS FORMAT

70

4.3.3 Cylinder distribution source
Parameters for the cylinder source are shown below. The order of parameters is free. If a parameter has adefault value (D=***), the parameter can be omitted.
Table 4.30: Parameters for cylinder sources-type = 1
x0 =
y0 =
z0 =
z1 =
r0 =
r1 =
dir =

phi =
dom =
e0 =
e-type =Cylinder or circle source.
(D=0.0) x coordinate of center position of cylinder source[cm].
(D=0.0) y coordinate of center position of cylinder source[cm].
(D=0.0) Minimum z of cylinder source[cm].
(D=0.0) Maximum z of cylinder source[cm], (when z1=z0, circle plane source).
(D=0.0) Radius of cylinder source, (when r0=0.0, a pencil source results)[cm].
(D=0.0) Inner radius for inner void of cylinder.
(D=1.0) Direction cosine of projectile against z axis.
If all is set, source is isotropic.
If data is set, an a-type subsection is necessary.
(D=none; random) Azimuthal angle[degree].
(D=0.0) Solid angle[degree].
= −1 ; cos2 bias distribution.
(For mono-energy) Projectile energy[MeV/u].
(For energy spectrum) Projectile energy[MeV/u].

4.3.4 Rectangular solid distribution source
Parameters for a rectangular solid source are shown below. The order of parameters is free. If a parameter has
a default value (D=***), the parameter can be omitted.
Table 4.31: Parameters for rectangular solid sources-type = 2
x0 =
x1 =
y0 =
y1 =
z0 =
z1 =
dir =

phi =
dom =
e0 =
e-type =Rectangular solid and rectangle source.
(D=0.0) Minimum x coordinate[cm].
(D=0.0) Maximum x coordinate[cm].
(D=0.0) Minimum y coordinate[cm].
(D=0.0) Maximum y coordinate[cm].
(D=0.0) Minimum z coordinate[cm].
(D=0.0) Maximum z coordinate[cm], when (z1=z0), rectangle source.
(D=1.0) Direction cosine of projectile against z axis.
If all is set, source is isotropic.
If data is set, an a-type subsection is necessary.
(D=none; random) Azimuthal angle[degree].
(D=0.0) Solid angle[degree].
= −1 ; cos2 bias distribution.
(For mono-energy) Projectile energy[MeV/u].
(For energy spectrum) Projectile energy[MeV/u].

4.3 [ Source ] section

71

4.3.5 Gaussian distribution source (x,y,z independent)
The Gauss distribution is consist of independent Gaussian in each x, y, z direction. Parameters for Gaussian
source are shown below. The order of parameters is free. If a parameter has a default value (D=***), the parametercan be omitted.
Table 4.32: Parameters for Gaussian sources-type = 3
x0 =
x1 =
y0 =
y1 =
z0 =
z1 =
dir =

phi =
dom =
e0 =
e-type =Gaussian source.
(D=0.0) x coordinate of Gaussian center[cm].
(D=0.0) FWHM in x direction[cm].
(D=0.0) y coordinate of Gaussian center[cm].
(D=0.0) FWHM in y direction[cm].
(D=0.0) z coordinate of Gaussian center[cm].
(D=0.0) FWHM in z direction[cm].
(D=1.0) Direction cosine of projectile against z axis.
If all is set, source is isotropic.
If data is set, an a-type subsection is necessary.
(D=none; random) Azimuthal angle[degree].
(D=0.0) Solid angle[degree].
= −1 ; cos2 bias distribution.
(For mono-energy) Projectile energy[MeV/u].
(For energy spectrum) Projectile energy[MeV/u].

4.3.6 Generic parabola distribution source (x,y,z independent)
The generic parabola distribution consists of independent parabola in each x, y, z direction. Parameters forgeneric parabola source are shown below. The order of parameters is free. If a parameter has a default value(D=***), the parameter can be omitted.
Table 4.33: Parameters for generic parabola distributions-type = 7
x0 =
x1 =
y0 =
y1 =
z0 =
z1 =
rn =
dir =

phi =
dom =
e0 =
e-type =Generic parabola source.
(D=0.0) x coordinate of X-parabola center[cm].
(D=0.0) X-parabola width[cm].
(D=0.0) y coordinate of Y-parabola center[cm].
(D=0.0) Y-parabola width[cm].
(D=0.0) Minimum z of parabola[cm].
(D=0.0) Maximum z of parabola[cm].
(D=2) Order of generic parabola.
(D=1.0) Direction cosine of projectile against z axis.
If all is set, source is isotropic.
If data is set, an a-type subsection is necessary.
(D=none; random) Azimuthal angle[degree].
(D=0.0) Solid angle[degree].
= −1 ; cos2 bias distribution.
(For mono-energy) Projectile energy[MeV/u].
(For energy spectrum) Projectile energy[MeV/u].

4 SECTIONS FORMAT

72

4.3.7 Gaussian distribution source (x-y plane)
The source of the Gaussian distribution in x-y plane can be set. Parameters for Gaussian source are shown
below. The order of parameters is free. If a parameter has a default value (D=***), the parameter can be omitted.
Table 4.34: Parameters for Gaussian sources-type = 13
x0 =
y0 =
r1 =
z0 =
z1 =
dir =

phi =
dom =
e0 =
e-type =Gaussian source.
(D=0.0) x coordinate of Gaussian center[cm].
(D=0.0) y coordinate of Gaussian center[cm].
(D=0.0) FWHM in xy plane[cm].
(D=0.0) Minimum z coordinate[cm].
(D=z0) Maximum z coordinate[cm].
(D=1.0) Direction cosine of projectile against z axis.
If all is set, source is isotropic.
If data is set, an a-type subsection is necessary.
(D=none; random) Azimuthal angle[degree].
(D=0.0) Solid angle[degree].
= −1 ; cos2 bias distribution.
(For mono-energy) Projectile energy[MeV/u].
(For energy spectrum) Projectile energy[MeV/u].

4.3.8 Generic parabola distribution source (x-y plane)
The source of the generic parabola distribution in x-y plane can be set. Parameters for generic parabola source
are shown below. The order of parameters is free. If a parameter has a default value (D=***), the parameter canbe omitted.
Table 4.35: Parameters for generic parabola distributions-type = 15
x0 =
y0 =
r1 =
z0 =
z1 =
rn =
dir =

phi =
dom =
e0 =
e-type =Generic parabola source.
(D=0.0) x coordinate of X-parabola center[cm].
(D=0.0) y coordinate of Y-parabola center[cm].
(D=0.0) Parabola width in xy plane[cm].
(D=0.0) Minimum z of parabola[cm].
(D=0.0) Maximum z of parabola[cm].
(D=2) order of generic parabola.
(D=1.0) Direction cosine of projectile against z axis.
If all is set, source is isotropic.
If data is set, an a-type subsection is necessary.
(D=none; random) Azimuthal angle[degree].
(D=0.0) Solid angle[degree].
= −1 ; cos2 bias distribution.
(For mono-energy) Projectile energy[MeV/u].
(For energy spectrum) Projectile energy[MeV/u].

4.3 [ Source ] section

73

4.3.9 Sphere and spherical shell distribution source
Parameters for sphere and spherical shell sources are shown below. The order of parameters is free. If aparameter has a default value (D=***), the parameter can be omitted.
Table 4.36: Parameters for sphere and spherical shell sources-type = 9
x0 =
y0 =
z0 =
r1 =
r2 =
dir =

e0 =
e-type =Sphere and spherical shell source.
(D=0.0) x coordinate of sphere center[cm].
(D=0.0) y coordinate of sphere center[cm].
(D=0.0) z coordinate of sphere center[cm].
(D=0.0) Inside radius[cm]. If r1=0, sphere source.
(D=0.0) Outside radius[cm].
(D=1.0) Direction.
dir = 1.0 : Outgoing from the center with normal line direction.
dir = -1.0 : Inverse direction with dir=1.0.
dir = all : Isotropic.
dir = -all : Inverse direction against dir=1.0, and with cosine distribution. This is usedfor volume and area calculation with cos2 bias.
dir=iso : Uniform distribution on a circle of radius r2 on a spherical shell of radius r1 withthe direction orthogonal to a circle of radius r2 toward the sphere.
(For mono-energy) Projectile energy[MeV/u].
(For energy spectrum) Projectile energy[MeV/u].

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 equalto (or larger than) r2.

r2
r1

Figure 4.3: Schematic of the source in the case of dir=iso.

4 SECTIONS FORMAT

74

4.3.10 s-type = 11This is a uniform distribution source in a phase space which is vertical with beam direction. Parameters forthis source type are shown below. The order of parameters is free. If a parameter has a default value (D=***), theparameter can be omitted.
Table 4.37: Parameters for s-type=11
s-type = 11
x0 =
x1 =
y0 =
y1 =
z0 =
z1 =
rx =
ry =
wem =
dir =
e0 =

Uniform distribution in a phase space vertical with beam direction.
(D=0.0) x coordinate of beam center[cm].
(D=0.0) Ratio of (maximum radius)/(minimum radius) for x direction[cm/mrad].
(D=0.0) y coordinate of beam center[cm].
(D=0.0) Ratio of (maximum radius)/(minimum radius) for y direction[cm/mrad].
(D=0.0) Minimum z[cm].
(D=0.0) Maximum z[cm].
(D=0.0) Gradient of ellipse in a phase space on x direction[rad].
(D=0.0) Gradient of ellipse in a phase space on y direction[rad].
(D=0.0) Emittance (π cm × mrad).
(D=1) Direct cosine. (1 or −1 only).
(For mono-energy) Projectile energy[MeV/u].

4.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.
Table 4.38: Parameters for s-type=12
s-type = 12
x0 =
y0 =
z0 =
dir =
file =

Decay-turtle reading.
(D=0.0) x coordinate oﬀset of beam[cm].
(D=0.0) y coordinate oﬀset of beam[cm].
(D=0.0) z coordinate oﬀset of beam[cm].
(D=1) Direct cosine. (1 or −1 only).
Decay-turtle filename (with full pathname).

The format of decay-turtle is double precision, and ascii, and each record is asxp, xq, yp, yq, e0, wt0, pz0

Table 4.39: Decay-turtle data
variable
xp, ypxq, yqe0
wt0
pz0

explanation
Incoming position of beam particle[cm].
Angle against vertical face with beam direction[mrad].
Momentum of beam particle[GeV/c].
Weight of beam particle.
Polarizing of beam particle (be not in use).

4.3 [ Source ] section75

4.3.12 Cone shape
Parameters for cone shape source are shown below. In this case, source particles are generated on the sidesurface of the cone. The order of parameters is free. If a parameter has a default value (D=***), the parameter canbe omitted.
Table 4.40: Parameters for cone shapes-type = 18
x0 =
y0 =
z0 =
x1 =
y1 =
z1 =
r0 =
r1 =
r2 =
dir =

phi =
dom =
e0 =
e-type =Cone shape.
(D=0.0) x coordinate oﬀset of top of cone[cm].
(D=0.0) y coordinate oﬀset of top of cone[cm].
(D=0.0) z coordinate oﬀset of top of cone[cm].
(D=0.0) x-component of vector from top to center of bottom circle[cm].
(D=0.0) y-component of vector from top to center of bottom circle[cm].
(D=0.0) z-component of vector from top to center of bottom circle[cm].
(D=0.0) distance between top and upper end of source locations on axis of cone[cm].
(D=0.0) Distance between top and lower end of source locations on axis of cone[cm].
(D=0.0) Angle between generatrix and axis of cone[degree].
(D=1.0) Direction cosine of projectile against z axis.
If all is set, source is isotropic.
If data is set, an a-type subsection is necessary.
(D=none; random) Azimuthal angle[degree].
(D=0.0) Solid angle[degree].
= −1 ; cos2 bias distribution.
(For mono-energy) Projectile energy[MeV/u].
(For energy spectrum) Projectile energy[MeV/u].

4 SECTIONS FORMAT

76

4.3.13 Triangle prism shape
Parameters for triangle prism shape source are shown below. The order of parameters is free. If a parameterhas a default value (D=***), the parameter can be omitted.
Table 4.41: Parameters for triangle prism shapes-type = 20
x0 =
y0 =
z0 =
x1 =
y1 =
z1 =
x2 =
y2 =
z2 =
x3 =
y3 =
z3 =
exa =
dir =

phi =
dom =
e0 =
e-type =Triangle prism shape.
(D=0.0) x-coordinate of origin apex of triangle[cm].
(D=0.0) y-coordinate of origin apex of triangle[cm].
(D=0.0) z-coordinate of origin apex of triangle[cm].
(D=0.0) x vector from the origin to the first apex[cm].
(D=0.0) y vector from the origin to the first apex[cm].
(D=0.0) z vector from the origin to the first apex[cm].
(D=0.0) x vector from the origin to the second apex[cm].
(D=0.0) y vector from the origin to the second apex[cm].
(D=0.0) z vector from the origin to the second apex[cm].
(D=0.0) x vector from the origin to the third apex[cm].
(D=0.0) y vector from the origin to the third apex[cm].
(D=0.0) z vector from the origin to the third apex[cm].
(D=0.0) Attenuation coeﬃcient. exa>0; exp (−ax), exa=0; uniform.
(D=1.0) Direction cosine of projectile against z axis.
If all is set, source is isotropic.
If data is set, an a-type subsection is necessary.
(D=none; random) Azimuthal angle[degree].
(D=0.0) Solid angle[degree].
= −1 ; cos2 bias distribution.
(For mono-energy) Projectile energy[MeV/u].
(For energy spectrum) Projectile energy[MeV/u].

Figure 4.4: Coordinates of triangle prism4.3 [ Source ] section

77

4.3.14 xyz-mesh distribution source
By specifying s-type=22, a complex spatial distribution of sources can be set. In stype=22, mono-energetic
particles can be generated. The spatial distribution can be defined by x,y,z-type subsections and data of relative
intensities Ii jk , (i = 1, · · · , n x ; j = 1, · · · , ny ; k = 1, · · · , nz ). The data should be written below the subsections. The
direction of the sources can be specified by dir, phi, and dom. Note that the direction in each xyz-bin cannot
be changed. Parameters for xyz-mesh distribution source are shown in Table 4.42. The order of parameters is free
except for the data of the relative intensities. If a parameter has a default value (D=***), the parameter can beomitted.
Table 4.42: Parameters for xyz-mesh distribution sources-type = 22
mesh = xyz
x-type =y-type =z-type =

dir =

phi =
dom =
e0 =
e-type =xyz-mesh distribution source.
Geometry mesh. Only xyz can be set.
Mesh type for x-axis. x-type subsection is needed below this option.
Mesh type for y-axis. y-type subsection is needed below this option.
Mesh type for z-axis. z-type subsection is needed below this option.
Put data of relative intensities Ii jk below x, y, z-type subsections. The change of thedata element should be in the order of x, y, z. Note that the change in x, y, z axes should be
ascending order if nx, ny, nz are positive, and it should be descending order if nx, ny,
nz are negative.
(D=1.0) Direction cosine of projectile against z axis.
If all is set, source is isotropic.
If data is set, an a-type subsection is necessary.
(D=none; random) Azimuthal angle[degree].
(D=0.0) Solid angle[degree].
= −1 ; cos2 bias distribution.
(For mono-energy) Projectile energy[MeV/u].
(For energy spectrum) Projectile energy[MeV/u].

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 .
In the latter case, the data with k = nz =|nz| should be first put.
An example using s-type=22 is shown below.
Example 1: Example of xyz-mesh distribution source
1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:

[ Source ]s-type = 22
proj = neutrone0 = 1.0
dir = allmesh = xyz
x-type = 2
nx = 3xmin = -10
xmax = 10
y-type = 2
ny = -3ymin = -10
ymax = 10z-type = 2
nz = -2
zmin = -10(3)

4 SECTIONS FORMAT

78

18:
19:
20:
21:
22:
23:
24:
25:

zmax = 10
1 2 3
4 5 6
7 8 9
1 0 3
0 5 0
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 2bins, respectively. Because ny and nz are negative, the relative intensities Ii jk should be written in descending orderfor 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 I121
I111

I231
I221
I211

 
I331   1
 
I321  =  0
 
7
I311

0
5
0


3 

0  .

9(5)

Figure 4.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

3

4

5

6

7

8

9

10−4

−10

0

2

3

4

5

6

7

8

9

10−4

−10
11

−20
−20

1

Number [1/source]02y [cm]

10
1

Number [1/source]y [cm]

10

11

−10

0
x [cm]

10

20

−20
−20

−10

0
x [cm]

10

20

Figure 4.5: Results of example 1 in the region of [0cm≤ z ≤10cm] (left panel) and [−10cm≤ z ≤0cm] (rightpanel).

4.3 [ Source ] section

79

4.3.15 Tetra-mesh source
By specifying s-type=24, particle generation from tetrahedrons defined in tetrahedron geometry can be considered (sec. 4.6.5). Specification of the cell number of the universe where tetrahedrons belong is needed. Particles
are produced uniformly from each tetrahedron which belongs to the specified universe with a rate proportional toits volume. Here only one cell number can be specified and therefore multi-source (sec. 4.3.1) have to be used
to select more than one cell. The direction of the sources can be specified by dir, phi, and dom. Parameters
for tetra-mesh source are shown in Table 4.43. The order of parameters is free. If a parameter has a default value(D=***), the parameter can be omitted. Please refer also ppt files and sample input files in \utility\TetraGEOM.

Table 4.43: Parameters for tetra-mesh sources-type = 24
tetreg =
dir =

phi =
dom =
e0 =
e-type =Tetra-mesh source.
The cell number of the universe where tetrahedrons belong. Only one cell number can be
specified.
(D=1.0) Direction cosine of projectile against z axis.
If all is set, source is isotropic.
If data is set, an a-type subsection is necessary.
(D=none; random) Azimuthal angle[degree].
(D=0.0) Solid angle[degree].
= −1 ; cos2 bias distribution.
(For mono-energy) Projectile energy[MeV/u].
(For energy spectrum) Projectile energy[MeV/u].

An example using s-type=24 is shown below.
Example 2: Example of tetra-mesh source
1:
2:
3:
4:
5:
6:

[ Source ]s-type = 24
proj = proton
tetreg = 201
dir = alle0 = 70In 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 43.

4 SECTIONS FORMAT

80

4.3.16 Reading dump file
By setting s-type=17, information on particles recorded in a file can be used as sources. The “dump” filecan be obtained by using the dump option in the [t-cross], [t-product], and [t-time] tallies. There are twoalternative methods for treating the dump data, which can be switched between using the idmpmode parameter: by
setting idmpmode=0, each particle’s data recorded in the dump file can treated as an independent history; by setting
idmpmode=1, the correlations between particles at the time of data dump can be taken into account via statisticalprocessing based on history information recorded in the dump file. For continuous calculation using the dump file
based on the history information from the previous step, the use of idmpmode=1 is recommended. 46
Parameters for s-type=17 are shown below. The order of parameters is free. If a parameter has a default value(D=***), the parameter can be omitted.
Table 4.44: Parameters for dump file source (1)s-type = 17
file =
dump =(next line)(omitted)
x0 =
x1 =
y0 =
y1 =
z0 =
z1 =
sx =
sy =
sz =
dir =

phi =
dom =
e0 =
e-type =wgt =Reading dump file.
Dump filename (with full pathname).
Dump data number; if this is negative, data are written as Ascii.
identification of dump data.
If the following parameters are specified, these values have priority over the dump data. If the
dump data do not include the following data, the relevant parameters should be specified.
Minimum x coordinate[cm].
Maximum x coordinate[cm].
Minimum y coordinate[cm].
Maximum y coordinate[cm].
Minimum z coordinate[cm].
Maximum z coordinate[cm].
(D=0) x-component of spin.
(D=0) y-component of spin.
(D=0) z-component of spin.
Direction cosine of projectile against z axis.
If all is set, source is isotropic.
If data is set, an a-type subsection is necessary.
(D=none; random) Azimuthal angle[degree].
(D=0.0) Solid angle[degree].
= −1 ; cos2 bias distribution.
(For mono-energy) Projectile energy[MeV/u].
(For energy spectrum) Projectile energy[MeV/u].
(D=1.0) Weight of source particle.

46 The option idmpmode=1 and re-used calculation using the option dmpmulti were introduced by referring to the presentation “Estimationof uncertainty in multi-step Monte Carlo calculation” (N50) by Dr. Y. Namito et al. at the 2015 annual meeting of AESJ (Hitachi, Japan).

4.3 [ Source ] section

81

Table 4.45: Parameters for dump file source (2)(omitted)factor =t-type =reg =ntmax =
trcl =
idmpmode =dmpmulti =The following parameters can also be specified.
(D=1.0) normalization of source particle.
(D=0) time distribution.
(D=all) specify the region.
(D=1000) maximum re-try number when reg is specified.
(D=none) transform number, or definition of transform.
Control parameter to select dump source mode.
(D=0) (nocas and nobach) not included in the case history information dump data.
(D=1) (nocas and nobach) included in the case history information dump data.
=0: Each particle data recorded in the dump file is treated as an independent history.
=1: Particle data in the dump file are processed by taking account of particle correlations in theprevious step.
Control parameter for reuse of dump file.
(D=0.0) With idmpmode=0.
(D=1.0) With idmpmode=1.
=0.0: The dump file is rewound and re-used until total histories are finished, as specified by(maxcas*maxbch). However, this mode cannot be used with idmpmode=1.
>0.0: The dump file is re-used the number of times specified by this parameter. The digits
after the decimal point reflect the probability with which the Russian roulette routine will adopt
another reproduction of the particle data.

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 beplaced 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 diﬀerent random number. The digits after
the decimal point indicate the probability of creating another reproduction of the particle as stochastically determined by running the Russian roulette procedure for each particle. For example, in the case of dmpmulti=2.3, theparticle 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 allowedwith dmpmulti=0.0, in which case it should be noted that the calculation might give biased results unless the dump
file contains suﬃciently 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 suﬀcient, the statisticaluncertainties may not satisfactorily diminish even if a large dmpmulti factor is selected. In this case, it will benecessary to re-calculate from the previous step to create suﬀcient dump data.

4 SECTIONS FORMAT

82

The parameter dump specifies the number of dump data points per record. If this number is positive, the data areread 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 4.46 and 4.47.
Table 4.46: Dump data id number (1)physical quantities
id number

kf
1

x
2

y
3

z
4

u
5

v
6

w
7

e
8

wt
9

time
10

c1
11

c2
12

c3
13

sx
14

sy
15

sz
16

Table 4.47: Dump data id number (2)physical quantities
id number

name
17

nocas
18

nobch
19

no
20

In the table, kf is the particle kf-code (see Table 3.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 areassumed 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

4.3 [ Source ] section

83

4.3.17 User definition source
An original source function can be used by editing “usrsors.f,” and setting s-type=100. If the following
parameters are set, these values have the priority. If a parameter has a default value (D=***), the parameter can beomitted.
Table 4.48: Parameters can be specified in s-type=100
s-type = 100
x0 =
x1 =
y0 =
y1 =
z0 =
z1 =
sx =
sy =
sz =
dir =

phi =
dom =
e0 =
e-type =wgt =factor =t-type =reg =ntmax =
trcl =

User definition source.
If below parameters are specified, these values have priority over the user defined data.
Minimum x coordinate[cm].
Maximum x coordinate[cm].
Minimum y coordinate[cm].
Maximum y coordinate[cm].
Minimum z coordinate[cm].
Maximum z coordinate[cm].
(D=0) x-component of spin.
(D=0) y-component of spin.
(D=0) z-component of spin.
Direction cosine of projectile against z axis.
If all is set, source is isotropic.
If data is set, an a-type subsection is necessary.
(D=none; random) Azimuthal angle[degree].
(D=0.0) Solid angle[degree].
= −1 ; cos2 bias distribution.
(For mono-energy) Projectile energy[MeV/u].
(For energy spectrum) Projectile energy[MeV/u].
(D=1.0) Weight of source particle.
(D=1.0) Normalization of source particle.
(D=0) Time distribution.
(D=all) Specify the region.
(D=1000) Maximum re-try number when reg is specified.
(D=none) Transform number, or definition of transform.

User-defined variables c1-c99 by setting set can be used in “usrsors.f” as cval(1-99). Note that the lastsetting of set is available if the same variable is defined several times.

4 SECTIONS FORMAT

84

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 thelast 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 theopen and close the data file. The remaining part shows a list of the variables which user should define in thissubroutine.
File 2: usrsors.f
1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:
28:
29:
30:
31:
32:
33:
34:
35:
36:
37:
38:
39:
40:
41:
42:
43:
44:
45:
46:
47:
48:
49:
50:
51:
52:
53:

************************************************************************
subroutine usrsors(x,y,z,u,v,w,e,wt,time,name,kf,nc1,nc2,nc3,&sx,sy,sz)*
sample subroutine for user defined source.
**
variables :**x, y, z : position of the source.
**u, v, w : unit vector of the particle direction.
**e: kinetic energy of particle (MeV).
**wt: weight of particle.
**
time: initial time of particle. (ns)**name: usually = 1, for Coulmb spread.
**kf: kf code of the particle.
**
nc1: initial value of counter 1**
nc2: initial value of counter 2**
nc3: initial value of counter 3**
sx,sy,sz : spin components**----------------------------------------------------------------------**
kf code table**kf-code: ityp : description**
2212 :
1 : proton**
2112 :
2 : neutron
*
*
211 :
3 : pion (+)
*
*
111 :
4 : pion (0)**-211 :
5 : pion (-)
*
*
-13 :
6 : muon (+)**
13 :7 : muon (-)
*
*
321 :
8 : kaon (+)
*
*
311 :
9 : kaon (0)**-321 : 10 : kaon (-)**
kf-code of the other transport particles
*
*
12 :
nu_e
*
*
14 :
nu_mu
*
*
221 :
eta
*
*
331 :
eta’
*
*
-311 :
k0bar**-2112 :
nbar**
-2212 :
pbar**
3122 :
Lanbda0**3222 :
Sigma+**
3212 :
Sigma0**3112 :
Sigma**
3322 :
Xi0**
3312 :
Xi**
3334 :
Omega**----------------------------------------------------------------------**
available function for random number**
unirn(dummy) : uniform random number from 0 to 1**
gaurn(dummy) : gaussian random number**
for exp( - x**2 / 2 / sig**2 ) : sig = 1.0 *************************************************************************
implicit real*8 (a-h,o-z)*----------------------------------------------------------------------parameter ( pi = 3.141592653589793d0 )4.3 [ Source ] section

54:
55:
56:
57:
58:
59:
60:
61:
62:
63:
64:
65:
66:
67:
68:
69:
70:
71:
72:
73:
74:
75:
76:
77:
78:
79:
80:
81:
82:
83:
84:
85:
86:
87:
88:
89:
90:
91:
92:
93:
94:

85

data ifirst / 0 /save ifirstcharacter filenm*50*----------------------------------------------------------------------*
example of initialization*----------------------------------------------------------------------if( ifirst .eq. 0 ) thencfilenm = ’input.dat’cinquire( file = filenm, exist = exex )cif( exex .eqv. .false. ) thencwrite(*,*) ’file does not exist => ’, filenmccall parastop( 887 )cend ifcopen(71, file = file(i), status = ’old’ )cclose(71)
ifirst = 1

end if*----------------------------------------------------------------------*
example for 3 GeV proton with z-direction*----------------------------------------------------------------------x = 0.0
y = 0.0
z = 0.0
u = 0.0v = 0.0
w = 1.0
e = 3000.0
wt = 1.0
time = 0.0
name = 1
kf = 2212
nc1 = 0nc2 = 0nc3 = 0sx = 0.d0
sy = 0.d0
sz = 0.d0*----------------------------------------------------------------------returnend

4 SECTIONS FORMAT

86

4.3.18 Definitions for energy distribution
The energy-distributed source can be defined by e-type subsection instead of by e0. Note that e0 have tobe deleted or set to invalid by comment marks when the e-type subsection is given. For d, t, α, and nuclei, thisenergy is expressed in units of [MeV/nucleon].
Available types of the source energy distribution are shown in Table 4.49. There are integral and diﬀerential
types as the format of the distribution; for the integral type, the source intensity should be given as an energyintegrated value, while for the diﬀerential type, the intensity should be given as the energy diﬀerential value
expressed in [particles/MeV]. As generation method of the source particles, two methods can be selected. In
the first one, the number of particles generated in a bin is proportional to the intensity, and the specified energy
distribution is statistically described. In the second one, the number of source particles generated in each bin is thesame for all energy bins, but the weight values of source particles are adjusted to be proportional to the intensity.
Table 4.49: Types of source energy distribution. There are two methods for generation of source particles; one isto 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 (Å).
Type
Continuous energy
distribution withintegral type

Generation method
Number of particles
Weight value

e-type1, (11)4, (14)

Continuous energy
distribution with
diﬀerential type

Number of particles
Weight value21, (31)24, (34)

Discrete energy
distribution

Number of particles
Weight value

8, (18)9, (19)Discrete+Continuous
energy distribution
with integral type

Number of particles
Weight value

22, (32)
23, (33)

Gaussian distribution
with diﬀerential type

Number of particles

2, (12)

Maxwellian distribution
with diﬀerential type

Number of particles
Weight value

3
7

Analytical function with
diﬀerential type
Energy distribution for
RI source

Number of particles
Weight value
Number of particles
Weight value

5, (15)
6, (16)28
29

Energy distribution oftally results

Number of particles

20

Explanation
A continuous energy distribution can be specified
by providing the data set of lower limits of energy
bins and integrated values of the particle generation probabilities in each bin.
A continuous energy distribution can be specified
by providing the data set of the minimum of energy bins and diﬀerential probabilities of the particle generation in each bin.
A discrete energy distribution can be specified bygiving data set of energy points and probabilitiesof the particle generation at each points.
Any energy distribution can be specified by providing the data set of the minimum and maximumof energy bins, and integrated values of particle
probabilities in each bin.
A diﬀerential spectrum of Gaussian distribution
can be specified by giving a mean value and
FWHM of Gaussian.
A diﬀerential spectrum of Maxwellian distribution can be specified by giving a temperature parameter of Maxwellian.
A diﬀerential spectrum can be specified by giving
analytical functions.
The α, β, and γ-rays of radioisotope (RI) decay
are generated by simply specifying the activity
and names of the RIs.
A energy distribution can be specified by using
results of tallies.

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.

4.3 [ Source ] section

87

Continuous energy distribution with integral value
Table 4.50: Parameters for source energy distribution (1)parametere-type = 1, (11)ne =e-type = 4, (14)ne =p-type = 0, 1

explanation
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 (Å).
Number of energy groups.
If this is a positive number, source particles are generated so that the energy diﬀerential
fluxes in units of [1/MeV] become constant in each bin. If negative, the fluxes in unitsof [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 tow(i).
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 byhand. The number of source particles generated in each bin is the same for all energybins, 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 bechanged by specifying p(i). For case 14, the energy is given by wave length (Å).
Number of energy groups.
If this is a positive number, source particles are generated so that the energy diﬀerential
fluxes in units of [1/MeV] become constant in each bin. If negative, the fluxes in unitsof [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).
(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.

4 SECTIONS FORMAT

88

In the case of e-type=1, the format is as follows.

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)In this case, the energy distribution is given ase(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

4.3 [ Source ] section

89

Continuous energy distribution with diﬀerential value
Table 4.51: Parameters for source energy distribution (2)parametere-type = 21, (31)ne =e-type = 24, (34)ne =p-type = 0, 1

explanation
Any energy distribution can be specified by giving data set of energy bins
e(i) and diﬀerential probabilities of the particle generation dφ/dE(i) by hand.
The integrated number of the particle generation in the bin is proportional todφ/dE(i)*{e(i+1)-e(i)}, and the specified energy distribution is statistically described.
For 31 case, energy is given by wave length (Å).
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),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)}.
The same energy distribution as in the case of e-type=21,(31) can be specified. Unlike 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 weightof 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 specifying p(i).
For 34 case, energy is given by wave length (Å).
Number of energy group.
If it is given by positive number, source particles are generated so that the energy
diﬀerential 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 eachbin. 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 integrated number of source particles generated in each bin is proportional to p(i).
(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).

4 SECTIONS FORMAT

90

Discrete energy distribution
Table 4.52: Parameters for source energy distribution (3)parametere-type = 8, (18)ne =e-type = 9, (19)ne =p-type = 0, 1

explanation
Any energy distribution can be specified by giving data set of energy points e(i) andprobabilities of the particle generation w(i) by hand. The number of the particle generation 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 (Å).
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).
The same energy distribution as in the case of e-type=8,(18) can be specified. Unlike 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 particles 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 ofsource particles generated in each bin can also be changed by specifying p(i).
For 19 case, energy is given by wave length (Å).
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).
(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).

4.3 [ Source ] section

91

Energy distribution by free format
Table 4.53: Parameters for source energy distribution (4)parametere-type = 22, (32)ne =e-type = 23, (33)ne =p-type = 0, 1

explanation
Any energy distribution can be specified by providing the data set of the minimumemin(i) and maximum emax(i) of energy bins, and the integrated values of theparticle 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 number 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 (Å).
Number of energy groups. If this is a positive number, source particles are generated
so that the energy diﬀerential fluxes in units of [1/MeV] become constant in each bin.
If negative, the fluxes in units of [1/Lethargy] become constant for eachbin.
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 generated in each energy bin is proportional to w(i).
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 ofsource 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 specifyingp(i).
For case 33, the energy is given by wave length (Å).
Number of energy groups. If this is a positive number, source particles are generated
so that the energy diﬀerential fluxes in units of [1/MeV] become constant in each bin.
If negative, the fluxes in units of [1/Lethargy] become constant for eachbin.
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).
(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 isset to = 32, 33, the wavelength (Å) is used as the energy unit. In the other cases, the expression e0 = 8.180425e8/13**2 is used, which corresponds to the energy of a neutron with a 13Åwavelength.

4 SECTIONS FORMAT

92

In the case of e-type = 22, the format is as follows:

e-type = 22
ne = nemin(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

4.3 [ Source ] section

93

Gaussian energy distribution
Table 4.54: Parameters for source energy distribution (5)parametere-type = 2, (12)
eg0 =
eg1 =
eg2 =
eg3 =
e-type = 3
nm =

et0 =
et1 =
et2 =
e-type = 7

nm =

et0 =
et1 =
et2 =
p-type = 0, 1

explanationDiﬀerential spectrum dφ/dE(i) is given by Gaussian distribution.
For 12 case, energy is given by wave length (Å).
center of Gaussian distribution [MeV].
FWHM of Gaussian distribution [MeV].
minimum cut oﬀ for Gaussian distribution [MeV].
maximum cut oﬀ for Gaussian distribution [MeV].
Diﬀerential spectrum dφ/dE(i) is given by Maxwellian distribution: f (x) =x exp(−x/T )(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.
temperature parameter T [MeV].
minimum cut oﬀ for Maxwellian distribution [MeV].
maximum cut oﬀ for Maxwellian distribution [MeV].
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 allenergy 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 ineach bin can also be changed by specifying p(i).
(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).
temperature parameter T [MeV].
minimum cut oﬀ for Maxwellian distribution [MeV].
maximum cut oﬀ for Maxwellian distribution [MeV].
(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).

4 SECTIONS FORMAT

94

Energy distribution defined by analytical functions
Table 4.55: Parameters for source energy distribution (6)parametere-type = 5, (15)f(x) =
nm =

eg1 =
eg2 =
e-type = 6, (16)f(x) =
nm =

eg1 =
eg2 =
p-type = 0, 1

explanationDiﬀerential spectrum dφ/dE(i) is given by f (x).
For 15 case, energy is given by wave length (Å).
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).
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).
minimum cut oﬀ for energy distribution [MeV].
maximum cut oﬀ for energy distribution [MeV].
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 forall 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 bechanged by specifying p(i).
For 16 case, energy is given by wave length (Å).
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).
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).
minimum cut oﬀ for energy distribution [MeV].
maximum cut oﬀ for energy distribution [MeV].
(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).

4.3 [ Source ] section

95

Energy distribution of RI source
Table 4.56: Parameters for source energy distribution (7)parametere-type= 28,29

ni=dtime=

explanation
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 thisfunction, 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 particle 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.
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.
(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 halflife×|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 ahalf-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 equilibrium 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 absoluteintensity 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.

47 A. Endo, Y. Yamaguchi and K.F. Eckerman, Nuclear decay data for dosimetry calculation - Revised data of ICRP Publication 38, JAERI

1347 (2005).

4 SECTIONS FORMAT

96

Table 4.57: Parameters for source energy distribution (8)parameter
actlow=

norm=

iaugers=icharctx=

explanation(continued in the cases of e-type= 28,29)(D=1.0e-10) Option for lower limit of the activity [Bq].
If the activity following the passage of the specified time is smaller than actlow, the decay ofthe corresponding RI is not included in the sources.
(D=0) Option for normalization of tally results.
0: Tally results are normalized in units of [/s]. In this case, the source intensity is determined by
the specified activity (if dtime>0, its decrease owing to decay is also taken into account).
1: Tally results are normalized in units of [/source]. This is equivalent to the general normalization of PHITS.
(D=0) Option for the production of Auger & internal conversion (IC) electrons. (only for
proj=electron)
0: All electrons (β-rays, Auger & IC electrons) are generated.
1: Only β-rays are generated.
2: Only Auger & IC electrons are generated.
(D=0) Option for the production of characteristic X-rays. (only for proj=photon)
0: All photons (γ-rays and characteristic X-rays) are generated.
1: Only γ-rays are generated.
2: Only characteristic X-rays are generated.

The following is an example using e-type = 28,29:[ 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.

4.3 [ Source ] section

97

Energy distribution of result of tally
Table 4.58: Parameters for source energy distribution (9)parametere-type= 20

file=

explanation
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, energy diﬀerential and integrated values, in accordance with unit given in the tally section. Theenergy 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 isnormalized to the integrated value of the tally result.
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 thatparticles 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
proj = neutron
dir =
1.0
r0 =
0.
z0 =
0.
z1 =
0.
e-type =20
file = cross.out# axial source with energy spectrum# kind of incident particle# z-direction of beam [cosine]# radius [cm]# minimum position of z-axis [cm]# maximum position of z-axis [cm]# energy distribution given by tally output# file name of tally output

4 SECTIONS FORMAT

98

4.3.19 Definition for angular distribution
When setting dir=data, angular distribution parameters are required as shown below. If a parameter has adefault value (D=***), the parameter can be omitted.
Table 4.59: Parameters for source angular distribution (1)parametera-type = 1, (11)na =a-type = 4, (14)na =q-type = 0, 1

explanation
Any angular distribution can be specified by giving data set of angle bins a(i) andintegrated values of the particle generation probability w(i) by hand. The number ofthe 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 11case, given by degree.
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).
The same angular distribution as in the case of a-type=1,(11) can be specified. Unlike 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 generated in each bin is the same for all angle bin, but integrated values of the weight ofsource particles are adjusted to be proportional to w(i). The number of source particles generated in each bin can also be changed by specifying q(i). For 4 case, angle isgiven by cosine, and for 14 case, given by degree.
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 integrated number of source particles generated in each bin is proportional to q(i).
(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).

4.3 [ Source ] section

99

Table 4.60: Parameters for source angular distribution (2)parametera-type = 5, (15)g(x) =
nn =
ag1 =
ag2 =
a-type = 6, (16)g(x) =
nn =q-type = 0, 1

explanation
Angular distribution dφ/dΩ(i) is given by g(x). For 5 case, angle is given by cosine,for 15 case, given by degree.
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).
Number of angular group.
minimum cut oﬀ for angular distribution.
maximum cut oﬀ for angular distribution.
The same angular distribution as in the case of a-type=5,(15) can be specified. Unlike a-type=5,(15), the number of source particle generated in each bin is the samefor 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.
any analytical function of x, Fortran style. One can use intrinsic functions and constants
C.
Number of angular group.
In default (q-type=0), equal number of particle is generated in each cell. The integrated number of source particles generated in each bin is proportional to q(i).
(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).

4 SECTIONS FORMAT

100

4.3.20 Definition for time distribution
For t-type=0,1,2,3,4,5,6, the time distribution function can be set to define the time spectrum of thesource particles. If a parameter has a default value (D=***), the parameter can be omitted.
Table 4.61: Parameters for time distribution (1)parametert-type = 0, 1, 2

t0 =
tw =
tn =
td =
tc =
t-type = 3

ntt =t-type = 4ntt =o-type = 0, 1

explanation(D=0) time distribution.
0: no time-distribution, t=0.0.
1: rectangle distribution.
2: Gaussian distribution.
(D=0.0) center of time when t-type = 1 [ns]. )width of time distribution [ns]. When t-type=1, it means full width. When t-type=2,
it means FWHM of Gaussian distribution.
number of time distribution.
interval of time distribution [ns].
(D=10×tw) cut oﬀ time when Gaussian distribution t-type=2 [ns]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.
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).
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) andweights of the source particle w(i) by hand. The number of source particles generated in each bin is the same for all time bin, but integrated values of the weight ofsource 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).
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 integrated number of source particles generated in each time bin is proportional to o(i).
(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).

4.3 [ Source ] section

101

Table 4.62: Parameters for time distribution (2)parametert-type = 5
h(x)
ll

tg1
tg2
t-type = 6

h(x)
ll

tg1
tg2
o-type = 0, 1

explanationDiﬀerential spectrum (dφ/dt) is given by h(t).
Any analytical function of x[ns], Fortran style. One can use intrinsic function and constants
C.
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. Integrated number of source particles generated
in each cell is proportional to h(x).
Minimum cut oﬀ for time distribution [ns].
Maximum cut oﬀ for time distribution [ns].
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 integrated 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).
Any analytical function of x[ns], Fortran style. One can use intrinsic function and constants
C.
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).
Minimum cut oﬀ for time distribution [ns].
Maximum cut oﬀ for time distribution [ns].
(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.
Table 4.63: Parameters for time distribution (3)parametert-type = 100
tg1
tg2

explanation
User define time distribution. User can write any type of time distribution in the source
program of “sors.f”.
Minimum cut oﬀ for time distribution [ns].
Maximum cut oﬀ for time distribution [ns].

4 SECTIONS FORMAT

102

4.3.21 Example of multi-source
The following is an example of multi-source, which includes energy distribution and angular distribution described by analytic functions.
Example 3: Example of multi-source
1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:
28:
29:
30:
31:
32:
33:
34:
35:
36:
37:
38:
39:
40:
41:
42:
43:
44:
45:
46:
47:
48:
49:

[ Source ]totfact = 3<source> = 9.72
s-type = 1
proj = protonz0 = 2z1 = 29r0 = 5r1 = 4
dir = 0.0
e-type = 6
eg1 = 1.e-6
eg2 = 1.e-3
nm = -200
set: c10[1.e-4]
f(x) = x**(1.5)*exp(-x/c10)<source> = 1
s-type = 1
proj = photonz0 = 1z1 = 2r0 = 5dir = -1e-type = 5
eg1 = 1.e-3
eg2 = 5.e-1
nm = 200
set: c10[1.e-1]
set: c20[1.e-1/2.35482]
f(x) = exp(-(x-c10)**2/2/c20**2)<source> = 1
s-type = 1
proj = neutronz0 = 29z1 = 30
r0 = 5e-type = 6
eg1 = 1.e-2
eg2 = 1.e+3
nm = -200
set: c10[92.469]
set: c20[5.644e+10]f(x) = c10/c20*exp(-sqrt(x*(x+1876))/c10)*(x+938)/sqrt(x*(x+1876))
dir = dataa-type = 5
ag1 = 0ag2 = 1nn = 200g(x) = exp(-(x-1)**2/0.3**2)

4.3 [ Source ] section

103

In this example, there are three source subsections started from <source>. In the first source subsection, acylinder 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 theregion 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 fromz =29 cm to z =30 cm with 5 cm radius. The numbers defined after each <source> denote the relative weight ofthe 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. 4.6 using [t-product] tally with output=source, and icntl=6.

x [cm]

4
2
10−3

0
−2
−4

Number [1/cm3/source]

6

−6
0

10

20

30

z [cm]

6

6

z=1.5cm

10−3

0
−2
−4

2
y [cm]y [cm]

2

10−3

0
−2
−4

−6

−6
−6

−4

−2

0
x [cm]

2

4

6

−6

−4

−2

0
x [cm]

Figure 4.6: Multi-source, coordinate distribution

2

4

6

Number [1/cm3/source]4
Number [1/cm3/source]

4

z=15cm4 SECTIONS FORMAT

104

The source particles of the multi-source are proton, photon and neutron. In each subsection, the energy distribution 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 theexpression by e-type=7 ase-type = 7
et0 = 1.e-4
et1 = 1.e-6
et2 = 1.e-3

The second Gaussian distribution is also equivalent to the expression by e-type=2 ase-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. 4.7 with diﬀerent colors.

10−1

Number [1/source]

10−2
10−3

protonphoton10−4neutron

10−5
10−6
10−6 10−5 10−4 10−3 10−2 10−1 100 101 102 103
Energy [MeV]
Figure 4.7: Multi-source, energy distribution

4.3 [ Source ] section

105

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 definedby a-type description in which an analytic function is used for an angular distribution. The angular distributionof the third one is shown in Fig. 4.8 by using [t-cross] tally.

Angular distribution

0.00150.00100.00050.0000
0.0

0.2

0.4

0.6
cos(θ)

0.8

Figure 4.8: Multi-source, angular distribution

1.0

4 SECTIONS FORMAT

106

4.3.22 Duct source option
For the simulation of neutrons through the long beam-line from the moderator of spallation neutron sourceor the reactor to the detector room, the following duct source options can be used to reduce the variance of thecalculations. The beam current transported through the beam-line decreases proportional to the inverse square of
the distance from the moderator. This means that the current crossing the wall of the beam-line, which is calledas ‘wall current,’ at 100 m point is six order of magnitude smaller than that at 1 m point from the source if an
isotropic distribution of the source direction is assumed. To reduce this variance, a special option of the source
function cab be used. When using this option, the wall current of the simulation particles is equalized at any pointof the beam-line by changing the importance weight of the particles to simulate a real situation of the current inside
the beam-line.
The duct source option is available when setting dom=-10 in the circle or rectangle source, which are set bys-type=1 or 2, respectively. The parameters for the duct source options are summarized in Table 4.64.
Table 4.64: Parameters for duct source options
parameter
dom = -10
dl0 =
dl1 =
dl2 =
dpf =
drd =
dxw =
dyw =

explanation
specify the duct source
starting z position of the beam-line from z0[cm].
starting z position of the duct source from z0[cm].
ending z position of the duct source from z0[cm].
portion of pass through particles at dl2
radius of circle beam line for s-type = 1[cm].
x size of rectangle beam line for s-type = 2[cm].
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 thedirection 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 seenat all duct wall positions from dl0 to dl2, the normalization factor is set to be 1. If the source region at z0 islarger than the area of the beam-line at dl0, the source particle from the outer region at z0 is not counted as thenormalization number at dl0. This means that the extra region at z0 increases the current in the beam-line withoutchanging 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.

z0

dl0

dl1

True
dyw
dxw
False

Figure 4.9: Schematic image of the duct source.

Some example of the duct source option are shown below.

dl2

4.3 [ Source ] section

107

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:
Example 4: duct source option, example (1)
1
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:
28:
29:
30:

[ Source ]set: c1[200]$dl0set: c2[500]$dl1
set: c3[5000]$dl2
set: c4[5.0]$x*2 at z0
set: c5[5.0]$y*2 at z0
set: c10[5.0]$dxw
set: c20[5.0]$dyw
set: c30[0.001] $dpf
s-type = 2
proj= neutrone0= 20.0x0= -c4/2
x1= c4/2y0= -c5/2
y1= c5/2
z0
= 0.0
z1
= 0.0
dir
= 1.0
phi
= 0.0
dom = -10
dl0 = c1
dl1 = c2dl2 = c3
dxw = c10
dyw = c20
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 thebeam-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 andthe current, wall current by using the cross tally. The results are shown in Fig. 4.10 compared with an ideal casein 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.
Example 5: duct source option, example (2)
1
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:

[ Source ]set: c1[200]$dl0set: c2[500]$dl1
set: c3[5000]$dl2
set: c4[10.0]$x*2 at z0
set: c5[10.0]$y*2 at z0
set: c10[5.0]$dxw
set: c20[5.0]$dyw
set: c30[0.001] $dpf
s-type = 2
proj= neutrone0= 20.0x0= -c4/2
x1= c4/2

4 SECTIONS FORMAT

108

101

Current [n/source]

1 / L2100

1 / L3Current, PHITS

10−1

Wall Current, PHITS

10−2
10−3
10−4
10−5
10−6
0

1000

2000

3000
z [cm]

4000

5000

Figure 4.10: Duct source option, example 1

17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:
28:
29:
30:

y0
y1
z0
z1
dir
phi

= -c5/2= c5/2
= 0.0
= 0.0
= 1.0
= 0.0

dom = -10
dl0 = c1
dl1 = c2dl2 = c3
dxw = c10
dyw = c20
dpf = c30

Figure 4.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 / L210

1 / L3Current, PHITS

10−1

Wall Current, PHITS

Current [n/source]

0

10−2
10−3
10−4
10−5
10−6
0

1000

2000

3000
z [cm]

4000

5000

Figure 4.11: Duct source option, example 2

4.4 [ Material ] section

109

4.4 [ Material ] section
4.4.1 Formats
Materials, which are used to define 3-dimensional geometry, are defined in this section. The defined materials
are refered to some sections such as [cell] section.
The [material] section is defined by material number, elements (or nuclides), and their composition ratios.
Following a material number, element symbols and their ratios should be alternately written to define a compoundor mixture. The format is:[ 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 toa material number of 99,999 unless it is over-defined. Note that a blank space cannot be set between MAT and [ inthe 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 inthis 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.

4.4.2 Element (nuclide) definition
The element in the above format can be specified using element symbols. To define nuclide (isotope), add its
mass number to the symbol as follows: 208Pb, Pb-208, or 82208. For instance, hydrogen is defined as 1H,
H-1, or 1001. The natural abundance of isotopes can be defined using only an element symbol or a no-massstyle as, e.g., Pb, 82000. Note that the natural isotope ratio format cannot be used for an isotope not included in
the nuclear data library JENDL-4.0.
To use nuclear data libraries other than JENDL-4.0, copy all addresses of the new library and then paste it at
the end of the address file file(7) (D=xsdir). When setting the new library of low-energy neutrons (below
20MeV) other than JENDL-4.0, specify the “library id” in each material number by NLIB parameter, which isshown in Table 4.65. The “library id” consists of the library number (double-digit) and data class (character a-z).
For example, 50c for the low-energy neutron data library of JENDL-4.0. The libraries of photons, electrons, andprotons can be also specified by PLIB, ELIB, HLIB, respectively. The library id can be specified by nuclide
instead of by material number following the element definition and a period as, e.g., 208Pb.50c, Pb-208.50c,
or 82208.50c. In PHITS, only one type of the library should be used for each incident particle, and the id shouldbe specified by the NLIB, PLIB, ELIB, HLIB parameters. Only for neutrons, the second library can be used;in this case, after specifying the library id by NLIB, define the nuclide by the expression of 208Pb.50c. If thelibrary id is not specified by the user, PHITS searches the address file file(7) (D = xsdir) from the top line
for the library number id corresponding to the nuclide and uses the corresponding data library. Information on thedata library used in a PHITS calculation is written in the summary output file file(6) (D=phits.out) when
kmout=1 is set in the [parameters] section.
When using EGS5, restrict the number of elements (not nuclides) in one material number to 20.

4.4.3 Composition ratio definition
The composition ratios of the defined elements are given in ratio in the above format. Two ways are available
for the ratio definition: if ratio takes a positive value, it means atomic ratio; for negative value, it does mass ratio.
For instance, water (H2 O) can be defined as follows:
MAT[1] H 2
orO 1

4 SECTIONS FORMAT

110

MAT[1] H -2/18

O -16/18

In the latter case, the mass ratios of hydrogen and oxygen are given as about 2/18 and 16/18, respectively, because
the molecular mass of the water is about 18.
The material densities used in transport calculations are given in the [cell] section. Note that material densities must be defined in the [material] section instead of composition ratios when using letmat parameterin [t-deposit], [t-deposit2], [t-let], [t-sed] sections. In this case, if it takes a positive value, theparticle density is [1024 atoms/cm3 ], and for negative value, it is given as a mass density [g/cm3 ].

4.4.4 Material parameters
For regions in which nuclear data are used, the material parameters for each material can be set using the format
keyword=value. The parameters can be set anywhere in the material subsection. The full set of material parameters
is listed in Table 4.65.
Table 4.65: Material parametersparameter
GAS

ESTEP
NLIB
PLIB
ELIB
HLIB
COND

value
D = 0
= 0
= 1
= n
= id
= id
= id
= id
< 0
= 0
> 0

4.4.5

explanation
Density eﬀect correction to electron stopping power.
Appropriate for materials in the condensed (solid or liquid) state used.
Appropriate for material in the gaseous state.
Make sub step number n for electron transport: ignored when n is smaller than thebuilt-in default value.
Change default neutron library number id.
Change default photon library number id.
Change default electron library number id.
Change default proton library number id.
Conductor settings.
Non-conductor.
(default) Non-conductor if there exists at least 1 non-conductor; otherwise, conductor.
Conductor if there exists at least 1 conductor.

S (α, β) settings

In the transport of low-energy neutrons, the library of the thermal scattering law data S (α, β) may be required.
This library plays an important role in describing the transport of thermal neutrons. This library can be set as
follows:
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
MT1

H
2.0
O
1.0
lwtr.20t

See “\phits\XS\tsl\tsl-table” for detailed information for these data.

4.4 [ Material ] section

111

4.4.6 Examples
Some examples using the materials parameter are shown below.
Example 6: material example (1)
1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:

[ Material ]MAT[ 1 ]
1H
1.0000000E-04
208Pb
1.7238000E-02
204Pb
4.6801000E-04
206Pb
7.9430000E-03
207Pb
7.2838000E-03
MAT[ 2 ]1H
1.0000000E-09
14N
4.6801000E-05
16O
7.9430000E-06

By default, the order is element, then ratio; these can be specified in reverse by putting den and nuc as,
Example 7: material example (2)
1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:

[ Material ]den
MAT[ 1 ]1.0000000E-04
1.7238000E-02
4.6801000E-04
7.9430000E-03
7.2838000E-03
MAT[ 2 ]1.0000000E-09
4.6801000E-05
7.9430000E-06

nuc<------

1H
208Pb
204Pb
206Pb
207Pb
1H
14N
16O

Example 8: material example (3)
1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:

[ Material ]m180196.49c 5.9595d-5
80198.49c 3.9611d-3
80199.49c 6.7025d-3
80200.49c 9.1776d-3
80201.49c 5.2364d-3
80202.49c 1.1863d-2
80204.49c 2.2795d-3
c...Be...
m3
4009.37c 1.2362E-1
mt3
be.01
c
...h2o (25C)...
m4
1001.37c 6.6658d-2
8016.37c 3.3329d-2
mt4
lwtr.01c...b4c (natural boron; 25%-density)...
m5
6012.37c 6.8118d-3
5011.37c 2.1825d-2c...liquid-h2 (20K)...
m6
1001.49c 3.1371d-2
1011.49c 1.0457d-2
mt6
orthoh.00
parah.00

4 SECTIONS FORMAT

112

4.5 [ Surface ] section
4.5.1 Formats
In the [surface] section, surfaces can be set to define cells in the [cell] section. Several surfaces, including
planes, sphere surfaces, cylindrical surfaces, etc., can be set in terms of the parameters in the equations defining
their respective shapes. Only C and $ can be used as comment marks in [surface]. To use continuation lines, atleast five blanks can be placed at the line head in place of the line sequential mark at the end of line.
The [surface] section is defined in the order data: surface number, coordinate transform number, surface
symbol, and surface definition; these are explained in Table 4.66. The format is as follows:[ Surface ]surface number

transform number

surface symbol

surface definition

The surfaces expressed by the equations in Table 4.67 or the macro body in Table 4.67 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 isuseful to develop an infinite repeated structure.

Table 4.66: Surface definition format
item
surface number
transform number
surface symbol
surface definition

explanation
Use any number from 1 to 999,999.
Specifies the number n of TRn defined in the [transform] section. Does not specify if
not using the coordinate transform.
Specifies a surface symbol in Tables 4.67 and 4.68.
Species parameters of 1 ∼ 15 inputs, which depend on the surface symbol.

4.5 [ Surface ] section

113

Table 4.67: Surfaces expressed by equations
Surface Symbol

Type

Explanation

Equation

Parameters

P
PX
PY
PZ
P

plane

Ax + By + Cz − D = 0
x−D=0
y−D=0
z−D=0

SO
S
SX
SY
SZ
C/X
C/Y
C/Z
CX
CY
CZ
K/X
K/Y
K/Z
KX
KY
KZ

spheremulti-purpose
vertical with X-axis
vertical with Y-axis
vertical with Z-axis
defined by
3 coordinatesorigin is center
multi-purpose
center on X-axis
center on Y-axis
center on Z-axis
parallel with X-axis
parallel with Y-axis
parallel with Z-axison X-axis
on Y-axis
on Z-axis
parallel with X-axis
parallel with Y-axis
parallel with Z-axison X-axis
on Y-axis
on Z-axis

A, B, C, D
D
DD
x1 , y1 , z1 , x2 , y2 , z2 ,x3 , y3 , z3R
x0 , y0 , z0 , R
x0 , Ry0 , Rz0 , Ry0 , z0 , R
x0 , z0 , R
x0 , y0 , R
R
R
R
x0 , y0 , z0 , |t|2 , k
x0 , y0 , z0 , |t|2 , k
x0 , y0 , z0 , |t|2 , k
x0 , |t|2 , k
y0 , |t|2 , k
z0 , |t|2 , k
k is ±1 or unspecified
A, B, C, D, E,
F, G, x0 , y0 , z0

SQ

GQ

TX
TY
TZ

plane

cylindercone

ellipse,hyperboloid,
paraboloid
cylinder,cone,
ellipse,hyperboloid,
paraboloid
ellipse torus
torus

x2 + y2 + z2 − R2 = 0(x − x0 )2 + (y − y0 )2 + (z − z0 )2 − R2 = 0(x − x0 )2 + y2 + z2 − R2 = 0
x2 + (y − y0 )2 + z2 − R2 = 0
x2 + y2 + (z − z0 )2 − R2 = 0(y − y0 )2 + (z − z0 )2 − R2 = 0(x − x0 )2 + (z − z0 )2 − R2 = 0(x − x0 )2 + (y − y0 )2 − R2 = 0
y 2 + z2 − R2 = 0
x 2 + z2 − R2 = 0
x2 + y2 − R2 = 0√22√(y − y0 ) + (z − z0 ) ∓ |t| (x − x0 ) = 022√(x − x0 ) + (z − z0 ) ∓ |t| (y − y0 ) = 0
2(x − √x0 ) + (y − y0 )2 ∓ |t| (z − z0 ) = 0
22√y + z ∓ |t| (x − x0 ) = 022√x + z ∓ |t| (y − y0 ) = 0
2x + y2 ∓ |t| (z − z0 ) = 0

parallel with
X-, Y-,or Z- axis
non parallel with
X-, Y- andZ-axisA(x − x0 )2 + B(y − y0 )2 + C(z − z0 )2+2D(x − x0 ) + 2E(y − y0 ) + 2F(z − z0 )+G = 0Ax2 + By2 + Cz2 + Dxy + Eyz+Fzx + Gx + Hy + Jz + K = 0

parallel with
X-, Y-, orZ-axis(x − x0 )2 /B2 +2( (y − y0 ) + (z − z0 )2 − A)2 /C 2 − 1 = 0(y − y0 )2 /B2 +√2( (x − x0 ) + (z − z0 )2 − A)2 /C 2 − 1 = 0(z − z0 )2 /B2 +√( (x − x0 )2 + (y − y0 )2 − A)2 /C 2 − 1 = 0√

A, B, C, D, E,
F, G, H, J, K

x0 , y0 , z0 , A, B, C
x0 , y0 , z0 , A, B, C
x0 , y0 , z0 , A, B, C

When using the surfaces defined in the [surface] section in the [cell] section, the interior of the shapeshould 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 theequation 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, theregion 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 13); If parameter k is set = 1, theupper sheet is used, while the lower sheet is used when k = −1. If k is not specified, both sheets are used. Notethat 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4 SECTIONS FORMAT

114

the underside of the cone— must be specified.
Note that when using TX,TY,TZ to define an elliptical torus or torus, the shape’s coordinates cannot be transformed by setting the [transform] section.
Table 4.68: Macro body
SymbolType

BOX

Optional BOX(all angles are 90◦ )RPP

Rectangular solid(Each surface is verticalwith x, y, z axes)
Sphere(the same with general sphere S)

SPH

RCC

Cylinder

RHP
or
HEX

Optional hexagonal prism
Prism

REC

Right elliptical cylinder

TRC

Truncated right-angle cone

ELL

Ellipsoid of revolution(Spheroid)

WED

Wedge

Parameters

Explanation

x0 , y0 , z0 ,A x , Ay , Az ,Bx , By , Bz ,C x , Cy , Cz
xmin , xmax ,ymin , ymax ,zmin , zmax
x0 , y0 , z0 ,Rx0 , y0 , z0 ,H x , Hy , Hz ,R
x0 , y0 , z0 ,H x , Hy , Hz ,A x , Ay , Az ,Bx , By , Bz ,C x , Cy , Cz
x0 y0 z0 ,H x , Hy , Hz ,A x , Ay , Az ,Bx , By , Bz
x0 , y0 , z0 ,H x , Hy , Hz ,R1 ,R2
If R > 0,x1 , y1 , z1 ,x2 , y2 , z2 ,R

Base point coordinate
Vector from base point to first surface.
Vector from base point to second surface.
Vector from base point to third surface.
Minimum and Maximum of x.
Minimum and Maximum of y.
Minimum and Maximum of z.
Center coordinate.
Radius.
Center coordinate of bottom face.
Height vector from center of bottom face to that of top face.
Radius.
Base point coordinate.
Height vector from base point.
Vector from base point to first surface.
Vector from base point to second surface.
Vector from base point to third surface.
Center coordinate of bottom face.
Height vector from center of bottom face (H).
Major axis vector of ellipse orthogonal to H (A).
Minor axis vector of ellipse orthogonal to H and A (B).
Center coordinate of bottom face of cone.
Height vector from center of bottom.
Radius of bottom face.
Radius of top face.

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.
Center coordinate of ellipsoid.
Major axis vector.
Radius of minor axis.
Coordinate of top.
Vector to first side of triangle ( A).
Vector to second side of triangle (B).
Height vector (H).

x0 , y0 , z0 ,A x , Ay , Az ,R
x0 , y0 , z0 ,A x , Ay , Az ,Bx , By , Bz ,H x , Hy , Hz

Coordinate of first focus.
Coordinate of second focus.
Radius of major axis.

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.

4.5 [ Surface ] section

115

4.5.2 Examples
This section shows examples of the surface definitions listed in Tables 4.67 and 4.68.
Example 9: Example of Plane (1)1:2:[surface]
1
PY

5

z

PX,PY,PZ define planes perpendicular to the x, y, z axes, respectively.
In this example, a plane of surface number 1, corresponding to y = 5
and perpendicular to y axis, is defined by setting the symbol to PY
and the parameter to D = 5. Surface number 1 corresponds to theplane shown as a dashed line in Fig. 4.12.

5

x

y

y=5
Figure 4.12: The plane y = 5 defined in
Example 9.

Example 10: Example of Plane (2)
1:
2:
3:

[surface]
1
P
2
P

2 2 1
5 0 0

10
0 5 0

0 0 10Arbitrary planes can be defined by specifying P as the symbol. In
this case, two types of description can be used to define the plane:
four parameters, A, B, C, D, can be used to specify the plane equation Ax + By + Cz − D = 0; otherwise, the coordinates of threepoints, (x1 , y1 , z1 ), (x2 , y2 , z2 ), (x3 , y3 , z3 ), can be specified. The former method is useful when the normal vector (s, t, u) and coordinates(x0 , y0 , z0 ) of one point on the plane are known. An equation of theplane satisfying these conditions would be given ass(x − x0 ) + t(y − y0 ) + u(z − z0 ) = 0.

(6)

z
10

5
x

y

5
2x+2y+z-10=0

Then, becausesx + ty + uz − (sx0 + ty0 + uz0 ) = 0,

Figure 4.13: The plane defined in Exam(7) ple 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 10 is defined as a plane having the normal vector (2, 2, 1) and containing the coordinate (5, 0, 0). Thissurface corresponds to the plane denoted by the dashed line in Fig. 4.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). Thissurface coincides with surface 1 in Figure 4.13.

4 SECTIONS FORMAT

116

Example 11: Example of Sphere Surface
1:
2:
3:
4:

[surface]
1
SO
2
SZ
3
S

5
10 3
10 10 03z
To define a sphere surface, the symbols
Surface Number 2
SO,SX,SY,SZ,S can be used. SO is used todefine a sphere surface centered at the origin
10
by specifying its radius R as a parameter. In
Surface Number 1
10
the second line of Example 11, a sphere sury
face centered at the origin with a radius of 5 cm
Surface Number 3
is defined as surface number 1. The symbols
10
SX,SY,SZ can be used to define sphere surfaces
centered on the x, y, z axes, respectively. To usexthese symbols, two parameters —a coordinate
value on the appropriate axis, and the radius of
the sphere— must be specified. In the third line Figure 4.14: The three sphere surfaces defined in Example 11.
of Example 11, a sphere surface centered at the coordinate (0, 0, 10), which is a point on the z axis, with a radiusof 3 cm is defined as surface number 2. S can be used to define a sphere surface centered at an arbitrary coordinate(x0 , y0 , z0 ). In this case, four parameters —the coordinate values x0 , y0 , z0 and the radius R— must be specified.
In the fourth line of Example 11, a sphere surface centered at the coordinate (10, 10, 0) with a radius of 3 cm isdefined as surface number 3. The three sphere surfaces defined in Example 11 are shown in Fig. 4.14.

Example 12: Example of Cylinder Surface
1:
2:
3:

[surface]
1
CY
2
C/Y

5
15 0

3

z
To define a cylinder surface having a central axis along either theSurface Number 1
x, y, z axes, the symbols CX,CY,CZ, respectively, can be specified.
In this case, the radius R must be specified as a parameter. In thesecond line of Example 12, a cylinder surface with a central axis on
R=5
the y axis with a radius of 5 cm is defined. This surface corresponds
to the surface of the cylinder shown in the upper-right of Fig. 4.15.
R=3 y
The symbols C/X,C/Y,C/Z, can be used to define a cylinder surfacexwith a central axis parallel to the x, y, z axes, respectively. In thiscase, two coordinate values and the radius of the cylinder must be
Surface Number 2
specified. The third line of Example 12 defines a cylinder surface
with a central axis parallel to the y axis. The coordinates x0 = 15, z0 = Figure 4.15: The two cylinder surfaces de0 are specified as the first and second parameters, respectively, and fined in Example 12.
the radius is given by the third parameter. This surface corresponds
to the cylinder in the lower-left side of Fig. 4.15.
To define a cylinder surface with a central axis that is NOT parallel to any of the x, y, z axes, the symbol GQ
can be used. However, it is easier to use CX,CY,CZ,C/X,C/Y,C/Z and then perform a coordinate transformation
using the [transform] section than it is to use GQ.

4.5 [ Surface ] section

117

Example 13: Example of Cone Surface
1:
2:
3:

[surface]
1
KZ
2
K/Z

0 1
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 13.
The first parameter is the z-coordinate of the vertex
zof the cone, z0 = 0, and the second defines |t|2 = 1.
The equation of KZ is
45o
Surface Number 2√
30ox2 + y2 ∓ |t| (z − z0 ) = 0.
(8)
Surface Number 1
After substituting each of the parameters, the fol20 y
lowing equations are obtained:x√x2 + y2 − z = 0, (z > 0)
(9)
Figure 4.16: The cone surface defined in Example 13.
√
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. 4.16. The cone in the regionz > 0 is represented by Eq. (9), while that in z < 0 is given by Eq. (10); these surfaces are specified by k = 1 andk = 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 generatingline. 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 beused. The third line of Example 13 shows an example in which K/Z is specified. The coordinate of the vertex is2◦(0, 20, 0), and√ the cone has a central axis parallel to the z axis. Its angle θ is = 30 , corresponding to |t| = 1/3, ortan θ = 1/ 3. In this case, only one cone surface in the region of z > 0 is defined by specifying k = 1.

Example 14: Example of Ellipsoid Surface
1:
2:[surface]
1SQ

1/9**2 1/6**2 1/3**2

0 0 0

-1

0 0 0

z

To define an ellipsoid surface as shown in Fig. 4.17, the symbol SQ is specified. The general equation of an ellipsoid surfaces isx2 y2 z2++
=1
a2 b2 c2

a=9

(11)

x

c=3
b=6
y

where a, b, c are the lengths of the semi-principal axes along the x, y, z axes,
respectively. An ellipsoid surface can therefore be defined by specifying
the first to the seventh parameters of SQ as A = 1/a2 , B = 1/b2 , C = 1/c2 , Figure 4.17: The ellipsoid surface
D = E = F = 0, and G = −1, respectively. In Example 14, an ellipsoid defined in Example 14.
surface with lengths a = 9, b = 6, c = 3 cm is defined. To define a spheroid
surface, the two lengths along the two axes that are not the rotational axis must have same values. For example,
if the x axis is the rotational axis, b must be set = c, namely, B = C. The eighth, ninth, and tenth parameters of
SQ correspond to the coordinates of the center (x0 , y0 , z0 , respectively). In Example 14, the center of the ellipsoidis the origin (0, 0, 0). Note that if D, E, F are set to non-zero values, a quadric surface other than an ellipsoid isdefined.

4 SECTIONS FORMAT

118

Example 15: Example of Hyperboloid Surface
1:
2:
3:

[surface]
1
SQ
2
SQ

1/6**2 1/3**2 -1/5**2 0 0 0 -1 0 0 0-1/6**2 -1/3**2 1/5**2 0 0 0 -1 0 20 0

The symbol SQ can be specified to define hyperboloid surfaces, as shown in the center and right-hand side ofFig. 4.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
z=0+−
= 1, (12)z
a2 b2 c2x2 y2 z2
− 2 − 2 + 2 = 1. (13)
b=3
a
b
c

y
Here, the central axis is the z axis.
a=6
If a = b, the shape is called a hy(0,20,0)
perboloid of revolution. The surfacexxnumber 1 defined in the second lineyof Example 15 corresponds to thehyperboloid of one sheet shown inthe center of Fig. 4.18. In the second
Figure 4.18: The hyperboloid surface defined in Example 15.
line, the first to the seventh parameters 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 tox0 = 0, y0 = 0, z0 = 0, respectively. The intersection of this hyperboloid with a plane vertical to the z axis is anellipse. The figure in the left side of Fig. 4.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 thethird line of Example 15 corresponds to the hyperboloid of two sheets shown in the right-hand side of Fig. 4.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 todefine 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 shownin the right-hand side of Fig. 4.18 should be specified as ‘positive.’

Example 16: Example of Paraboloid Surface
1:
2:[surface]
1SQ

1 1/2**2 0

0 0 -10

0 0 0

To define a paraboloid surface as shown in Fig. 4.19, the symbol SQ can be specified as described in Example 16.
The equation ofz
a paraboloid sury=0
x=0face with a cenzz
tral axis coinciding with the z axis
z=x2
is given asz= 41 y 2z=

x2 y2
+ . (14)
a2 b2

x

x

y
y

This surface canFigure 4.19: The paraboloid surface defined in Example 16.
be defined by specifying 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 theleft and right panels of Fig. 4.19, respectively. The coordinates of the vertex are specified by eighth through tenthparameters; in this case, x0 = 0, y0 = 0, z0 = 0.

4.5 [ Surface ] section

119

Example 17: Example of GQ
1:
2:
3:
4:
5:

[surface]
set: c1[30]set: c2[cos(c1/180*pi)]
set: c3[sin(c1/180*pi)]
1GQc2**2 1/2**2 c3**2

0 0 -2*c2*c3-c3 0 -c20z

Arbitrary surfaces expressed by quadratic equations in x, y, z by can be defined specifying the symbol GQ. Although there similar surfaces such as
CX,KX,SQ are also expressed by quadratic equations, GQ can be used torepresent quadratic surfaces with a central axis that is NOT parallel to thex, y, z axes. Note that it is easier to use apply a coordinate transformationyin the [transform] section to CX,KX,SQ than it is to use GQ. Example 17x
represents a paraboloid surface obtained by rotating the surface in Example
16 by an angle of 30◦ around the y axis. The result is shown in Fig. 4.20.
The parameters of this example were obtained by calculating the following Figure 4.20: The paraboloid surtransform defined by rotating the coordinate (x, y, z) by an angle of θ around face defined in Example 17.
y axis:  ′   x   cos θ 0 sin θ   x  
 ′  
01
0   y  .
(15)
 y  =  z− sin θ 0 cos θz′This relation gives   x   cos θ   y  =  0
sin θ
z


 

0 − sin θ   x′   x′ cos θ − z′ sin θ   ′  
′
y
1
0
 .
  y  = ′′′x sin θ + z cos θz
0 cos θ(16)

After substitution of this result into Eq. (14), the following equation of x′ , y′ , z′ is obtained:x′ sin θ + z′ cos θ=x′ sin θ + z′ cos θ=x′ sin θ + z′ cos θ=0 =(x′ cos θ − z′ sin θ)2 y′ 2
+ 2,
a2
b
x′ 2 cos2 θ + z′ 2 sin2 θ − 2x′ z′ cos θ sin θ y′ 2
+ 2,
a2
b
2
2
cos θ ′ 2 sin θ ′ 2 2 cos θ sin θ ′ ′ y′ 2
x + 2 z −xz + 2,a2
aa2
bcos2 θ ′ 2 1 ′ 2 sin2 θ ′ 2 2 cos θ sin θ ′ ′x + 2y + 2 z −x z − x′ sin θ − z′ cos θ
a2
b
a
a2

(17)

Comparing this result with the equation of GQ in Table 4.67 and specifying the corresponding parameters defines aparaboloid surface rotated by an angle θ around y axis. In this example, θ = 30◦ is given as the constant c1, whilec2 and c3 are defined as sin θ and cos θ, respectively.

4 SECTIONS FORMAT

120

Example 18: Example of Torus Surface
1:
2:[surface]
1
TZ

0 0 0

10 3 5

A torus surface, as shown in the center of Fig. 4.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(√

x2 + y2 − R

)2

a2

+

z2
= 1.
b2

(18)

In this case, the ellipse has major and minor radii z and b, respectively, and a distance between the center of theellipse and the rotational axis given by R. The center of the torus surface in Example 18 is set at the origin bysetting 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 shownin the left panel of Fig. 4.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. 4.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

y=0

z

z
a=5

x

R=10

x
b=3

a=5

R=10

y

x

Figure 4.21: The torus surface defined in Example 18.

Example 19: Example of BOX
1:
2:[surface]
1
BOX

5 5 0

9 0 0

0 6 0

0 0 3

The symbol BOX can be specified to define the surfaces ofan arbitrary rectangular solid. As parameters of BOX, thecoordinates of the base point P(x0 , y0 , z0 ) and each component of three vectors A(A x , Ay , Az ), B(Bx , By , Bz ), andC(C x , Cy , Cz ) must be defined. Figure 4.22 shows the relation between the basepoint and the three vectors. In Example 19, the coordinate of the basepoint is (5, 5, 0) and thethree vectors are given as A = (9, 0, 0), B = (0, 6, 0), andC = (0, 0, 3). In using BOX, vectors A, B, C do not have tobe parallel to the x, y, z axes, but they should be vertical toeach other.

z
C(Cx,Cy,C z)=(0,0,3)P(x0 ,y0 ,z0)=(5,5,0)x
A(Ax ,Ay ,Az )=(9,0,0)y
B(Bx ,By ,Bz )=(0,6,0)Figure 4.22: The rectangular surface defined in Example 19.

4.5 [ Surface ] section

121

Example 20: Example of RPP
1:
2:[surface]
1
RPP

5 14

5 11

0 3

To define the surfaces of a rectangular solid surrounded by threesets of two planes parallel to the xy, yz, zx planes, the symbol RPP
can be used. Unlike BOX, an arbitrary rectangular solid with surfaces not parallel to the x, y, z axes CANNOT be defined. The six
parameters of RPP must be set by the user as the maximum andminimum values in the x, y, z coordinate system. In Example 20,
xmin = 5, xmax = 14, ymin = 5, ymax = 11, and zmin = 0, zmax = 3
are specified as the six parameters. The result is the same rectangular solid defined in Example 19 and is shown in Fig. 4.23.

zzmax=3zmin=0xmin=5ymin=5ymax=11yxmax=14x
Figure 4.23: The rectangular surface definedin Example 20.

Example 21: Example of SPH
1:
2:[surface]
1
SPH

5 5 5

5

z

Symbol SPH can be used to define a sphere surface with an arbitrary coordinate as its center. The first, second, and third parameters are components of the coordinate (x0 , y0 , z0 ) and the fourthparameter is the radius of the sphere. A sphere surface centeredat (5, 5, 5) with a radius of 5 cm is defined in Example 21. Thereis no functional diﬀerence between the symbols SPH and S.

R =5

z0=5

y0=5
y

x 0=5
x
Figure 4.24:
Example 21.

The sphere surface defined in

Example 22: Example of RCC
1:
2:[surface]
1
RCC

5 5 0

0 0 105

The symbol RCC can be used to define an arbitrary cylinder surface. The parameters of RCC are the coordinates of the center ofthe 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
relation between these parameters is shown in Fig. 4.25. In Example 22, 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 symbols 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.

z

H(Hx ,Hy,Hz )=(0,0,10)

R =5
y
x
P(x0 ,y0 ,z0)=(5,5,0)
Figure 4.25: The cylinder surface defined in
Example 22.

4 SECTIONS FORMAT

122

Example 23: Example of RHP
1:
2:[surface]
1
RHP

0 0 0

0 0 105 0 0

2 -5 0-2 -5 0The symbols RHP or HEX can be used to define hexagonal prism surfaces as shown in the right panel of Fig. 4.26.
As parameters, the center coordinate of the bottom of the prism, P(x0 , y0 , z0 ), a vector from the bottom to thetop, 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. 4.26
shows the relation between point P and the three vectors; namely, the lengths and directions of the perpendicularlines between P and the three contiguous sides of the hexagon determine the three vectors. In Example 23, theorigin is at the center of the bottom hexagon and the height along the z axis of the prism is 10 cm. The componentsof the origin (0, 0, 0) are specified as the first, second, and third parameters of RHP, respectively, and those of thevector 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=0z

H(Hx ,Hy ,Hz )=(0,0,10)Py
B(Bx ,By ,Bz )yxx=(2,-5,0)A(Ax ,Ay ,Az )=(5,0,0)P(x0 ,y0 ,z0)=(0,0,0)

Figure 4.26: The hexagonal prism surface defined in Example 23.

Example 24: Example of REC
1:
2:[surface]
1
REC

0 0 0

0 0 10

5 0 0

0 2 0

B(Bx ,By ,Bz )=(0,2,0)
The symbol REC defines elliptiH(Hx ,Hy ,Hz )=(0,0,10)
cal cylinder surfaces as shown
z=0z
in the right panel of Fig. 4.27.
The parameters of REC are thePcoordinates of the center coordinate of the bottom sury
face, P(x0 , y0 , z0 ), the compoy
nents of a vector from the bottomxx
to the top, H(H x , Hy , Hz ), andthe components of two vectors,
P(x0 ,y0 ,z0)=(0,0,0)A(Ax ,Ay ,Az )=(5,0,0)A(A x , Ay , Az ) and B(Bx , By , Bz ).
The relation between the point
Figure 4.27: The elliptical cylinder surface defined in Example 24.
P and the two vectors A and
B is shown in the left panel ofFig. 4.27. The major and minor axis vectors A and B must both be defined using initial point, P, which is thecenter of the ellipse. The surfaces of an elliptical cylinder with a height along the z axis of 10 cm are defined in Example 24. The center of the bottom is the origin; the first, second, and third parameters of REC are the coordinatesof the origin (0, 0, 0), and the fourth, fifth, and sixth parameters are those of vector H(H x , Hy , Hz ) = (0, 0, 10). Thex, y, z components of A and B are given in the seventh to twelfth parameters. The vectors A and B are used to form
the ellipse shown in the left panel of the figure.

4.5 [ Surface ] section

123

Example 25: Example of TRC
1:
2:[surface]
1
TRC

0 0 0

0 0 105

2

H(Hx ,Hy ,Hz )=(0,0,10)z
The surfaces of a truncated right-angle cone, as shown in
Fig. 4.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 Examyple 25, the surfaces of the truncated right-angle cone of heightx
10 cm along the z axis are defined. The center of the botP(x0 ,y0 ,z0)=(0,0,0)
tom circle is the origin. The coordinates of the origin (0, 0, 0)
are specified as the first, second, and third parameters, respectively, and those of vector H(H x , Hy , Hz ) = (0, 0, 10) are given Figure 4.28: The cut cone surface defined in Exas the fourth through sixth parameters. The radius of the bot- ample 25.
tom is R1 = 5 cm and that of the top is R2 = 2 cm with R1 andR2 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.

Example 26: Example of ELL (1)1:2:[surface]
1
ELL

3 3 0

-3 -3 09z=0z
The surface of an ellipsoid of revolution
P2(x2 ,y2 ,z2)=(-3,-3,0)(a spheroid) can be set by defining thesymbol ELL. After defining an ellipse by
2R=18
P2
specifying the coordinates of two focal
yypoints or the coordinate of its center, theP1ellipsoid of revolution is defined by rotating the ellipse around its major axis.
xx
P1(x1 ,y1 ,z1)=(3,3,0)Note that the meanings of the first six
parameters of ELL depend on the sign of
Figure 4.29: The spheroid surface defined in Example 26.
the seventh parameter, R. Example 26 is
an example with R > 0. In this case, thecoordinates of the two focal points and the radius of the major axis must be specified. The coordinate of the first
focus, P1 (x1 , y1 , z1 ), is given by the first, second, and third parameters, while that of the second, P2 (x2 , y2 , z2 ), is
given by the fourth, fifth, and sixth parameters. The seventh parameter is the radius of the major axis, R. The
surface of the ellipsoid of revolution defined in Example 26 is shown on the right side of Fig. 4.29. The first andsecond focal points are P1 (x1 , y1 , z1 ) = (3, 3, 0) and P2 (x2 , y2 , z2 ) = (−3, −3, 0), respectively. The ellipse is on thexy plane, as shown in the left panel of the figure, with an angle between the major axis and the x axis of 45◦ . The
length of the major axis is 2R = 18 cm. The ellipsoid is defined by rotating this ellipse around the major axis.
Although an ellipsoid surface can also be defined using SQ, it is easier to define an ellipsoid with an inclined
rotational axis using ELL. Note that only surfaces of ellipsoids of revolution can be defined using ELL.

4 SECTIONS FORMAT

124

Example 27: Example of ELL (2)1:2:[surface]
1
ELL

0 0 0

6 6 0

-6

z=0
z
Example 27 apples to the case R < 0 in
P(x0 ,y0 ,z0)=(0,0,0)
ELL. In this case, the center coordinate,|R|=6
P, major axis, A, and radius of the minor axis of the ellipse must be defined.
yyP
In this example, the center of the ellipse corresponds to the origin. The first,
second, and third parameters of ELL arexxgiven as P(x0 , y0 , z0 ) = (0, 0, 0), while
the fourth, fifth, and sixth parameters are
A(Ax ,Ay ,Az )=(6,6,0)
A(A x , Ay , Az ) = (6, 6, 0). The ellipse defined by these parameters is shown in
Figure 4.30: The spheroid surface defined in Example 27.
the left panel of Fig. 4.30. The absolutevalue of the seventh parameter, R, whichcorresponds to the radius of the minor axis, is 6 cm. The ellipsoid surface obtained by rotating this ellipse aroundthe major axis is shown in the right side of Fig. 4.30.

Example 28: Example of WED
1:
2:[surface]
1
WED

0 0 0

10 0 00 10 00 0 5

H(Hx ,Hy ,Hz )=(0,0,5)
A wedge surfaces, as shown in Fig. 4.31,
z
can be obtained by specifying the symbol WED. Note that only a right triangle
B(Bx ,By ,Bz )=(0,10,0)
can be used as the bottom of a wedge
defined by WED. In Example 28, one verA(Ax ,Ay ,Az )ytex of the bottom triangle P(x0 , y0 , z0 ) =x(0, 0, 0) is given in the first, second, and=(10,0,0)P(x0 ,y0 ,z0)=(0,0,0)
third parameters of WED, respectively.
Two vectors A(A x , Ay , Az ) = (10, 0, 0)
and B(Bx , By , Bz ) = (0, 10, 0) with iniFigure 4.31: The wedge surface defined in Example 28.
tial point P are specified in the fourth toninth parameters. The triangle defined by the two vectors is a right triangle. The height vector of the wedge,H(H x , Hy , Hz ) = (0, 0, 5) is given in the tenth through twelfth parameters.

4.5 [ Surface ] section

125

4.5.3 Surface definition by macro bodyIn using a surface defined by a macro body in the cell definition, ‘-’ refers to the inside of the macro bodyand ‘+’ is the outside. Each surface comprising a macro body can be used in the cell definition, in which case themacro body surface number should be written as ‘.’ plus the macro body surface number.
The surface numbers are listed in Table 4.69.
Table 4.69: Macro Body Surface Numbers
SymbolBOX

RPP

Macro Body Surface Number
1
2
3
4
5
6
1
2
3
4
5
6

SPH
RCC

RHP
or
HEX

REC

TRC

ELL
WED

1
2
3
1
2
3
4
5
6
7
8
1
2
3
1
2
3
1
2
3
4
5

Explanation
Surface vertical with the end of (A x , Ay , Az ).
Surface vertical with the origin of (A x , Ay , Az ).
Surface vertical with the end of (Bx , By , Bz ).
Surface vertical with the origin of (Bx , By , Bz ).
Surface vertical with the end of (C x , Cy , Cz ).
Surface vertical with the origin of (C x , Cy , Cz ).
Surface at xmax .
Surface at xmin .
Surface at ymax .
Surface at ymin .
Surface at zmax .
Surface at zmin .
Only a user-defined surface number is used.
Side face of cylinder.
Surface vertical with the end of (H x , Hy , Hz ).
Surface vertical with the origin of (H x , Hy , Hz ).
Surface vertical with the end of (A x , Ay , Az ).
Opposite face for surface 1.
Surface vertical with the end of (Bx , By , Bz ).
Opposite face for surface 3.
Surface vertical with the end of (C x , Cy , Cz ).
Opposite face for surface 5.
Surface vertical with the end of (H x , Hy , Hz ).
Surface vertical with the origin of (H x , Hy , Hz ).
Side face of cylinder.
Surface vertical with the end of (H x , Hy , Hz ).
Surface vertical with the origin of (H x , Hy , Hz ).
Side face of cone.
Surface vertical with the end of (H x , Hy , Hz ).
Surface vertical with the origin of (H x , Hy , Hz ).
Only a user-defined surface number is used.
Surface including the top and bottom hypotenuses.
Surface including B and H.
Surface including A and H.
Surface including A, B, and the end of H.
Surface including A, B, and the origin of H.

4 SECTIONS FORMAT

126

4.6 [ Cell ] section
4.6.1 Formats
In the [cell] section, cells can be defined in terms of surfaces described in the [surface] section. The
format for this definition is based on General Geometry (GG). A cell should be set as a closed space, and a virtual
space for particle transport calculation can be generated by combining defined cells. In PHITS, an ‘outer void’
must be explicitly defined as a cell.
Only C and $ can be used as comment marks in this section; in particular, # cannot be used as a comment markas this character is used for the cell definition. To use continuation lines, it suﬃces to place at least five blanks at
the line head instead of using the line sequential mark at the end of the line.
The [cell] section is defined in this data order: cell number, material number, material density, cell definition,and cell parameter as keyword style. These are explained in Table 4.70. The format is shown below.

[ Cell ]cell numbermat.

numbermat.

densitycell def.

cell parameterIn the LIKE n BUT format, the cell parameter format and repeated structures with lattices can be used: seeSec. 4.6.5 for some examples showing how to use this format. The cell parameters are listed and explained inTable 4.71.
Table 4.70: Cell definition format
item
cell number
material number
material density

cell definition

LIKE n BUT
cell parameter

explanation
Any number from 1 to 999,999 can be used.
Set 0 for void, −1 for outer void, or use a material number defined in the [material]
section.
If the cell is void or outer void, no input. When the given value is positive or negative, it
is a particle density [1024 atoms/cm3 ] or mass density [g/cm3 ], respectively. A composition
ratio defined in the [material] section is used. Thus, diﬀerent density materials with thesame composition as the original can be set in this section. A new parameter, matadd, isused to add diﬀerent material numbers.
Cell geometry is defined by both surface numbers in the [surface] section and the Boolean
operators, ⊔(blank)(AND), :(OR), and #(NOT). Parentheses ( and ) can be also used. See
Sec. 4.6.2 for details.
A cell using this format is the same as an n cell except for using only parameters described
after BUT.
The format is keyword=value.
As a keyword, VOL(volume), TMP(temperature),
TRCL(transform), U(universe), LAT(lattice), or FILL can be used. In the LIKE n BUT format, MAT(material) and RHO(density) can be used as well.

When defining cells with the same material number but diﬀerent densities, the cells assume material numbersthat diﬀer from that of the first cell.
In operation of the cell definition, ⊔(blank) has a higher priority than :.

4.6 [ Cell ] section

127

Table 4.71: Cell parameters
item
VOL
TMP
TRCL
U
LAT
FILL
MAT
RHO

explanation
Volume [cm3 ] of the cell is given.
Temperature [MeV] of the material in the cell is given.
Coordinate transform for position of the cell is performed using the defined coordinate transformnumber defined in the [transform] section or the transform format.
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. 4.6.3 for details.
Lattice number. Setting LAT=1 or 2 defines a quadratic or hexangular prism, respectively: seeSec. 4.6.4 for details.
Set universe numbers to fill the cell with the universe.
This is used with the LIKE n BUT MAT=m format. Using MAT, a cell can be duplicated except withits material number changed to m.
This is used with the LIKE n BUT RHO=x format. Using RHO, a cell can be duplicated except withits density changed to x.

4.6.2 Description of cell definition
Cells are defined by treating regions divided by surfaces defined in the [surface] section. When giving acell definition, in some cases the concept of ‘surface sense’ must be used to create a distinction between two
regions divided by the surface corresponding to an equation, f (x, y, z) = 0; in other cases, the Boolean operators,⊔(blank)(AND), :(OR), and #(NOT) must be used to treat the regions.
‘Surface sense’ defines one region including a point (x0 , y0 , z0 ) by treating f (x0 , y0 , z0 ) > 0 in a ‘positive sense’and the region f (x0 , y0 , z0 ) < 0 in a ‘negative sense.’ To define a region in the positive sense, a positive surface
number is written in the cell definition space; conversely, a negative surface number is used in the definition to
denote a negative sense. An example of the definition of sense is shown below.
Example 29: [cell] section example (1)
1:
2:
3:
4:
5:

[ Cell ]
1
0 -10
2 -1
10
[ Surface ]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. 4.32.
10x [cm]

5

0

void

1

−5
−10
−10

−5

0
z [cm]

5

10

Figure 4.32: Result of [cell] section example (1).

4 SECTIONS FORMAT

128

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 #.
Example 30: [cell] section example (2)
1:
2:
3:
4:
5:
6:
7:
8:
9:
10:

[ Cell ]1
0 11 -12
2 -1 #1[ Surface ]11 PX -612 PX
613 PY -614 PY
615 PZ -6
16 PZ
6

13

-14

15

-16

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 definedwith ⊔(blank) as the first cell, which is the interior of a 12-cm cube. The outside of the cube is defined by thecomplement operator # as the outer void. Figure 4.33 shows the result of this example.
10x [cm]

5

0

1

void

−5
−10
−10

−5

0
z [cm]

5

10

Figure 4.33: Result of [cell] section example (2).
The next example uses : and parentheses to combine the sphere in the first example and the cube in the second
example.
Example 31: [cell] section example (3)
1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:

[ Cell ]1
0 -10 : (112 -1 #1[ Surface ]
10 SZ
3 5
11 PX -612 PX
613 PY -614 PY
615 PZ -6
16 PZ
6

-12

13

-14

15

-16)

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) isdefined using the union operator : as the first cell. The result is shown in Fig. 4.34.

4.6 [ Cell ] section

129

10

x [cm]

5

0

1

void

−5
−10
−10

−5

0
z [cm]

5

10

Figure 4.34: Result of [cell] section example (3).

The next example shows the division of a cube into two regions by a spherical surface.
Example 32: [cell] section example (4)
1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:

[ Material ]mat[1] 1H 2 16O 1[ Cell ]
1
0
-10
2
1 1.0
10 (113 -1#1 #2[ Surface ]
10 SZ
3 5
11 PX -612 PX
613 PY -614 PY
615 PZ -6
16 PZ
6

-12

13

-14

15

-16)

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 definedby the parentheses. The cell is filled with water as defined in the [material] section and the result is shown in
Fig. 4.35. The interior of the sphere is the first cell, which is filled with void.
10x [cm]

5

0

void

2

−5
−10
−10

water

1

−5

0
z [cm]

5

10

Figure 4.35: Result of [cell] section example (4). The first and second cells are filled with void and water,
respectively.

4 SECTIONS FORMAT

130

4.6.3 Universe frame
In PHITS, the cell parameter U can be used to define a region of the main space used for particle transport
calculation that can be translated to a corresponding region in any universe. This function is very useful for setting
the repeated structures introduced in Sec. 4.6.5.
An example using three spaces (one main space and two universes) and shown in Fig. 4.36 is explained below.
The main space comprises two rectangular solids. One universe includes a cylinder filled with water, while theother has an iron cylinder surrounded by water. The first cell is filled with a region of universe 1, while the second
cell is filled with a region of universe 2.
(a) Main space10x [cm]

5

0

1

2

void

−5
−10
−10

−5

0
z [cm]

510(c) Universe 2
10

5

5

0

void
water

101

x [cm]

x [cm](b) Universe 1
10

0

−5

iron

−5
202

102

−10
−10

water

201

−5

0
z [cm]

5

−10
−10

10

−5

0
z [cm]

5

10

Figure 4.36: (a) Two rectangular solids. (b) Cylinder filled with water. (c) Iron cylinder in water.

Example 33: [cell] section example (5)
1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:

[ Material ]mat[1] 1H 2 16O 1
mat[2] Fe 1
[ Cell ]1 0
11 -12 13
2 0
11 -12 13
101 1 1.0 -10 13 -14102 0#101 U=1
201 2 10.0 -10 13 -14
202 1 1.0 #201 U=2
9 -1
#1 #2
[ Surface ]10 CY
511 PX -612 PX
613 PY -614 PY
615 PZ -6
16 PZ
6
17 PZ
0

-14
-14
U=1
U=2

15
17

-17
-16

FILL=1
FILL=2

4.6 [ Cell ] section

131

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 diﬀer, as shown in Fig. 4.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. 4.37, in which it can be seen that thefirst cell comprises the 101st and 102nd cells in universe 1, while the second cell comprises the 201st and 202nd
cells in universe 2.
10x [cm]

5

0

101

void
water

201

iron

−5

102

−10
−10

−5

202

0
z [cm]

5

10

Figure 4.37: Result of [cell] section example (5).

It is not possible to use an undefined region from one of the universes. If the 102nd cell is not defined in theeighth 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 inany universe agreeing with those in any other universe. If a diﬀerent value of PX is in the fourteenth and fifteenthlines, the cube will not include some of the cylinder, as shown in Fig. 4.38.
10x [cm]

5

102

202

101

0

void
water

201

iron

−5
−10
−10

−5

0
z [cm]

5

10

Figure 4.38: Result of [cell] section example (5) with the region is shifted in the x-direction.

4.6.4 Lattice definition
The cell parameter LAT (lattice parameter) is very useful for making repeated structures. In this section, thedefinition of a unit lattice structure and its simple use are explained using some examples: see Sec. 4.6.5 for a morepractical description.
The quadratic and hexangular prisms shown in Fig. 4.39 can be used as a unit structure by setting LAT=1 orLAT=2, respectively. A universe can be constructed using repeated structure of such a lattice, and any region canbe filled using this universe. Note that each unit must also be filled with another universe defined with any material

4 SECTIONS FORMAT

132

or void. The numbering of each unit component in Fig. 4.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
2

LAT=1

5
2

1

3
1

LAT=2

6

4

4

Figure 4.39: Unit structure of lattice.
An example using a quadratic prism (LAT=1) is shown below.
Example 34: [cell] section example (6)
1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:

[ Material ]mat[1] 1H 2 16O 1[ Cell ]10
11 -12
13 -14 15 -16 FILL=1
101
0
-26
25 -2221 LAT=1 U=1 FILL=2201
1 1.0 -90 U=2
2 -1#1[ Surface ]11 PX -612 PX
613 PY -614 PY
615 PZ -616 PZ
6
21 PX -222 PX
223 PY -224 PY
225 PZ -2
26 PZ
2
90 BOX -10 -10 -10 20 0 0 0 20 0 0 0 20

In the fifth line, a unit cell with LAT=1 is defined using four surface numbers. Setting U=1 defines as the repeatedstructures 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. 4.40. Note that the unit has an infinite length in the y direction of universe 1 because of only four
20
surfacesare defined. To define a finite-length prism, -24 23 must be added to the cell definition in the fifth line.
1015x [cm]

5

10(-1,1,0) (0,1,0) (1,1,0)

0(-1,0,0) (0,0,0) (1,0,0)−5(-1,-1,0) (0,-1,0) (1,-1,0)

water

5

−10
−10
0
0

5

10

15

20

−5

0
z [cm]

5

10

Figure 4.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. 4.40. Note that the ordering this coordinate notation corresponds to the general coordinate

4.6 [ Cell ] section

133

ordering (x, y, z) and are defined by the order of surface numbers written in the cell definition. To specify any cellusing 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. 5.1.2 for more information on this format. The latticecoordinates can be viewed using the [t-gshow] tally with output=7 or 8.
The following example involves a hexangular prism (LAT=2).
Example 35: [cell] section example (7)
1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:

[ Material ]mat[1] 1H 2 16O 1[ Cell ]10
11 -12 13 -14 15 -16 FILL=1101
0-31 32 -33 34 -35 36 -24 23
201
1 1.0 -90 U=2
2 -1#1[ Surface ]11 PX -612 PX
613 PY -614 PY
615 PZ -616 PZ
623 PY -2
24 PY
2
set: c1[2]31 PZ [ c1*cos(pi/6)]
32 PZ [-c1*cos(pi/6)]
33 P
1 0 [ 1/tan(pi/3)] [ c1]34 P
1 0 [ 1/tan(pi/3)] [-c1]35 P
1 0 [-1/tan(pi/3)] [ c1]36 P
1 0 [-1/tan(pi/3)] [-c1]
90 BOX -10 -10 -10 20 0 0 0 20 0 0 0 20

LAT=2

U=1

FILL=2A 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 theuniverse 2, i.e., water, as specified in the sixth line. The first cell has the repeated structure defined in universe 1.
Figure 4.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. 5.1.2 for more information on this format. The lattice coordinates can be shownusing 20the [t-gshow] tally with output=7 or 8.
10
15

5

(-3,2,0) (-2,2,0) (-1,2,0) (0,2,0) (1,2,0)x [cm](-2,1,0) (-1,1,0) (0,1,0) (1,1,0)
10

0(-2,0,0) (-1,0,0) (0,0,0)(-1,-1,0) (0,-1,0) (1,-1,0)

−5
5

−10
−10
0
0

5

10

15

20

water

(1,0,0) (2,0,0)(2,-1,0)(-1,-2,0) (0,-2,0) (1,-2,0) (2,-2,0) (3,-2,0)−50z [cm]

5

10

Figure 4.41: Result of [cell] section example (7) in 3D (left) and 2D (right) images.

4 SECTIONS FORMAT

134

4.6.5 Repeated structures
There are several simple procedures in PHITS that can be used to create repeated structures in which the sameor similar units are repeated. Using the lattice parameter described in Sec. 4.6.4 is one such method; another is the
LIKE n BUT cell parameter format.
LIKE n BUT cell parameter
Using this format, a cell that diﬀers slightly from an original cell can be created. In this format, the cell parameters following the BUT statement diﬀer from the those in the original cell (n). The cell parameters that can be usedin this format are shown in Table 4.71. In the following example, two cell parameters, TRCL and MAT, are used.
Example 36: [cell] section example (8)
1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:

[ Material ]mat[1] 1H 2 16O 1
mat[2] Fe 1
[ Cell ]1
0-10 13 -14 #2 #3 #4
2
1 1.0
11 -12 13 -14 15 -16
3
LIKE 2 BUT TRCL=1
4
LIKE 2 BUT TRCL=2 MAT=2
5 -1#(-10 13 -14)
[ Surface ]10 CY
1011 PX -212 PX
213 PY -214 PY
2
15 PZ -2
16 PZ
2
[ Transform ]*tr1
3 0 -5*tr2
0 0 6 30 90 120 90 0 90 60 90 30

1

A 4 cm cube filled with water and placed at the origin of the coordinate system is defined in the sixth line. Theinterior of this cube is the second cell, which is regarded as the original cell in this example. In the seventhand eighth lines, respectively, the third and fourth cells are defined using the LIKE n BUT format with n = 2.
Figure 4.42 shows the result of this example. The coordinate system of the third cell is transformed using the cellparameter 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 cellis replaced with iron defined using the material number 2 in the third line.
105x [cm]

3
void

0
−5
−10
−10

4

2

iron
water

1

−5

0
z [cm]

5

10

Figure 4.42: Result of [cell] section example (8).

4.6 [ Cell ] section

135

Nesting structure with lattice
A nesting structure can be used based on the universe frame described in Sec. 4.6.3.. For example, universe 1
can be filled with universe 2, and universe 2 can be filled with universe 3, with this process continued following auser-defined nesting structure. The maximum number of nestings is 10, which corresponds to the parameter mxlv
given in the file “param.inc.”
In the next example, there are nine square poles defined using LAT=1; three of these have unique structures.
Example 37: [cell] section example (9)
1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:

[ Material ]mat[1] 1H 2
mat[2] Fe 1
[ Cell ]
1
0
101
0

16O 1

11 -12
13 -14 15 -16 FILL=1-26
25 -2221 LAT=1 U=1
FILL=-1:1 -1:1 0:0
2 2 3 2 3 2 3 2 2-90 U=2-10 U=3
10 U=3
#1

201
1 1.0
301
2 10.0302
02 -1[ Surface ]
10 CY
1.5
11 PX -612 PX
613 PY -614 PY
615 PZ -616 PZ
6
21 PX -222 PX
225 PZ -2
26 PZ
2
90 BOX -10 -10 -10

20 0 00 20 00 0 20The 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 diﬀers: in the seventh 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 filledwith universe 3. Universe 2 is defined in the ninth line as a space filled with water, while the universe 3 is definedin the tenth and eleventh lines has an iron cylinder centered at the origin. The result of this example is shownin Fig. 4.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. 5.1.2 for more informationon this format.
10

5(-1,1,0)(0,1,0)(1,1,0)(-1,0,0) (0,0,0)(0,0,0)(1,0,0)x [cm](-1,1,0)

0
−5
−10
−10

water
void
iron

(-1,-1,0) (0,-1,0) (1,-1,0)(1,-1,0)−50z [cm]

5

10

Figure 4.43: Result of [cell] section example (9).

4 SECTIONS FORMAT

136

A more complex example is shown below.
Example 38: [cell] section example (10)
1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:
28:
29:
30:
31:
32:

[ Material ]mat[1] 1H 2
mat[2] Fe 1
[ Cell ]
1
0
101
0

201
301

1
0

1.0

16O 1

11 -12
13 -14 15 -16 FILL=1-26
25 -2221 LAT=1 U=1
FILL=-1:1 -1:1 0:0
2 2 3(1 0 1) 2 3(1 0 1) 2 3(1 0 1) 2 2-90 U=2-36
35 -3231 LAT=1 U=3
FILL=-1:0 -1:0 0:0
4 2 2 4
-10 U=4
10 U=4#1401
2 10.0402
02 -1[ Surface ]
10 CY
0.5
11 PX -612 PX
613 PY -614 PY
615 PZ -616 PZ
6
21 PX -222 PX
225 PZ -226 PZ
2
31 PX -132 PX
135 PZ -1
36 PZ
1
90 BOX -10 -10 -10

20 0 00 20 00 0 20The virtual space formed by this input is shown in Fig. 4.44, in which there are nine square poles defined using thelattice 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 isrepresented as [s t u], can be used to specify any cell using mesh=reg in the tally sections: see Sec. 5.1.2 formore information on this format.
10x [cm]

5
water

0

void
iron

−5
−10
−10

−5

0
z [cm]

5

10

Figure 4.44: Result of [cell] section Example (10).

4.6 [ Cell ] section

137

Voxel phantom
In PHITS, a virtual space can be created using voxel phantoms for calculation on complex structures such as thehuman body or an organism. To define a voxel phantom, a small cube must first be defined as the unit of a latticewith 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.
Example 39: [cell] section example (11)
1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:

[ Material ]mat[1] 1H 2 16O 1
mat[2] Fe 1
[ Cell ]10
11 -12
13 -14 15 -16 FILL=1101
0 -20 LAT=1 U=1
FILL=-2:2 -2:2 -2:2
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 2 3 3 2 2 2 3 4 3 2 2 3 3 2 2
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 2 2 3 3 2 2 3 4 3 2 2 2 3 3 2
2 2 2 2 2 2 2 2 2 2 2 2 3 2 2 2 2 2 2 2201
0-90 U=2301
2 10.0 -90 U=3401
1 1.0 -90 U=4
2 -1#1[ Surface ]11 PX -512 PX
513 PY -514 PY
515 PZ -516 PZ
520 BOX -1 -1 -1 2 0 0 0 2 0 0 0 2
90 BOX -10 -10 -10 20 0 0 0 20 0 0 0 20

2 2 2 2 2
2 2 2 2 2
2 2 2 2 2
2 2 2 2 2
2 2 2 2 2

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 isvoid, while 3 and 4 correspond to universes 3 and 4, which are of iron and water, respectively. Figure 4.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 represented by [s t u], can be used: see Sec. 5.1.2 for more information. Note that formats such as, e.g., (301 <101[-2:2 -2:2
-2:2] < 1) cannot be used because20 not all 101[-2:2 -2:2 -2:2] cells have a 301st cell.
20

15

15

10

10

5

5

0

0

0
5 [cell] section
10
15
5
10
15 right panel
20
Figure 4.45: Resultsof theexample(11) in0203D images.
The structurein theis equivalent
to that in the left panel with part of its iron surface removed.

4 SECTIONS FORMAT

138

From the PHITS version 3.09, the array of universe numbers at the 8th through 12th lines of the example 39
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 withminus sign followed by the universe number. Following this rule, the array of universe number at the 8th through12th lines of the example 39 can be rewritten as follows.
Example 40: [cell] section example (11’)
8:
9:
10:
11:
12:

2 -11 3 2 -17 3 -1 2 -2 3
4 3 2 -1 3 -1 2 -12 3 -2
2 3 4 -2 3 2 3 -2 2 -12 3-1 2 -1 3 4 3 2 -2 3 -1 2
-17 3 2 -11

In the example 39 after the universe number 2 are aligned 12 times, the universe number 3 comes. On the other
hand in the example 40, 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 verylarge amount of voxel data is used, it may be more convenient to use infl.
Use of tetrahedron geometry
In this section, a definition and the basic usage of tetrahedron geometry are given using an example. Tetrahedrongeometry is a type of polygon mesh geometry that can express complex geometries by combining tetrahedrons ofvarying sizes.
PHITS adopts two tetrahedron geometry formats. One is the format for the tetrahedral mesh generator, TetGenand the other is the format for the finite element analysis program NASTRAN.
The TetGen format is represented by two files:• the node file (a list of the xyz space coordinates of the tetrahedron nodes);• the element file (a list of four nodes IDs for each tetrahedron element).
In PHITS, the node and the element files have a common name with diﬀerent suﬃxes—“.node” and “.ele,” respectively: please refer to the ppt file or sample input file in \phits\utility\TetraGEOM\ for a more detailed
explanation.
Examples of a node file and an element file are given below.
Example 41: Example of node file
1:
2:
3:
4:
5:
6:
7:
8:

# Simple two elements
5
3 0 0# pointID x y z
10.0 -2.5 -4.0
2
-4.0 -2.5
0.0
3
4.0 -2.5
0.0
4
0.0 -2.5
4.0
5
0.0
2.5
0.0

The node file begins with the number of nodes and the number of dimensions (second line). PHITS operates onlyin 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]Example 42: Example of element file4.6 [ Cell ] section

1:
2:
3:
4:
5:

139

# Simple two elements
2 4 1# elementID point(1:4) universe
1
1 2 3 51001
2
5 2 3 41002

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 thenode file. The element universe no. specifies the universe used to fill the tetrahedron element; the definition of thisuniverse should be given in the PHITS input file (See Example 43). Arbitrary comment lines starting with # canbe 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 eﬀort. TetGen can be obtained free ofcharge 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 acceptedin 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 isused 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.
Example 43: [cell] section example (12)
1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:

[Material]mat[1] 14N 78.1 16O 20.9 40Ar 0.93
mat[2] 1H 2 16O 1
mat[3] 56Fe 1[Surface]
10 rpp-5.0 5.0 -3.0 3.0 -5.0 5.0
20 rpp-7.0 7.0 -5.0 5.0 -7.0 7.0
90 so
500.0
[Cell]
101
1 -0.001205 -20 U=1 LAT=3 tfile=Tetra
1
0-10 FILL=1
2 -1
10
201
2 -1.0-90 U=1001
202
3 -7.874-90 U=1002

TSFAC=1.0

Example 44: [cell] section example (13)
10:

101

1 -0.001205 -20

U=1

LAT=3

nfile=Tetra

TSFAC=1.0

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4 SECTIONS FORMAT

140

Node 4

Element 1
Node 5

Node 3

Node 2Element 2

Node 1Figure 4.46: Results of the [cell] section example (12) in 3D images.

TFILE. For a file of the NASTRAN bulk data format, the name should be specified accompanied by file NFILE as
in the example 44. The file of the name with the suﬃx .bdf will be imported. Note that the upper and lower casesof the file name diﬀer 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 withcell no. 1 is defined as a rectangular box of dimensions 10 cm × 6 cm × 10 cm. Using the FILL option, thisregion 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; theuniverses 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 43 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 thisoption, 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 suﬃx. The universe no.
and its density should be specified for each line as 45. The addional cells will be provied with the same material no.
as the cell. Error messages as shown in 46 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 definedaccording 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.
Example 45: [cell] Example of txt file1:
2:

1001 -1.01002 -7.874

Example 46: [cell] Example of error message*** ERROR : undefined material
TETRA material (MID): 1001
should be defined as material ID number:*** ERROR : undefined material
TETRA material (MID): 1002
should be defined as material ID number:

5001

5002

4.7 [ Transform ] section

141

4.7 [ Transform ] section
4.7.1 Formats
In this section, the coordinate transform can be defined. Only C and $ can be used as a comment mark. Using[transform], only rotation and translation of the coordinate can be set, and enlarge or shrink cannot be set.
The coordinate transformation defined in this section can be used in [source] section, [surface] section,[cell] section, r-z, xyz mesh of tally and the magnetic field.
Formats and examples are shown below.

[ Transform ]
TRn
O1 O2

O3

B1

B2

B3

B4

B5

B6

B7

B8

B9

M

Table 4.72: Transform definition
itemn
O1 O2 O3
B1 ∼ B9M

explanation
Transform number. Use any number from 1 to 999,999.
∗TRn means that Bi is not a cosine, but an angle [degree].
Transposition vector.
Rotation matrix. Only rotation matrix can be defined. The determinant of the matrix is automatically adjusted to 1.
= 1 means that transposition vector is in sub coordinate system defined in main coordinate system.
= −1 means that transposition vector is in main coordinate system defined in sub coordinate system.
= ±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 transform of M = 2 and −2 isthe same as M = 1 and −1, respectively.

Default values are shown below.

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 aroundz, y, x-axes, respectively. For B4 -B9 , any values, such as zero, should be set.

4.7.2 Mathematical definition of the transform
The mathematical definition in terms of transposition vector and rotation matrix is the following:in the case of M = 1,

4 SECTIONS FORMAT

142

 ′   x   B1
 ′   y  =  B4
z′
B7

B2
B5
B8

  

B3   x   O1    
B6   y  +  O2   
B9z
O3

in the case of M = −1,
 ′   x   B1 y′  =  B4
 ′  
z
B7

B2
B5
B8

  
B3   x   B1
  
B6   y  −  B2
  
B9
z
B3

B4
B5
B6



B7   O1 
B8   O2 


B9
O3

Here,
B1

=

cos(x′ , x)

B2
B3
B4

=
=
=

cos(x′ , y)cos(x′ , z)cos(y′ , x)

B5
B6

=
=

cos(y′ , y)cos(y′ , z)

B7
B8
B9

=
=
=

cos(z′ , x)cos(z′ , y)cos(z′ , z)

In the case of M = 1, the object used this transform function is rotated and then translated. On the other hand, inthe 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.

4.7.3 Examples (1)Example 47: [transform] section example (1)
1:
2:
3:
4:
5:
6:
7:
8:
9:

[ Transform ]*tr1
0.0000000E+00
1.3500000E+02
9.0000000E+01
2.2500000E+02*tr20.0000000E+00
3.0000000E+02
9.0000000E+01
3.0000000E+01

0.0000000E+00
9.0000000E+01
0.0000000E+00
9.0000000E+01
0.0000000E+00
9.0000000E+01
0.0000000E+00
9.0000000E+01

1.4000000E+03
4.5000000E+01
9.0000000E+01
1.3500000E+02
2.5800000E+03
2.1000000E+02
9.0000000E+01
3.0000000E+02

1

1

In this example, tr1 rotates the coordinate by 135 degrees around y axis, and transports 140 cm to z direction,
while tr2 rotates 300 degrees around y axis, and transports 258 cm to z direction. Because of TRn with ∗, angles(in units of degree) directly are given for Bi , (i = 1, . . . , 9).

4.7.4 Examples (2)Example 48: [transform] section example (2)
1:
2:
3:
4:
5:
6:
7:
8:
9:

[ Transform ]set: c10[90] $ angle of around Z (degree)
set: c20[30] $ angle of around Y (degree)
set: c30[0]$ angle of around X (degree)
tr1

0 0 0
cos(c10/180*pi)*cos(c20/180*pi)
sin(c10/180*pi)*cos(c30/180*pi)+cos(c10/180*pi)*sin(c20/180*pi)*sin(c30/180*pi)
sin(c10/180*pi)*sin(c30/180*pi)-cos(c10/180*pi)*sin(c20/180*pi)*cos(c30/180*pi)

4.7 [ Transform ] section

10:
11:
12:
13:
14:
15:
16:

143

-sin(c10/180*pi)*cos(c20/180*pi)
cos(c10/180*pi)*cos(c30/180*pi)-sin(c10/180*pi)*sin(c20/180*pi)*sin(c30/180*pi)
cos(c10/180*pi)*sin(c30/180*pi)+sin(c10/180*pi)*sin(c20/180*pi)*cos(c30/180*pi)
sin(c20/180*pi)-cos(c20/180*pi)*sin(c30/180*pi)
cos(c20/180*pi)*cos(c30/180*pi)
1

In this example, tr1 rotates the coordinate by c10 degrees around z axis, c20 degrees around y axis and finallyc30 degrees around x axis. By setting c10, c20, c30, the rotation can easily be defined.
Example 49: [transform] section example (3)
1:
2:
3:

[ T r a n s f o r m ]*tr1
0 0 0 90300
tr2
0 0 0 pi/2 pi/6 0

0 0 0 0 0 0
0 0 0 0 0 0

2
2

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.

4 SECTIONS FORMAT

144

4.8 [ Temperature ] section
Free-Gas Thermal Temperature [MeV] can be defined in this section. This section corresponds to TMP cardbut the time definition can be set. This value can be set in the [cell] section. If the temperature is double defined,
temperatures defined in this [temperature] sections are used. If no definition, the default value 2.53 × 10−8 MeV
is used.

[ Temperature ]reg
1
11( { 2 - 5 } 8 9 )( 11 12 15 )
16
....
....

tmp
1.0*1.e-8
5.0*1.e-8
2.0*1.e-8
3.0*1.e-8
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.

4.9 [ Mat Time Change ] section

145

4.9 [ Mat Time Change ] section
By this section, you can change the material of certain cells to the other material as a function of time. Thisfunction is useful to describe a shutter of beam line, T0 chopper and the other devices for neutron optics. The unitof time is nsec.

[ Mat Time Change ]
mat
time
1
50.0
2
100.0
3
1000.0....
........
....
........

change11
120

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 tovoid 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.

4 SECTIONS FORMAT

146

4.10 [ Magnetic Field ] section
4.10.1 Charged particle
A magnetic field can be set in the PHITS calculation. To use this function for electron and positron, set EGS5
mode.
Cell number (reg), magnetic field type (typ), half distance of magnets (gap)[cm], magnetic field intensity(mgf), transformation (trcl) and time dependence (time) should be defined in this section. Setting imagnf=1 in
the [parameters] section enables simulation of particle transport in the magnetic field.

[ Magnetic Field ]
reg
typ
1
4
2
4
3
2
4
2
( 150 < 61 )4
( 150 < 62 )4
( 150 < 63 )4
( 150 < 64 )4
( 150 < 65 )4
( 150 < 66 )
4
...
...
...
...

gap
10.00000
10.00000
10.00000
10.00000
13.00000
13.00000
13.00000
13.00000
13.00000
13.00000........
........

mgf-5.956540
6.416140-7.611980
3.516000
7.880140-7.440800
9.441010-8.295220
3.694830-2.099350........
........

trcl
3
1
0
0
2
2
2
2
2
2
...
...

time
non
non
0.0
pi/2
non
non
non
non
non
non
...
...

The column of trcl is omitted. The zero for trcl means no transformation. The time is a parameter of user definedtime 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 timedependent 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 quadrupoleelectromagnet, respectively. mgf denotes the strength of the magnetic field [kG], and trcl is the coordinatetransformation 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 diﬀerent 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 isavailable 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 directionof 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 topositive direction of z-axis. The coordinate transformation by trcl is needed for diﬀerent geometrical situation.
When specifying charge number of the projectile particle with izst in [source] section, the motion of theparticle with the number in the magnetic field is described. Using izst, PH I TS can simulate the motion of theparticle 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 aﬀected by the value of izst; the charge ofthe 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.

4.10 [ Magnetic Field ] section

147

4.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
1
60
0.00000
261
0.00000
3106
5.00000
4104
0.00000
5102
0.00000
6101
3.00000
7103
0.00000...
...
........
...
...
........

mgf
35000.035000.07130.03.5
0.20
7130.035000.0........
........

trcl
3
1
0
0
0
2
0
...
...

polar
non
1
0
non
non
1
-1
...
...

time
non
non
non
5.0
non
non
non
...
...

We cannot take into account of the gravity nor additional dipole magnet. For 60 case, it is assumed that the spinalways 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, theeﬀects of the gravity and additional dipole field can be taken into account. 106 is sextupole, 104 quadrupole, and102 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 datameasured by the neutron optics group in JAERI are read from the file and used the calculation. The strength of thisfield 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, theinitial spin is defined at the moment when the neutron goes into the magnetic field. The ratio of the number ofparallel 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 asP=ϕ+ − ϕ−,ϕ+ + ϕ−here, ϕ+ and ϕ− are the number of the parallel and anti-parallel particles.

4 SECTIONS FORMAT

148

4.10.3 Implementation of the magnetic field map
Since version 3.10, PHITS can read arbitrary magnetic fields given in the xyz or r-z grid data. The example of[magnetic field] for reading the magnetic field map is below:[ Magnetic Field ]
reg
typ
gap
101
-1
10.0
102
-2
100.0
103
-3
10.0
104
-4
1.0

mgf
0.5
3.0
10.0
1.0

trcl
0
0
0
1

file
xyzlist.dat
rzlist.dat
xyzmap.dat
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 4.73. (see Sec. 4.10.4 in more detail):
Table 4.73: Available types of magnetic fieldtyp−1 or −101
−2 or −102
−3 or −103
−4 or −104

explanation
xyz grid, data list typer-z grid, data list typexyz grid, data map typer-z grid, data map typeThe meanings of gap and mgf are diﬀerent 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 positronstep sizes in the magnetic field are automatically determined irrelevant to gap. Name of the magnetic field map
file is specified by file parameter.

4.10 [ Magnetic Field ] section

149

4.10.4 Format of magnetic field map file
The magnetic field map file should consist of the header and data parts. In the header part, comment remarks
can be inserted using # and $ in similar to the PHITS input file. Examples of the magnetic field map files together
with the PHITS input files to read them are included in \phits\utility\magmap folder.

Header format
In the header part, discrimination between lowercase and uppercase characters is not performed, and blankis ignored in the same as PHITS input. Only one parameter can be specified in one line. Table 4.74 shows theparameter list to be specified in the header part:
Table 4.74: parameter list in the header partparameter
nx
ny
nz
nr
xmin
xmax
ymin
ymax
zmin
zmax
rmin
rmax
ibxmapibymapibzmapibrmapextendx
extendyextendz
data

explanation
number of x grid (only for typ=-1 & -3, not omissible)
number of y grid (only for typ=-1 & -3, not omissible)
number of z grid (only for typ=-1 & -3, not omissible)
number of r grid (only for typ=-2 & -4, not omissible)
minimum value of x grid in cm (only for typ=-3，D=0)
maximum value of x grid in cm (only for typ=-3, not omissible)
minimum value of y grid in cm (only for typ=-3，D=0)
maximum value of y grid in cm (only for typ=-3, not omissible)
minimum value of z grid in cm (only for typ=-3 & -4，D=0)
maximum value of z grid in cm (only for typ=-3 & -4, not omissible)
minimum value of r grid in cm (only for typ=-4，D=0)
maximum value of r grid in cm (only for typ=-4, not omissible)
existence of the Bx map (yes=1, no=0) (only for typ=-3, D=1)
existence of the By map (yes=1, no=0) (only for typ=-3, D=1)
existence of the Bz map (yes=1, no=0) (only for typ=-3 & -4, D=1)
existence of the Br map (yes=1, no=0) (only for typ=-4, D=1)
extend the field to negative x (only for typ=-1 & -3, omissible)
extend the field to negative y (only for typ=-1 & -3, omissible)
extend the field to negative z (for all typ, omissible)
End of header.

If you want to flip the direction of magnetic field in
the extended field, you have to write e.g. flip=bx, bz,
where bx and bz indicate the direction of magnetic field tobe flipped. For example, if you set:
extendx flip = bz
extendy flip = bz
the magnetic field for z-direction (Bz ) is flipped as shownin the Fig. 4.47. Note that the magnetic fields for x and y
directions are not flipped in this case.

Figure 4.47: Example of the extended magnetic fieldwith the flip command4 SECTIONS FORMAT

150

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 gridshould be given instead of that at the center of each grid-mesh. The followings are the format of each field type:• typ=-1: xyz grid, data list type
x1
x1
..
.

y1
y1
..
.

z1
z2
..
.

Bx1,1,1
Bx1,1,2..
.

By1,1,1
By1,1,2..
.

Bz1,1,1
Bz1,1,2
..
.

x1
x1
..
.

y1
y2
..
.

znz
z1
..
.

Bx1,1,nz
Bx1,2,1..
.

By1,1,nz
By1,2,1..
.

Bz1,1,nz
Bz1,2,1
..
.

x1
x2
..
.

yny
y1
..
.

zny
z1
..
.

Bx1,ny,nz
Bx2,1,1..
.

By1,ny,nz
By2,1,1..
.

Bz1,ny,nz
Bz2,1,1
..
.

xnx

yny

zny

Bxnx,ny,nzBynx,ny,nzBznx,ny,nz• typ=-2: r-z grid, data list type
r1
r1
..
.

z1
z2
..
.

Br1,1
Br1,2
..
.

Bz1,1
Bz1,2

r1
r2
..
.

znz
z1
..
.

Br1,nzBr2,1..
.

Bz1,nz
Bz2,1

rnr

znz

Brnr,nzBznr,nz• typ=-3: xyz grid, data map typeBx1,1,1
Bx2,1,1..
.

Bx1,2,1
Bx2,2,1..
.

Bx1,3,1
Bx2,3,1..
.

Bxnx,1,1
Bx1,1,2..
.

Bxnx,2,1
Bx1,2,2..
.

Bxnx,3,1
Bx1,3,2
..
.

···
···
..
.

···
···
..
.

Bx1,ny,1
Bx2,ny,1..
.
Bxnx,ny,1
Bx1,ny,2..
.

Bxnx,1,nz Bxnx,2,nz Bxnx,3,nz · · · Bxnx,ny,nz(continue the data for By and Bz in the same format)

4.10 [ Magnetic Field ] section151• typ=-4: r-z grid, data map type
· · · Br1,nz· · · Br2,nz
..
..
.
.
Brnr,1 Brnr,2 Brnr,3 · · · Brnr,nz(continue the data for Br in the same format)
Br1,1
Br2,1
..
.

Br1,2
Br2,2
..
.

Br1,3
Br2,3
..
.

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 theascending 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.

4 SECTIONS FORMAT

152

4.11 [ Electro Magnetic Field ] section
Uniform electric and magnetic fields in any region can be set. Defining parameters in this section and setting
ielctf=1 in [parameters] section, PHITS can simulate a motion of a charged particle in the fields. To use thisfunction for electron and positron, set EGS5 mode.
Both the electric and magnetic fields can be set. It is noted that a quadrupole magnet cannot be defined, unlike
the case of [Magnetic Field] section.
Cell number (reg), strength of the electric and magnetic fields (elf and mgf, respectively), direction of thetwo fields (trcle and trclm) should be defined. Units of elf and mgf are kV/cm and kGauss, respectively. The
coordinate transformation number trcl, which are defined in [transform] section, should be set to trcle andtrclm. When trcle is 0, the direction of the electric field is positive direction of x-axis. When trclm is 0, thedirection of the magnetic field is positive direction of y-axis. trcle and trclm are not omissible. In the case that
there is no need to When setting elf or mgf to 0, or not using the transformation, trcle and trclm should be set
to 0. Set the parameters as follows.

[ Electro Magnetic Field ]
reg
elf
mgf
trcle
1
100
1
1
2
100
1
1

trclm
2
2

When specifying charge number of the projectile particle with izst in [source] section, the motion of theparticle 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 aﬀected by the value of izst; the charge ofthe 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 continuouly changes particles’ momenta. Please adjust deltm to describe the trajectory curve more smoothly.

4.12 [ Delta Ray ] section

153

4.12 [ Delta Ray ] section
In this section, you can set parameters used in the function to generate knocked-out electrons so-called δrays, which are produced along the trajectory of a charged particle in materials, as secondary particles. In the
PHITS calculation, an energy transfer to the material is estimated by Linear Energy Transfer (LET; dE/dx), andis assumed to be deposited only on the particle trajectory. However, it is well known that owing to a high energy
δ-ray the energy deposition is spread far away from the orbit of the primary particle. You can take the eﬀect of
δ-rays into account using this function. The production cross sections of δ-rays from those particles in liquid water
were calculated using the model proposed by Butts and Katz, 48 considering the relativistic collision dynamics.
This function shouldn’t be used together with [t-sed] tally.
You can set a threshold energy Eth (MeV) for each region except outer void to control the production of δrays. As the secondary particle, δ-rays with energies above Eth are explicitly generated and transported. For lower
energies than Eth , the deposition energies from δ-rays are included in LET. A minimum energy of Eth you can
set is 0.001MeV (= 1keV). It is noted that in case of very low Eth or setting of a material thiner than 10µg/cm2 ,a behavior of the charged particle slightly changes. This is because the eﬀective stopping power of the charged
particles becomes smaller than its real value due to too many delta-ray productions. A default value of Eth is
1.e + 10, i.e. δ-rays are not produced in the PHITS calculation except for setting the Eth parameter in this section.
The region number and Eth are given by reg and del, respectively. Set these parameters as follows.
[ 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 numericvalue. You cannot use the lattice and universe style as ( 6 < 10[1 0 0] < u=3 ). If you want to replace theorder 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).

4 SECTIONS FORMAT

154

4.13 [ Track Structure ] section
Performing the track-structure simulation 49 for electrons or positrons of low energy below 1 keV, those deceleration processes caused by much collision events for ionization, excitation, and molecular vibration and rotation
can be calculated precisely. Currently, the cross sections only for liquid water are prepared in PHITS, and thosefor other materials are simply obtained from electron density scaling based on the data. The track-structure simulation takes so long time that we cannot recommend to activate this mode in a conventional-scale particle transport
simulation (cm orders) due to much production of low energy electrons around 10 eV. Please take cares that the
track-structure mode can be adapted only to [t-track] and [t-deposit] tallies.
In this section, you have to specify the cells where you would like to perform track-structure simulation. mID
represents the index of the cross sections database used in the track-structure simulation, and currently you canselect only 0 (no track structure simulation) or 1 (track structure simulation using the database of liquid water). If
you will activate mID = 1, mean free paths of the particles in target materials are derived from electron density
scaling based on the database for liquid water. We are planning to prepare the cross section databases for othermaterials in future.

[track structure]
reg mID1
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 numericvalue. You cannot use the lattice and universe style as ( 6 < 10[100] < u=3 ). If you want to replace theorder 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 useof 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

49 T. 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).

4.14 [ Super Mirror ] section155

4.14 [ Super Mirror ] section
The reflection of low energy neutron by super mirror is defined by this section. We assume the following
empirical formula to describe the reflectivity of the super mirrors.
{R
if Q ≤ Qc
R = 10
(1
(1
R
−
tanh
[(Q
−
mQ
)/W])
−
α(Q
−
Q
))
if
Q > Qc0cc2where Q is the scattering vector (in Å−1 ) defined by
Q = |ki − k f | =4π sin θ.
λ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, thereflectivity starts falling linearly with a slope α until a cutoﬀ at Q = mQc . The width of the cutoﬀ is denoted W.
These parameters are defined as[ Super Mirror ]
r-in
r-out
{2001-2020}
3001
2500
3500
2600
3600
....
....
....
....
....
....

mm
3
3
3
..
..
..

r0
qc
am
0.99 0.0217 3.0
0.99 0.0217 3.0
0.99 0.0217 3.0
...
....
...
...
....
...
...
....
...

wm
0.003
0.003
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 wmin Å−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.

4 SECTIONS FORMAT

156

4.15 [ Elastic Option ] section
In this section, you can set some parameters for user defined elastic option for low energy neutrons. By thisfunction, you can change angle distributions of elastic collisions of data based neutron reactions. We prepare two
sample routines, “usrelst1.f” and “usrelst2.f.” You can choose one of these two by usrelst=1, 2 in the parameter
section. You should define the regions to which this function is applied and 4 parameters as,[ Elastic Option ]
reg
1
2
3
....
....

c1
5
1
3
...
...

c2
1
1
1
...
...

c3
3.3
1.1
0.3
...
...

c4
0.4
0.7
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 typeof angular distribution described by an analytic formula.

4.16 [ Data Max ] section

157

4.16 [ Data Max ] section
dmax(i), which is the maximum energy of library use for i-th particle, can be defined for each nucleus inmaterials in this section. Maximum 6 [Data Max] sections are allowed to be used in a input file.
[Data Max]
part = neutron protonmat
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 andall 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, youdefine 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 areshown in the output file, file(6) (D=phits.out).

4 SECTIONS FORMAT

158

4.17 [ Frag Data ] section
The function to read user defined cross sections can be defined in the [frag data] section. By using thisfunction, you can simulate nuclear reaction events in the calculation on the basis of information given by the crosssection data. It is noted that nuclear data libraries are preferentially used, even in the case of a nuclear reaction you
specify in this section. You can set only proton, neutron, and nuclei as incident particles. Photons and elections
cannot be used. Elastic scattering events for nucleons are separately considered by the default model implemented
in PHITS.
Because weight values of the secondary particles produced by this option change from 1.0, you should decrease
the value of the cutoﬀ weight parameter wc2(i) in the [parameters] section.
Set the parameters as follows.

[ Frag Data ]
opt
proj
0
12C
1
proton
....
...
....
...

targ
16O
63Cu
...
...

file
DDX_12C-16O.dat
DDX_p-63Cu.dat
...
...
...
...

The user defined cross sections are not used when opt=0. In the case of opt=1, PHITS reproduces the crosssection 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 thecase 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
targetneiein(1) ein(2) ein(3) ...... ein(nei+1)
totxs(1) totxs(2) totxs(3) ...... totxs(nei+1)
neoeout(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)
proxs(1,1) proxs(1,2) proxs(1,3) ...... proxs(1,nfrg)
ddx(1,1,1,1) ddx(1,1,1,2) ddx(1,1,1,3) ...... ddx(1,1,1,nag)ddx(1,1,2,1) ddx(1,1,2,2) ddx(1,1,2,3) ...... ddx(1,1,2,nag).........
ddx(1,1,neo,1) ddx(1,1,neo,2) ddx(1,1,neo,3) ...... ddx(1,1,neo,nag)ddx(1,2,1,1) ddx(1,2,1,2) ddx(1,2,1,3) ...... ddx(1,2,1,nag)ddx(1,2,2,1) ddx(1,2,2,2) ddx(1,2,2,3) ...... ddx(1,2,2,nag).........
ddx(1,2,neo,1) ddx(1,2,neo,2) ddx(1,2,neo,3) ...... ddx(1,2,neo,nag).........
.........

4.17 [ Frag Data ] section

159（continued）

ddx(1,nfrg,1,1) ddx(1,nfrg,1,2) ddx(1,nfrg,1,3) ...... ddx(1,nfrg,1,nag)ddx(1,nfrg,2,1) ddx(1,nfrg,2,2) ddx(1,nfrg,2,3) ...... ddx(1,nfrg,2,nag).........
ddx(1,nfrg,neo,1) ddx(1,nfrg,neo,2) ddx(1,nfrg,neo,3) ...... ddx(1,nfrg,neo,nag)proxs(2,1) proxs(2,2) proxs(2,3) ...... proxs(2,nfrg)
ddx(2,1,1,1) ddx(2,1,1,2) ddx(2,1,1,3) ...... ddx(2,1,1,nag)ddx(2,1,2,1) ddx(2,1,2,2) ddx(2,1,2,3) ...... ddx(2,1,2,nag).........
ddx(2,1,neo,1) ddx(2,1,neo,2) ddx(2,1,neo,3) ...... ddx(2,1,neo,nag).........
.........
.........
.........
proxs(nei+1,1) proxs(nei+1,2) proxs(nei+1,3) ...... proxs(nei+1,nfrg)
ddx(nei+1,1,1,1) ddx(nei+1,1,1,2) ddx(nei+1,1,1,3) ...... ddx(nei+1,1,1,nag)ddx(nei+1,1,2,1) ddx(nei+1,1,2,2) ddx(nei+1,1,2,3) ...... ddx(nei+1,1,2,nag).........
ddx(nei+1,1,neo,1) ddx(nei+1,1,neo,2) ddx(nei+1,1,neo,3) ...... ddx(nei+1,1,neo,nag).........
.........
ddx(nei+1,nfrg,1,1) ddx(nei+1,nfrg,1,2) ddx(nei+1,nfrg,1,3) ...... ddx(nei+1,nfrg,1,nag)ddx(nei+1,nfrg,2,1) ddx(nei+1,nfrg,2,2) ddx(nei+1,nfrg,2,3) ...... ddx(nei+1,nfrg,2,nag).........
ddx(nei+1,nfrg,neo,1) ddx(nei+1,nfrg,neo,2) ddx(nei+1,nfrg,neo,3) ...... ddx(nei+1,nfrg,neo,nag)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 ofenergy mesh points of the outgoing particles. In the next line, you set neo+1 points of the energy (eout in the unitof MeV/u), and then in the next next line you set neo+1 data of total reaction cross sections (totxs in the unit ofmb). 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 theangles 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 isdegree. 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 diﬀerential 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.
Example 50: example of data file of user defined cross sections
1:
2:
3:
4:
5:
6:
7:
8:
9:

proton
63Cu
1
10.0
100.0
1000.0 500.03
1.0 10.0 50.0-6
0.0 30.0 60.0

100.0
90.0

120.0

150.0

180.0

4 SECTIONS FORMAT

160

10:
11:
12:
13:
14:
15:
16:
17:
18:
19:

1
neutron
300.0
10.0 10.0
15.0 13.0
10.0 11.0
0.0
5.0
5.0
10.0
8.0
5.0
6.0

10.0
12.0
10.0

10.0
11.0
11.0

10.0
10.0
10.0

10.0
10.0
10.0

5.0
7.0
5.0

5.0
6.0
6.0

5.0
5.0
5.0

5.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 ofincident 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 ofdegree. 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 diﬀerential crosssections 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.

4.18 [ Importance ] section

161

4.18 [ Importance ] section
The importance for GG cell can be defined in this section. If the importance is not defined, it is set as 1.0.
Maximum 6 [importance] sections are allowed to be defined in an input file.

[ Importance ]part = protonreg
1
11( { 2 - 5 } 8 9 )( 11 12 15 )( 6<10[1 0 0]<u=3 )
....
....

neutronimp
1.000000
5.000000
2.000000
3.000000
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 cellat bottom level can be defined by above format. By using the format, we can define diﬀerent importance into eachlattice. 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:
2:
3:
4:
5:
6:

[ Importance ]reg( 5 6 7 < 11 )( 5 6 7 < 12 )( 5 6 7 < 13 )( 11 12 13 )

imp
2.0
4.0
8.0
1.0

1:
2:
3:
4:
5:
6:

[ Importance ]reg( 5 6 7 )
11
12
13

imp
1.0
2.0
4.0
8.0

or

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.

4 SECTIONS FORMAT

162

4.19 [ Weight Window ] section
The weight window function can be defined in this section. Maximum 6 [weight window] sections areallowed to be defined in a input file.

[ Weight Window ]mesh = regpart = proton neutroneng = 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
110.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. 5.
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, eachnucleus 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 forwwi 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, theposition 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.

4.20 [ WW Bias ] section

163

4.20 [ WW Bias ] section
In the [ww bias] section, minimum values of the weight window defined in [weight window] can be biased for certain regions. This option is useful when the [weight window] parameters for a certain region arebiased after automatically generating the [weight window] section by [t-wwg]. Figure 4.48 shows a flowchart
how to perform the transport calculation using [weight window] and [ww bias]. First, generate the [weightwindow] section by [t-wwg]. If the obtained parameters of [weight window] are enough to eﬀectively use thevariance reduction technique, the [ww bias] section is not needed. However, if they are not enough, the variancereduction technique can be used more eﬀectively by biasing the [weight window] parameters for a certain region
with [ww bias]. There are two methods to set the [ww bias] section; an automatic method using [t-wwbg],
which is a Weight Window Bias Generator (WWBG), and a manual method by a user, which will be explained
below. For details of [t-wwbg], see Sec. 6.16. When performing a transport calculation with [ww bias] and[weight window], set icntl=0 and iwwbias=1 in [parameters].
Set [weight window]
・With setting [t-wwg], perform

Set [ww bias]
・With setting [t-wwbg], performa normal calculation (icntl=0).

a sample calculation (icntl=15).

([weight window] is automatically set.)([ww bias] is automatically set.)or・Set [ww bias] manually.

Transport calculation with [weight window] and [ww bias]
・Set [weight window] and [ww bias] in the same input ﬁle.
・Execute PHITS with icntl=0 and iwwbias=1 in [parameters].

Figure 4.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 = neutroneng = 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. Eachnuclides cannot be specified. Next, the energy mesh should be defined. The line starting with eng= specifies thenumber 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 thecolumns of wwbi. The skip operator non can be used. Each wwbi column corresponds to energies of ei−1 < E < ei .

4 SECTIONS FORMAT

164

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 thedefined biases in [ww bias] are used. In this case, the products of the multiplication are output in the input echoof [weight window], and [ww bias] with off is output. If an input file without [ww bias] is used, all valuesof [ww bias] in the input echo are set to 1.
An example of [ww bias] is as follows.

Example 51: Example of [ww bias]
1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:

[ WW Bias ]part = neutroneng = 11.00000E+05
reg
1
2
3
4
5
6
7
8
9
10
11
12

wwb1
1/7
1/6
1/5
1/4
1/3
1/2
1
2
3
4
5
6

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.

4.20 [ WW Bias ] section

165

Figure 4.49(a) shows the xz cross-section view of a geometry; a concrete cylinder with a central axis on the zaxis with a radius of 100cm. Two results of the neutron fluence obtained by the transport calculation without andwith [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], theresult 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 cellnumbers. On the other hand, the fluence in Fig. (c) was distributed in only the large cell numbers, which wereDate = 13:14 16-Aug-2017
File = D:\home\hashimoto\STUDY\houkoku\phits\manual\tex\old-file\WWBG\WWBias\geometry\weight-dose-xz-g.out[t-track] in xyz meshto focus on a certain region, the calculation canbiased by [ww bias] of the example 51. As seen in this example,
be eﬃciently performed by [ww bias].
emin = 1.0000E-10 [MeV](a) Geometry

emax = 1.0000E+03 [MeV]ymin = -2.0000E+01 [cm]ymax = 2.0000E+01 [cm]part. = neutron
mset = 1100

x [cm]

50

0

1

2

3

4

5

6

8

7

9

10

11

void

12

1

−50

−100

Date = 13:17 16-Aug-2017
File = D:\home\hashimoto\STUDY\houkoku\phits\manual\tex\old-file\WWBG\WWBias\without-bias\weight-dose-xz-n.out
File = D:\home\hashimoto\STUDY\houkoku\phits\manual\tex\old-file\WWBG\WWBias\with-bias\weight-dose-xz-n.out

50100
z [cm]

emin = 1.0000E-10 [MeV]emax = 1.0000E+03 [MeV] (c) With [WW Bias]ymin = -2.0000E+01 [cm]ymax =100
2.0000E+01 [cm]part. = neutron
mset = 1

calculated
by PHITSBias]
2.95(b) Without
[WW

100
10−3
10−4

0

1

2

3

4

5

6

7

8

9

10

11

12

10−6
10−7
10−8

−50

10−3
10−4
10−5

x [cm]

x [cm]

10−5emin = 1.0000E-10 [MeV]emax = 1.0000E+03 [MeV]ymin = -2.0000E+01 [cm]ymax = 2.0000E+01 [cm]part. = neutron
mset = 1

plotted by ANGEL 4.35

50(µSv/h)/(source/sec)

50

Date = 13:17 16-Aug-2017[t-track] in xyz mesh

150

10−6

0

1

2

3

4

5

6

7

8

9

10

11

12

10−7

(µSv/h)/(source/sec)[t-track] in xyz 0mesh

10−8

−50
10−9

10−9

10−10

−100

calculated by PHITS 2.95

10−10

0

50

100
z [cm]

150−100

calculated by PHITS 2.95

0

50

100
z [cm]

150

plotted by ANGEL 4.35

Figure 4.49: (a) xz cross-section view of the geometry. (b) Result without [ww bias]. (c) Result with [wwbias] of Example 51.

plotted by ANGEL 4.35

4 SECTIONS FORMAT

166

4.21 [ Forced Collisions ] section
The forced collisions are used for improving tally statistics or thin target analysis by enlarging the collision
probabilities. When specified particle comes into a region defined as the forced collision region, the particle isdivided into two particles. One has a weight by (penetration probability) × (its weight), this particle pass throughto the next region. The other has a weight of (1 - penetration probability) × (its weight), and it is forced to collidewith a target in the region. The collision point is randomly determined according to cross sections. Regions andfactors for the forced collisions can be defined in this section. Non-defined regions are set factor zero.
Maximum 6 [forced collisions] sections are allowed to be defined in an input file.

[ Forced Collisions ]part = proton neutron
reg
fcl
1
1.000000
110.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 theskip 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 diﬀerent forced collision factor for each lattice. If the same cell is re-defined, thevalue, 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 oﬀ in theforced collisions region. When f cl < 0, secondary particles produced by forced collisions are treated by thenormal process. In this case, weight cut oﬀ is not performed. When f cl > 0, the forced collision is also applied
to secondary particles. In this case, weight cut oﬀ is performed. Even if a particle is killed by this weight cut oﬀ,
of course the particle is tallied before killed. There is a possibility that all particles are killed by this weight cut
oﬀ, if you set the weight cut oﬀ and the forced collisions without consideration. For example, it corresponds totallying 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 ofthe cutoﬀ weight parameter wc1(i) in the [parameters] section.

4.22 [ Volume ] section

167

4.22 [ Volume ] section
Volume for GG cell (cm3 ) can be defined in this section. If the volume is double defined, the value defined inthis section is used. The volume is utilized in the tally sections. If you do not set volume, it has 1.0 cm3 volume.

[ Volume ]reg
1
11( { 2 - 5 } 8 9 )( 11 12 15 )
16
....
....

vol
1.000000
5.000000
2.000000
3.000000
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.

4 SECTIONS FORMAT

168

4.23 [ Multiplier ] section
In the [multiplier] section, multiplier sets consisting of factors that depend on particle energies can be set
as multipliers of [t-track], [t-cross], [t-point] tally results. To use this function, the multiplier subsectionsin the tally section must be defined. For example, this function can be used for dose estimation using any doseconversion factor.
Only one multiplier set can be defined per [multiplier] section; a maximum of 100 [multiplier] sections
that can be defined in an input file. The format of this section is given as follows.

[ 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.010.55
2000.010.98
5000.012.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 coeﬃcients for several types of radiation doses and soft error rate (SER)
on semiconductor devices are pre-defined. Table 4.75 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 fork = −200). The unit of conversion coeﬃcients 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 coeﬃcients for SER are derived from the neutron-induced SEU cross section for a virtual semiconductor 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
coeﬃcients 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
downloaded from http://phits.jaea.go.jp/expacs

4.23 [ Multiplier ] section

169

Table 4.75: Pre-defined conversion coeﬃcients.
Multiplier ID
-200
-201
-202
-203
-204
-210
-211
-212
-213
-214
-215
-216
-299

Data informationH ∗ (10)52
Eﬀective dose based on ICRP60 (AP irradiation)53
Eﬀective dose based on ICRP103 (AP irradiation)54
Eﬀective dose based on ICRP103 (ISO irradiation)54
New operational quantity H ∗ (Maximum eﬀective dose among the all irradiation conditions54
Sex-averaged eﬀective dose equivalent (ISO irradiation)55
Eﬀective dose equivalent for male (ISO irradiation)55
Eﬀective dose equivalent for female (ISO irradiation)55
Dose equivalent for male red-bone marrow (ISO irradiation)55
Dose equivalent for female red-bone marrow (ISO irradiation)55
Dose equivalent for male skin (ISO irradiation)55
Dose equivalent for female skin (ISO irradiation)55
Soft error rate on semiconductor device (ISO irradiation)56

4.23.1 Multiplier subsection
The multiplier option of the tally section is used to define a multiplier set following the basic format (C k),where C is a normalization factor and k is the ID number of the set (note that k should be negative). The format of
the multiplier subsection is given as follows.

multiplier = number of materialpart = neutron
emax = 1000
mat
mset1
mset2
1
( 1
-201 ) ( 2 -202 )2( 1.2 -201 ) ( 3 -202 )
....
....
....
....
....
....
....
....

The line starting with multiplier= specifies the number of materials for which multiplication is considered; allcan 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 isthe 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 resultof each set is printed out. Although several multiplier subsections can be defined in one tally section, the numberof multiplier sets should be constant across subsections.
Some parameter sets built-in PHITS can be used. If you set k = −1, a value of 1/weight is used as the multiplication factor. 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 /phits/data/multiplier/directory without specifying the [multiplier] section in the input file. Currently, the databases of the conversion
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 coeﬃcients 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).

4 SECTIONS FORMAT

170

coeﬃcients for several types of radiation doses are included in the directory (see Table 4.75 in detail). The unit ofthe dose conversion coeﬃcients 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
coeﬃcients 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 eﬀective 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 thismethod is not recommended anymore because the corresponding doses can be calculated by k = −201. Note thatthe unit of these dose conversion coeﬃcients is (µSv/h)/(n/sec/cm2 ), i.e. the doses in the unit of µSv/h can bedirectly calculated when the calculated fluence is normalized to the unit of /cm2 /sec. It should be noted that theinterpolation 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.

multiplier = number of materialpart = proton
emax = 150
mat
mset1
mset2
1
( 0.1236 1 1 -4 ) ( 0.0 )2( 0.0060 2 1 -4 ) ( 0.0 )3( 0.0032 3 1 -4 ) ( 0.0 )
....
....
....
....
....
....
....
....
multiplier = number of materialpart = neutron
emax = 150
mat
mset1
mset2
1
( 0.1236 1 1 -4 : -6 -8 ) ( 1.0 -1 33 0.543 )2( 0.0060 2 1 -4 : -6 -8 ) ( 1.0 -1 34 0.321 )3( 0.0032 3 1 -4 : -6 -8 ) ( 1.0 -1 35 0.678 )
....
....
....
....
....
....
....
....
In above example, the mset1 is for heat and the mset2 is zero for proton, attenuator set for neutron.

4.24 [ Mat Name Color ] section

171

4.24 [ Mat Name Color ] section
Material names, size and colors for graphical output by [t-gshow] and [t-3dshow] tallies are defined in thissection. By default, the name is set as material number and the color is set automatically.

[ Mat Name Color ]
mat
0
1
2
3
{ 4 - 7 }
....
....

name
void
air
{mat 2}{mat 3}Fe........
........

size
1
0.5
2
2
3

color
lightgrayyellowgreen
orangeyellow{ 0.067 0.600 1.00 }mossgreen

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 inname 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 todefine a name is 80.
When defining two (or more) cells of diﬀerent 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 orangeblue), or HSB numeric H(hue) S (chroma) B(brightness). In the case HSB numeric definition, close each numericby { }. If only one HSB numeric is defined, chroma and brightness are set 1.
Color symbols, names, and HSB numerics are shown from next page.

4 SECTIONS FORMAT

172

Table 4.76: Gray scale
Symbol HSB Output
Name

W
O
K
J
F
E

−1.0
−0.8
−0.6
−0.4
−0.2
−0.0

white
lightgraygraydarkgraymatblack
black

Table 4.77: Color definition by symbols
Symbol HSB Output
Name

R
RR
RRR
Y
YY
YYY
G
GG
GGG
C
CC
CCC
B
BB
BBB

1.000
0.933
0.867
0.800
0.733
0.667
0.600
0.533
0.467
0.400
0.333
0.267
0.200
0.133
0.067

red
orange−yellow
−
−
green
−
−
cyan
−
−
blue
violetmagenta

Table 4.78: Color definition by names and HSB numerics
Name
OutputHSB

darkredredpinkpastelpink
orangebrown
darkbrown
pastelbrownorangeyellow
camel
pastelyellow
yellow
pastelgreen
yellowgreen
green
darkgreenmossgreen
bluegreen
pastelcyan
pastelblue
cyan
cyanblue
blue
violetpurplemagentawineredpastelmagenta
pastelpurple
pastelviolet

1.000 1.000 0.600
1.000 1.000 1.000
1.00 0.500 1.000
0.900 0.500 1.000
0.933 1.000 1.000
0.900 1.000 0.500
0.900 1.000 0.300
0.900 0.600 0.500
0.867 1.000 1.000
0.800 0.700 0.700
0.800 0.700 1.000
0.800 1.000 1.000
0.700 0.600 1.000
0.700 1.000 1.000
0.600 1.000 1.000
0.600 1.000 0.600
0.500 1.000 0.300
0.500 1.000 1.000
0.400 0.400 1.000
0.250 0.400 1.000
0.400 1.000 1.000
0.400 1.000 0.500
0.200 1.000 1.000
0.133 1.000 1.000
0.100 1.000 0.500
0.067 1.000 1.000
0.002 0.800 0.700
0.067 0.600 1.000
0.100 0.400 0.500
0.133 0.400 1.000

4.25 [ Reg Name ] section

173

4.25 [ Reg Name ] section
Region names and their font sizes for graphic output by [t-gshow], [t-rshow], and [t-3dshow] are definedin this section. When you set the gshow or rshow option in the other tallies, this definition is applied. By default,a region name is set to its region number.

[ Reg Name ]
reg
1
2
3
4
{ 5 - 8 }
....
....

name
cover
body
{cell 2}{cell 3}tube........
........

size
1
0.5
2
2
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 isdefined, 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 namedefinition. 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 candefine is 80. You can specify a font size as a relative value to the default size.

4 SECTIONS FORMAT

174

4.26 [ Counter ] section
The counter function can be defined in this section. Three counters can be used in tally sections. The counterbasically counts when
(1) a particle comes into specified region (in)(2) a particle goes out specified region (out)(3) a particle takes scattering (or nuclear reaction) in specified region (coll)(4) a particle reflects back on a certain boundary of the region (ref)You can set one progress value of the counter from -9999 to 9999, or zero set (10000). Counter values are attachedto particles. Secondary particles produced in collisions inherit the counter value of their parent. Capacity of thecounter is from -9999 to 9999. Counter changes only this range. You can set the counter for each particle by using
part= definition, and you can exclude some particles from the counter actions by *part= definition.

[ 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
01
counter = 3
part = 208Pb
regcoll( 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 inout ref. You can use the skip operator non. At least one must be defined in the in out coll ref. If nothingis 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.

4.26 [ Counter ] section

175

From ver. 2.90, by detailed classification for coll, the opportunities shown in Table 4.79 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 statistical decay model (GEM) are chosen.
Table 4.79: Categories of reaction events belonging coll.
Interaction
nucl

Event
elst
iels
fiss

atom
delt
knoe
fluo
auge
brem
phel
cmpt
pprd
anih
rayl
dcay

Explanation
A particle takes nuclear interactions in specified region.
A particle takes elastic scattering in specified region.
A particle takes inelastic scattering in specified region.
A particle takes fission in specified region.
A particle takes atomic interactions and generate secondary particle in specified region.
A particle generates delta-rays in specified region.
An electron or positron generates knock-on electrons in specified region.
A particle generates atomic fluorescence x-rays in specified region.
A particle generates Auger electrons in specified region.
A particle takes bremsstrahlung in specified region.
A particle takes photoelectric eﬀect in specified region.
A particle takes Compton scattering in specified region.
A particle generates electron-positron pair in specified region.
A particle is annihilated in specified region.
A particle takes Rayleigh scattering in specified region.
A particle decays in specified region.

4 SECTIONS FORMAT

176

4.27 [ Timer ] section
The timer function can be defined in this section. The timer controls the time of each particle when (1) aparticle comes into specified region, (2) a particle goes out specified region, (3) a particle takes scattering inspecified region, and (4) a particle reflects back on a certain boundary of the region. You can set the time to bezero(-1), stopped(1) or nothing(0).
[ Timer ]
reg
1
11
....
....
....

in
0
1
....
....
....

out
-1
0
....
....
....

coll
0
0
....
....
....

ref
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 isdefined, 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.

177

5

Common parameters for tallies
PHITS has the following tally functions.

Table 5.1: Tally sections
name[t-track][t-cross][t-point][t-deposit][t-deposit2][t-heat][t-yield][t-product][t-dpa][t-let][t-sed][t-time][t-interact] (formerly named [t-star])[t-dchain][t-wwg][t-wwbg][t-volume][t-userdefined][t-gshow][t-rshow][t-3dshow]

explanation
Particle fluence in a certain region.
Particle fluence crossing at a certain surface.
Particle fluence at a certain point.
Deposit energy in a certain region.
Deposit energies in certain two regions.
Heat generation in a certain region. (Not recommended57 )Residual nuclei yield in a certain region.
Produced particle in a certain region.
Displacement Per Atom (DPA) in a certain region.
LET distribution in a certain region.
Microdosimetric quantity distribution in a certain region.
Time information of particle in a certain region.
Number of interactions occurred in specified regions.
Residual nuclide yields (in combination with DCHAIN-SP).
Output parameters for [weight window].
Output parameters for [ww bias].
Automatic calculation of region volume.
Any quantities that user defined.
2D geometry visualization.
2D geometry visualization with physical quantities.
3D geometry visualization.

Common parameters used in these tallies are described below.

5.1 Geometrical mesh
In the tallies shown by Table 5.1, GG region mesh (reg), r-z scoring mesh (r-z), and xyz scoring mesh (xyz)can be used for geometrical mesh of tallying area. Additionally tetrahedral mesh (tet) can be used for [t-track],[t-deposit], [t-yield], [t-product], and [t-dpa].
You can choose one mesh from:mesh =[ reg,

r-z,

xyz, tet ]5.1.1 Region mesh
The region mesh defined by the cell number can be written by:

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.

5 COMMON PARAMETERS FOR TALLIES

178

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 (format can be used for defining sequential region numbers.

). The following

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 eachlattice 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.

5.1.2 Definition of the region and volume for repeated structures and lattices
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 thisexample, lattices, which from 1 to 2 in s direction, 3 to 6 in t direction, and 1 in u direction, are defined. You canalso specify individually as 160[1 3 4, 2 3 4, 3 3 4]. The style () in one level can be used to combinesome regions. See next example.
Example 52: mesh=reg example (1)
1:
2:
3:
4:
5:
6:

mesh = reg
reg = (all)({ 201 - 205 })( 161 < 160[1:2 3:6 1:1] )( (201 202 203 204) < (161 162 163 ) )( ( 90 100 ) 120 < 61 ( 62 63 ) )This region mesh definition is echoed as
Example 53: mesh=reg example (2)
1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:

mesh = reg# mesh type is region-wise
reg = ( all ) ( { 201 - 205 } ) ( 161 < 160[ 1:2 3:6 1:1 ] ) ( ({ 201 - 204 } ) < ( { 161 - 163 } ) ) ( ( 90 100 ) 120 < 61
( 62 63 ) )volume# combined, lattice or level structure
non
reg
vol
# reg definition
1 100018.1000E+01 # ( all )2 100025.0000E+00 # ( { 201 - 205 } )3 100031.0000E+00 # ( 161 < 160[ 1 3 1 ] )4 10004
1.0000E+00 # ( 161 < 160[ 2 3 1 ] )5 10005
1.0000E+00 # ( 161 < 160[ 1 4 1 ] )6 10006
1.0000E+00 # ( 161 < 160[ 2 4 1 ] )7 100071.0000E+00 # ( 161 < 160[ 1 5 1 ] )8 10008
1.0000E+00 # ( 161 < 160[ 2 5 1 ] )9 10009
1.0000E+00 # ( 161 < 160[ 1 6 1 ] )5.1 Geometrical mesh

16:
17:
18:
19:
20:
21:

10
11
12
13
14
15

10010
10011
10012
10013
10014
10015

179

1.0000E+00 # ( 161 < 160[ 2 6 1 ] )4.0000E+00 # ( ( { 201 - 204 } ) < ( { 161 - 163 } ) )2.0000E+00 # ( ( 90 100 ) < 61 )1.0000E+00 # ( 120 < 61 )2.0000E+00 # ( ( 90 100 ) < ( 62 63 ) )1.0000E+00 # ( 120 < ( 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 volumeof 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 inu direction, are used for the tally. In the echo, the number of regions in bottom level is echoed 1. In the case, youhave 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} )volumereg
vol1
1.000025.000036.000041.000010001
6.000010002
5.0000In 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 theskip operator non.
In the input echo, numbered entry is given in non column. When axis=reg, the numbered entry is used as avalue of x-axis.
When you define regions in the bottom level, set same region twice as ( 3000 < 3000[1:2 3:61:1] ).

5.1.3 r-z mesh
When you use the r-z scoring mesh, first, oﬀsets for x and y coordinate of the center of cylinder can be definedas5 COMMON PARAMETERS FOR TALLIES

180

mesh = r-zx0 = 1.0y0 = 2.0

This can be omitted. Then, define r and z mesh as

mesh
= r-z
r-type = [1-5]..........
..........
z-type = [1-5]..........
..........

Mesh definition is described later.
You can add θ degree of freedom in r-z mesh of [t-track] tally. You can use a-type mesh definition to
specify θ of r-z mesh in the same manner as in the other angle mesh cases. However, the maximum angle of θmesh is restricted 360 degree (2π) in this case. You can obtain the θ dependence of results of [t-track] tally by
setting axis=rad or axis=deg. The rad represents the θ in radian, while deg in degree.

5.1.4 xyz mesh
When you use the xyz scoring mesh, set x, y, and z mesh as

mesh
= xyz
x-type = [1-5]..........
..........
y-type = [1-5]..........
..........
z-type = [1-5]..........
..........

Mesh definition is described later.

5.1.5 tet meshThis mesh is applicable only when tetrahedron geometry4.6.5 is used in the geometry and only active in [ttrack], [t-deposit], [t-yield], [t-product], [t-dpa] tallies. When you use the tet scoring mesh, a cell no. of therectangular box where the tetrahedron geometry is implemented needs to be specified following to the mesh definition as5.2 Energy mesh

mesh
reg

181

= xyz
= 100

The physical quantities specfied in the tally will be scored in all the tetrahedrons separatelly. Extraction ofsome 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 tetrahedrongeometry. It should be noticed also the volume of tetrahedron is simply computed from the coordinates of thenodes and thus incorrect qunatities may be obtained when the tetrahedron geometry is clipped out through the useof nest structure of “universe”and “fill”. In such a case, the region mesh (mesh=reg) should be used instead.

5.2 Energy mesh
Energy mesh begins as

e-type = [1-5]..........
..........

e1-type and e2-type are also used in DEPOSIT2 tally. Mesh definition is described later.

5.3 LET mesh
LET mesh begins asl-type = [1-5]..........
..........

Mesh definition is described later.

5.4 Time mesh
Time mesh is defined ast-type = [1-5]..........
..........

Mesh definition is described later.

5 COMMON PARAMETERS FOR TALLIES

182

5.5 Angle mesh
Angle mesh in cross tally is defined asa-type = [1, 2, -1, -2]..........
..........

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.

5.6 Mesh definition

183

5.6 Mesh definition
There are 8 kinds of mesh definition as e-type, t-type, x-type, y-type, z-type, r-type, a-type
and l-type. The format is common for every mesh types. So only the e-type definition is described below.
For other types, replace e into t, x, y, ... and a. For example, replace ne as nt, nx, ny, ... , na, emin as
tmin, xmin, ymin, ... , amin, and so on.
In the defined mesh, emin itself is included in the minimum bin, while emax itself is not included in the
maximum bin.

5.6.1 Mesh type
You can use 5 kinds of mesh type as shown below.
Table 5.2: Mesh typemesh type
1
2
3
4

5

explanation
Give number of groups and mesh points by data.
Give number of groups, minimum and maximum values. Mesh is divided equally by linear scale.
Give number of groups, minimum and maximum values. Mesh is divided equally by log scale.
Give mesh width, minimum and maximum values. Mesh points are given by linear scale. Numberof groups is set automatically as resulting maximum value becomes same with given value, or
takes larger value with small excess as possible.
Give minimum and maximum values and log value of mesh width. Mesh points are given by log
scale. Number of groups is set automatically as resulting maximum value becomes same withgiven value, or takes larger value with small excess as possible.

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.

5.6.2

e-type=1

When you use e-type=1, set number of group, then numerical data ase-type = 1
ne = number of groupdata(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.

5 COMMON PARAMETERS FOR TALLIES

184

5.6.3

e-type=2,3

When you use e-type=2,3, set number of group, minimum value, and maximum value ase-type = 2, 3
ne = number of groupemin = minimum value
emax = maximum value

5.6.4

e-type=4

When you use e-type=4, set mesh width, minimum value, and maximum value ase-type = 4
edel = width of meshemin = minimum value
emax = maximum value

5.6.5

e-type=5

When you use e-type=5, set mesh width, minimum value, and maximum value ase-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 ).

5.7 Other tally definitions
5.7.1 Particle definition
You can define particles aspart = proton neutron pion+ 3112 208Pb

or5.7 Other tally definitions

185

part = protonpart = neutron
part = pion+
part = 3112
part = 208Pb

See Table 3.4 for particle identification. You can also use the kf code number.
If you define all particles aspart = 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.

part = ( proton neutron ) all pion+ 3112 208Pb

In this case, as the first group, the sum of proton and neutron contribution is tallied, the second is the sum of all. 5groups 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.

5.7.2 axis definition
X axis value for output is described here. There are many kinds of axis shown as (depend on kinds of tallies
or geometrical meshes),eng, reg, x, y, z, r, t, xy, yz, zx, rz,cos, the, mass, charge, chart, dchain
let, t-eng, eng-t, t-e1, e1-t, t-e2, e2-t, e12, e21axis = eng

You can set multiple axis per one tally byaxis = eng

or

x

y

5 COMMON PARAMETERS FOR TALLIES

186

axis = eng
axis = xaxis = y

If you define multiple axes, output results are written in diﬀerent 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.

5.7.3 file definition
The format to define name of output file is,file = file.001

file.002

file.003

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

5.7.4 resfile definition
The format to specify a file name of past tally in the restart calculation is,
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.

5.7.5 unit definition
Set output unit asunit = number

The unit number and its meanings are described in each tally explanation.

5.7 Other tally definitions

187

5.7.6 factor definition
You can set normalize factor by this format.

factor = numberThis value is multiplied to output values. When you use the [t-gshow] tally, this factor defines line thickness
instead.

5.7.7 output definition
Set output type as

output = name of output

Details are described in each tally explanation.

5.7.8 info definition
This option defines whether detailed information is output or not. Set 0 or 1 asinfo = 0, 1

5.7.9 title definition
This option is for title astitle = title of the tally

It is omitted, and in this case, default is used.

5.7.10 ANGEL parameter definition
In order to add ANGEL parameters in tally output, define asangel = xmin(1.0) ymin(1.3e-8)

Defined parameters are converted to the ANGEL format asp: xmin(1.0) ymin(1.3e-8)

5 COMMON PARAMETERS FOR TALLIES

188

These parameters change the minimum of the horizontal and vertical axes, respectively. The main ANGEL parameters are shown in Table 5.3. Please see the ANGEL manual in more detail.
Table 5.3: ANGEL parameter
ANGEL parameter
xmin
xmax
ymin
ymax
xlin
xlog
ylin
ylog
cmnm
cmum
cmmm
cmmt
cmkm

Explanation
Minimum of horizontal axis.
Maximum of horizontal axis.
Minimum of vertical axis.
Maximum of vertical axis.
Change horizontal axis to liner scale.
Change horizontal axis to logarithmic scale.
Change vertical axis to liner scale.
Change vertical axis to logarithmic scale.
Convert cm to nm.
Convert cm to µm.
Convert cm to mm.
Convert cm to m.
Convert cm to km.

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 aneps file. The characters given in parentheses represent each output size.

5.7.11 Sangel parameter definition
This definition can be used to insert all ANGEL parameters into tally output files unlike the usual ANGEL
parameter definition, which can specify only ANGEL parameters defined by p:. For example, defining infl:
parameter for ANGEL, the tally file includes an experimental data file, and both calculated results and the experimental data can be plotted in a figure (eps file).
The SANGEL parameter can be set using the format sangel=number of definition lines, and then writing thelines to define the ANGEL parameters. An example with sangel is as follows.
sangel = 2
infl:{exp.dat}
w: ($\theta=$ 0 deg) / X(10) Y(100)where “exp.dat” is a data file of the experimental data. The data can be shown on the figure of the tally result. By
using w: parameter, the comment “θ=0 deg” can be put at the coordinate of X=10, Y=100 in the figure.

5.7.12 2d-type definition
When you define 2 dimensional output as axis=xy, you must set this 2d-type option as

2d-type =1, 2, 3, 4, 5, 6, 7

These 2d-types give the format of data arrange.
• 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 )

5.7 Other tally definitions

189

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 forcluster 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 doend do3 data of x(ix), y(iy) and data(ix,iy) are written in a line.
• 2d-type = 5
Data are written by below formaty/x ( x(ix), ix = 1, nx )do iy = ny, 1, -1( y(iy), data(ix,iy), ix = 1, nx )end donx+1 data are written in a line, and total ny+1 lines. It is useful to use in the tabular soft like Excel.

5.7.13 gshow definition
This option can be used in all tallies without [t-gshow] and [t-rshow]. If you set gshow option with xyz
mesh, xy, yz, or xz axis, and 2d-type=1,2, or 3, ANGEL can create a graphical plot with region boundaryand material name, or region name, or lattice number on the two dimensional output. You can also obtain graphicalplots directory from the PHITS calculation by the epsout option.

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 indicationof 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 goodor not, before long time calculation.

5.7.14 rshow definition
You can use rshow definition in all tallies except for [t-cross] and [t-gshow] tallies. This option is available with region mesh, xy, yz, zx axis. This option makes a two dimensional plot in which each region is coloredwith the amount of its region’s output value. And region boundaries, material name, or region name numbers arealso displayed. The xyz mesh definition is required after this rshow definition.

5 COMMON PARAMETERS FOR TALLIES

190

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 boundaryand material name, 3 means rshow with region boundary and region name numbers. If rshow=0, xyz meshdefinition is not required, comment out it. When you increase the resolution of the plot by resol parameter, theindication 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, diﬀerent colors are used for diﬀerent materials. You should check whether regions are correct anda xyz mesh resolution is good or not, before long time calculation.

5.7.15 x-txt, y-txt, z-txt definition
If you want to change x, y, and z axis titles in the output figure, use these option. These title cannot be definedin the ANGEL parameter.
x-txt = x axis title
y-txt = y axis title
z-txt = z axis title

5.7.16 volmat definition
The volmat parameter corrects a volume where xyz mesh crosses region boundaries. This option is eﬀectivein the case that mesh is xyz, and the material parameter is defined. This corrected volume is calculated by theMonte Carlo method for specified material. volmat denotes the number of scanning parallel to x, y, and z axis
respectively for the Monte Carlo calculation. So if you set too large volmat, the calculation takes long time. You
need to take care of it. If volmat is given by negative value, all xyz mesh is scanned. If positive value, the scanning
is not performed when 8 apexes of the mesh are included in the same material.

5.7.17 epsout definition
If you set epsout=1, output file is treated by ANGEL automatically and an eps file is created. This eps filename is named by replacing the extension into “.eps.” With itall=1 setting, the eps file is created after every
batch calculation. You can monitor the PHITS results in real time, by displaying the eps file with the ghostview
and by setting refresh function for a file updating by typing ‘w’ key on the ghostview.

5.7 Other tally definitions

191

5.7.18 counter definition
You can make a gate to the tallying quantities by using the counter defined by [counter] section. Set minimum ctmin(i) and maximum value ctmax(i) for each counter. The i is the counter number from 1 to 3. By
default, ctmin(i)=-9999, and ctmax(i)=9999. When multiple counters are specified, the common part of theseterms is tallied.

5.7.19 resolution and line thickness definitions
You can increase the resolution of the region boundaries in the gshow, rshow, and 3dshow with keeping xyz
mesh by resol. Default value is 1, it is same as xyz mesh resolution. If you set resol=2, the resolution becomes
2 times for each side. It is useful to draw smooth line for xyz mesh. Also you can obtain clear graphics by set
resol larger for the 3dshow. Even if you set resol larger, memory usage is not changed.
The width shows the line thickness for gshow, rshow, and 3dshow. Default value is 0.5.

5.7.20 trcl coordinate transformation
By this trcl option, you can transform the coordinate of the r-z, and xyz mesh. There are two ways to define
the transformation as below.

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 todefine the transformation directly here with 13 parameters as same as in [transform] section. If the data are notwritten in a line, you can write them in multiple lines without the line sequential mark. But you need to put morethan 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.

5.7.21 dump definition
In the [t-cross], [t-time], and [t-product] tallies, information on the particles can be dumped on the
file.
By the parameter of dump =, the number of the dump data in one record is specified. If this number is given bypositive number, the data are read as binary data. If negative, the data are read as ascii data. In next line, the data
sequence of one record is described. The relation between the physical quantities and id number is the followings,
Table 5.4: id number of dump data (1)physical quantities
id number

kf
1

x
2

y
3

z
4

u
5

v
6

w
7

e
8

wt
9

time
10

c1
11

c2
12

Table 5.5: id number of dump data (2)physical quantities
id number

name
17

nocas
18

nobch
19

no
20

c3
13

sx
14

sy
15

sz
16

5 COMMON PARAMETERS FOR TALLIES

192

Here kf means the kf-code of the particles (see Table 3.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 theinitial 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

To read this data, we write the parameters as
dump = 9
1 8 9

2

3

4

5

6

7

When you use this dump parameter, axis and file are restricted to one axis and one file, and unit is always
1. The dumped data are written on a file named “*** dmp,” where “***” indicates the file name specified by
file=“***.” The normal output of the tally is written on “***.” From this file, you can get the information on
the total normalization factor. (In the former version of PHITS (before 2.66), the normal output was written on
a configuration file (.cfg), and the dumped data were written on “***.” ) In the parallel computing, files to thenumber of (PE−1) corresponding to each PE (Processor Element) are created for writing and reading dumped data.
If you set idpara=0 or 1, a file is made in the directory named by /wk/uname/ on each of the nodes. If you set
idpara=1 or 3, the each IP number is put at the end of the filename. The each PE writes down its result on only
the corresponding file, and reads it from the same file in the re-calculation.

5.8 Function to sum up two (or more) tally results

193

5.8 Function to sum up two (or more) tally results
After version 2.74, PHITS has a function to sum up two (or more) tally results. There are two methods for
sum up; one is to integrate the tally results considering the history number of each simulation, while the other isto add the tally results weighted by user defined ratios. The former can be used for the parallel calculation on
computers in which MPI protocol is not installed. On the other hand, the latter is suit for the simulation with
diﬀerent source terms whose intensities cannot be fixed before the simulation, such as that for Intensity-Modulated
Radiation Therapy (IMRT).
In order to use this function, you have to satisfy the following conditions:• icntl is set to 13 in [parameters] section• The parameters for each tally results such as mesh, axis and part are identical to one another• “sumtally” subsection is defined in the tally section that outputs one of the summing up tallies. 58 59“sumtally” subsection is ignored when icntl parameter is not set to 13 in [parameters] section. (From ver. 2.88,“sumtally” works all tallies.) Please see ppt file 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 sumtallysubsection.
The parameters used in “sumtally” subsection are summarized in Table 5.6.
Table 5.6: Parameters used in “sumtally” subsection
nameisumtally =value
1(default), 2

nfile =
(next line)

Numberfilename value

sfile =
filename
sumfactor = （Omitted, D=1.0）

description
Summing up procedure.
1: Integration of tally results considering history number of each simulation.
2: Sum of tally results weighted by user defined ratios.
Number of summing up files.
Summing up file name, weighted value. Sum of the weighted values is
automatically normalized to sumfactor for isumtally=2.
Output file name.
Normalization factor.

For example, if you have two tally results “result-1.out” and “result-2.out” that were obtained from maxcas=100
and maxbch=10 and 20, respectively, and you would like to obtain their summing up results considering their histories, you have to write:
Example 54: example for isumtally=1
1:
2:
3:
4:
5:
6:
7:
8:

sumtally start
isumtally = 1$(D=1) sumtally option, 1:integration, 2:weighted sum
nfile = 2
$ number of tally files
result-1.out 1.0
result-2.out 1.0
sfile = result-s.out $ file name of output by sumtally option
sumfactor = 1.0$ (D=1.0) normalization factor
sumtally end

Using this sumtally subsection, you can obtain the results for maxcas=100 and maxbch=30. Please be surethat the initial random seeds for calculating “result-1.out” and “result-2.out” should be diﬀerent from each other,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
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
occurs the error in the setting without the definition of file.
59 Before ver. 2.85, only one “sumtally” subsection can be defined in a PHITS input file.

5 COMMON PARAMETERS FOR TALLIES

194

1 for isumtally=1, unless you would like to change the weight of source particles. The output file obtained fromthis 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:X̄ = F

N
∑
rj
j=1

r

X̄ j

(19)

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 byvut N ( )∑ rj 2σX = F
σ2X j
(20)
r
j=1
where σX j is the standard deviation of j-th tally results.
If you have two tally results “result-l.out” and “result-r.out,” and you would like to sum up them weighted byfactors of 2.0 and 3.0, respectively, you have to write:
Example 55: example for isumtally=2
1:
2:
3:
4:
5:
6:
7:
8:

sumtally start
isumtally = 2$(D=1) sumtally option, 1:integration, 2:weighted sum
nfile = 2
$ number of tally files
result-l.out 2.0
result-r.out 3.0
sfile = result-s.out $ file name of output by sumtally option
sumfactor = 5.0$ (D=1.0) normalization factor
sumtally end

You can obtain the same results by using multi-source function, but it is more convenient to use sumtallysubsection when you would like to change the weighted values for several cases. It should be mentioned that thesum 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.

195

6

Tally input format

6.1 [ T-Track ] section
This tally can be used to obtain the fluence in any specified region. In this tally, the track length is evaluatedwhenever particles pass through a specified region, as shown in Fig. 6.1, and the sum of the track lengths in unitsof [cm] is scored. Based on this, a particle fluence in units of [/cm2 /source] is determined by dividing the scoredtrack lengths by the volume of the region and the number of source particles.

V

track length
Figure 6.1: [T-Track] tally: track length (solid line) is calculated.
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 ofcounts in the response.
Table 6.1: [t-track] parameters (1)namemesh =

value
reg, r-z, xyz, tetpart =
material =all (default),
particle name(omitted)all,number of materials(next line)
e-type =2 5 8
1, 2, 3, 4, 5

t-type =1, 2, 3, 4, 5
(omitted)
1, 2, -1, -2a-type =explanation
Geometry mesh: a geometry mesh subsection is required below thisoption.
There is a maximum of six particles in a [t-track].
Specify materials for scoring.
all : default (same as no definition).
To set number of materials, define the material numbers in the next
line. The number of materials can be set as a negative value, inwhich case the specified materials are not included for scoring.
Material numbers.
Energy mesh: an energy mesh subsection is required below this option.
Time mesh: a time mesh subsection is required below this option.
Angle mesh with θ degrees of freedom for mesh=r-z: an angle meshsubsection is required below this option.

6 TALLY INPUT FORMAT

196

Table 6.2: [t-track] parameters (2)nameunit =

value
1, 2, 3, 4

11, 12, 13, 14

axis =

file =
resfile =eng, reg, x, y, z, r
tet
xy, yz, xz, rz
tfile name(omitted, D=file)x-txt =
y-txt =
z-txt =
gshow =

(omitted, D=1.0)(omitted)(omitted)(omitted)
1, 2, 3, 4, 5, 6, 7
(omitted, D=3)
(omitted)(omitted)(omitted)0 (default), 1, 2, 3, 4, 5

rshow =

0 (default), 1, 2, 3

ginfo =

0 (default),
1

factor =title =
angel =
sangel =2d-type =2

explanation
1: [1/cm2 /source]
2: [1/cm2 /MeV/source]
3: [1/cm2 /Lethargy/source]
4: [cm/source]
11: [1/cm2 /nsec/source]
12: [1/cm2 /MeV/nsec/source]
13: [1/cm2 /Lethargy/nsec/source]
14: [cm/nsec/source]
x axis value of output data.
x axis value of output data (only active with mesh=tet).
2-dimensional.
Time axis.
Define file names. This is required by each setting of axis.
Define a file name of the past tally in the restart calculation:even if several axis parameters were defined, specify only one
resfile.
Normalization factor.
Title.
ANGEL parameters.
Special format for ANGEL parameters.
Options for 2-dimensional plot.
x axis title.
y axis title.
z axis title.
When mesh=xyz and axis=xy,yz,xz, region border (1), material name (2), region name (3), and LAT number (4) are plottedusing this option. gshow=5 outputs only material colors in pixel
style when icntl=8.
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.
No geometry check in the case of gshow or rshow> 0.
Check geometry and draw a two-dimensional view with error
information.
Check geometry, draw two-dimensional view, and output a geometry error file (“.err”).

‘Lethargy’ in unit=3 or 13 is the natural logarithmic unit of energy defined by ln(Eref /E) using a referenceenergy 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 thesum 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=rador axis=deg, where rad and deg represent θ in radians and degrees, respectively.

6.1 [ T-Track ] section

197

Table 6.3: [t-track] parameters (3)nameresol =value
1 (default)

width =
volume0.5 (default)(omitted)reg vol
iechrl =volmat =72 (default)(omitted, D=9)

epsout =0 (default), 1, 2

bmpout =0(default), 1

vtkout =0(default), 1

vtkfmt =0(default), 1

foamout =0(default), 1

ctmin(i) =ctmax(i) =trcl =
gslat =
stdcut =multiplier =(omitted, D=-9999)(omitted, D= 9999)(omitted)1(default), 0(omitted, D=-1)
Number of material(omitted)

explanation
This option multiplies the region line resolution by a factor of resolwith the gshow or rshow option set to define the line thickness.
The option defines the line thickness.
This option defines the volume for each region for reg mesh. Volume definitions are required below this option. Values defined in[volume] are used in the case of no definition. If special description
such as using () is used to specify a region in reg=, its internally defined region number is output in input echo when this volume
subsection is not defined.
Volume definition. For details see Sec. 5.1.2.
Maximum number of columns for volume input echo.
This option corrects the volume value for each mesh when material
is defined by the xyz mesh. (0 means no correction). Value of volmat
is the number of scans per one xyz mesh side.
When epsout=1, results are plotted into eps files. The eps file isnamed by replacing the extension with “.eps.” When epsout=2, error bars are also displayed in the eps file, except for the 2-dimensional
type (axis=xy, yz, xz, rz).
Generate Bitmap figure of 2-dimensional tally output. This file isnamed by replacing the extension with “.bmp.” When mesh=xyz
and axis=xy, yz, xz, it is available.
Output the tally results in the xyz-mesh in the input format of ParaView. This file is named by replacing the extension with “.vtk.”
When mesh=xyz and axis=xy, yz, xz, it is available.
Format of output file for ParaView.
0: ascii, 1: binary.
Generate a file with OpenFOAM field data format. This file isnamed by replacing the extension with “.foam.” When mesh=tet
and axis=tet, it is available.
Minimum value for i-th counter.
Maximum value for i-th counter.
Coordinate transformation number or definition for r-z or xyz mesh.
1: show lattice boundary in gshow, 0: do not show.
Threshold value of STD cut oﬀ.
Multiplier for each material:a multiplier subsection is required below this option. See Sec. 4.23.1
for its detailed usage.

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.

6 TALLY INPUT FORMAT

198

6.2 [ T-Cross ] section
This tally can be used to obtain the current or flux (actually, the fluence) on any specified surface. In this tally,a particle crossing the surface simply adds 1 to the current and 1/ cos θ to the flux, where θ is the angle between
the direction of the particle trajectory and the normal vector to the surface. In PHITS, the current and flux are
similar but distinct physical quantities; they diﬀer in terms of the surface element used to calculate the numberof the particles crossing per unit area. The current is evaluated by dividing by the area of the surface S shown in
Fig. 6.2; by contrast, the flux is calculated by dividing by S cos θ. The value of S is given in the geometry meshsubsection as area for mesh=reg and is calculated automatically for the r-z and xyz meshes.

direction ofparticle trajectory

Scosθ
S
θ

Figure 6.2: Relation between the areas S and S cos θ.
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.

6.2 [ T-Cross ] section

199

Table 6.4: [t-cross] parameters (1)namemesh =

value
reg, r-z, xyz

part =all (default),
particle name1, 2, 3, 4, 5

e-type =t-type =a-type =1, 2, 3, 4, 5
(omitted)
1, 2, -1, -2

unit =

1, 2, 3, 4, 5, 6

11, 12, 13, 14, 15, 16

explanation
Geometry mesh: a geometry mesh subsection is required below
this option.
There is a maximum of six particles in a [t-cross].
Energy mesh: an energy mesh subsection is required below thisoption.
Time mesh: a time mesh subsection is required below this option.
Angle mesh (=1,2; cosine mesh, =-1,-2; angle (in units of degree) mesh): an angle mesh subsection is required below this option for output=a-curr or =oa-curr.
1: [1/cm2 /source]
2: [1/cm2 /MeV/source]
3: [1/cm2 /Lethargy/source]
4: [1/cm2 /sr/source]
5: [1/cm2 /MeV/sr/source]
6: [1/cm2 /Lethargy/sr/source]
11: [1/cm2 /nsec/source]
12: [1/cm2 /MeV/nsec/source]
13: [1/cm2 /Lethargy/nsec/source]
14: [1/cm2 /sr/nsec/source]
15: [1/cm2 /MeV/sr/nsec/source]
16: [1/cm2 /Lethargy/sr/nsec/source]

There may be cases in which results of a tally are incorrect when r-z or xyz mesh surface agrees with that ofthe defined cell.
The current for a specified angle can be obtained using the angle mesh shown in Fig. 6.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 meshsize of the angle-bin defined in the angle mesh subsection.

θFigure 6.3: Schematic of tally using angle mesh.
‘Lethargy’ in unit=3,6,13,16 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 andElow 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.

6 TALLY INPUT FORMAT

200

Table 6.5: [t-cross] parameters (2)nameaxis =

file =
resfile =factor =title =
angel =
sangel =2d-type =output =x-txt =
y-txt =
z-txt =
gshow =

ginfo =

value
eng, reg, x, y, z, rcos, the, t
xy
yz, xz, rz
file name(omitted, D=file)(omitted, D=1.0)(omitted)(omitted)(omitted)
1, 2, 3, 4, 5, 6, 7
(omitted, D=2)
flux
current
f-currb-curro-currof-currob-curr
a-curroa-curr(omitted)(omitted)(omitted)0 (default), 1, 2, 3, 4, 5

0 (default),
12

resol =

1 (default)

width =

0.5 (default)

explanation
x axis value of output data.
Angle (cosine, θ[degree]) and time mesh.
2-dimensional.
2-dimensional, only for enclos=1.
Define file names. This is required by each setting of axis.
Define a file name of the past tally in the restart calculation:even if several axis parameters were defined, specify only one
resfile.
Normalization factor.
Title.
ANGEL parameters.
Special format for ANGEL parameters.
Options for 2-dimensional plot.
Flux by surface crossing.
Current by surface crossing.
Forward current by surface crossing.
Backward current by surface crossing.
Omni60 current by surface crossing.
Omni60 forward current by surface crossing.
Omni60 backward current by surface crossing.
Angle mesh current by surface crossing.
Angle mesh omni60 current by surface crossing.
x axis title.
y axis title.
z axis title.
When mesh=xyz and axis=xy,yz,xz, region border (1), material name (2), region name (3), and LAT number (4) are plottedusing this option. gshow=5 outputs only material colors in pixel
style when icntl=8.
No geometry check in the case of gshow or rshow> 0.
Check geometry and draw a two-dimensional view with error
information.
Check geometry, draw two-dimensional view, and output a geometry error file (“.err”).
This option multiplies the region line resolution by a factor ofresol with the gshow or rshow option set to define the line
thickness.
The option defines the line thickness.

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.

60 Omni means the energy integrated.

6.2 [ T-Cross ] section

201

Table 6.6: [t-cross] parameters (3)nameepsout =value
0 (default), 1, 2

ctmin(i) =ctmax(i) =trcl =
dump =(omitted, D=-9999)(omitted, D= 9999)(omitted)
Number of data

(next line)

Data sequencegslat =
stdcut =multiplier =1(default), 0(omitted, D=-1)
Number of material(omitted)

enclos =0(default)
1

explanation
When epsout=1, results are plotted into eps files. The eps file isnamed by replacing the extension with “.eps.” When epsout=2, error bars are also displayed in the eps file, except for the 2-dimensional
type (axis=xy).
Minimum value for i-th counter.
Maximum value for i-th counter.
Coordinate transformation number or definition for r-z or xyz mesh.
For mesh=reg, the information is dumped on the file. If dump is
negative, data are written by ascii, if positive, by binary.
Define the data sequence. The history information (nocas andnobch) is necessary to use idmpmode=1.
1: show lattice boundary in gshow, 0: no.
Threshold value of STD cut oﬀ.
Multiplier for each material.61
Multiplier subsection is required below this parameter.
See
Sec. 4.23.1 for its detailed usage.
Define crossing surfaces on z and r for mesh=r-z, and define crossing
surface on z for mesh=xyz.
Define crossing surfaces by closed surface separated by each mesh.

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 thedump 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 perunit area.

61 From ver. 2.86, multiplier option can be used in [t-cross] tally.

6 TALLY INPUT FORMAT

202

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 theexample below 62 .

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 nextline, the values of r-in r-out, and area should be written as a matrix format. The default order for this definitionis 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. Whenspecifying 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 canbe 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 thiscase, 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.

62 Before 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.

6.3 [ T-Point ] section

203

6.3 [ T-Point ] section
It is impractical to calculate particle fluence at a specific point or line using the [t-track] tally. To address
this, the point estimator tally [t-point] was introduced to estimate these quantities within a short computational time. However, to use this tally the following conditions must be satisfied in the PHITS simulation using[t-point]:(1) particle energy should not exceed the maximum energy of the data library used, i.e., dmax;(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.
Table 6.7: [t-point] parameters (1)namepoint =
ring =
part =
e-type =t-type =unit =

value
number of data
number of dataall (default),
particle name1, 2, 3, 4, 5
1, 2, 3, 4, 5
(omitted)
1, 2, 3

11, 12, 13

axis =
file =
resfile =eng, tfile name(omitted, D=file)

factor =title =
angel =
sangel =epsout =(omitted, D=1.0)(omitted)(omitted)(omitted)0 (default), 1, 2

ctmin(i) =ctmax(i) =(omitted, D=-9999)(omitted, D= 9999)

explanation
Option for point detectors: a subsection is required below this option.
Option for ring detectors: a subsection is required below this option.
There is a maximum of six particles in a [t-point].
Energy mesh: an energy mesh subsection is required below this option.
Time mesh: a time mesh subsection is required below this option.
1: [1/cm2 /source]
2: [1/cm2 /MeV/source]
3: [1/cm2 /Lethargy/source]
11:[1/cm2 /nsec/source]
12:[1/cm2 /nsec/MeV/source]
13:[1/cm2 /Lethargy/nsec/source]
x axis value of output data.
Define file names. This is required by each setting of axis.
Define a file name of the past tally in the restart calculation: even if
several axis parameters were defined, specify only one resfile.
Normalization factor.
Title.
ANGEL parameters.
Special format for ANGEL parameters.
When epsout=1, results are plotted into eps files. The eps file is namedby replacing the extension with “.eps.” When epsout=2, error bars
are also displayed in the eps file, except for the 2-dimensional type(axis=xy, yz, xz, rz).
Minimum value for i-th counter.
Maximum value for i-th counter.

‘Lethargy’ in unit=3 or 13 is the natural logarithmic unit of energy defined by ln(Eref /E) using a referenceenergy 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.

6 TALLY INPUT FORMAT

204

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
non
x
1
10.0

# number of point detectors
y
z
r0
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 (formore 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
non
axis
1
z

# number of ring detectors
ar
rr
r0
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 thecenter 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 thesefactors, 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].
Table 6.8: [t-point] parameters (2)namestdcut =multiplier =value(omitted, D=-1)
Number of material(omitted)

explanation
Threshold value of STD cut oﬀ.
Multiplier for each material:a multiplier subsection is required below this option. See Sec. 4.23.1
for its detailed usage.

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.

6.4 [ T-Deposit ] section

205

6.4 [ T-Deposit ] section
This tally can be used to obtain deposition energies (heat) in certain regions. After version 3.05, it tallies thedeposition energies not only by ionization of charged particles but also kerma of neutral particles. The necessityof the use of kerma approximation is automatically judged based on [parameters] section: neutron kerma approximation is not used when e-mode≥1, while photon kerma approximation is not used when negs=1. Please seeSec. 4.2.9 in more detail. Note that the neutron kerma approximation is available only for energies below dmax(2)(usually 20 MeV is set).
In the calculation of deposition energies by ionization of charged particle, any factor can be multiplied using theuser-defined subroutines “usrdfn1.f” and “usrdfn2.f.” As examples, the default program of “usrdfn1.f” returns
the dose equivalent calculated from the product of the deposit energy with the Q(L) relationship defined in the
ICRP60, while that of “usrdfn2.f” estimates biological dose on the basis of Microdosimetric Kinetic Model 63 .
Any factor can be changed and added using this routine. Note that letmat should be set to water when thesedefault programs are used (see “\ParticleTherapy\” in the recommendation setting in more detail). It should bealso noted that this function cannot be applied to the deposition energy calculation by kerma approximation andtrack structure mode.
To tally the energy losses for particles entering the tally region, the counter should be defined by using part inthe [counter] section as well as ctmin and ctmax in this tally section.
Table 6.9: [t-deposit] parameters (1)namemesh =

value
reg, r-z, xyz, tetpart =all (default),
particle namematerial =(omitted)all,number of materials(next line)
letmat =2 5 8(omitted)dedxfnc =(omitted, D=0)

explanation
Geometry mesh: a geometry mesh subsection is required below thisoption.
There is a maximum of six particles in a [t-deposit].
When output=deposit and deposit=0, all is necessary and only
maximum 5 particles can be set.
Deposition energies calculated by kerma approximation for neutronsand photons are scored in part=neutron and photon, respectively,
as well as part=all.
Specify materials for scoring.
all : default (same as no definition).
To set number of materials, define the material numbers in the next
line. The number of materials can be set as a negative value, inwhich case the specified materials are not included for scoring.
Material numbers.
Material id for LET(dE/dx).
If omitted, a real material is assumed.
If a material not used in the geometry is selected, its material density
must be defined in [material]. To calculate LET in water, definewater with 1 g/cm3 in [material].
When letmat<0 is set, PHITS automatically calculates dE/dx forwater with 1 g/cm3 for electrons and positrons: please see “ParticleTherapy” in the recommendation setting for more details.
0: without; 1: use “usrdfn1.f;” 2: use “usrdfn2.f.”
As examples, the default program of “usrdfn1.f” returns the dose
equivalent calculated from deposit energy multiplied by the Q(L)relationship defined in the ICRP60, while that of “usrdfn2.f” estimates biological dose on the basis of Microdosimetric Kinetic
Model.

63 T.Sato et al., “Biological dose estimation for charged-particle therapy using an improved PHITS code coupled with a microdosimetrickinetic model,” Radiat. Res. 171, 107-117 (2009).

6 TALLY INPUT FORMAT

206

Table 6.10: [t-deposit] parameters (2)namee-type =value
1, 2, 3, 4, 5

t-type =1, 2, 3, 4, 5
(omitted)dose
depositoutput =unit =

0, 1, 2, 3, 4, 5

deposit =0(default), 1

axis =

eng, reg, x, y, z,r, ttet
xy, yz, xz, rz,
t-eng, eng-t
file name(omitted, D=file)

file =
resfile =factor =title =
angel =
sangel =2d-type =x-txt =
y-txt =
z-txt =

(omitted, D=1.0)(omitted)(omitted)(omitted)
1, 2, 3, 4, 5, 6, 7
(omitted, D=3)
(omitted)(omitted)(omitted)

explanation
Energy mesh: an energy mesh subsection is required below this option.
Time mesh: a time mesh subsection is required below this option.
Score the energy loss of charged particles and nuclei.
Score the variance of deposition energies by individual history (ane-type subsection is required).
0: Dose [Gy/source]; only for output=dose.
1: Dose [MeV/cm3 /source]
2: Dose [MeV/source]
3: Number [1/source]; only for output=deposit
4: Number [1/nsec/source]; only for output=deposit
5: Dose [J/m3 1/source]; only for output=dose
Option for deposit energy plot when output=deposit.
0: distribution of total deposit energy with contribution of each particle (please use this setting normally).
1: distribution of deposit energy by each particle (default setting
until ver. 2.81).
x axis value of output data.
x axis value of output data (only active with mesh=tet).
2-dimensional.
Define file names. This is required by each setting of axis.
Define a file name of the past tally in the restart calculation: even if
several axis parameters were defined, specify only one resfile.
Normalization factor.
Title.
ANGEL parameters.
Special format for ANGEL parameters.
Options for 2-dimensional plot.
x axis title.
y axis title.
z axis title.

Note that deposition energies calculated by kerma approximation are not included in this mode. It should bealso noted that this mode cannot be used when weights of particles depositing energy change within a history, suchas 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, thevolumes 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 averagevalue of the region. For example, when there are two materials with masses M1 and M2 , and absorption energies
E2 V1
E1 V1
2
+M
in this tally, even though its average dose is ME11 +E
E1 and E2 , respectively, PHITS gives M+M2 . Here,1 V1 +V2
2 V1 +V2
V1 and V2 are volumes of the two materials.
By setting output=deposit, this tally can be also used for calculating the probability density of depositionenergies by each history. This mode is useful for estimating the detector responses and the soft-error rates ofsemi-conductor devices.
When output=deposit and deposit=0, the contribution of each type of particle set in part can be obtained
from the result of all. In this case, if all is not set in part, part=all is automatically set.
By setting output=deposit and deposit=1, the distribution of energies deposited by each type of particle

6.4 [ T-Deposit ] section

207

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 valuesof part=all calculated independent of istdev as standard deviations using history variance mode.

6 TALLY INPUT FORMAT

208

Table 6.11: [t-deposit] parameters (3)namegshow =value
0 (default), 1, 2, 3, 4, 5

rshow =

0 (default), 1, 2, 3

ginfo =

0 (default),
12

resol =

1 (default)

width =
volume0.5 (default)(omitted)reg vol
iechrl =volmat =72 (default)(omitted, D=9)

epsout =0 (default), 1, 2

bmpout =0(default), 1

vtkout =0(default), 1

vtkfmt =0(default), 1

foamout =0(default), 1

explanation
When mesh=xyz and axis=xy,yz,xz, region border (1), material name (2), region name (3), and LAT number (4) are plottedusing this option. gshow=5 outputs only material colors in pixel
style when icntl=8.
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.
No geometry check in the case of gshow or rshow> 0.
Check geometry and draw a two-dimensional view with error
information.
Check geometry, draw two-dimensional view, and output a geometry error file (“.err”).
This option multiplies the region line resolution by a factor ofresol with the gshow or rshow option set to define the line
thickness.
The option defines the line thickness.
This option defines the volume for each region for reg mesh.
Volume definitions are required below this option. Values defined in [volume] are used in the case of no definition. If special description such as using () is used to specify a region
in reg=, its internally defined region number is output in input
echo when this volume subsection is not defined.
Volume definition. For details see Sec. 5.1.2.
Maximum number of columns for volume input echo.
This option corrects the volume value for each mesh whenmaterial is defined by the xyz mesh. (0 means no correction).
Value of volmat is the number of scans per one xyz mesh side.
When epsout=1, results are plotted into eps files. The eps file isnamed by replacing the extension with “.eps.” When epsout=2,
error bars are also displayed in the eps file, except for the 2dimensional type (axis=xy, yz, xz, rz, t-eng, eng-t).
Generate Bitmap figure of 2-dimensional tally output. This
file is named by replacing the extension with “.bmp.” Whenmesh=xyz and axis=xy, yz, xz, it is available.
Output the tally results in the xyz-mesh in the input format of
ParaView. This file is named by replacing the extension with“.vtk.” When mesh=xyz and axis=xy, yz, xz, it is available.
Format of output file for ParaView.
0: ascii, 1: binary.
Generate a file with OpenFOAM field data format. This fileis named by replacing the extension with “.foam.” Whenmesh=tet and axis=tet, it is available.

6.4 [ T-Deposit ] section

209

Table 6.12: [t-deposit] parameters (4)namectmin(i) =ctmax(i) =trcl =
gslat =
dresol =value(omitted, D=-9999)(omitted, D= 9999)(omitted)1(default), 0(omitted, D=0.0)

dfano =

(omitted, D=0.0)

stdcut =nlatcel(omitted, D=-1)(omitted)nlatmem(omitted, D=1000)

explanation
Minimum value for i-th counter.
Maximum value for i-th counter.
Coordinate transformation number or definition for r-z or xyz mesh.
1: show lattice boundary in gshow, 0: do not show.
Parameter for representing detector resolution. This is valid only for
output=deposit. When dresol=σr and dfano=F, the depositionenergy E of each event √fluctuates following a Gaussian distribution
with standard deviation σ2r + FE. If dresol<0, the energy resolutions (energy dependencies, spectral peak shapes, etc) are overwrittenby those defined in “usresol.f.”
Parameter for representing detector resolution.
Valid only for
output=deposit. When dresol=σr and dfano=F, the depositionenergy E of each event √fluctuated following a Gaussian distribution
with standard deviation σ2r + FE.
Threshold value of STD cut oﬀ.
By setting cell number which has LAT parameter, deposit energies
in cells, which have same cell number but placed in diﬀerent lattice coordinates, are processed as diﬀerent cells. It works only for
output=deposit.
The maximum number of cells deal with separately in one history.

Although the fano factor is generally defined as a dimensionless quantity, the dfano parameter is defined as aquantity 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,iare multiplied by specified coeﬃcients, αi (Nlist ), and then summed up as written by:

Ehistory =∑αi (Nlist ) × Ehistory,i .

(21)

i

This option weights depending on deposited energies in each history, and it can be applied to simulation, forexample 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 beused only mesh=reg, and it can be executed when you specify reg convolution. Formats and examples are shown
below;

6 TALLY INPUT FORMAT

210

mesh = reg
reg = weightsum
ncond = 4nocelloperator
1
100
ge
2
100
gt
3
100
eq
and
200
lt
4
100
le
ncell = 5
celllist01
list02
100
0.0
0.5
200
0.1
0.6
300
0.2
0.7
400
0.3
0.8
500
0.4
0.9

ethres
0.1
0.2
0.0
0.4
0.5

list
1
1
2
2
3

list03
1.0
2.0
3.0
4.0
5.0

list00
1.0
1.0
1.0
1.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 ispreferred when the history satisfies some conditions. If the history does not satisfy all the condition, coeﬃcientsof 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 needto 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 coeﬃcients are described. In thecell 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 samedeposited energy is added up many times when you set same cell number many times. If you do not define list00,
coeﬃcients of list00 are set to zero.

6.5 [ T-Deposit2 ] section

211

6.5 [ T-Deposit2 ] section
This tally scores deposit energy distribution in two regions and plot the correlation between two deposit energies. By this, one can simulate, for an example, dE, E counters and plot the correlations in 2-dimensional graph.
In the calculation of deposition energies by ionization of charged particle, In the same as [t-deposit], any factor
can be multiplied using the user-defined subroutines “usrdfn1.f” and “usrdfn2.f.”Table 6.13: [t-deposit2] parameters (1)namemesh =

value
reg

reg =
part =
letmat1 =r1 r2
all (default),
particle name(omitted)

letmat2 =(omitted)dedxfnc1 =dedxfnc2 =(omitted, D=0)
(omitted, D=0)

e-type1 =1, 2, 3, 4, 5

e-type2 =1, 2, 3, 4, 5

t-type =1, 2, 3, 4, 5

unit =(omitted)
1, 2

axis =

eng1, eng2, te12, e21, t-e1, t-e2,
e1-t, e2-t

explanation
Geometry mesh: a reg mesh subsection is required below thisoption.
Specify two cell numbers.
There is a maximum of six particles in a [t-deposit2].
Material id for LET(dE/dx) of region r1. If omitted, real material is assumed.
Material id for LET(dE/dx) of region r2. If omitted, real material is assumed.
If a material not used in the geometry is selected, its material
density must be defined in [material]. To calculate LET inwater, define water with 1 g/cm3 in [material].
When letmat1, or 2<0 is set, PHITS automatically calculates dE/dx for water with 1 g/cm3 for electrons and positrons:
please see “ParticleTherapy” in the recommendation setting for
more detail.
For region r1; 0: without; 1: use “usrdfn1.f;” 2: use “usrdfn2.f.”
For region r2; 0: without; 1: use “usrdfn1.f;” 2: use “usrdfn2.f.”
As examples, the default program of “usrdfn1.f” returns thedose equivalent calculated from deposit energy multiplied by
the Q(L) relationship defined in the ICRP60, while that of “usrdfn2.f” estimates biological dose on the basis of Microdosimetric Kinetic Model.
Energy mesh: for region r1, an energy mesh subsection is required below this option.
Energy mesh: for region r2, an energy mesh subsection is required below this option.
Time mesh: a time mesh subsection is required below this option.
1: Number [1/source]
2: Number [1/nsec/source]
x axis value of output data.
2-dimensional.

6 TALLY INPUT FORMAT

212

Table 6.14: [t-deposit2] parameters (2)namefile =
resfile =value
file name(omitted, D=file)

factor =title =
angel =
sangel =2d-type =x-txt =
y-txt =
z-txt =
volume(omitted, D=1.0)(omitted)(omitted)(omitted)
1, 2, 3, 4, 5, 6, 7
(omitted, D=3)
(omitted)(omitted)(omitted)(omitted)reg vol
iechrl =epsout =72 (default)
0 (default), 1, 2

ctmin(i) =ctmax(i) =stdcut =(omitted, D=-9999)(omitted, D= 9999)(omitted, D=-1)

explanation
Define file names. This is required by each setting of axis.
Define a file name of the past tally in the restart calculation: even if
several axis parameters were defined, specify only one resfile.
Normalization factor.
Title.
ANGEL parameters.
Special format for ANGEL parameters.
Options for 2-dimensional plot.
x axis title.
y axis title.
z axis title.
This option defines the volume for each region for reg mesh. Volume definitions are required below this option. Values defined in[volume] are used in the case of no definition. If special description such as using () is used to specify a region in reg=, its
internally defined region number is output in input echo when thisvolume subsection is not defined.
Volume definition. For details see Sec. 5.1.2.
Maximum number of columns for volume input echo.
When epsout=1, results are plotted into eps files. The eps
file is named by replacing the extension with “.eps.” Whenepsout=2, error bars are also displayed in the eps file, except forthe 2-dimensional type (axis=e12, e21, t-e1, t-e2, e1-t,e2-t).
Minimum value for i-th counter.
Maximum value for i-th counter.
Threshold value of STD cut oﬀ.

To tally the energy loss for each projectile particle entering the tally region, the counter should be defined usingpart 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.

6.6 [ T-Heat ] section

213

6.6 [ T-Heat ] section
This tally can be used to obtain deposition energies (heat) in certain regions using kerma approximation. However, the function to calculate deposition energy using kerma approximation was also implemented in [t-deposit]
after version 3.05, and thus, we do not recommend to use [t-heat] after that version.
Although the deposition energy from neutrons is zero for e-mode≥1, it can be calculated instead from theenergy loss of all charged particles and nuclei. The deposition energy from photons is also usually obtained fromkerma factors. For electron=1 with electron transport, photon kerma factors are not used; instead, depositionenergies are obtained from the energy loss of electrons.
Table 6.15: [t-heat] parameters (1)namemesh =

value
reg, r-z, xyz

axis =

reg, x, y, z, r
xy, yz, xz, rz,
file name(omitted, D=file)

file =
resfile =material =(omitted)all,number of materials(next line)
output =

2 5 8
heat
simpleexplanation
Geometry mesh: a geometry mesh subsection is required below thisoption.
x axis value of output data.
2-dimensional.
Define file names. This is required by each setting of axis.
Define a file name of the past tally in the restart calculation: even if
several axis parameters were defined, specify only one resfile.
Specify materials for scoring.
all : default (same as no definition).
When setting more than one material number, the material numbers
should be specified in the next line. By setting a material number toa negative value the specified material is excluded from scoring.
Material numbers.
total: Total deposit energy.
total: Total deposit energy.
ncut, gcut, pcut: Deposit energies of neutrons, photons, and protons, respectively, below cut-oﬀ energy when incut>0, igcut>0,
ipcut>0.
leakage: Kinetic energy of particles entering the outer void.
total: Total deposit energy.
recoil: Kinetic energy of residual nuclei when cut-oﬀ energyemin(15-19) is set.
ionization: Energy deposited by energy-loss of charged particles.
low neutron: Energy deposit calculated by neutron kerma factors.
photon: Energy deposit by kerma factors: (If electron=1, contributions of electrons below cut-oﬀ energy.)
others: Excitation energy of residual nuclei. Setting igamma=1 makes
this value 0 owing to photon emission.

Neutrons, photons, and protons below the cut-oﬀ energy are not tallied in the ncut, gcut, and pcut components 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.

6 TALLY INPUT FORMAT

214

Table 6.16: [t-heat] parameters (2)nameoutput =(continued)

value
all

part =

particle name(omitted)

unit =

0, 1, 2

factor =title =
angel =
sangel =2d-type =x-txt =
y-txt =
z-txt =
gshow =

(omitted, D=1.0)(omitted)(omitted)(omitted)
1, 2, 3, 4, 5, 6, 7
(omitted, D=3)
(omitted)(omitted)(omitted)0 (default), 1, 2, 3, 4, 5

rshow =

0 (default), 1, 2, 3

ginfo =

0 (default),
12

resol =

1 (default)

width =

0.5 (default)

explanation
In addition to the above parameters;
Contributions of d, t,3 He, α, and residual nuclei to recoil. Contributions of p, π+ , π− , and others to ionization (contributions ofparticles specified by part are output. but not plotted in the epsfile). stopped particle: Kinetic energy of stopped proton, neutron, π+ , π− , and other particles in materials (contributions ofparticles specified by part are output but not plotted in the epsfile). others: Remaining excitation energy and fission components. When axis is 2-dimensional, all is the same as simple.
Only total, recoil, ionization, low neutron, electron, and others
are output.
When output set =all, deposit energies for ionization andstopped particles specified here are output. Results are not plotted in the eps file.
Photon and neutron contributions calculated with kerma factor
cannot be distinguished by specifying part. For this purpose,
please see the output obtained by output=simple.
0: [Gy/source]
1: [MeV/cm3 /source]
2: [MeV/source]
Normalization factor.
Title.
ANGEL parameters.
Special format for ANGEL parameters.
Options for 2-dimensional plot.
x axis title.
y axis title.
z axis title.
When mesh=xyz and axis=xy,yz,xz, region border (1), material name (2), region name (3), and LAT number (4) are plottedusing this option. gshow=5 outputs only material colors in pixel
style when icntl=8.
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.
No geometry check in the case of gshow or rshow> 0.
Check geometry and draw a two-dimensional view with error
information.
Check geometry, draw two-dimensional view, and output a geometry error file (“.err”).
This option multiplies the region line resolution by a factor ofresol with the gshow or rshow option set to define the line
thickness.
The option defines the line thickness.

6.6 [ T-Heat ] section

215

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-oﬀ 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 theparameters of the transport are changed.
Table 6.17: [t-heat] parameters (3)namevolumevalue(omitted)reg vol
iechrl =volmat =72 (default)(omitted, D=9)

epsout =0 (default), 1, 2

bmpout =0(default), 1

vtkout =0(default), 1

vtkfmt =0(default), 1

electron =0 (default), 1

ctmin(i) =ctmax(i) =trcl =
gslat =
stdcut =(omitted, D=-9999)(omitted, D= 9999)(omitted)1(default), 0(omitted, D=-1)

explanation
This option defines the volume for each region for reg mesh. Volume
definitions are required below this option. Values defined in [volume]are used in the case of no definition. If special description such as using() is used to specify a region in reg=, its internally defined region
number is output in input echo when this volume subsection is not defined.
Volume definition. For details see Sec. 5.1.2.
Maximum number of columns for volume input echo.
This option corrects the volume value for each mesh when material isdefined by the xyz mesh. (0 means no correction). Value of volmat is
the number of scans per one xyz mesh side.
When epsout=1, results are plotted into eps files. The eps file is namedby replacing the extension with “.eps.” When epsout=2, error bars
are also displayed in the eps file, except for the 2-dimensional type(axis=xy, yz, xz, rz, t-eng, eng-t).
Generate Bitmap figure of 2-dimensional tally output. This file isnamed by replacing the extension with “.bmp.” When mesh=xyz andaxis=xy, yz, xz, it is available.
Output the tally results in the xyz-mesh in the input format of ParaView. This file is named by replacing the extension with “.vtk.” Whenmesh=xyz and axis=xy, yz, xz, it is available.
Format of output file for ParaView.
0: ascii, 1: binary.
Eelectron contribution options.
0: using photon kerma factors (electron and positron should NOT betransported, otherwise their deposition energies are double-counted)
1: calculating by ionization loss (electron and positron transport are required)
Minimum value for i-th counter.
Maximum value for i-th counter.
Coordinate transformation number or definition for r-z or xyz mesh.
1: show lattice boundary in gshow, 0: do not show.
Threshold value of STD cut oﬀ.

When unit is set =0 with output=dose, results can be obtained in units of [Gy/source]. When mesh=reg, thevolumes 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 averagevalue of the region. For example, when there are two materials with masses of M1 and M2 , and absorption energies
E2 V1
+E2
E1 V1
+ M
in this tally, even though its average dose is ME11 +M.
of E1 and E2 , respectively, PHITS gives M
1 V1 +V2
2 V1 +V2
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.

6 TALLY INPUT FORMAT

216

6.7 [ T-Yield ] section
This tally gives information on produced nuclei. Products produced by neutrons in the energy below dmax(2)are not scored in this section by default, but they are scored with e-mode≥1.
Table 6.18: [t-yield] parameters (1)namemesh =

value
reg, r-z, xyz, tet

special =D=0 (omitted)

part =all (default),
particle name(omitted)all,number of materials

material =(next line)
mother =2 5 8(omitted)all,number of mother nuclei(next line)

208Pb Pb

nucleus =(next line)(omitted)all,number of nuclei
208Pb Pb

elastic =1(default),0,-1

unit =

1, 2

explanation
Geometry mesh: a geometry mesh subsection is required below
this option.
When special> 0, nuclear reactions are repeated more than once
to increase statistics.
There is a maximum of six particles in a [t-yield].
Specify materials for scoring.
all : default (same as no definition).
To set number of materials, define the material numbers in the next
line. The number of materials can be set as a negative value, inwhich case the specified materials are not included for scoring.
Material numbers.
Specify mother nuclei.
all : default (same as no definition).
When setting the number of mother nuclei, define the mothers in
the next line. The number of mother can be set as a negative value,
in which case the specified mothers are not included for scoring.
Nucleus if specified using mass: without mass, all nuclei are isotopes of Pb. To specify multiple mother groups, use multiple[t-yield] tallies.
Specify output nuclei.
all : default (same as no definition).
When setting number of nuclei, define the nuclei in the next line.
Nucleus if specified with mass. Without mass, all nuclei are isotopes of Pb.
Option for contribution of recoil nucleus in elastic collision.
1: include contribution
0: exclude recoil target nucleus produced by elastic collision.
-1: exclude the same nucleus as the target nucleus.
1: [1/source]
2: [1/cm3 /source]

In the [t-yield] section, projectiles to tally can be specified by part, but the output is the sum of theircontributions. To obtain each contribution separately, set multiple [t-yield] sections.

6.7 [ T-Yield ] section

nameaxis =

file =
resfile =output =info =
factor =title =
angel =
sangel =2d-type =x-txt =
y-txt =
z-txt =
gshow =

rshow =

ginfo =

resol =

width =
reg vol
iechrl =volmat =217

Table 6.19: [t-yield] parameters (2)explanation
x axis value of output data.
x axis value of output data (only active with mesh=tet).
2-dimensional.
Mass distribution: if the nucleus is specified, isotope distribution
is used.
chargeCharge distribution: nucleus cannot be specified.
chart
Nucleus chart (x:N, y:Z). Nucleus cannot be specified.
dchainfor dchain-sp output. All isotopes are output only for mesh=reg
For this tally, only one axis parameter is defined in the[t-yield] section.
file nameDefine file names. This is required by each setting of axis.
(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.
(omitted)
Change the timing of the score.
product (default)
Nuclei produced by nuclear reaction are tallied.
cutoffNuclei stopped by energy cutoﬀ are tallied. If nuclei are nottransported, this is the same as product.
0, 1With stable nuclei and magic number for chart.
(omitted, D=1.0)
Normalization factor.
(omitted)
Title.
(omitted)
ANGEL parameters.
(omitted)Special format for ANGEL parameters.
1, 2, 3, 4, 5, 6, 7
Options for 2-dimensional plot.
(omitted, D=3)
(omitted)
x axis title.
(omitted)y axis title.
(omitted)z axis title.
0 (default), 1, 2, 3, 4, 5 When mesh=xyz and axis=xy,yz,xz, region border (1), material name (2), region name (3), and LAT number (4) are plottedusing this option. gshow=5 outputs only material colors in pixel
style when icntl=8.
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.
0 (default),
No geometry check in the case of gshow or rshow> 0.
1
Check geometry and draw a two-dimensional view with error
information.
2
Check geometry, draw two-dimensional view, and output a geometry error file (“.err”).
1 (default)This option multiplies the region line resolution by a factor ofresol with the gshow or rshow option set to define the line
thickness.
0.5 (default)
The option defines the line thickness.
Volume definition. For details see Sec. 5.1.2.
72 (default)
Maximum number of columns for volume input echo.
(omitted, D=9)
This option corrects the volume value for each mesh whenmaterial is defined by the xyz mesh. (0 means no correction).
Value of volmat is the number of scans per one xyz mesh side.
value
reg, x, y, z, r
tet
xy, yz, xz, rz
mass

When igamma=3 in the [parameters] section, information on the isomer production based on the EBITEM
model can be obtained by setting axis=chart or =dchain in this tally.
If output=cutoff is specified, the parameters of part and mother are neglected.

6 TALLY INPUT FORMAT

218
Table 6.20: [t-yield] parameters (3)namevolumevalue(omitted)reg vol
iechrl =volmat =72 (default)(omitted, D=9)

epsout =0 (default), 1, 2

bmpout =0(default), 1

vtkout =0(default), 1

vtkfmt =0(default), 1

foamout =0(default), 1

ctmin(i) =ctmax(i) =trcl =
gslat =
stdcut =ndata =

(omitted, D=-9999)(omitted, D= 9999)(omitted)1(default), 0(omitted, D=-1)
0(default), 1, 2, 3

explanation
This option defines the volume for each region for reg mesh. Volume
definitions are required below this option. Values defined in [volume]are used in the case of no definition. If special description such as
using () is used to specify a region in reg=, its internally defined
region number is output in input echo when this volume subsection is
not defined.
Volume definition. For details see Sec. 5.1.2.
Maximum number of columns for volume input echo.
This option corrects the volume value for each mesh when material
is defined by the xyz mesh. (0 means no correction). Value of volmat
is the number of scans per one xyz mesh side.
When epsout=1, results are plotted into eps files. The eps file is namedby replacing the extension with “.eps.” When epsout=2, error bars
are also displayed in the eps file, except for the 2-dimensional type(axis=xy, yz, xz, rz).
Generate Bitmap figure of 2-dimensional tally output. This file isnamed by replacing the extension with “.bmp.” When mesh=xyz andaxis=xy, yz, xz, it is available.
Output the tally results in the xyz-mesh in the input format of ParaView. This file is named by replacing the extension with “.vtk.” Whenmesh=xyz and axis=xy, yz, xz, it is available.
Format of output file for ParaView.
0: ascii, 1: binary.
Generate a file with OpenFOAM field data format. This file is named byreplacing the extension with “.foam.” When mesh=tet and axis=tet,
it is available.
Minimum value for i-th counter.
Maximum value for i-th counter.
Coordinate transformation number or definition for r-z or xyz mesh.
1: show lattice boundary in gshow, 0: do not show.
Threshold value of STD cut oﬀ.
When setting ndata=1, production cross section data are used innucleon-induced reactions on α, 14 N, 16 O targets, as shown below.
When setting ndata=2, pre-defined production cross section data in a
directory specified by file(27) are used in nuclear reactions only on
the target using the nuclear data library. This option is not available in
the energy region that e-mode is used.
When setting ndata=3, pre-defined production cross section data in a
directory specified by file(27) are used in nuclear reactions on all
targets. Note that except for e-mode, the nuclear data library and thenuclear reaction model are not used to calculate the yield on the target
whose production data are defined in file(27).

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.

6.7 [ T-Yield ] section

219

The following nuclear reactions are included in the available nuclear data for ndata=1:
4

He(n, x)3 H
N(n, x)14 C
16O(n, x)11 C
16
O(n, x)15 O
14N(p, x)13 N
16O(p, x)11 C
14

14

N(n, x)3 H
N(n, x)13 N
16O(n, x)14 C
4He(p, x)3 H
14
N(p, x)14 O
16O(p, x)14 C
1414N(n, x)7 Be
O(n, x)3 H
16
O(n, x)15 C
14N(p, x)7 Be
16
O(p, x)3 H
16
O(p, x)13 N
16

14N(n, x)11 Be
O(n, x)7 Be
16
O(n, x)13 N
14N(p, x)11 Be
16
O(p, x)7 Be
16
O(p, x)14 O
16

14N(n, x)10 C
O(n, x)11 Be
16O(n, x)16 N
14N(p, x)10 C
16
O(p, x)11 Be
16
O(p, x)15 O
16

14N(n, x)11 C
O(n, x)10 C
16
O(n, x)14 O
14N(p, x)11 C
16
O(p, x)10 C
16

For ndata=2,3, a file name of the production cross section data should be given as “[element symbol]+[massnumber(three digits)]+[-y-]+[incident particle(p or n)]+[.dat],” e.g., “O 016-y-n.dat” or “Pd107-y-n.dat.” Here, pand 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 metastablestate. The interpolation method INT = (1,2,3,4,5) are as follows.
INT = 12
3
4
5

: Histogram: Linear - Linear: Log - Linear: Linear - Log: Log - Log

The second line should be written as,# Elab (MeV)sigma (b)The incident energy [MeV] and cross section [barn] should be written in the first and second columns from thethird line. The number of the energy bin is not limited. Note that when the incident energy falls outside the energy
range specified by the data, the cross section data at the minimum or maximum energies are used, respectively forthe lower and higher energies. Larger nuclei than He are tallied from the data.

6 TALLY INPUT FORMAT

220

6.8 [ T-Product ] section
This tally gives particles and nuclei produced by nuclear reactions, decays, and fission, and also tallies source
particles. It diﬀers from [t-yield] in that the energy distribution and time distribution of produced particles andnuclei can be obtained in [t-product]. This tally is not available for produced particles by reactions of photons,
electrons, or low energy neutrons below dmax(2), which are described by data libraries. For e-mode≥1, however,particles and nuclei produced by neutron-induced reactions from the library can be obtained.
Table 6.21: [t-product] parameters (1)namemesh =

value
reg, r-z, xyz, tetpart =all (default),
particle name(omitted)all,number of materials

material =(next line)
mother =2 5 8(omitted)all,number of mother nuclei(next line)

208Pb Pbe-type =1, 2, 3, 4, 5

t-type =1, 2, 3, 4, 5
(omitted)
1, 2, -1, -2a-type =explanation
Geometry mesh: a geometry mesh subsection is required below
this option.
There is a maximum of six particles in a [t-product].
Specify materials for scoring.
all : default (same as no definition).
To set number of materials, define the material numbers in the next
line. The number of materials can be set as a negative value, inwhich case the specified materials are not included for scoring.
Material numbers.
Specify mother nuclei.
all : default (same as no definition).
When setting the number of mother nuclei, define the mothers in
the next line. The number of mother can be set as a negative value,
in which case the specified mothers are not included for scoring.
When output=atomic, mother cannot be specified.
Nucleus if specified using mass: without mass, all nuclei are isotopes of Pb. To specify multiple mother groups, use multiple[t-product] tallies.
Energy mesh: an energy mesh subsection is required below thisoption.
Time mesh: a time mesh subsection is required below this option.
Angle mesh with θ degrees of freedom for mesh=r-z: an angle
mesh subsection is required below this option.

6.8 [ T-Product ] section

221

Table 6.22: [t-product] parameters (2)nameunit =

value
1, 2, 3, 4, 5, 6

11, 12, 13, 14, 15, 16

21, 22, 23, 24, 25, 26

31, 32, 33, 34, 35, 36

explanation
1: [1/source]
2: [1/cm3 /source]
3: [1/MeV/source]
4: [1/cm3 /MeV/source]
5: [1/Lethargy/source]
6: [1/cm3 /Lethargy/source]
11:[1/nsec/source]
12:[1/cm3 /nsec/source]
13:[1/MeV/nsec/source]
14:[1/cm3 /MeV/nsec/source]
15:[1/Lethargy/nsec/source]
16:[1/cm3 /Lethargy/nsec/source]
21: [1/sr/source]
22: [1/cm3 /sr/source]
23: [1/MeV/sr/source]
24: [1/cm3 /MeV/sr/source]
25: [1/Lethargy/sr/source]
26: [1/cm3 /Lethargy/sr/source]
31:[1/nsec/sr/source]
32:[1/cm3 /nsec/sr/source]
33:[1/MeV/nsec/sr/source]
34:[1/cm3 /MeV/nsec/sr/source]
35:[1/Lethargy/nsec/sr/source]
36:[1/cm3 /Lethargy/nsec/sr/source]‘Lethargy’ in unit=5, 6, 15, 16, 25, 26, 35 or 36 is the natural logarithmic unit of energy defined byln(Eref /E) using a reference energy Eref and the particle energy E. Setting these units enables obtaining resultsin units of Lethargy, which are given as Lethargy widths, ln(Ehigh /Elow ), for each energy bin in the energy meshsubsection. 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.

6 TALLY INPUT FORMAT

222

Table 6.23: [t-product] parameters (3)nameaxis =

file =
resfile =output =valueeng, reg, x, y, z, r
tet
xy, yz, xz, rz
tfile name(omitted, D=file)x-txt =
y-txt =
z-txt =
gshow =

sourcenuclear (default)
nonelaelastic
decay
fissionatomic(omitted, D=1.0)(omitted)(omitted)(omitted)
1, 2, 3, 4, 5, 6, 7
(omitted, D=3)
(omitted)(omitted)(omitted)0 (default), 1, 2, 3, 4, 5

rshow =

0 (default), 1, 2, 3

ginfo =

0 (default),
1

factor =title =
angel =
sangel =2d-type =2resol =

1 (default)

width =
volume0.5 (default)(omitted)reg vol
iechrl =72 (default)

explanation
x axis value of output data.
x axis value of output data (only active with mesh=tet).
2-dimensional.
Time axis.
Define file names. This is required by each setting of axis.
Define a file name of the past tally in the restart calculation:even if several axis parameters were defined, specify only one
resfile.
Source particle.
Particles from nuclear reaction, including elastic.
Particles from nonelastic collision.
Particles from elastic collision.
Particles from decay.
Particles from fission.
Particles from atomic interaction.
Normalization factor.
Title.
ANGEL parameters.
Special format for ANGEL parameters.
Options for 2-dimensional plot.
x axis title.
y axis title.
z axis title.
When mesh=xyz and axis=xy,yz,xz, region border (1), material name (2), region name (3), and LAT number (4) are plottedusing this option. gshow=5 outputs only material colors in pixel
style when icntl=8.
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.
No geometry check in the case of gshow or rshow> 0.
Check geometry and draw a two-dimensional view with error
information.
Check geometry, draw two-dimensional view, and output a geometry error file (“.err”).
This option multiplies the region line resolution by a factor ofresol with the gshow or rshow option set to define the line
thickness.
The option defines the line thickness.
This option defines the volume for each region for reg mesh.
Volume definitions are required below this option. Values defined in [volume] are used in the case of no definition. If special description such as using () is used to specify a region
in reg=, its internally defined region number is output in input
echo when this volume subsection is not defined.
Volume definition. For details see Sec. 5.1.2.
Maximum number of columns for volume input echo.

6.8 [ T-Product ] section

223

Table 6.24: [t-product] parameters (4)namevolmat =value(omitted, D=9)

epsout =0 (default), 1, 2

bmpout =0(default), 1

vtkout =0(default), 1

vtkfmt =0(default), 1

foamout =0(default), 1

ctmin(i) =ctmax(i) =trcl =
dump =(omitted, D=-9999)(omitted, D= 9999)(omitted)
Number of data

(next line)

Data sequencegslat =
stdcut =1(default), 0(omitted, D=-1)

explanation
This option corrects the volume value for each mesh when material isdefined by the xyz mesh. (0 means no correction). Value of volmat is
the number of scans per one xyz mesh side.
When epsout=1, results are plotted into eps files. The eps file is namedby replacing the extension with “.eps.” When epsout=2, error bars
are also displayed in the eps file, except for the 2-dimensional type(axis=xy, yz, xz, rz).
Generate Bitmap figure of 2-dimensional tally output. This file isnamed by replacing the extension with “.bmp.” When mesh=xyz andaxis=xy, yz, xz, it is available.
Output the tally results in the xyz-mesh in the input format of ParaView. This file is named by replacing the extension with “.vtk.” Whenmesh=xyz and axis=xy, yz, xz, it is available.
Format of output file for ParaView.
0: ascii, 1: binary.
Generate a file with OpenFOAM field data format. This file is named byreplacing the extension with “.foam.” When mesh=tet and axis=tet,
it is available.
Minimum value for i-th counter.
Maximum value for i-th counter.
Coordinate transformation number or definition for r-z or xyz mesh.
For mesh=reg, the information is dumped on the file. If dump is negative, data are written by ascii, if positive, by binary.
Define the data sequence. The history information (nocas and nobch)
is necessary to use idmpmode=1.
1: show lattice boundary in gshow, 0: do not show.
Threshold value of STD cut oﬀ.

In the [t-product] tally, the dump option can only be used. If the dump option is set, the meshes of e-type
and t-type have only the meaning of 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, 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.
[t-product] can tally source particles, and the function can be used to modify the dump file. Dump files canbe read and information written to a new dump file through modifications made by setting the dump parameter andoutput=source in this tally section and icntl=6 in the [parameters] 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.
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.

6 TALLY INPUT FORMAT

224

6.9 [ T-DPA ] section
This tally gives the displacement per atom (DPA) value, or number of displaced atoms per target atom, which
represents radiation damage in materials irradiated by energetic particles. The result produced by this tally includes
the contribution of the Coulomb scattering cross section for charged particle transportation. The DPA of low energy
neutron incident reactions can be also obtained using e-mode≥1.
Table 6.25: [t-dpa] parameters (1)namemesh =

value
reg, r-z, xyz, tetpart =all (default),
particle name(omitted)all,number of materials

material =(next line)
mother =2 5 8(omitted)all,number of mother nuclei(next line)

208Pb Pb

unit =

1, 2

axis =

eng, reg, x, y, z, r
tet
xy, yz, xz, rz
file name(omitted, D=file)

file =
resfile =explanation
Geometry mesh: a geometry mesh subsection is required below
this option.
There is a maximum of six particles in a [t-dpa].
Specify materials for scoring.
all : default (same as no definition).
To set number of materials, define the material numbers in thenext line. The number of materials can be set as a negative value,
in which case the specified materials are not included for scoring.
Material numbers.
Specify mother nuclei.
all : default (same as no definition).
When setting the number of mother nuclei, define the mothers in
the next line. The number of mother can be set as a negativevalue, in which case the specified mothers are not included forscoring.
Nucleus if specified using mass: without mass, all nuclei are isotopes of Pb. To specify multiple mother groups, use multiple[t-dpa] tallies.
1: [DPA*1.e-24/source]
2: [DPA/source]
x axis value of output data.
x axis value of output data (only active with mesh=tet).
2-dimensional.
Define file names. This is required by each setting of axis.
Define a file name of the past tally in the restart calculation:even if several axis parameters were defined, specify only one
resfile.

6.9 [ T-DPA ] section

225

Table 6.26: [t-dpa] parameters (2)nameoutput =value
dpa
simplex-txt =
y-txt =
z-txt =
gshow =

all(omitted, D=1.0)(omitted)(omitted)(omitted)
1, 2, 3, 4, 5, 6, 7
(omitted, D=3)
(omitted)(omitted)(omitted)0 (default), 1, 2, 3, 4, 5

rshow =

0 (default), 1, 2, 3

ginfo =

0 (default),
1

factor =title =
angel =
sangel =2d-type =2resol =

1 (default)

width =
volume0.5 (default)(omitted)reg vol
iechrl =volmat =72 (default)(omitted, D=9)

explanation
Total DPA value.
total: total DPA value.
cutoﬀ1: DPA value when energies of charged particles produced
by reactions are below the cutoﬀ energy (emin).
cutoﬀ2: DPA value when energies of charged particles transported in materials are below the cutoﬀ energy (emin).
transpt: DPA value when charged particles are transported.
add d, t, 3 He, α, and nucleus contributions as PKA to simple.
Normalization factor.
Title.
ANGEL parameters.
Special format for ANGEL parameters.
Options for 2-dimensional plot.
x axis title.
y axis title.
z axis title.
When mesh=xyz and axis=xy,yz,xz, region border (1), material name (2), region name (3), and LAT number (4) are plottedusing this option. gshow=5 outputs only material colors in pixel
style when icntl=8.
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.
No geometry check in the case of gshow or rshow> 0.
Check geometry and draw a two-dimensional view with error
information.
Check geometry, draw two-dimensional view, and output a geometry error file (“.err”).
This option multiplies the region line resolution by a factor ofresol with the gshow or rshow option set to define the line
thickness.
The option defines the line thickness.
This option defines the volume for each region for reg mesh.
Volume definitions are required below this option. Values defined in [volume] are used in the case of no definition. If special description such as using () is used to specify a region
in reg=, its internally defined region number is output in input
echo when this volume subsection is not defined.
Volume definition. For details see Sec. 5.1.2.
Maximum number of columns for volume input echo.
This option corrects the volume value for each mesh whenmaterial is defined by the xyz mesh. (0 means no correction).
Value of volmat is the number of scans per one xyz mesh side.

6 TALLY INPUT FORMAT

226

Table 6.27: [t-dpa] parameter (3)nameepsout =value
0 (default), 1, 2

bmpout =0(default), 1

vtkout =0(default), 1

vtkfmt =0(default), 1

foamout =0(default), 1

ctmin(i) =ctmax(i) =trcl =
gslat =
stdcut =(omitted, D=-9999)(omitted, D= 9999)(omitted)1(default), 0(omitted, D=-1)

explanation
When epsout=1, results are plotted into eps files. The eps file is namedby replacing the extension with “.eps.” When epsout=2, error bars
are also displayed in the eps file, except for the 2-dimensional type(axis=xy, yz, xz, rz).
Generate Bitmap figure of 2-dimensional tally output. This file isnamed by replacing the extension with “.bmp.” When mesh=xyz andaxis=xy, yz, xz, it is available.
Output the tally results in the xyz-mesh in the input format of ParaView. This file is named by replacing the extension with “.vtk.” Whenmesh=xyz and axis=xy, yz, xz, it is available.
Format of output file for ParaView.
0: ascii, 1: binary.
Generate a file with OpenFOAM field data format. This file is named byreplacing the extension with “.foam.” When mesh=tet and axis=tet,
it is available.
Minimum value for i-th counter.
Maximum value for i-th counter.
Coordinate transformation number or definition for r-z or xyz mesh.
1: show lattice boundary in gshow, 0: do not show.
Threshold value of STD cut oﬀ.

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.

6.10 [ T-LET ] section

227

6.10 [ T-LET ] section
This tally can be used to obtain information on track length and dose as a function of the LET(dE/dx) of a given
material. This tally counts the energy losses of charged particles and nuclei; accordingly, the Event Generator mode(e-mode≥1) must be used to transport low-energy neutrons. Note that this tally does not consider the contributionsof electrons or positrons below their cutoﬀ energies ((emin)) in the result.
Table 6.28: [t-let] parameters (1)namemesh =

value
reg, r-z, xyz

part =
material =all (default),
particle name(omitted)all,number of materials(next line)
letmat =2 5 8(omitted)l-type =1, 2, 3, 4, 5

explanation
Geometry mesh: a geometry mesh subsection is required below thisoption.
There is a maximum of six particles in a [t-let].
Specify materials for scoring.
all : default (same as no definition).
To set number of materials, define the material numbers in the next line.
The number of materials can be set as a negative value, in which casethe specified materials are not included for scoring.
Material numbers.
Material id for LET(dE/dx).
If omitted, a real material is assumed.
If a material not used in the geometry is selected, its material density
must be defined in [material]. To calculate LET in water, definewater with 1 g/cm3 in [material].
When letmat<0 is set, PHITS automatically calculates dE/dx for water with 1 g/cm3 for electrons and positrons: please see “ParticleTherapy” in the recommendation setting for more details.
LET mesh:a LET mesh subsection must be added below this option. Note that the
LET spectrum may have unnatural peaks when a very fine mesh, e.g.,
20 meshes per order of magnitude, is set.

6 TALLY INPUT FORMAT

228

Table 6.29: [t-let] parameters (2)nameunit =

value
1, 2, 3, 4, 5, 6

7, 8, 9, 10, 11, 12

13, 14axis =
file =
resfile =factor =title =
angel =
sangel =2d-type =x-txt =
y-txt =
z-txt =

let, reg, x, y, z, r
xy, yz, xz, rz
file name(omitted, D=file)(omitted, D=1.0)(omitted)(omitted)(omitted)
1, 2, 3, 4, 5, 6, 7
(omitted, D=3)
(omitted)(omitted)(omitted)

explanation
1: Track [cm/(keV/µm)/source]
2: Dose [MeV/(keV/µm)/source]
3: Track [cm/ln(keV/µm)/source]
4: Dose [MeV/ln(keV/µm)/source]
5: Track [cm/source]
6: Dose [MeV/source]
7: Track [1/cm2 /(keV/µm)/source]
8: Dose [MeV/cm3 /(keV/µm)/source]
9: Track [1/cm2 /ln(keV/µm)/source]
10:Dose [MeV/cm3 /ln(keV/µm)/source]
11:Track [1/cm2 /source]
12:Dose [MeV/cm3 /source]∫
13: L ∗ f (L) [dimensionless], wheref (L)dL = 1.
∫
14: L ∗ d(L) [keV/µm], where d(L)dL = 1.
x axis value of output data.
2-dimensional.
Define file names. This is required by each setting of axis.
Define a file name of the past tally in the restart calculation: even if
several axis parameters were defined, specify only one resfile.
Normalization factor.
Title.
ANGEL parameters.
Special format for ANGEL parameters.
Options for 2-dimensional plot.
x axis title.
y axis title.
z axis title.

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 diﬀerent 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.

6.10 [ T-LET ] section

229

Table 6.30: [t-let] parameters (3)namegshow =value
0 (default), 1, 2, 3, 4

rshow =

0 (default), 1, 2, 3

ginfo =

0 (default),
12

resol =

1 (default)

width =
volume0.5 (default)(omitted)reg vol
iechrl =volmat =72 (default)(omitted, D=9)

epsout =0 (default), 1, 2

ctmin(i) =ctmax(i) =trcl =(omitted, D=-9999)(omitted, D= 9999)(omitted)

gslat =
stdcut =1(default), 0(omitted, D=-1)

explanation
When mesh=xyz and axis=xy,yz,xz, region border (1), materialname (2), region name (3), and LAT number (4) are plotted using
this option.
When mesh=xyz and axis=xy,yz,xz, region border (1), materialname (2), and region name (3) are plotted using this option. A xyz
mesh section must be added below this option.
No geometry check in the case of gshow or rshow> 0.
Check geometry and draw a two-dimensional view with error information.
Check geometry, draw two-dimensional view, and output a geometry error file (“.err”).
This option multiplies the region line resolution by a factor ofresol with the gshow or rshow option set to define the line thickness.
The option defines the line thickness.
This option defines the volume for each region for reg mesh. Volume definitions are required below this option. Values defined in[volume] are used in the case of no definition. If special description such as using () is used to specify a region in reg=, its
internally defined region number is output in input echo when thisvolume subsection is not defined.
Volume definition. For details see Sec. 5.1.2.
Maximum number of columns for volume input echo.
This option corrects the volume value for each mesh whenmaterial is defined by the xyz mesh. (0 means no correction).
Value of volmat is the number of scans per one xyz mesh side.
When epsout=1, results are plotted into eps files. The eps file isnamed by replacing the extension with “.eps.” When epsout=2,
error bars are also displayed in the eps file, except for the 2dimensional type (axis=xy, yz, xz, rz).
Minimum value for i-th counter.
Maximum value for i-th counter.
Coordinate transformation number or definition for r-z or xyz
mesh.
1: show lattice boundary in gshow, 0: do not show.
Threshold value of STD cut oﬀ.

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.

6 TALLY INPUT FORMAT

230

6.11 [ T-SED ] section
Calculation of the probability density of deposition energies in microscopic sites, called the lineal energy y or
specific energy z, is of great importance in the estimation of the relative biological eﬀectiveness (RBE) of charged
particles. However, such microscopic probability densities cannot be directly calculated by PHITS simulation
using the [t-deposit] tally, as PHITS is designed to simulate particle motion on a macroscopic scale and employs a continuous-slowing-down approximation (CSDA) for calculating the energy loss of charged particles. We
therefore introduced a special tally named [t-sed] for calculating the microscopic probability densities using amathematical function that can instantaneously calculate quantities around trajectories of charged particles. The
function was developed on the basis of track structure simulations considering productions of δ-rays and Auger
electrons. Note that the name ‘SED’ derives from ‘Specific Energy Distribution.’ Details of the calculation procedure are given elsewhere. 64 65 The function of [delta ray] section shouldn’t be used together with this tally.
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 diﬀerent 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 inmicroscopic sites can be expressed as the deposit energy ε in MeV, the lineal energy y in keV/µm, or the specificenergy z in Gy. The definitions of these quantities are given in ICRU Report 36. Usage of [t-sed] is similar tothat of [t-let].
Table 6.31: [t-sed] parameters (1)namemesh =

value
reg, r-z, xyz

part =
material =all (default),
particle name(omitted)all,number of materials(next line)
letmat =2 5 8(omitted)

se-unit =1, 2, 3

cdiam =

(omitted, D=1.0)

explanation
Geometry mesh: a geometry mesh subsection is required below thisoption.
There is a maximum of six particles in a [t-sed].
Specify materials for scoring.
all : default (same as no definition).
To set number of materials, define the material numbers in the next line.
The number of materials can be set as a negative value, in which casethe specified materials are not included for scoring.
Material numbers.
Material id for LET(dE/dx).
If omitted, a real material is assumed.
If a material not used in the geometry is selected, its material density
must be defined in [material]. To calculate LET in water, definewater with 1 g/cm3 in [material].
When letmat<0 is set, PHITS automatically calculates dE/dx for water with 1 g/cm3 for electrons and positrons: please see “ParticleTherapy” in the recommendation setting for more details.
Unit of deposition energy in microscopic sites.
1: deposit energy ε in MeV
2: lineal energy y in keV/µm
3: specific energy z in Gy
Diameter of the microscopic site in µm. A value from 0.001 to 2.0 canbe selected.

64 T. Sato, R. Watanabe and K. Niita, “Development of a calculation method for estimating the specific energy distribution in complex
radiation fields,” Radiat. Prot. Dosim. 122, 41-45 (2006).
65 T. Sato, Y. Kase, R. Watanabe, K. Niita and L. Sihver, “Biological dose estimation for charged-particle therapy using an improved PHITS
code coupled with a microdosimetric kinetic model,” Radiat. Res. 171, 107-117 (2009).

6.11 [ T-SED ] section

231

Table 6.32: [t-sed] parameters (2)namese-type =value
1, 2, 3, 4, 5

unit =

1, 2, 3, 4, 5, 6

7,8

axis =
file =
resfile =factor =title =
angel =
sangel =2d-type =x-txt =
y-txt =
z-txt =

sed, reg, x, y, z, r
xy, yz, xz, rz
file name(omitted, D=file)(omitted, D=1.0)(omitted)(omitted)(omitted)
1, 2, 3, 4, 5, 6, 7
(omitted, D=3)
(omitted)(omitted)(omitted)

explanationε, y or z mesh (unit is defined by se-unit):
an energy mesh subsection (specified in ne, emin, emax, etc.)
is required below this option. If a ‘Warning: Z bin is notenough!’ message occurs, the emin, emax, and ne parametersmust be changed. This warning indicates that the microdosimetric function cannot calculate the y (or z) distribution because therange is too small or the mesh resolution is too poor. For example, set se-type=3, emin=0.01, emax=10000.0, ne=60 or
higher for calculating the y distribution for cite diameter = 1 µm
(cdiam=1.0, se-unit=2).
1: Track [cm/(keV/µm)/source]
2: Dose [MeV/(keV/µm)/source], proportional to y ∗ f (y).
3: Track [cm/ln(keV/µm)/source]
4: Dose [MeV/ln(keV/µm)/source], proportional to y ∗ d(y).
5: Track [cm/source]
6: Dose [MeV/source]∫
7: y ∗ f (y) [dimensionless], wheref (y)dy = 1.
∫
8: y ∗ d(y) [keV/µm], where d(y)dy = 1.
These units are for the case of se-unit=2. For se-unit=1 and 3,[keV/µm] is replaced by [MeV] and [Gy], respectively.
x axis value of output data.
2-dimensional.
Define file names. This is required by each setting of axis.
Define a file name of the past tally in the restart calculation: even if
several axis parameters were defined, specify only one resfile.
Normalization factor.
Title.
ANGEL parameters.
Special format for ANGEL parameters.
Options for 2-dimensional plot.
x axis title.
y axis title.
z axis title.

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 diﬀerent
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.

6 TALLY INPUT FORMAT

232

Table 6.33: [t-sed] parameters (3)namegshow =value
0 (default), 1, 2, 3, 4, 5

rshow =

0 (default), 1, 2, 3

ginfo =

0 (default),
12

resol =

1 (default)

width =
volume0.5 (default)(omitted)reg vol
iechrl =volmat =72 (default)(omitted, D=9)

epsout =0 (default), 1, 2

ctmin(i) =ctmax(i) =trcl =(omitted, D=-9999)(omitted, D= 9999)(omitted)

gslat =
stdcut =1(default), 0(omitted, D=-1)

explanation
When mesh=xyz and axis=xy,yz,xz, region border (1), material name (2), region name (3), and LAT number (4) are plotted using this option. gshow=5 outputs only material colors in
pixel style when icntl=8.
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.
No geometry check in the case of gshow or rshow> 0.
Check geometry and draw a two-dimensional view with error
information.
Check geometry, draw two-dimensional view, and output a geometry error file (“.err”).
This option multiplies the region line resolution by a factor ofresol with the gshow or rshow option set to define the line
thickness.
The option defines the line thickness.
This option defines the volume for each region for reg mesh.
Volume definitions are required below this option. Default values are given in input echo in the case of no definition.
Volume definition. For details see Sec. 5.1.2.
Maximum number of columns for volume input echo.
This option corrects the volume value for each mesh whenmaterial is defined by the xyz mesh. (0 means no correction). Value of volmat is the number of scans per one xyz
mesh side.
When epsout=1, results are plotted into eps files. The eps
file is named by replacing the extension with “.eps.” Whenepsout=2, error bars are also displayed in the eps file, except
for the 2-dimensional type (axis=xy, yz, xz, rz).
Minimum value for i-th counter.
Maximum value for i-th counter.
Coordinate transformation number or definition for r-z or xyz
mesh.
1: show lattice boundary in gshow, 0: do not show.
Threshold value of STD cut oﬀ.

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.

6.12 [ T-Time ] section

233

6.12 [ T-Time ] section
This tally gives information on the number of particles of energy cut-oﬀ, escape, and decay in the time mesh[nsec]. Energy spectra of the particles can be also obtained. Especially, this is the unique tally can obtain energy
spectra of only the particles of energy cut-oﬀ.
Table 6.34: [t-time] parameters (1)explanation
Geometry mesh: a geometry mesh subsection is required below this option.
There is a maximum of six particles in a [t-time].

namemesh =

value
reg, r-z, xyz

part =
material =all (default),
particle name(omitted)all,number of materials(next line)
t-type =2 5 8
1, 2, 3, 4, 5

e-type =1, 2, 3, 4, 5

unit =

1, 2, 3, 4

axis =t, eng, reg, x, y, z, r
xy, yz, xz, rz
file name(omitted, D=file)

file =
resfile =output =factor =title =
angel =
sangel =2d-type =x-txt =
y-txt =
z-txt =

allcutoffescapedecay(omitted, D=1.0)(omitted)(omitted)(omitted)
1, 2, 3, 4, 5, 6, 7
(omitted, D=3)
(omitted)(omitted)(omitted)Specify materials for scoring.
all : default (same as no definition).
To set number of materials, define the material numbers in thenext line. The number of materials can be set as a negativevalue, in which case the specified materials are not included
for scoring.
Material numbers.
Time mesh: a time mesh subsection is required below thisoption.
Energy mesh: an energy mesh subsection is required below
this option.
1: [1/source]
2: [1/nsec/source]
3: [1/nsec/cm3 /source]
4: [1/nsec/cm3 /MeV/source]
x axis value of output data.
2-dimensional.
Define file names. This is required by each setting of axis.
Define a file name of the past tally in the restart calculation:even if several axis parameters were defined, specify only
one resfile.
Energy cut oﬀ, escape, and decay particles.
Energy cut oﬀ particles.
Escape particles.
Eecay particles.
Normalization factor.
Title.
ANGEL parameters.
Special format for ANGEL parameters.
Options for 2-dimensional plot.
x axis title.
y axis title.
z axis title.

6 TALLY INPUT FORMAT

234

Table 6.35: [t-time] parameters (2)namegshow =value
0 (default), 1, 2, 3, 4, 5

rshow =

0 (default), 1, 2, 3

ginfo =

0 (default),
12

resol =

1 (default)

width =
volume0.5 (default)(omitted)reg vol
iechrl =volmat =72 (default)(omitted, D=9)

epsout =0 (default), 1, 2

bmpout =0(default), 1

vtkout =0(default), 1

vtkfmt =0(default), 1

ctmin(i) =ctmax(i) =trcl =(omitted, D=-9999)(omitted, D= 9999)(omitted)

explanation
When mesh=xyz and axis=xy,yz,xz, region border (1), material name (2), region name (3), and LAT number (4) are plotted using this option. gshow=5 outputs only material colors in
pixel style when icntl=8.
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.
No geometry check in the case of gshow or rshow> 0.
Check geometry and draw a two-dimensional view with error
information.
Check geometry, draw two-dimensional view, and output a geometry error file (“.err”).
This option multiplies the region line resolution by a factor ofresol with the gshow or rshow option set to define the line
thickness.
The option defines the line thickness.
This option defines the volume for each region for reg mesh.
Volume definitions are required below this option. Values defined in [volume] are used in the case of no definition. If
special description such as using () is used to specify a region in reg=, its internally defined region number is output in
input echo when this volume subsection is not defined.
Volume definition. For details see Sec. 5.1.2.
Maximum number of columns for volume input echo.
This option corrects the volume value for each mesh whenmaterial is defined by the xyz mesh. (0 means no correction). Value of volmat is the number of scans per one xyz
mesh side.
When epsout=1, results are plotted into eps files. The eps
file is named by replacing the extension with “.eps.” Whenepsout=2, error bars are also displayed in the eps file, except
for the 2-dimensional type (axis=xy, yz, xz, rz).
Generate Bitmap figure of 2-dimensional tally output. This
file is named by replacing the extension with “.bmp.” Whenmesh=xyz and axis=xy, yz, xz, it is available.
Output the tally results in the xyz-mesh in the input format of
ParaView. This file is named by replacing the extension with“.vtk.” When mesh=xyz and axis=xy, yz, xz, it is available.
Format of output file for ParaView.
0: ascii, 1: binary.
Minimum value for i-th counter.
Maximum value for i-th counter.
Coordinate transformation number or definition for r-z or xyz
mesh.

6.12 [ T-Time ] section

235

Table 6.36: [t-time] parameters (3)namedump =

value
Number of data

(next line)

Data sequencegslat =
stdcut =1(default), 0(omitted, D=-1)

explanation
For mesh=reg, the information is dumped on the file. If dump is negative, data
are written by ascii, if positive, by binary.
Define the data sequence. The history information (nocas and nobch) is necessary to use idmpmode=1.
1: show lattice boundary in gshow, 0: no.
Threshold value of STD cut oﬀ.

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 calculationsof 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.

6 TALLY INPUT FORMAT

236

6.13

[T-Interact] section (formerly named [T-Star])

This tally gives the number of interactions occurred in the specified regions. It was formerly named [t-star]because it can calculate the star density, but we changed the name from version 3.04 in order to explicitly statethat it is the tally for counting the number of interactions. Note that the former name, [t-star], can still be
accepted even after version 3.04. To calculate the number of atomic interactions using this tally, use the EGS5
mode (negs=1).
Table 6.37: [t-interact] parameters (1)namemesh =

value
reg, r-z, xyz

MorP =

mean, prob(omissible)

part =all (default),
particle name(omitted)all,number of materials

material =(next line)
mother =2 5 8(omitted)all,number of mother nuclei(next line)

208Pb Pb

nucleus =(next line)(omitted)all,number of nuclei
208Pb Pbe-type =1, 2, 3, 4, 5

t-type =1, 2, 3, 4, 5
(omitted)
1, 2

unit =

11, 12
axis =

maxact =eng, reg, x, y, z, r
xy, yz, xz, rztact(omitted, D=100)

explanation
Geometry mesh: a geometry mesh subsection is required below
this option.
Output the mean number (mean) or probability density (prob) ofinteractions. Only when mesh=reg, select prob.
There is a maximum of six particles in a [t-interact].
Specify projectile particles of the reaction.
Specify materials for scoring.
all : default (same as no definition).
To set number of materials, define the material numbers in thenext line. The number of materials can be set as a negative value,
in which case the specified materials are not included for scoring.
Material numbers.
Specify mother nuclei.
all : default (same as no definition).
When setting the number of mother nuclei, define the mothers in
the next line. The number of mother can be set as a negativevalue, in which case the specified mothers are not included forscoring.
When output=atomic, mother cannot be specified.
Nucleus if specified using mass: without mass, all nuclei are isotopes of Pb. To specify multiple mother groups, use multiple[t-interact] tallies.
Specify output nuclei.
all : default (same as no definition).
When setting number of nuclei, define the nuclei in the next line.
Nucleus if specified with mass. Without mass, all nuclei are isotopes of Pb.
Energy mesh: an energy mesh subsection is required below thisoption.
Time mesh: a time mesh subsection is required below this option.
1: [1/cm3 /source]
2: [1/cm3 /MeV/source]
11:[1/cm3 /nsec/source]
12:[1/cm3 /nsec/MeV/source]
x axis value of output data.
2-dimensional.
Time axis.
Number of interaction (for MorP=prob).
Maximum number of interactions per history for axis=act. If
the number of interactions exceeds this value, the history is
counted as ‘overflow,’ whose probability is outputted just above‘sum over’ line.

6.13[T-Interact] section (formerly named [T-Star])

237

Table 6.38: [t-interact] parameters (2)namefile =
resfile =value
file name(omitted, D=file)

output =alldecay
elastic
nuclearfissionabsorption
heavyiontransmut
atomicdeltarayknockelec
atmfluauger
brems
photoelec
comptonpairprodannih
ets elast
ets ionizets e-exc
ets v-exc
ets p-exc
ets r-exc
ets dea
ets ioniz e-exc

x-txt =
y-txt =
z-txt =
gshow =

(omitted, D=1.0)(omitted)(omitted)(omitted)
1, 2, 3, 4, 5, 6, 7
(omitted, D=3)
(omitted)(omitted)(omitted)0 (default), 1, 2, 3, 4, 5

rshow =

0 (default), 1, 2, 3

factor =title =
angel =
sangel =2d-type =explanation
Define file names. This is required by each setting of axis.
Define a file name of the past tally in the restart calculation:even if several axis parameters were defined, specify only one
resfile.
Reaction type. Only one can be set.
All reactions.
Decay reaction.
Elastic scattering.
Nuclear reaction excluding elastic scattering. This corresponds
to nonela in [t-product].
Fission.
Absorption.
Heavy Ion reaction.
Reactions inducing transmutation of target nuclei.
Atomic interaction excluding multiple scattering.
Delta-ray production.
Production of knock-on electrons by electrons and positrons.
Atomic fluorescence x-ray emission.
Auger electron emission.
Bremsstrahlung.
Photoelectric eﬀect.
Compton scattering.
Electron-positron pair production.
Positron annihilation.
Elastic scattering in the track-structure mode.
Ionization in track-structure mode.
Electronic excitation in track-structure mode.
Vibration excitation in track-structure mode.
Photon excitation in track-structure mode.
Rotation excitation in track-structure mode.
Dissociative electron attachment in track-structure mode.
Sum of the ionization and electronic excitation in track-structuremode.
Normalization factor.
Title.
ANGEL parameters.
Special format for ANGEL parameters.
Options for 2-dimensional plot.
x axis title.
y axis title.
z axis title.
When mesh=xyz and axis=xy,yz,xz, region border (1), material name (2), region name (3), and LAT number (4) are plottedusing this option. gshow=5 outputs only material colors in pixel
style when icntl=8.
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.

6 TALLY INPUT FORMAT

238

Table 6.39: [t-interact] parameters (3)nameginfo =value
0 (default),
12

resol =

1 (default)

width =
volume0.5 (default)(omitted)reg vol
iechrl =volmat =72 (default)(omitted, D=9)

epsout =0 (default), 1, 2

bmpout =0(default), 1

vtkout =0(default), 1

vtkfmt =0(default), 1

ctmin(i) =ctmax(i) =trcl =
gslat =
stdcut =(omitted, D=-9999)(omitted, D= 9999)(omitted)1(default), 0(omitted, D=-1)

explanation
No geometry check in the case of gshow or rshow> 0.
Check geometry and draw a two-dimensional view with error information.
Check geometry, draw two-dimensional view, and output a geometryerror file (“.err”).
This option multiplies the region line resolution by a factor of resolwith the gshow or rshow option set to define the line thickness.
The option defines the line thickness.
This option defines the volume for each region for reg mesh. Volume
definitions are required below this option. Values defined in [volume]are used in the case of no definition. If special description such as using() is used to specify a region in reg=, its internally defined region
number is output in input echo when this volume subsection is not defined.
Volume definition. For details see Sec. 5.1.2.
Maximum number of columns for volume input echo.
This option corrects the volume value for each mesh when material isdefined by the xyz mesh. (0 means no correction). Value of volmat is
the number of scans per one xyz mesh side.
When epsout=1, results are plotted into eps files. The eps file is namedby replacing the extension with “.eps.” When epsout=2, error bars
are also displayed in the eps file, except for the 2-dimensional type(axis=xy, yz, xz, rz).
Generate Bitmap figure of 2-dimensional tally output. This file isnamed by replacing the extension with “.bmp.” When mesh=xyz andaxis=xy, yz, xz, it is available.
Output the tally results in the xyz-mesh in the input format of ParaView. This file is named by replacing the extension with “.vtk.” Whenmesh=xyz and axis=xy, yz, xz, it is available.
Format of output file for ParaView.
0: ascii, 1: binary.
Minimum value for i-th counter.
Maximum value for i-th counter.
Coordinate transformation number or definition for r-z or xyz mesh.
1: show lattice boundary in gshow, 0: do not show.
Threshold value of STD cut oﬀ.

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.

6.14 [ T-Dchain ] section239

6.14 [ T-Dchain ] section
This tally is used for generating input files for DCHAIN-SP. Figure 6.4 illustrates the flowchart of the connection calculation between PHITS and DCHAIN-SP.
PHITS

DCHAIN-SP

Nuclear reaction andtransport calculations

DCHAIN-SP data library•Neutron activation cross sections

with 175 group energy structure•Decay data library including

gamma-ray spectrum

Files produced by [T-dchain]

nuclear production yieldneutron energy spectrum with 175

group energy structure below 20 MeV

basic input file of DCHAIN-SP
information about link to the folder
having DCHAIN-SP data library•Data library about ratio of electron

capture and beta+ decay

DCHAIN-SP

Calculation of
production yield

Execution usingshell script

Calculated results

At arbitrary time
Production yieldRadioactivity(Bq)Decay heat(W)Gamma-ray spectrum

Figure 6.4: Concept of the connection calculation between PHITS and DCHAIN-SP.

In the PHITS calculation, [t-dchain] automatically creates [t-track] and [t-yield] as well as the input
file of DCHAIN-SP. The [t-track] tally calculates the neutron energy spectra below 20 MeV with a 1968energy-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-SP calculation, the neutron energy spectra are multiplied by the activation cross section
contained in the DCHAIN-SP 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-SP evaluates radioactivity, nuclide, decay heat, and the gamma energy spectrum at irradiation and cooling time. Please see the“\phits\recommendation\dchain\” folder for more details. When publishing results obtained using this tally,please provide a reference to the document 66 in footnote below.
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-SP calculation.
Setting e-mode≥1 in the [parameters] section enables calculation of the yields of radioactive nuclides produced by low-energy neutron reactions below 20 MeV using PHITS instead of the activation cross sections contained in the DCHAIN-SP data library. However, the accuracy of the event generator mode relative to that of the
DCHAIN-SP data library in terms of calculating the residual-nuclide yields has not been verified, and it is therefore 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-SP calculation.
From ver. 3.00, the natural isotope expansion defined in [material] was eﬀective in input files of DCHAINSP 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 eﬀective. For example, if a material is defined as follows:
MAT[1] Fe 1

56Fe 1a contribution of 56Fe included in Fe is ignored in the DCHAIN-SP calculation.

66 Tetsuya Kai, et al., “DCHAIN-SP 2001: High Energy Particle Induced Radioactivity Calculation Code”, JAERI-Data/Code-2001-016(2001) in Japanese6 TALLY INPUT FORMAT

240

Table 6.40: [t-dchain] parameters (1)
name
mesh=

value
reg, xyz

file=

file nametitle=
stdcut=ndata =

(omitted)(omitted, D=-1)
0(default), 1, 2, 3

timeevo=(next line)

numbertime and factor

outtime=(next line)

numbertime

explanation
Geometry mesh (Currently ONLY reg mesh and xyz mesh can be specified): a geometry mesh subsection must be added below this option. (reg= cell number).
Input file name of DCHAIN-SP. Any extension except .dtrk, .dyld,
or .dout can be used.
Title.
Threshold value of STD cut oﬀ.
When setting ndata=1, production cross section data are used in nucleoninduced reactions on α, 14 N, 16 O targets, as shown below.
When setting ndata=2, pre-defined production cross section data in a directory specified by file(27) are used in nuclear reactions only on thetarget using the nuclear data library. This option is not available in theenergy region that e-mode is used.
When setting ndata=3, pre-defined production cross section data in a directory specified by file(27) are used in nuclear reactions on all targets.
Note that except for e-mode, the nuclear data library and the nuclear reaction model are not used to calculate the yield on the target whose production data are defined in file(27).
Number of irradiation and cooling steps in DCHAIN-SP calculation.
time: time step of irradiation and/or cooling.
factor: normalized factor for beam intensity.
Time should be calculated from the end of the last step and not from thestart 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.
Number of output timings in the DCHAIN-SP calculation.
Output timing.
If a positive value is given as the output timing, it is calculated from thestart of the first irradiation step. If a negative value is given, it is calculated
from the end of last irradiation step. Except for this positive and negative
rule, the format for specifying the timing is the same as that for timeevo.
The timing cannot be specified until after all steps defined in timeevo arefinished.
To output the timing when no radioactive nuclide exists, e.g., 0.0 m, set
iprtb2=0 in the [t-dchain] 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.
See Sec. 6.7 for ndata.

6.14 [ T-Dchain ] section

241

Table 6.41: [t-dchain] parameters (2)
name
amp=
target =value(omitted,D=1.0)0, 1(omitted,D=0)

explanation
Power of source (source/second).
0: OFF; Not necessary to write target information:
the information is automatically determined from the [material], [cell],and [volume] sections.
1: ON; Necessary to write target information.
*To add nuclides that are not defined in the [material] in the DCHAIN-SP
calculation, and/or the volume is not set in the [volume], write target=1
and provide the related information as in Example 57.
*See example of target subsection for target=1 in Example 57.

In addition to the above parameters, the DCHAIN-SP 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, iprtb1, iprtb2, rprtb2, iprtb3, igsorg, ebeam, prodnp
The respective meanings of these parameters are given in the DCHAIN-SP manual.
Example 56: Example of input for [t-dchain] tally
1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:

mesh = reg
reg = 100
file = testDC.spd
title = [t-dchain] test calc.
amp = 1.0E12
timeevo = 4
3.0 h
2.0 h
3.5 h
15.5 h<-region mesh<-cell number<-file name of DCHAIN-SP input<-source power (source/sec)<-number of irradiation and cooling steps<-irradiation for 3 hours<-cooling for 2 hours<-irradiation for 3.5 hours<-cooling for 15.5 hours

1.0
0.0
1.0
0.0

outtime = 33.0 h-1.0 h
-3.0 h<-number of output timing<-3 hours later from the 1st irradiation start time<-1 hour later from the end of the last irradiation step<-3 hour later from the end of the last irradiation step

Calculation steps for irradiation and cooling time: timeevo

start

irradiation cooling irradiation

0

3h

2h

3.5h

cooling15.5h

Last irradiation time

3h
-1h
Output times of calculation results:outtime-3h

Not allowed to set

Figure 6.5: Relation between steps for irradiation and cooling and output times.

6 TALLY INPUT FORMAT

242

Example 57: Example for the setting of target material compositions and volumes for target=1
:
:
:
:
:
:
:
:
:

.......
target = 1
non
reg
vol
1
1
8000.0tg-list = 2
H-1
6.689E-02
O-16 3.345E-02
2
2
2000.0tg-list = 1
Fe-56 8.385E-02<-target material composition ON<-omissible<-serial number, cell number, volume<-number of the nuclides<-Element ID, Atomic Number,and Density of the atom (10ˆ24/cmˆ3)<-serial number, cell number, volume<-Number of the nuclides

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-SP.
• 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-SP: file name is set in the [t-dchain] tally.
• 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-SP data library is in “dch link.dat.”
Note that when DCHAIN-SP 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”

6.15 [ T-WWG ] section

243

6.15 [ T-WWG ] section
This tally gives parameters used for the [Weight Window] section. The tally serves as a Weight Window
Generator (WWG) to automatically obtain eﬀective settings of [Weight Window] for a user-defined virtual space.
When using this function, a test calculation using an input file including the [t-wwg] tally must be performed.
Long calculations can then be performed using the [Weight Window] section generated from this test calculation.
The parameters are determined by the number of particles entering the cells 67 . In the test calculation, PHITS
records the number of particles entering the cells specified in [t-wwg], and normalizes their values so as to set the
maximum of the weight window to 1. If no particle arrives at a specified cell, the weight window is set to the samevalue as that in the cell with the minimum fluence. This tally outputs one set of the [Weight Window] section foreach type of particle specified by part. If the energy or time mesh is defined in [t-wwg], the [Weight Window]
sections are output for each bin. You have to give volumes of each cells in [volume] section.
When you perform the restart calculation or use the sumtally function with an input file including [t-wwg],
set ireschk=1 in the [parameters] section.
The [t-wwg] parameters are formatted as follows.
Table 6.42: [t-wwg] parameters (1)namemesh =

value
reg, xyz

part =all (default),
particle name(omitted)all,number of materials

material =(next line)
e-type =t-type =unit =
axis =

2 5 8
1, 2, 3, 4, 5
1, 2, 3, 4, 5
(omitted)1(omitted)
eng, reg, txy, yz, xz
wwg

file =
resfile =file name(omitted, D=file)

factor =title =
angel =
rshow =

(omitted, D=1.0)(omitted)(omitted)0 (default), 1, 2, 3

explanation
Geometry mesh: only reg and xyz can be set; a geometry mesh subsection is required below this option.
There is a maximum of six particles in a [t-wwg].
Specify materials for scoring.
all : default (same as no definition).
To set number of materials, define the material numbers in the nextline.
Material numbers.
Energy mesh: an energy mesh subsection is required below this option.
Time mesh: a time mesh subsection is required below this option.
1: [1/cm2 /source]
x axis value of output data.
2-dimensional.
They are the same as [t-track].
To obtain [Weight Window] section, set axis=wwg.
To perform restart calculation, set two (or more) axis parameters, andthen set the first axis to reg, eng, or t.
Define file names. This is required by each setting of axis.
Define a file name of the past tally in the restart calculation: even if
several axis parameters were defined, specify only one resfile.
Normalization factor.
Title.
ANGEL parameters.
When mesh=xyz and axis=xy,yz,xz, region border (1), materialname (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.
67 To be precise, it is determined by the fluence of a Monte Carlo particle, i.e., a particle always having weight= 1.

6 TALLY INPUT FORMAT

244

Table 6.43: [t-wwg] parameters (2)nameginfo =value
0 (default),
12

resol =

1 (default)

width =
volume0.5 (default)(omitted)

epsout =0 (default), 1, 2

ctmin(i) =ctmax(i) =trcl =
gslat =
stdcut =(omitted, D=-9999)(omitted, D= 9999)(omitted)1(default), 0(omitted, D=-1)

explanation
No geometry check in the case of gshow or rshow> 0.
Check geometry and draw a two-dimensional view with error information.
Check geometry, draw two-dimensional view, and output a geometryerror file (“.err”).
This option multiplies the region line resolution by a factor of resolwith the rshow option set to define the line thickness.
The option defines the line thickness.
This option defines the volume for each region for reg mesh. Volume
definitions are required below this option. Values defined in [volume]are used in the case of no definition. If special description such as using() is used to specify a region in reg=, its internally defined region
number is output in input echo when this volume subsection is not defined.
When epsout=1, results are plotted into eps files. The eps file is namedby replacing the extension with “.eps.” When epsout=2, error bars
are also displayed in the eps file, except for the 2-dimensional type(axis=xy, yz, xz, wwg).
Minimum value for i-th counter.
Maximum value for i-th counter.
Coordinate transformation number or definition for r-z or xyz mesh.
1: show lattice boundary in gshow, 0: do not show.
Threshold value of STD cut oﬀ.

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
set:
set:

c71[0.0]c74[0.0]c72[c71+2.13496E-08]
c75[c74+9.29569E-09]

part = neutroneng = 21.00000E-03

c73[1.25478E-04]
c76[2.08987E-04]

1.00000E+03

reg
ww1
1
(8.94092E-05+c71)/c73
2(1.25478E-04+c71)/c73
3(8.53835E-05+c71)/c73

ww2(2.08987E-04+c74)/c76(1.26817E-04+c74)/c76(5.78131E-05+c74)/c76

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.

6.16 [ T-WWBG ] section245

6.16 [ T-WWBG ] section
This tally gives parameters used for the [ww bias] section. The tally serves as a Weight Window Bias Generator (WWBG) to automatically obtain eﬀective settings of [ww bias], which is used to bias [weight window].
The [ww bias] function is useful when the [weight window] parameters for a certain region are biased after
automatically generating the [weight window] section by [t-wwg]. Figure 4.48 shows a flowchart how to perform the transport calculation using [weight window] and [ww bias]. First, generate the [weight window]
section by [t-wwg]. If the obtained parameters of [weight window] are enough to eﬀectively use the variancereduction technique, the [ww bias] section is not needed. However, if they are not enough, the variance reduction
technique can be used more eﬀectively by biasing the [weight window] parameters for a certain region with [wwbias]. There are two methods to set the [ww bias] section; an automatic method using [t-wwbg], which is a
Weight Window Bias Generator (WWBG) and will be explained below, and a manual method by a user. Only one[t-wwbg] section can be set in one input file. [t-wwbg] is eﬀective only when icntl=15 in [parameters].
For details of [ww bias], see Sec. 4.20. When performing a transport calculation with [ww bias] and [weightwindow], set icntl=0 and iwwbias=1 in [parameters].
Set [ww bias]

Set [weight window]
・With setting [t-wwg], perform

・With setting [t-wwbg], performa normal calculation (icntl=0).

a sample calculation (icntl=15).

([weight window] is automatically set.)([ww bias] is automatically set.)or・Set [ww bias] manually.

Transport calculation with [weight window] and [ww bias]
・Set [weight window] and [ww bias] in the same input ﬁle.
・Execute PHITS with icntl=0 and iwwbias=1 in [parameters].

Figure 6.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 avector defined by two points (x0,y0,z0) and (x1,y1,z1), shown in Fig. 6.7. Figure 6.7 shows a cross-section
view of three diﬀerent 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 diﬀerences of radii and heights ofthe cylinders are given by r-mesh, z-mesh, respectively. In these parameters, the same number of values as then-mesh must be given. The bias values can be set from the inside of the cylindrical regions in f-mesh. f-meshmust be set of (n-mesh)+1. The last value of f-mesh is the bias value in the outside of the cylinders. The
fm4

zm3 zm2 zm1

rm3

fm3

rm2

fm2

rm1

fm1

(x0,y0,z0)(x1,y1,z1)

Figure 6.7: Parameters to define cylindrical regions.

6 TALLY INPUT FORMAT

246

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 beextended by the r-out parameter.
The [t-wwbg] parameters are formatted as follows.
Table 6.44: [t-wwbg] parametersnamemesh =

value
regpart =
e-type =all (default),
particle name1, 2, 3, 4, 5

t-type =1, 2, 3, 4, 5

axis =(omitted)
xy, yz, xz, wwbg

file =
angel =
x-txt =
y-txt =
z-txt =
rshow =

file name(omitted)(omitted)(omitted)(omitted)0 (default), 1, 2, 3

ginfo =

0 (default),
12

resol =

1 (default)

width =
epsout =0.5 (default)
0 (default), 1

x0, y0, z0 =x1, y1, z1 =n-mesh =r-mesh =n
rm1,rm2,· · · ,rmn

z-mesh =zm1,zm2,· · · ,zmn

f-mesh =fm1,fm2,· · · ,fmn,fm(n+1)

r-out =

(omissible, D=0)

explanation
Geometry mesh: only reg can be set; a geometry mesh subsection is required below this option.
There is a maximum of six particles in a [t-wwbg].
Energy mesh: an energy mesh subsection is required below thisoption.
Time mesh: a time mesh subsection is required below this option.
Restart calculation cannot be performed. When xy, yz, zx,
the rshow option is needed.
Define file names. This is required by each setting of axis.
ANGEL parameters.
x axis title.
y axis title.
z axis title.
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.
No geometry check in the case of gshow or rshow> 0.
Check geometry and draw a two-dimensional view with error
information.
Check geometry, draw two-dimensional view, and output a geometry error file (“.err”).
This option multiplies the region line resolution by a factor ofresol with the rshow option set to define the line thickness.
The option defines the line thickness.
When epsout=1, results are plotted into eps files. The eps fileis named by replacing the extension with “.eps.”
x, y, z coordinates of an initial point.
x, y, z coordinates of a terminal point.
The number of cylindrical regions.
The diﬀerence of radii of cylinders. The number of n-meshmust be set.
The diﬀerence of heights of cylinders. The number of n-meshmust be set.
Bias values in cylindrical regions. The number of (n-mesh)+1
must be set.
Radius to extend the outer void [cm].

6.16 [ T-WWBG ] section

247

The following is an example of [t-wwbg].
Example 58: Example of [t-wwbg].
1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:

[ T - WWBG ]mesh = reg
reg = allaxis = wwbg
file = wwbg.out
axis = yz
file = wwbyz.out
part = neutrone-type =1
ne =2
0.0 1e-3 1.0
x0 = 0.0
y0 = -20
z0 = 50x1 = 0.0
y1 = 20z1 = 150
n-mesh =3
r-mesh =10 10 10z-mesh =10 10 10f-mesh =1.0 0.5 0.1
r-out = 1000

0.05

In this example, the initial and terminal points are (0, -20, 50) and (0, 20, 150), respectively. The three cylindricalregions are defined with the central axis on the vector defined the two points. Figure 6.8 shows a spatial distributionof the bias values given by Filetheexample input. The radii of the three cylinders are defined by Dater-mesh,the diﬀerences= wwbyz01.dat= 09:30 08-Aug-2017of 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. 6.8.
x

no. = 1, ix = 110= 0.0000E+00 [cm]0

WWB [WWB]y [cm]

50

0

10−1

−50

0

50

100
z [cm]

150

200

plotted by ANGEL 4.35

Figure 6.8: Spatial distribution of bias values given by Example 58.

calculated by PHITS 2.95

6 TALLY INPUT FORMAT

248

6.17 [ T-Volume ] section
When you set mesh=reg in tally sections, you have to give volumes of each cell to estimate results in the unitof (/volume). PHITS has a function of automatic calculation to obtain the volumes using [t-volume]. In thisfunction, PHITS calculates the volumes by performing a Monte Carlo integration with setting the material of eachcell to be void and a special source region.
[t-volume] is eﬀective only when setting icntl=14 in [parameters] section. Only one [t-volume]
section can be set in one input file.
The format of parameters in [t-volume] is as follows.
Table 6.45: [t-volume] parametersnamemesh =

value
reg

file =
resfile =r-out =
title =
method =file name(omitted, D=file)(omitted, D=0.0)(omitted)(omitted, D=0)s-type =1, 2x0, y0, z0,
x1, y1, z1,
r0 =stdcut =(omitted, D=-1)

explanation
Geometry mesh: only reg can be set; a geometry mesh subsection isrequired below this option.
Define file names.
Define a file name of the past tally in the restart calculation.
Radius of the outer void. [cm]Title.
Option for Monte Carlo integration.
0: By particle track lengths.
1: By source points.
Source type for volume calculation.
1: Sphere source. The coordinates of the sphere, (x0, y0, z0), and its
radius, r0, have to be defined.
2: Rectangular solid source. The coordinates x0, x1, y0, y1, z0,
and z1 have to be defined.
Coordinates and radius.

Threshold value of STD cut oﬀ.

The source type in the volume calculation is specified by s-type. In s-type=1, the source generates on asphere 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 arectangular 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.

6.17 [ T-Volume ] section

249

An example of [t-volume] is as follows.
Example 59: Example of [t-volume]
1:
2:
3:
4:
5:
6:
7:
8:
9:

[ T - V o l u m e ]mesh = reg
reg = 101 102 103
file = volume.out
s-type =1x0 = 0.0
y0 = 0.0
z0 = 0.0
r0 = 50.0# mesh type is region-wise
104 105# file name of output for [volume]# 1: Sphere source, 2: Rectangular source# (D=0.0) x of sphere center# (D=0.0) y of sphere center# (D=0.0) z of sphere center# radius of sphere[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 formatof the output file is as follows.
[ T - V o l u m e ] offmesh = reg
....
....
....
....
[ V o l u m e ]
non
reg
1
101
2
102
....
....

# mesh type is region-wise
....
....
....
....

vol
non
5.0370E+02 0.2909
2.4727E+03 0.1634
....
....
....
....
....
....

# Information for Restart Calculation
....
....
....
....
....
....
....
....

Because the volumes are outputted in the format of [volume] section, the results can be used in the main calculation 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.

6 TALLY INPUT FORMAT

250

6.18 [ T-Userdefined ] section
This tally is used for estimating and outputting physical quantities that cannot be calculated by the other tallies.
To use this tally, the user must change “usrtally.f” and re-compile PHITS.
When [t-userdefined] is defined in an input file, PHITS calls the subroutine “usrtally” at each moment in
the PHITS simulation, i.e., with the same timing used for calling the dumpall option. A subroutine for outputting
all information is written in the default of “usrtally.f,” and the user can set the output so that only required information is output by revising this file: please see the read-me file or sample input file in “\phits\utility\usrtally\”
for more detail.
In [t-userdefined], several parameters can be used: file, for specifying a file name; nudtvar, for specifying the number of variables udtvar(i); udtvar(i)68 , for specifying a numerical value. These parameters can beused in the subroutine ‘usrtally’ without recompiling PHITS.
Table 6.46: [t-userdefined] parametersnamefile =

value
file namenudtvar =udtvar(i) =0(default)
Numerical value (D=0)

explanation
Output file names used in usrtally subroutine.
A maximum of 50 files can be used (the device numbers of these files
are from 151 to 200).
The number of available udtvar(i).
Parameters used in usrtally subroutine: these can be defined upto
i =nudtvar.

Example 60: An example input for [t-userdefined]
1:
2:
3:
4:
5:

file = output1.dat
file = output2.dat
nudtvar = 2
udtvar(1) = 20.0
udtvar(2) = -10.0<-its device number is iudtf(1)=151<-its device number is iudtf(2)=152<-nudtvar<-udtvar(1)<-udtvar(2)The following parameters can be used in the subroutine usrtally.
(1) NCOL:
This is an intrinsic variable in the program and denotes identification of process.
NCOL
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15

:
:
:
:
:
:
:
:
:
:
:
:
:
:
:

start of calculation
end of calculation
end of a batchsourcedetection of geometry error
recovery of geometry error
termination by geometry error
termination by weight cut-oﬀ
termination by time cut-oﬀ
geometry boundary crossing
termination by energy cut-oﬀ
termination by escape or leakage(n,x) reaction(n,n’x) reaction
sequential transport only for tally

68 This parameter plays the same role as udtparai (i = 0 − 9) before ver. 3.01. udtparai can be also set after ver. 3.02.

6.18 [ T-Userdefined ] section

251(2) npe, me:
These are the number of used PEs (Processor Elements) and ID number of each processor, respectively, inthe distributed-memory parallel computing.
(3) ipomp, npomp:
These are ID number of each core and the total number of used cores, respectively, in the shared memory
parallel computing.
(4) iusrtally:
This is a parameter to control whether subroutine usrtally is used or not. If [t-userdefined] isdefined 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 definedin [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.
(8) NOCAS, NOBCH, RCASC, RSOUIN:
NOCAS
NOBCH
RCASC
RSOUIN::::current history number in this batchcurrent batch number
real number of NOCAS+maxcas*(NOBCH-1)
sum of the weight of source particle(9) NO, IDMN, ITYP, KTYP, JTYP, MTYP, RTYP, OLDWT:
NO
IDMN
ITYP
KTYP
JTYP
MTYP
RTYP
OLDWT

:
:
:
:
:
:
:
:

cascade id in this history
material id
particle typeparticle kf-code
charge number of the particle
baryon number of the particle
rest mass of the particle (MeV)wight of the particle at (x,y,z)(10) QS:This is dE/dx for electrons at (x,y,z).

(11) IBLZ1, IBLZ2, ILEV1, ILEV2:
IBLZ1
IBLZ2
ILEV1
ILEV2

:
:
:
:

cell id at (x,y,z)cell id after crossing
level structure id of the cell at (x,y,z)level structure id of the cell after crossing(a) ILAT1:
This is a variable of level structure of cell.
(b) ILAT2:This is a variable of level structure of cell.

6 TALLY INPUT FORMAT

252(12) COSTH, UANG(1), UANG(2), UANG(3), NSURF:
COSTH
UANG(1,2,3)
NSURF

:
:
:

cosine of an angle of incidence in a surface crossing
x,y,z component of a normal vector of its surface, respectively
internal number of the surface(This is diﬀerent from the surface number defined in the [surface] section.)(13) NAME, NCNT(1), NCNT(2), NCNT(3):NAME
NCNT(1,2,3)::

collision number of the particle
values of counter 1, 2, and 3(14) WT, U, V, W:
WT
U, V, W::wight of the particle at (xc,yc,zc)
unit vector of momentum of the particle(15) E, T, X, Y, Z:
E
T
X, Y, Z:::

energy of the particle at (x,y,z) (MeV)time of the particle at (x,y,z) (nsec)
position coordinate of the preceding event point (cm)(16) EC, TC, XC, YC, ZC:
EC
TC
XC, YC, ZC:::

energy of the particle at (xc,yc,zc) (MeV)time of the particle at (xc,yc,zc) (nsec)
position coordinate of the particle (cm)(17) SPX, SPY, SPZ:
SPX, SPY, SPZ:

unit vector of spin direction of the particle(18) NZST:This is charge state of the particle.
(19) NCLSTS:
This variable means the number of produced particle and nucleus.
(a) MATHZ, MATHN, JCOLL, KCOLL:
MATHZ
MATHN
JCOLL
KCOLL

:
:
:
:

Z number of the mother nucleus
N number of the mother nucleus
reaction type id1
reaction type id2

JCOLL and KCOLL indicate the following meaning.

6.18 [ T-Userdefined ] section

JCOLL
0
1
2
3
4
5
6
7
8
9
10
11
13
14

KCOLL
0
1
2
3
4
5
6

:
:
:
:
:
:
:
:
:
:
:
:
:
:

253

nothing happen
Hydrogen collisions
Particle Decays
Elastic collisions
High Energy Nuclear collisions
Heavy Ion reactions
Neutron reactions by data
Photon reactions by data
Electron reactions by data
Proton reactions by data
Neutron event modedelta ray production
Photon reactions by EGS5
Electron reactions by EGS5

:
:
:
:
:
:
:

normalhigh energy fission
high energy absorption
low energy n elastic
low energy n non-elastic
low energy n fission
low energy n absorption(b) ICLUSTS, JCLUSTS, QCLUSTS, JCOUNT:
These variables have a array and denote the information on the produced particle and nucleus.

ICLUSTS
0
1
2
3
4
5
6
7

JCLUSTS(i)
i=0
=1
=2
=3
=4
=5
=6
=7

kind of particle
nucleus
protonneutronpion
photonkaon
muon
others

:
:
:
:
:
:
:
:

:
:
:
:
:
:
:
:

angular momentum
proton number
neutron number
itypstatus of the particle 0: real, <0 : deadcharge number
baryon number
kf code6 TALLY INPUT FORMAT254

QCLUSTS(i)
i=0
=1
=2
=3
=4
=5
=6
=7
=8
=9
= 10
= 11
= 12

:
:
:
:
:
:
:
:
:
:
:
:
:

impact parameter
x-component of unit vector of momentum
y-component of unit vector of momentum
z-componentof unit vector of momentum√
etot = p2 + m2 (GeV)
rest mass (GeV)
excitation energy (MeV)
kinetic energy (MeV)
weighttime (nsec)
x coordinate (cm)y coordinate (cm)z coordinate (cm)

6.19 [ T-Gshow ] section

255

6.19 [ T-Gshow ] section
This tally produces graphical geometry output for regions bounded by xyz mesh. These outputs can be obtained
without transport calculation using the option icntl=7 in the [parameters] section.
The option of output=10 (gshow=5 for other tallies) is useful for lattice and tetrahedral geometry with veryfine mesh.
Table 6.47: [t-gshow] parametersnamemesh =

value
xyz

axis =
file =
output =resol =
width =
title =
angel =
sangel =x-txt =
y-txt =
epsout =xy, yz, xz
file name
1
2
3
4
5
6
7
8
9
10
1 (default)
0.5 (default)(omitted)(omitted)(omitted)(omitted)(omitted)0 (default), 1

bmpout =0(default), 1

vtkout =0(default), 1

vtkfmt =0(default), 1

trcl =
gslat =
ginfo =

(omitted)1(default), 0
0 (default),
1
2

explanation
Geometry mesh: only xyz mesh; a geometry mesh subsection is required below
this option.
2-dimensional.
Define file names. This is required by each setting of axis.
Region boundary
Region boundary + material color
Region boundary + material nameRegion boundary + material color + material nameRegion boundary + region nameRegion boundary + material color + region nameRegion boundary + LAT number
Region boundary + material color + LAT number
No output
Material color in pixel style
This option multiplies the region line resolution by a factor of resol.
The option defines the line thickness.
Title.
ANGEL parameters.
Special format for ANGEL parameters.
x axis title.
y axis title.
Results are plotted into eps files. This eps file is named by replacing the extension into “.eps ”.
Generate Bitmap figure of 2-dimensional tally output. This file is named byreplacing the extension with “.bmp.” When mesh=xyz, axis and axis=xy,
yz, xz, it is available.
Output the tally results in the xyz-mesh in the input format of ParaView. This
file is named by replacing the extension with “.vtk.” When mesh=xyz, axis
and axis=xy, yz, xz, it is available.
Format of output file for ParaView.
0: ascii, 1: binary.
Coordinate transformation number or definition for r-z or xyz mesh.
1: show lattice boundary in gshow, 0: do not show.
No geometry check in the case of gshow or rshow> 0.
Check geometry and draw a two-dimensional view with error information.
Check geometry, draw two-dimensional view, and output a geometry error file(“.err”).

6 TALLY INPUT FORMAT

256

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. 4.40 in Sec. 4.6.4 is generated by the input shown below.
Example 61: [t-gshow] example
1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:

[ T - gshow ]mesh = xyz
x-type = 2
nx = 100xmin = -10.
xmax = 10
y-type = 1
ny = 1-5.0 5.0
z-type = 2nz= 100zmin = -10.
zmax = 10.
axis = xz
output = 8
file = cell-example6.dat
epsout = 1

6.20 [ T-Rshow ] section257

6.20 [ T-Rshow ] section
This tally produces graphical geometry output for regions bounded by xyz mesh with color plotting in proportion to physical quantities of the regions. Usually, this tally uses results obtained by a PHITS calculation withreg mesh as input data to display the distribution of the physical quantity. These outputs can be obtained withouttransport calculation using the option icntl=9 in the [parameters] section.
A scale of the color gradation can be changed by setting ANGEL parameters zlog and zlin to log and linear
scales, respectively. Default setting is zlin.
Table 6.48: [t-rshow] parametersnamemesh =

value
xyz

axis =
file =
output =xy, yz, xz
file name12
3
4
1 (default)
0.5 (default)(omitted)(omitted)(omitted)(omitted)(omitted)(omitted)resol =
width =
title =
angel =
sangel =x-txt =
y-txt =
z-txt =
reg =value
reg valiechrl =epsout =72 (default)
0 (default), 1

bmpout =0(default), 1

trcl =
gslat =
ginfo =

(omitted)1(default), 0
0 (default),
1
2

explanation
Geometry mesh: only xyz mesh; a geometry mesh subsection is required below
this option.
2-dimensional.
Define file names. This is required by each setting of axis.
Region boundary
Region boundary + material nameRegion boundary + region nameRegion boundary + LAT numberThis option multiplies the region line resolution by a factor of resol.
The option defines the line thickness.
Title.
ANGEL parameters.
Special format for ANGEL parameters.
x axis title.
y axis title.
z axis title.
Region definition.
Value definition with the same format as volume definition. For details see
Sec. 5.1.2.
Maximum number of columns for volume input echo.
Results are plotted into eps files. This eps file is named by replacing the extension into “.eps ”.
Generate Bitmap figure of 2-dimensional tally output. This file is named byreplacing the extension with “.bmp.” When mesh=xyz, axis and axis=xy,
yz, xz, it is available.
Coordinate transformation number or definition for r-z or xyz mesh.
1: show lattice boundary in gshow, 0: do not show.
No geometry check in the case of gshow or rshow> 0.
Check geometry and draw a two-dimensional view with error information.
Check geometry, draw two-dimensional view, and output a geometry error file(“.err”).

6 TALLY INPUT FORMAT

258

For example, Figure 6.9 can be obtained by the [t-rshow] tally shown below from the example (6) shown inSec. 4.6.4.
Example 62: [t-rshow] example[ T - rshow ]mesh = xyz
x-type = 2
nx = 100xmin = -10.
xmax = 10.
y-type = 1
ny = 1-5.0 5.0
z-type = 2
nz = 100zmin = -10.
zmax = 10.
axis = xz
output = 1
file = cell-example6-rshow.dat
epsout = 1
reg = (201<101[-1 1 0]<1) (201<101[0 1 0]<1) (201<101[1 1 0]<1)(201<101[-1 0 0]<1) (201<101[0 0 0]<1) (201<101[1 0 0]<1)(201<101[-1 -1 0]<1) (201<101[0 -1 0]<1) (201<101[1 -1 0]<1)
value
non
reg
val
# reg definition
1 1000001
1.0000E+00 # ( 201 < 101[ -1 1 0 ] < 1 )2 1000002
2.0000E+00 # ( 201 < 101[ 0 1 0 ] < 1 )3 1000003
3.0000E+00 # ( 201 < 101[ 1 1 0 ] < 1 )4 1000004
4.0000E+00 # ( 201 < 101[ -1 0 0 ] < 1 )5 1000005
5.0000E+00 # ( 201 < 101[ 0 0 0 ] < 1 )6 1000006
6.0000E+00 # ( 201 < 101[ 1 0 0 ] < 1 )7 1000007
7.0000E+00 # ( 201 < 101[ -1 -1 0 ] < 1 )8 1000008
8.0000E+00 # ( 201 < 101[ 0 -1 0 ] < 1 )9 1000009
9.0000E+00 # ( 201 < 101[ 1 -1 0 ] < 1 )10Values5x [cm]

1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:
28:
29:
30:
31:

0

−5

−10
−10

−5

100

0
z [cm]

5

Figure 6.9: Example of [t-rshow].

10

6.21 [ T-3Dshow ] section259

6.21 [ T-3Dshow ] section
This tally produces graphical geometry output by 3-dimensional view. This tally can be generated withouttransport calculation using the option icntl=11 in the [parameters] section.
Table 6.49: [t-3dshow] parameters (1)nameoutput =

value
0
1
2
3 (default)(omitted)all,number of materials

explanation
Draft
Only region boundary
Without region boundary
Region boundary + color
Specify materials for display.
all : default (same as no definition).
To set number of materials, define the material numbers in the next
line. The number of materials can be set as a negative value: in thiscase the specified materials are not included for display.

(next line)
x0, y0, z0 =2 5 8
(D=0.0)e-the =
e-phi =
e-dst =
l-the =
l-phi =
l-dst =
w-wdt =
w-hgt =
w-dst =

(D=80)(D=140)(D=w-dst*10)(D=e-the)(D=e-phi)(D=e-dst)(D=100)(D=100)(D=200)w-mnw =
w-mnh =
w-ang =
heaven =mirror =(D=100)(D=100)(D=0.0)
(D=y)
(D=0)

Material numbers.
Coordinates of original point for view point and light source. Centerof screen is defined by this point and the view point.
View point angle θ [degrees] from z axis.
Zzimuthal angle for view point ϕ [degrees] from x axis.
Distance between view point and origin [cm].
Light source angle θ [degrees] from z axis.
Azimuthal angle for light source ϕ [degrees] from x axis.
Distance between light source and origin [cm].
Width of screen frame [cm].
Height of screen frame [cm].
Screen frame distance from origin [cm]. A straight line drawn between the center of the screen frame and the origin crosses the screen
surface vertically, and passes through the view point.
Number of meshes in horizontal direction.
Number of meshes in vertical direction.
Angle of frame [degrees].
Topside direction; set x, -x, y, -y, z, -z.
=-1; Mirror transformation in horizontal direction.

material =6 TALLY INPUT FORMAT

260

Polar
coordinates

Eye Point(e-the,e-phi,e-dst)

Picture Flame

Polar
Coordinates

Light source(l-the,l-phi,l-dst)
e-dst
w-dst
w-hgt
(w-mnh)w-wdt(w-mnw)

w-mnw 㽢 w-mnh 䠙 #Pixel
100 㽢 100 (default)

Origin (x0,y0,z0) XYZ-coordinates
Figure 6.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).

6.21 [ T-3Dshow ] section

261

Table 6.50: [t-3dshow] parameters (2)nameline =value
0 (default), 1

r-out =
shadow =bright =dark =
box =box
matinbox =(D=50000)(D=0)(D=0.8)(D=0.2)(D=0)
10 numbers(omitted)all,number of materials(next line)
reginbox =resol =
width =
file =
title =
angel =
sangel =x-txt =
y-txt =
z-txt =
epsout =258(omitted)all,region numbers
1 (default)
0.5 (default)
file name(omitted)(omitted)(omitted)(omitted)(omitted)(omitted)0 (default), 1

axishow =(D=1) 0, 1, 2

explanation
When output=1, 3,
0: material boundary + surface boundary;
1: material boundary + surface boundary + region boundary.
Radius of outer void including view point, and light source [cm].
Shadow level (0:no shadow, 2 is recommended).
Brightness limit (1:max, 0:no brightness).
Darkness limit (1:no darkness, 0:max).
Number of penetrations per box; maximum=5.
Box definition (see below).
Materials in the box for display.
all: default (same as no definition);
If number of materials is set, material numbers should be defined in thenext line (number of materials cannot be set as negative).
Material numbers.
Regions in the box for display.
all: default (same as no definition);If the matinbox is defined for a region, the region is not displayed.
This option multiplies the region line resolution by a factor of resol.
The option defines the line thickness.
Define file names.
Title.
ANGEL parameters.
Special format for ANGEL parameters.
x axis title.
y axis title.
z axis title.
Results are plotted into eps files. This eps file is named by replacing theextension into “.eps ”.
0: No. Axis not shown.
1: Small axis is shown in the lower-left of the figure.
2: Large axis is shown in the center of the figure.

The definitions of the rules for reg= and reginbox= are the same as that for the region mesh in Sec. 5.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.

6 TALLY INPUT FORMAT

262

6.21.1 Box definition
A maximum of five penetration boxes can be defined; defined boxes become transparent. To define a box, threepoints must first be set as b0 (x0 ,y0 ,z0 ), b1 (x1 ,y1 ,z1 ), and b2 (x2 ,y2 ,z2 ), respectively. The fourth point b3 from b0 isdefined to lie L cm in the vertical direction of the plane defined by these three points, i.e., in the ( b2 - b0 ) direction.
In the box definition, a coordinate transformation such as trcl= transform number or trcl = (........) canbe used prior to the definition of the points.
This function may fail when a void region is included in the penetration box; in this case, the user should fill
the void region with a material of very low density, e.g., air.
The box definition is shown below. Each relation is also shown in Fig. 6.11.

box = 2box
x0 y0 z0x1 y1 z1x2 y2 z2 Lbox
trcl = 2x0 y0 z0x1 y1 z1x2 y2 z2 Lbox
*trcl = (0 0 0
0.0 0.0 0.0-5.0 0.0 0.0
0.0 0.0 5.0

0 90 90

90 60 150

90 30 60

5.0

( x1 , y1 , z1 )( x3 , y3 , z3 )L

( x0 , y0 , z0 )( x2 , y2 , z2 )Figure 6.11: Example of box definition.

-1)6.21 [ T-3Dshow ] section263

6.21.2 3dshow example
Example 63: [t-3dshow] example (1)
1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:
28:
29:
30:
31:

[cell]
1 0 -1 fill=1
2 0 -41 42 -43 44 -45 46 u=1 fill=5
22 0 -41 42 -43 44 -45 46 u=1 trcl=(0 0 20) fill=6
23 like 22 but trcl=(0 0 40) fill = 7
5 0 -21 22 -23 24 -25 26 u=5 lat=1 fill=3
6 0 -21 22 -23 24 -25 26 u=6 lat=1 fill= -1:1 0:0 0:0 2 2(0 0 5) 2
7 0 -21 22 -23 24 -25 26 u=7 fill= -1:1 0:0 0:0 2 3 2 lat=1
3 1 3.97300E-02 3 u=2
4 6 4.18280E-02 -3 u=2
13 5 8.47130E-04 -3 u=3
14 3 1.23620E-01 3 u=3
8 -1 +1[surface]1rpp -15 15 -5 5 -5 55
21
px
5
22
px
-5
23
py
5
24
py
-5
25
pz
15
26
pz
-5
41
px
15
42
px -15
43
py
5
44
py
-5
45
pz
15
46
pz
-5
5
rpp -20 20 -5 5 -5 35
6rpp -20 20 -5 5 -5 15
7rpp -20 20 -5 5 35 55
3c/y
0 10 4In 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.

Example 64: [t-3dshow] example (2)
1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:

[t-3dshow]
output = 3
heaven = x
resol = 2
width = 0.1
x0 = 0y0 = 0z0 = 25e-the = 70
e-phi = 50
e-dst = 1000
l-the = 50l-phi = 25
l-dst = 2000
w-wdt = 60
w-hgt = 40
w-dst = 150
file = dshow.dat

6 TALLY INPUT FORMAT

264

The output result is thenA region boundary can be added using option line=1 to produce the following box, which shows how thelattices are set up:

Setting material number 5 to be transparent and adding shadows usingmaterial = -1
5
shadow = 2

produces the following box:

6.21 [ T-3Dshow ] section

265

Next, defining the following box:
box = 1
box
0
100
0

10
10
10

30
30
100 100

produces a transparent box that shows the inside of its body:As a final example, by adding
reg = ( 3 < 6[0 0 0] )matinbox = 1
6

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.

7 PROCESSING DUMP FILE

266

7

Processing dump file

You can write down the information on transport particles on dump file by [t-cross], [t-time], [t-product]
tallies. If you set the dump file as a source, you can calculate the sequential transport. Furthermore, you can get
the information which cannot be obtained by the tally functions in PHITS by processing the dump file. To process
the dump file, however, you need to make program to process the dump file. In the following, we show a program
to process the dump file as an example of such program.
The following program is a simple program which converts the ascii dump file to binary dump file, and viceversa. The following simple program could help you to make a program to process the dump file. The source
program “dump-a.f” is attached in the folder “\src\” and the execute file “dump a.exe” in Windows system isinclude in the folder “\bin\.”
File 3: dump-a.f
1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:
28:
29:
30:
31:
32:
33:
34:
35:
36:
37:
38:
39:
40:
41:
42:
43:
44:
45:
46:
47:
48:
49:
50:
51:
52:
53:
54:

***************************************************************************
This program exchanges the binary data and the ascii data**of dump file.
****modified by K.Niita on 2005/08/15
*
*
*
*
*
*
*
*
*
************************************************************************
implicit real*8 (a-h,o-z)*----------------------------------------------------------------------dimension isdmp(0:30)
dimension jsdmp(0:30)
data isdmp / 31*0 /data jsdmp / 31*0 /character chin*80
character chot*80
logical exex
character dmpc(30)*4
data dmpc / ’ kf’,’
x’,’
y’,’
z’,’
u’,’
v’,’
w’,
&
’
e’,’ wt’,’ tm’,’ c1’,’ c2’,’ c3’,&
’ sx’,’ sy’,’ sz’,’ n0’,’ nc’,’ nb’,’ no’,
&
’
’,’
’,’
’,’
’,’
’,’
’,
&
’
’,’
’,’
’,’
’/
dimension dmpd(30)dimension dmpp(30)data dmpp / 2112.,
0.0,
0.0,
0.0,
0.0,
0.0,
1.0,
&
100.,
1.0,
0.0,
0.0,
0.0,
0.0,
&
0.0,
0.0,
0.0,
0.0,
1.0,
1.0,
1.0,
&
0.0,
0.0,
0.0,
0.0,
0.0,
0.0,
0.0,
&
0.0,
0.0,
0.0/
*----------------------------------------------------------------------in = 5
io = 6
id = 20
ia = 21iserr = 0*----------------------------------------------------------------------*
user program frag : 0 => no, 1 => with user program*----------------------------------------------------------------------iuser = 0*----------------------------------------------------------------------*
read ascii or binary frag*----------------------------------------------------------------------write(io,*) ’ ** 0 => read binary to ascii’
write(io,*) ’ ** 1 => read ascii to binary’read(in,*,end=993) iasb*----------------------------------------------------------------------*
read the name of input dump file*----------------------------------------------------------------------write(io,*)write(io,*) ’ ** put the file name of input dump file’

267

55:
56:
57:
58:
59:
60:
61:
62:
63:
64:
65:
66:
67:
68:
69:
70:
71:
72:
73:
74:
75:
76:
77:
78:
79:
80:
81:
82:
83:
84:
85:
86:
87:
88:
89:
90:
91:
92:
93:
94:
95:
96:
97:
98:
99:
100:
101:
102:
103:
104:
105:
106:
107:
108:
109:
110:
111:
112:
113:
114:
115:
116:
117:
118:
119:
120:
121:
122:
123:
124:
125:

read(in,’(a80)’,end=998) chininquire( file = chin, exist = exex )if( exex .eqv. .false. ) thenwrite(io,*) ’ ** Error : the file does not exist’
goto 999
end ifif( iasb .eq. 0 ) thenopen(id, file = chin,&
form=’unformatted’,status = ’old’ )else
open(id, file = chin,&
form=’formatted’,status = ’old’ )end if*----------------------------------------------------------------------*
read the number of data and data sequence*----------------------------------------------------------------------write(io,*)write(io,*) ’ ** put the number of data in a record’read(in,*,end=997) isdmp(0)write(io,*)write(io,*) ’ ** put the ID numbers of data in a record’read(in,*,end=996) ( isdmp(i), i = 1, isdmp(0) )do k = 1, isdmp(0)if( isdmp(k) .gt. 20 .or.
&
isdmp(k) .le. 0 ) goto 992
jsdmp(isdmp(k)) = k
end dowrite(io,*)write(io,’(’’ # dump data : ’’,30(a4))’)&( dmpc(isdmp(j)), j = 1, isdmp(0) )*----------------------------------------------------------------------*
read the name of output dump file*----------------------------------------------------------------------write(io,*)write(io,*) ’ ** put the file name of output’read(in,’(a80)’,end=998) chotinquire( file = chot, exist = exex )if( exex .eqv. .true. ) thenwrite(io,*)write(io,*) ’ ** Warning : the file already exists’write(io,*) ’ ** Do you want to overwrite ?’write(io,*) ’ ** Yes <= 0, No <= 1’read(in,*,end=995) iyes
if( iyes .ne. 0 ) goto 999
end ifif( iasb .eq. 0 .or. iuser .ne. 0 ) thenopen(ia, file = chot,&
form=’formatted’,status = ’unknown’ )else
open(ia, file = chot,&
form=’unformatted’,status = ’unknown’ )end if*----------------------------------------------------------------------*
read the number of records to read*----------------------------------------------------------------------write(io,*)write(io,*) ’ ** put the number of records to read’
write(io,*) ’ ** all <= 0, or positive integer’read(in,*,end=994) irec*----------------------------------------------------------------------*
start reading the data*----------------------------------------------------------------------write(io,*)write(io,*) ’ ** start read and write the data’*----------------------------------------------------------------------jrec = 0100
jrec = jrec + 1
if( irec .gt. 0 .and. jrec .gt. irec ) goto 500
687
continueif( iasb .eq. 0 ) thenread(id,end=688,err=690)

7 PROCESSING DUMP FILE

268

126:
127:
128:
129:
130:
131:
132:
133:
134:
135:
136:
137:
138:
139:
140:
141:
142:
143:
144:
145:
146:
147:
148:
149:
150:
151:
152:
153:
154:
155:
156:
157:
158:
159:
160:
161:
162:
163:
164:
165:
166:
167:
168:
169:
170:
171:
172:
173:
174:
175:
176:
177:
178:
179:
180:
181:
182:
183:
184:
185:
186:
187:
188:
189:
190:
191:
192:
193:
194:
195:
196:

&

( dmpd(isdmp(k)), k = 1, isdmp(0) )else
read(id,’(30(1p1d24.15))’,end=688,err=690)&( dmpd(isdmp(k)), k = 1, isdmp(0) )end ifgoto 689
688
if( irec .gt. 0 ) thenrewind id
goto 687
else
goto 500
end if690
continueiserr = iserr + 1
write(io,’(’’ ** Error in dump file no =’’,i5)’) iserrgoto 687
689
continue*----------------------------------------------------------------------*
user program here*----------------------------------------------------------------------if( iuser .ne. 0 ) thendo k = 1, 20
if( jsdmp(k) .gt. 0 ) dmpp(k) = dmpd(k)end dokf = nint( dmpp(1) )x = dmpp(2)y = dmpp(3)z = dmpp(4)u = dmpp(5)v = dmpp(6)w = dmpp(7)e = dmpp(8)wt = dmpp(9)t = dmpp(10)n1 = nint( dmpp(11) )n2 = nint( dmpp(12) )n3 = nint( dmpp(13) )sx = dmpp(14)sy = dmpp(15)sz = dmpp(16)n0 = nint( dmpp(17) )nc = nint( dmpp(18) )nb = nint( dmpp(19) )no = nint( dmpp(20) )end if*----------------------------------------------------------------------*
write data on the file*----------------------------------------------------------------------if( iuser .eq. 0 ) thenif( iasb .eq. 0 ) thenwrite(ia,’(30(1p1d24.15))’)&( dmpd(isdmp(k)), k = 1, isdmp(0) )else
write(ia)&( dmpd(isdmp(k)), k = 1, isdmp(0) )end ifend if*----------------------------------------------------------------------goto 100*----------------------------------------------------------------------*
end of process*----------------------------------------------------------------------500
continue
write(io,*) ’ ** end of read and write the data’write(io,’(’’ ** number of processed records is ’’,&i8)’) jrec-1
write(io,*)close( id )close( ia )goto 999*-----------------------------------------------------------------------

269

197:
198:
199:
200:
201:
202:
203:
204:
205:
206:
207:
208:
209:
210:
211:
212:
213:
214:
215:
216:
217:
218:
219:
220:

992 continue
write(io,*) ’ ** Error : ID should be 1 - 20’
goto 999
993 continue
write(io,*) ’ ** Error : the ascii or binary frag is wrong’goto 999
994 continue
write(io,*) ’ ** Error : the number of records is wrong’goto 999
995 continue
write(io,*) ’ ** Error : the answer should be 0 or 1’
goto 999
996 continue
write(io,*) ’ ** Error : the ID numbers is wrong’goto 999
997 continue
write(io,*) ’ ** Error : the number of data is wrong’goto 999
998 continue
write(io,*) ’ ** Error : file name is wrong’goto 999
999 continue
stop
end

The input parameters are read from normal input, i.e., from console, in an interactive way. When you executethe program, it asks you as,** 0 => read binary to ascii** 1 => read ascii to binary
You put 0 for binary, 1 for ascii. Next it asks you the name of target dump file.
** put the file name of input dump file
You put the name of target dump file.
** put the number of data in a record
The program ask you the number of data in a record. You put positive number for both ascii and binary.
** put the ID numbers of data in a record
You put ID for the data. See kind of dump data and ID, in Tables 5.4 5.5.
** put the file name of output
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.
** put the number of records to read** all <= 0, or positive integer
If this number is larger than total record number, the program turns back to the top of the data. Finally, the numberof 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 3.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 directionof spin, respectively. By using these variables, you can make a program to obtain desired quantities.

8 OUTPUT CUTOFF DATA FORMAT

270

8Output cutoﬀ data format

The information for neutron, photon, electron, positron, and proton below the cut-oﬀ energy can be written in
the output file (file(12), file(13), and file(10)), in order to continue these transport calculation by otherMonte Carlo codes such as MCNP and EGS4. The data are written in binary. The format is shown below.

rd, rn, ( data(i), i = 1, nint(abs(rd)) )rd, rn, ( data(i), i = 1, nint(abs(rd)) )................
................

First, in the case of incut=1, and no importance option (rd<0).
rd, rn, x, y, z, ( e(i), u(i), v(i), w(i), i = 1, n )rd, rn, x, y, z, ( e(i), u(i), v(i), w(i), i = 1, n )................
................

Next, incut=1 with importance option (rd>0),
rd, rn, x, y, z, ( e(i), u(i), v(i), w(i), wt(i), i = 1, n )rd, rn, x, y, z, ( e(i), u(i), v(i), w(i), wt(i), i = 1, n )................
................

incut=2 and no importance option (rd<0),
rd, rn, x, y, z, ( e(i), u(i), v(i), w(i), t(i), i = 1, n )rd, rn, x, y, z, ( e(i), u(i), v(i), w(i), t(i), i = 1, n )................
................

incut=2 with importance option (rd>0),
rd, rn, x, y, z, ( e(i), u(i), v(i), w(i), wt(i), t(i), i = 1, n )rd, rn, x, y, z, ( e(i), u(i), v(i), w(i), wt(i), t(i), i = 1, n )................
................

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.

271

9

Region error check

In developing a complex geometry, it is diﬀcult to define the geometry without mistakes such as double-definedor undefined regions. Correspondingly, a function for automatically detecting double-defined or undefined regions
was implemented after version 2.67. This geometry check function works when specifying a tally for generating
the two-dimensional view of a geometry: such tallies include [t-gshow], [t-rshow], and other tallies involving
setting axis=xy,yz,xz or the gshow (icntl=8) or rshow (icntl=10) options.
The ginfo parameter is assigned to each tally to control this geometry check function. ginfo is set =0 for nogeometry check, =1 to check the geometry and draw a two-dimensional view with error information (see Fig. 9.1),
and =2 to check geometry, draw a two-dimensional view, and output a geometry error file that specifies the xyz
coordinates of the error location. The default value of ginfo for tallies depicting a two-dimensional geometry is 2.
Figure 9.1 shows an example of a two-dimensional view with geometry errors. Double-defined regions are
painted in black, while undefined regions are in purple. When an undefined region is detected, its surrounding
regions may disappear from the figure.

Figure 9.1: Output including geometry errors.
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:
Errors of cell definition in EPS Page No. =1
Overlapped Cell IDs x, y, z coodinates(Cells 0
0 indicate undefined region)
100
102-4.847761E+00 1.234568E-11 -1.211940E+00
00-4.241791E+00 -2.500000E+00 -8.079602E-01
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 detectgeometry 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.

10 COMPILATION OF PHITS

272

10

Compilation of PHITS

PHITS must be re-compiled by yourself for some circumstances; e.g. you need to extend the maximum memory 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). 69 Table 10.1
summarizes the combination of the Fortran compiler and OS by which we have succeeded in compiling PHITS for
four diﬀerent parallel options: single mode, MPI, OpenMP, and hybrid of MPI and OpenMP.
Table 10.1: The available fortran compilers for each OS
OS
WindowsMacLinux

single✓✓✓Intel FortranMPI Open MP
✓
✓
✓
✓
✓

hybrid✓✓single
✓
✓
✓

MPI
✓

gfortranOpen MPhybrid✓10.1 Compilation on Windows OS
10.1.1 Compilation using makefile
The PHITS code can be compiled using the “make” command. For this purpose, the “makefile” file in “\src”
folder should be revised to fit for the host computer. For example, to compile using the gfortran compiler on
Windows OS, the ENVFLAGS written in “makefile” should be set to WinGfort. To execute PHITS via parallel
computing using MPI or OpenMP, it is necessary to set USEMPI or USEOMP, respectively, to true. The name ofthe executable file is given as “phits XXX.exe,” where XXX is a parameter set to ENVFLAGS. For example, when
ENVFLAGS=WinGfort, the name is phits WinGfort.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.
To use gfortran for Windows, the latest installer version can be downloaded from “Downlaod Latest Version”
on the following web site:• MinGW-w64 - for 32 and 64 bit Windows(https://sourceforge.net/projects/mingw-w64/files/?source=navbar)
Running the downloaded installer, select “x86 64” or “i686” for 64-bit or 32 bit PC, respectively, as “Architecture.” It is unnecessary to change other parameters during the installation process.
The followings are the procedure of how to compile PHITS with the gfortran compiler.
(1) Revise “makefile” in “\phits\src\” folder: set ENVFLAGS=WinGfort. Note that OpenMP cannot be activated.
(2) Open a command prompt by clicking “mingw-w64.bat” in the gfortran installation folder.
(3) Use the “cd” command and go to “\phits\src\” folder. Type “mingw32-make” to compile PHITS.
The compiled PHITS by gfortran can be used as follows:(1) Copy “phits WinGfort.exe” to “\phits\bin\.”(2) Open “phits.bat” in “\phits\bin\”, and add
set PATH=C:\Program Files\mingw-64\...
69 Note that PHITS compiled by Intel fortran is much faster than that compiled by gfortran, so we recommend to use Intel Fortran

if it is available. Intel Fortran is free for students. Please check the link in more detail: https://software.intel.com/en-us/
qualify-for-free-software/student

10.2 Compilation on Mac OS

273

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 exceptions are signaling: IEEE DENORMAL.” , may show up, but can be be ignored.

10.1.2 Compilation using Microsoft Visual Studio with Intel FortranThe “\phits\bin\” folder contains a project file (“phits-intel.proj”) required for compiling PHITS using Microsoft Visual Studio coupled with Intel Fortran. PHITS can be compiled using these files as follows:(1) Double-click the “phits-intel.proj” file 70 .
(2) Build “phits-intel.vfproj” in release mode.
(3) Make an input file for PHITS in the “\bin\” folder.
(4) Execute the project in release mode.
(5) Type file=input_file_name in the console window.
(6) Check whether or not “xz track all.eps” is created.
To compile PHITS in the shared-memory parallel computing mode, it is necessary to change “a-angel.f” to“a-angel-winopenmp.f” in the “Source files” of “phits-intel.vfproj” and add “/Qopenmp” in the additional option
window (see project → property → Fortran → command line) before building “phits-intel.proj.”
To use the compiled PHITS using the “sendto” command, rewrite the environmental variable “PHITS EXE”
written in “phits.bat,”, e.g.,
set PHITS_EXE=C:\phits\bin\Release\phits-intel.exe
Although it is possible to use the “sendto” command to rename the compiled PHITS to the original file name, e.g.,“phits282 win.exe,” the original file should not be deleted, as it is required for PHITS version update.

10.2 Compilation on Mac OS
The PHITS code can be compiled using the “make” command. For this purpose, the “makefile” file in “\src”
folder should be revised to fit for the host computer. For example, to compile using Intel Fortran Compiler on Mac,
the ENVFLAGS written in “makefile” should be set to MacIfort. To execute PHITS via parallel computing using
MPI or OpenMP, it is necessary to set USEMPI or USEOMP, respectively, to true. The name of the executable file isgiven as “phits XXX.exe,” where XXX is a parameter set to ENVFLAGS. For example, when ENVFLAGS=MacIfort,
the name is phits MacIfort.exe. If USEOMP is also set to true, the name would become phits MacIfort 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.

10.3 Compilation on Linux OS
The PHITS code can be compiled using the “make” command. For this purpose, the “makefile” file in “\src”
folder should be revised to fit for the host computer. For example, to compile using Intel Fortran Compiler on
Linux, the ENVFLAGS written in “makefile” should be set to LinIfort. To execute PHITS via parallel computing using MPI or OpenMP, it is necessary to set USEMPI or USEOMP, respectively, to true. The name of theexecutable file is given as “phits XXX.exe,” where XXX is a parameter set to ENVFLAGS. For example, when
70 This file may be automatically updated when a new version of Visual Studio or Intel Fortran is used, and it cannot be opened by an older

version of Visual Studio (before 2005) and/or Intel Fortran (before 11.1).

274

10 COMPILATION OF PHITS

ENVFLAGS=LinIfort, the name is phits LinIfort.exe. If USEOMP is also set to true, the name would become
phits LinIfort OMP.exe. The compiler options given in “makefile” are simply examples, and users may need tochange 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.

275

11

Additional explanation for parallel computing

There are two types of parallel computing: distributed-memory parallel computing using the MPI protocol, andthe shared-memory parallel computing using OpenMP architecture. Parallel PHITS calculation can be performed
using either of these methods, or by using a hybrid method. To execute distributed-memory parallel computing,the MPI protocol must be installed in the user’s computer; by contrast, there is no additional software required forshared-memory parallel computing. Note that when the same number of CPU core is set, the computational time
for the distributed-memory parallel computing is often shorter than for the shared-memory parallel computing.
Each executable file must be generated according to the type of the parallel computing employed: see Sec. 10 for
details. Fortran compilers recommended to make the executable file are Intel Fortran Compiler 11.1 (or later) andgfortran 4.7 (or 4.8) for the distributed-memory parallel computing, while only the Intel compiler can be used forthe shared-memory parallel computing.
In distributed-memory parallel computing, jobs are distributed to each CPU core in batch units. When all jobs
assigned to each core are finished, the main core gathers their results. In this mode, all cores individually use
an amount of memory equivalent to that used in single processing; thus, the total RAM memory in the computer
system must be larger than the product of the memory used for single processing and the core number. As a result,
this type of parallel computing is not suitable for calculations requiring a large amount of memory, for instance,
calculations involving voxel phantoms.
In shared-memory parallel computing, jobs are distributed to each CPU core in the units of history. In thiscase, the cores share a large portion of the memories used by PHITS aside from those defined as “thread private”
variables. Thus, the memory required in this parallel computing mode is nearly the same as that required for single
processing. One disadvantage of shared parallel computing relative to memory-distributed computing is its slower
computational time as a result of the competition for access to shared memories. This disadvantage becomes very
important for calculations in which memories are frequently updated, such as those using the [t-sed] tally.

11.1 Distributed memory parallel computing
11.1.1 Installation of MPI protocol
It is necessary to install a MPI protocol for executing the distributed-memory parallel version of PHITS. In
this manual, the installation procedure of MPICH2 into a Windows PC is described, which is necessary for using
the MPI version of PHITS included in the PHITS package, i.e. “c:\phits\bin\phitsXXX win mpi.exe.” For othercases, please set up your machine environment with MPI protocol by yourself.
MPICH2 is mainly developed in Argonne National Laboratory. For easy installation, we recommend to download its version 1.4 from http://www.mpich.org/static/downloads/1.4/ because the Windows installer isprovided in the version. For 64-bit and 32-bit Windows, please select “mpich2-1.4-win-x86-64.msi” and “mpich21.4-win-ia32.msi,” respectively. During the installation, you have to select “C:\Program Files\MPICH2” (default)
as the installation folder, and select “Everyone” as users. You can input any “Passphrase,” but you have to set thesame “Passphrase” for each Windows PC if you use multiple machines for the MPI calculation. After the installation of MPICH2, you have to right-click “smpd-install.bat” contained in “\phits\document\mpi\”, and execute it
as the administrator.

11.1.2 Execution of MPI version of PHITS on Windows
For executing the MPI version of PHITS on Windows, you have to write $MPI=M before the 1st section ofyour input file, where M is the number of parallelization. For example, you have to write$MPI = 4
if you want to run PHITS as fast as possible in your computer with 4 CPU cores. Note that the actual number ofprocessing 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.

11 ADDITIONAL EXPLANATION FOR PARALLEL COMPUTING

276

11.1.3 Execution of MPI version of PHITS using command line
For Linux, Mac, or multiple Windows PCs connected via network, you have to use command line for executing
the MPI version of PHITS. For example, you have to typempirun -np 5 phits_LinIfort_MPI.exe
where “mpirun” is the executable file name of your MPI protocol, “phits LinIfort MPI.exe” indicates the PHITSexecutable file name and the number of processing elements (PEs) is set following “-np.” This command can besent 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_namewhere “input file name” is the name of the PHITS input file. This rule is only eﬀective for distributed memory
parallel computing. file=phits.in can also be written in the first line, with the contents of the PHITS input fileadded following the second line of phits.in: please see Sec. 2.3.2 for further details.

11.1.4 Adjustment of maxcas and maxbch
In distributed-memory parallel computing, jobs are distributed to each CPU core in units of batch. Hence, thenumber of batches (maxbch) should be a multiple of PE−1 (one of the PEs is used for control). If not, PHITS willautomatically change maxbch to a multiple of PE−1 and adjust the number of histories per batch, maxcas, to makethe total history number equivalent to the value set in the input file. In this case, relevant comments will be output
at the end of the input echo.
In restart mode (istdev<0), adjustment of maxcas is not performed, as this value should be set to the samevalue as was written in past tally results.

11.1.5 Treatment of abnormal ending
When PHITS stops as the result of an abnormal end in a PE, the PE is removed from the operation and a total
result by remaining PE is given as the final result. In this case, the user should check the ncut file, which will beincomplete.

11.1.6 ncut, gcut, pcut, and dumpall file definition in PHITS
For the parallel calculation, ncut, gcut, and pcut can be defined normally in an input file asfile(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 directorythat they specified under “/wk.”
inpara, igpara, and ippara are used as writing options. By default, they each have values of zero: resetting 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 givevalue 1, output files are given IP numbers as/wk/j9999/temp/ncut.dat.005

11.2 Shared-memory parallel computing

277

where 005 is the IP number.
Setting inpara, igpara, or ippara=3 averts addition of the default file path/wk/j9999/
In each case, setting the value= 3 places the IP number at the end of the file, as in the case = 1.

11.1.7 Read-in file definition in PHITS
The read-in files used in PHITS are Decay-Turtle source files. Although these files generally have only a small
eﬀect on network traﬃc, they can occasionally reach sizes as large as 100 MB and, if there is a read-in for every
event, their eﬀect to network traﬃc can increase. Thus, the Decay-Turtle data file should be copied and placedin each PE as “\wk\j9999\turtle\sours.dat” and then defined as file=/wk/j9999/turtle/sours.dat in the
PHITS input.

11.2 Shared-memory parallel computing
11.2.1 Execution
Except when Linux or PHITS is directly specified by a command input, PHITS calculation using sharedmemory parallel computing 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. When N = 0, all cores in the computer are used. If N = 1 is set, the parallel
computing is not used. From version 2.73, the installed executable file of the OpenMP version is available only on
64-bit Windows systems. Note that the function of $OMP is available only for using phits.bat(on Windows OS)or phits.sh(on Mac OS).
In the case when Linux or PHITS is directly specified by a command input, PHITS with shared-memory
parallel computing can be executed using the following command:
phits_LinIfort_OMP.exe < phits.inp
where phits LinIfort OMP.exe indicates a PHITS-executable file compiled using the OpenMP option and “phits.inp”
is the PHITS input file. Any name can be used for the PHITS input file, as the file name restriction to phits.in is
not valid in this case. To specify the number of cores to be used for parallel computing, the environment variable“OMP NUM THREADS” should be defined. Note that this variable should be set to equal the real number ofCPU-cores, not the number of total threadds, when using hyper-threading technology, as parallel computing using
this technology does not work in PHITS calculation. The environment variable can be changed as follows:
export OMP_NUM_THREADS=8Note that in hybrid parallel computing the environment variables need to be set individually on each node.
From version 2.73, the installed executable OpenMP version file is available only for 64-bit Windows systems,
as an error owing to heap memory shortage sometimes occurred on Windows OS when the executable file of the
OpenMP version for 32-bit was used with many cores. However, this error is avoided by using the executable filefor 64-bit Windows.

11.2.2 Important notices for shared-memory parallel computing
Using only one core for memory-shared parallel computing in PHITS takes approximately twice as much time
as is needed for single processing. Therefore, it is useless to select memory-shared parallel computing mode for acomputer with only one or two cores.
Runtime execution of ANGEL from PHITS by setting epsout≥1 is still inapplicable in shared-memory parallel computing (this is only possible for Intel Fortran-compiled PHITS on Windows). To avoid this problem,
the PHITS-executable file for memory-shared parallel computing contained in the current PHITS package wascompiled by replacing a-angel.f by a-angel-winopenmp.f, which outputs the file names specified by tallies
with epsout≥1 into angel-temporary.inp. phits.bat then automatically executes this stand-alone version of
ANGEL angel.bat using angel-temporary.inp as the input file. Note that even with itall=1, the eps file is
not automatically updated when each batch finished.

11 ADDITIONAL EXPLANATION FOR PARALLEL COMPUTING

278

Segmentation errors occur in executing memory-shared parallel computing PHITS on Linux may be caused by
the overuse of the stack memory; in this case, the stack size must be increased using the following command:
export OMP_STACKSIZE=1G
which sets the stack size to 1 GB.
In principle, the results obtained from single processing and shared-memory parallel computing should be thesame. Thus, the user should inform us (phits-oﬃce) if inconsistencies are found between the results obtained bythese two modes, as these may represent bugs in the programming.

279

12

FAQ

12.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 isnecessary. 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 setting. 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] todisable 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.2 Electrons and positrons are not transported.
A1.2 Transport of electrons and positrons are ignored in the default setting because they are time consuming. If
you want to transport them, you have to activate EGS5 mode by setting negs=1 in [parameters].
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 JQMD2.0 (irqmd=1) for precisely simulating nucleon-nucleon interactions, and SMM (ismm=1) for precisely estimating the residual nuclide yields after high-energy nuclear reactions, though they are time consumptive.
Q1.4 What kind of simulation is the event-generator mode suited to?
A1.4 Event generator mode is best suited to simulations in which it is necessary to obtain event-by-event information, e.g., detector response calculations and the design of semi-conductor devices. It is also useful for
simulations in which the energies and types of charged particles produced by low-energy neutron interactions must be determined. Specifically, event generator mode is generally most suited to simulations using[T-Deposit], [T-LET], [T-SED], [T-Yield], and/or [T-Product] tallies. On the other hand, it is notsuited to simulations only using [T-Track] and/or [T-Cross] tallies, such as shielding calculations. See“4.2.22 Event Generator Mode” for further details.
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 uncertainty 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 computational time occasionally becomes extremely long in history variance mode, especially in for tallies usinga 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 than10.
Q1.6 Is it possible to use nuclear data libraries other than JENDL-4.0?
A1.6 Yes. PHITS can use nuclear data libraries that are written in the ACE format, i.e., the MCNP format. The
following are instructions on how to use a new nuclear data library in PHITS:(1) using a text editor, open the “xsdir” file contained in the package of the new nuclear data library andcopy all nuclear data addresses (e.g., 1001.80c 0.999167 xdata/endf71x/H/1001.710nc 0 1 4 17969 0 02.5301E-08);

12 FAQ

280(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 andcopy 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 ofphoto-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, thephoton 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.

12.2 Questions related to errors occurred in compiling or executing PHITS
Q2.1 I got an error in compiling PHITS. How can I correct this to finish compiling?
A2.1 The PHITS oﬃce recommends using Intel Fortran Compiler 11.1 (or later) and gfortran 4.7 (or later). However, Windows gfortran 4.9 - 5.4 cannot compile PHITS properly. The recommended compiler is Intel
Fortran because PHITS compiled by Intel Fortran is much faster than that by gfortran. See section 10 for
further details.
Q2.2 A segmentation fault occurred during the execution of PHITS.
A2.2 This might have occurred as a result of an overflow of the memory used in PHITS. In this case, it may benecessary to increase the maximum size of memory acceptable to PHITS by redefining (increasing) the mdas
parameter in “param.inc” in the “src” directory and then re-compiling PHITS. It may also be necessary toincrease the latmax parameter to use huge lattice structures such as voxel phantoms. See the “3.7 Arraysizes” section for further details.
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”) canbe created with the first line file=phits.inp and used as the PHITS input file. For example:
phits_LinIfort < phits.in
See manual section 2.3.2 for further details.
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 diﬀerence in the ‘return code’ usedin Linux and Windows. If the input file is prepared in a Windows computer and transferred to a Linux systemusing FTP software, the status of the transfer mode must be checked, i.e., ‘ASCII mode’ must be selected in
the FTP software.
Q2.5 Can PHITS be executed on Cygwin?
A2.5 Yes. The Cygwin option can be found in the PHITS “makefile.”
Q2.6 Which is most suitable for compiling PHITS—Intel, Fortran, or gfortran?

12.3 Questions related to Tallies

281

A2.6 We generally recommend using the Intel Fortran compiler because it can make PHITS executable files thatare faster than those made using gfortran. When using gfortran, it is vital that you set ‘-O0’ instead ofusing 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). Notethat 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 usedmemory 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.

12.3 Questions related to Tallies
Q3.1 What is the diﬀerence between the [t-heat] and the [t-deposit] tallies?
A3.1 These two tallies essentially produce the same values of deposition energies. After version 3.05, [t-deposit]
gives the deposition energies not only by ionization of charged particles but also kerma of neutral particles.
Thus, we do not recommend to use [t-heat] after that version.
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 ionsshould be defined in MeV in the tally section but should be written in MeV/u in the [parameters] section.
Q3.3 Results obtained by [T-LET] and/or [T-SED] tally are strange.
A3.3 The density of the material selected by letmat must be checked: if a material not used in your geometry
is selected, it is necessary to define its absolute atomic densities (1H 6.893407e-2 16O 3.446704e-2) in the[material] section. In addition, if a very fine mesh (more than 10 meshes per decade) in [t-let] is set,
the results might have zigzag structure. In that case, the LET mesh should be widened.
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 “4.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 oﬀce 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 theoutput=deposit option.

282

12 FAQ

A3.7 When exothermic nuclear reactions occur, the total energy of secondary particles becomes greater than theincident energy. Such events are also observed when mesh=xyz or r-z and nedisp=t0 based on the outputof the algorithm for considering the energy straggling of charged particles in PHITS. In such case, it isnecessary to set mesh=reg in [t-deposit] and define cells corresponding to each xyz or r-z mesh in the[cell] section.

12.4 Questions related to source generation
Q4.1 How PHITS outputs be normalized when using an isotropic source (s-type=9 or 10, dir=-all)?
A4.1 If there is nothing inside the sphere of an isotropic source, the fluence inside the sphere is normalized to
1/π/r12 (/source), where r1 is the radius of the sphere. Therefore, to convert the tally output (/source) tothe unit fluence, it is necessary to multiply the result by πr12 . It should be noted that, as the weight control
method is employed in generating an isotropic source, event-by-event information cannot be derived fromsimulations using an isotropic source. To obtain event-by-event information for isotropic irradiation, set
dir=iso in the [source] section (PHITS must be updated to use this function).
Q4.2 What should be done if a source particle is not created in the desired location in a cell?
A4.2 To set the source generating surface (or point) precisely on the surface of a certain cell, PHITS sometimes
mis-identifies the cell where it should be located. In this case, the source surface should be moved so that it
diﬀers slightly from the cell surface.

12.5 Other questions
Q5.1 Can I use PHITS for commercial purpose?
A5.1 Basically yes. You can use PHITS for commercial purposes such as the design of radiation detector to be
sold, and radiation shielding calculation for the accelerator facilities for medical use. However, you have to
make an onerous contract if you want to sell a product that includes the executable file of PHITS, such as
the treatment planning system based on PHITS. In that case, please contact us.
Q5.2 What kinds of physical processes cannot be handled by PHITS?
A5.2 PHITS cannot handle interactions involved with more than (or equal to) two moving particles such as particle
collision experiments, transports and generations of non-ionizing radiation such as visible light, and changeof chemical or material properties after irradiation. More detailed information can be found in Appendix A.

283

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)• Eﬀect 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, luminescence)• Transport and generation of electrons below 1 keV 71• Physical processes related to electron current (e.g. electron avalanche)• Charge exchange interactions 71• Event-by-event analysis of atomic excitation and ionization 71• Polarization eﬀect 72• Chemical reactions (e.g. Transport and generation of radicals)• Biological reactions (e.g. Generation of DNA damage)• Change of chemical and material profiles after irradiation (e.g. time evolution of defects)• Consideration of the status of a material 73 (e.g. crystal & molecular structure, temperature)• Nuclear reactions originated from fine structure of nuclear shell 73 (e.g. Li(p,n) reaction)• Particle-induced X-ray emission (PIXE)• Generation of delayed neutrons

71 Feasible when the track-structure mode is used
72 Feasible in the simulation of nuclear florescence resonance (NRF)
73 Feasible when the nuclear data library is usedIndex<source>, 67, 95
S (α, β), 6∆ angular distribution, 42
δ-ray, 3, 5, 13, 14, 44, 230
γ decay, 40
θ-mesh, 8-all, 2, 282[Weight Window], 39, 243[cell], 12, 25, 26, 109, 112, 118, 126–129, 131–137,
139, 144, 161, 171, 241[counter], 3, 6, 8, 25, 174, 191, 205, 212, 218, 223[data max], 7, 25, 157[delta ray], 3, 14, 25, 153, 230[delta-ray], 9[elastic option], 25, 46, 156[electro magnetic field], 25, 68, 152[end], 26, 27[forced collisions], 2, 25, 166[frag data], 6, 25, 158[importance], 25, 52, 161, 206[magnetic field], 25, 68, 146, 152[mat name color], 25, 52, 171[mat time change], 25, 145[material], 6, 7, 12, 25, 27, 51, 56, 109, 111, 126, 129,
131–137, 139, 171, 205, 211, 227, 230, 239,
241, 279[multiplier], 2, 3, 14, 25, 55, 168, 169[parameters], 2, 4, 6–9, 11, 24, 25, 33, 95, 109, 138,
146, 152, 154, 157, 158, 163, 164, 166, 170,
171, 189, 193, 197, 201, 204, 205, 209, 212,
213, 215, 217, 218, 223, 226, 229, 232, 235,
238–240, 243–245, 248, 255, 257, 259, 279,
281
[reg name], 25, 173[source], 6, 8, 10–13, 25, 41, 66, 146, 152, 239, 248,
282
[super mirror], 25, 155[surface], 25, 26, 62, 112, 126–129, 131–137, 139, 252[t-3dshow], 6, 26, 33, 173, 177, 191, 259[t-cross], 1, 2, 4, 5, 11, 14, 26, 51, 80, 97, 168, 177, 183,
189, 191, 198, 266, 279, 281[t-dchain], 1, 2, 4–6, 8, 9, 13, 20, 22, 24, 26, 177, 239[t-deposit2], 26, 35, 110, 177, 211[t-deposit], 1–4, 6, 8, 9, 11, 12, 26, 35, 46, 65, 110, 154,
177, 205, 211, 213, 230, 279, 281, 282[t-dpa], 1, 5, 8, 26, 65, 177, 224[t-gshow], 1, 26, 33, 133, 173, 177, 187, 189, 255, 271[t-heat], 2, 9, 12, 26, 177, 213, 281[t-interact], 3, 26, 51, 97, 177, 236[t-let], 3, 26, 110, 177, 227, 230, 279, 281[t-point], 8, 26, 51, 97, 168, 177, 203[t-product], 1, 3, 6, 11, 14, 26, 33, 51, 65, 78, 80, 97,
177, 191, 266, 279[t-rshow], 26, 33, 173, 177, 189, 190, 257, 271[t-sed], 3, 26, 110, 153, 177, 230, 275, 279, 281[t-star], 3, 6, 8, 26, 177, 236[t-time], 11, 14, 26, 51, 80, 97, 177, 191, 233, 266[t-track], 1, 4, 8, 9, 14, 26, 51, 97, 146, 152, 154, 168,
169, 177, 195, 198, 203, 239, 279, 281[t-userdefined], 3, 14, 26, 177, 250[t-volume], 6, 26, 33, 177, 248[t-wwbg], 4, 26, 33, 163, 177, 245[t-wwg], 3, 6, 26, 163, 177, 243[t-yield], 1, 2, 8, 9, 26, 40, 65, 177, 186, 216, 220, 239,
279
[temperature], 25, 144[timer], 25, 176[title], 25, 32[tpoint], 8[track structure], 25, 154[transform], 2, 25, 112, 114, 127, 134, 141–143, 146,
191
[usrtally], 8[volume], 25, 52, 167, 179, 196, 206, 215, 241, 243,
249, 281[weight window], 2–4, 6, 25, 39, 162, 163, 177, 206,
245
[ww bias], 4, 25, 33, 39, 163, 177, 245$MPI, 17, 22, 275$OMP, 17, 19, 22, 275
2d-type, 188, 189, 196, 200, 206, 212, 215, 223, 226,
228, 231, 233, 238
3dshow, 191a-angel-winopenmp.f, 273
a-angel.f, 273
a-curr, 199, 200a-type, 11, 12, 68, 70–72, 77, 79, 80, 83, 98, 99, 181,
183, 195, 199, 201, 220, 223, 235
aama.dat, 55
abnormal end, 276
abort, 23absorption, 41, 238act, 236
actlow, 96
ag1, 99ag2, 99
all, 68, 77, 79, 157, 162, 164, 168, 169, 195, 199, 203,
205, 211, 213, 215, 216, 220, 224, 226, 227,
230, 233, 236, 238, 243, 246, 248, 259, 261
am, 155
amp, 241
andit, 41
ANGEL, 2, 3, 10, 19, 35, 187, 189, 190, 196, 200, 203,
206, 212, 215, 223, 226, 228, 231, 233, 238,
243, 246, 255, 257, 261, 277
angel, 4angel parameter, 187, 196, 200, 203, 233

284

INDEX

angle mesh, 181, 195, 199, 220angle straggling, 44
angular straggling, 4anih, 175
annih, 238
area, 202
array size, 31
ascat1, 44
ascat2, 5, 44
ASCII, 50
ATIMA, 7, 44, 68
atmflu, 238
atom, 175
atomic, 220, 223, 238auge, 175
Auger, 1auger, 238
Auger electron, 3, 5, 96, 230
automatic calculation of region volume, 26, 33, 177, 248
axis, 2, 3, 5, 9, 35, 40, 179, 185, 186, 188, 190, 192,
196, 199, 203, 206, 211–213, 217, 223, 228,
231, 233, 236, 243, 246, 255, 257, 271
axishow, 261

285

charge, 185
chart, 40, 185
cluster plot, 189
cmin(i), 36
cmkm, 188
cmmm, 188
cmmt, 188
cmnm, 4, 188
cmpt, 175
cmum, 188
coll, 174, 176
color, 171
color plot, 189
Command Prompt, 17comment mark, 27, 109, 112, 126, 141
compilation, 272, 273
compile, 66
composition ratio, 109
compound, 109
compton, 238
COND, 110cone shape source, 11
contour, 189
coordinate transform number, 112, 134
b-curr, 200cos, 185, 199
Baba, 40cosine, 70–72, 74, 141bank, 34
Coulomb diﬀusion, 44
batch, 23, 34, 51, 190, 276
counter, 82, 174, 191, 192, 203, 244
batch.out, 1, 7, 23, 55
cpu time, 52
Bertini, 36, 40, 42
Crimson Editor, 17
binary, 50, 53
ctmax, 191, 197, 201, 203, 205, 207, 212, 215, 218, 223,
Bitmap, 6, 197, 207, 218, 223, 226, 235, 238, 255, 257
226, 229, 232, 235, 238, 244
blank, 28, 178
ctmin, 191, 197, 201, 203, 205, 207, 212, 215, 218, 223,
blank line, 27
226, 229, 232, 235, 238, 244
bmpout, 197, 207, 215, 218, 223, 226, 235, 238, 255, Cugnon, 40
257
current, 198, 200
bnum, 57
cut-oﬀ energy, 13, 36, 41, 50, 55, 233, 270
Boolean operator, 126
cut-oﬀ time, 39
BOX, 114, 132, 133, 135–137
cut-oﬀ weight, 39box, 261
cutoﬀ, 5, 233
Bragg scattering, 46, 156
cval, 83
brem, 175
CX, 113
brems, 238
CY, 113, 131, 134–136
bremsstrahlung, 57
CZ, 113bright, 261
dark, 261
C/X, 113
data, 79
C/Y, 113
datapath, 16
C/Z, 113
dbcutoﬀ, 44
CAD, 2dcay, 175
cdiam, 230
dchain, 40, 185cell definition, 126, 127, 132, 133
DCHAIN-SP, 1, 4, 10, 19, 55, 239
cell number, 79, 126, 163, 177, 178
decay, 29, 223, 233, 238
cell parameter, 126, 127, 134
decay-turtle, 66, 74, 277
change, 145
DECDC, 7, 55, 95
characteristics x-ray, 2
dedxfnc, 205
chard, 59
dedxfnc1, 211

286

dedxfnc2, 211deg, 196
delayed neutron, 56
delt, 175
delt0, 44, 54
delta-ray, 25, 153deltaray, 238
deltb, 54deltc, 9, 54
deltg, 54deltm, 9, 51, 54, 146, 152deltt, 54den, 111
density, 12, 126
deposit, 1–3, 8, 11, 35, 205, 206, 282
dfano, 1, 209
dipole electromagnet, 146dir, 2, 3, 68, 70–77, 79, 80, 83, 248, 282
direction cosine, 74
distributed memory parallel computing, 251
distributed-memory parallel computing, 2, 17, 22, 34,
275, 281
dl0, 106dl1, 106dl2, 106dmax, 7, 157, 203dmax(12), 38, 41, 58
dmax(13), 38, 58
dmax(14), 38, 58
dmax(2), 5, 38, 216, 220dmax(i), 13, 36
dmpmulti, 81dnb, 56
dom, 68, 70–72, 75–77, 79, 80, 106
Doppler eﬀect, 40
dose, 206
DPA, 5, 14
dpa, 224, 226
dpf, 106drag and drop, 19
drd, 106
DRES, 40
dresol, 1, 3, 209
dtime, 95
duct source, 106
dump, 11, 14, 66, 80, 83, 191, 201, 223, 235, 266
dump file, 80
dumpall, 11, 14, 33, 50, 55, 61, 201, 223, 235, 250
DWBA, 12, 42
dxw, 106dyw, 106

INDEX

e-tyep, 86
e-type, 4, 6, 12, 66, 79, 80, 83, 87, 89–91, 93, 94, 181,
183, 184, 195, 199, 201, 203, 206, 220, 223,
233, 235, 236, 243, 246
e0, 4, 66, 70–77, 79, 80, 83, 86
e1-t, 185, 211
e1-type, 211e12, 185, 211
e2-t, 185, 211
e2-type, 211e21, 185, 211
EBITEM, 12, 40, 217
EEDL, 14eg0, 93eg1, 93, 94
eg2, 93, 94
eg3, 93, 94
EGS4, 270
EGS5, 2, 4, 5, 7–11, 36, 38, 46, 55, 58, 109, 146, 152,
154, 236, 279
eielfmax, 36
eielfmin, 36
einclmax, 36
einclmin, 36
eisobar, 36
ejamnu, 36
ejampi, 36
ejamqmd, 4, 36
elastic, 8, 216, 223, 238
elastic scattering, 40, 56
electro-magnetic field, 12
electromagnetic field, 41, 51
electron, 213, 215
element, 109
Element file, 138
element symbol, 109
elf, 152
ELIB, 109, 110
ELL, 13, 114
elst, 175
emax, 169, 170
emcnf, 56
emcpf, 57
emin, 226, 227emin(1), 36
emin(12), 2, 36, 38, 46, 57, 58, 154emin(13), 2, 36, 38, 46, 57, 58, 154emin(14), 38, 58
emin(2), 5, 38
emin(i), 36
emumax, 41
emumin, 41
e-dst, 259
e-mode, 2, 10, 11, 46, 65, 203, 205, 213, 216, 218, 220, enclos, 201
energy mesh, 181, 195, 199, 203, 220, 233, 236, 243,
224, 227, 239, 240
246
e-phi, 259
e-the, 259
energy straggling, 44

INDEX

287

eng, 9, 162, 163, 185, 196, 199, 203, 206, 223, 233, 236,
243
eng-t, 185, 206
eng1, 211
eng2, 211
ENSDF, 12enum, 57
eps, 186, 190, 197, 200, 203, 207, 212, 215, 218, 223,
226, 229, 232, 235, 238, 244, 246, 255, 257,
261
epsout, 5, 189, 190, 197, 200, 203, 207, 212, 215, 218,
223, 226, 229, 232, 235, 238, 244, 246, 255,
257, 261, 277
epstfl, 59
eqmdnu, 36
escape, 233
esmax, 7, 36
esmin, 7, 36
ESTEP, 110
et0, 93
et1, 93
et2, 93
ets dea, 238
ets e-exc, 238
ets elast, 238
ets ioniz, 238
ets ioniz e-exc, 238
ets p-exc, 238
ets r-exc, 238
ets v-exc, 238
etsmax, 36, 154
etsmin, 36, 154evaporation, 40
event generator mode, 46, 65, 279
exa, 76
Excel, 189
execution, 16

file(22), 7, 24, 55
file(23), 55
file(24), 55, 95
file(25), 55
file(26), 55
file(27), 55
file(28), 55
file(4), 55
file(6), 11, 31, 47, 52, 55, 109, 157, 171, 248
file(7), 38, 55, 109
FILL, 53, 126, 131–133, 135–137, 139, 140
fiss, 8, 175
fission, 223, 238
flight mesh, 54
fluence, 195, 198fluo, 175
flux, 198, 200
forced collisions, 39
Fortran, 28, 94, 99, 101, 104, 188, 273, 277

file(10), 55, 270
file(11), 55
file(12), 55, 270
file(13), 55, 270
file(14), 55
file(15), 50, 55
file(18), 53, 55, 138file(20), 11, 38, 55
file(21), 55

Hashimoto’s formula, 42
heat, 213
heaven, 259
heavyion, 238
HEX, 114
HLIB, 109, 110
HSB, 171

gap, 146
GAS, 110
gcut, 50, 213, 235, 276
GEM, 40, 175
geometry check, 271
geometry check function, 11
gfortran, 272
GG, 50, 52, 161, 166, 167, 177
GG(General Geometry), 126
ghigh, 168
Ghostscript, 17
ghostview, 190
giant-dipole resonance, 4ginfo, 196, 200, 207, 215, 217, 223, 226, 229, 232, 235,
238, 244, 246, 255, 257, 271
glow, 168
gmake, 272–274
GQ, 113
gravity, 46
f-curr, 200
gravx, 46
f-mesh, 246
factor, 68, 81, 187, 196, 200, 203, 206, 212, 215, 223, gravy, 46
gravz, 46
226, 228, 231, 233, 238, 243
groups, 183
FAQ, 279
gshow, 1, 33, 173, 189, 191, 196, 200, 207, 215, 223,
fcl, 166
226, 229, 232, 235, 238, 271
file, 35, 80, 158, 186, 192, 196, 200, 203, 206, 212, 213,
gslat,
197,
201, 207, 215, 218, 223, 226, 229, 232, 235,
223, 224, 228, 231, 233, 238, 240, 243, 246,
238,
244, 255, 257
248–250, 255, 257, 261
GSview,
17
file(1), 5, 38, 55

iaprim, 60

288

iauger, 59
iaugers, 96
ibad, 57
ibod, 26
ibound, 60
ibrdst, 60
icntl, 4, 33, 50, 55, 56, 163, 170, 189, 193, 223, 245,
248, 255, 257, 259, 271, 279
icommat, 6, 27, 56, 109, 279
icput, 52
icrdm, 7, 42
icrhi, 42, 159
ICRP phantom, 12
ICRP107, 7
ICRU Report, 230
icxsni, 42, 159
icxspi, 7, 42
idam(i), 56
idbg, 26
idelt, 9, 54
ides, 5, 57
idmpmode, 80, 81, 201, 223, 235
idpara, 50, 192
idwba, 42
iechrl, 197, 207, 212, 215, 218, 223, 226, 229, 232, 235,
238, 257
iedgfl, 59
iegsout, 58
iegsrand, 58
ieispl, 60
ielas, 40
ielctf, 41, 152
ieleh, 41ielms, 40iels, 175
ifixchg, 2, 44, 68
igamma, 2, 5, 10, 11, 40, 55, 65, 217
igchk, 54
igcut, 50, 213
igerr, 54
iggcm, 52
Ignatyuk, 40
igpara, 50, 277
ih2o, 44
iidfs, 42
ikerman, 46
ikermap, 46
imagnf, 41, 54, 146
iMeVperu, 3, 4, 51, 170
imout, 51
imp, 161
impacr, 60
implicit capture, 39
importance, 39, 52, 161
imsegs, 9, 58
imubrm, 41
imucap, 41

INDEX

imuint, 41
imuppd, 41
in, 174, 176
INC-ELF, 1, 14, 36
incelf, 36
INCL, 10, 13, 14, 36
inclg, 36
include files, 31
incohr, 60
incut, 50, 213, 270
infl, 4, 8, 188, 249
infl:, 22, 27, 279
info, 187
infout, 11, 47
inmed, 40
inpara, 50, 277
input echo, 33, 39, 51, 52, 164
input file, 25
installation, 16
installation folder, 55Intel Fortran, 10, 273, 274
internal conversion electron, 2interpolation, 168
inucr, 56
ionization potential, 44
ipara, 52
ipcut, 50, 213
ipegs, 9, 58
iphot, 57
iphter, 60
ipngdr, 41
ipnint, 9, 41, 58
ippara, 50, 277
iprdst, 60
ipreeq, 40
iprofr, 60
iprtb2, 241
iraylr, 59
ireschk, 34, 243, 280
irlet, 3, 5, 44
irqmd, 11, 36, 279
irskip, 34, 194
isaba, 56
iscorr, 67
ismm, 40, 279
iso, 3, 282
isobar, 40
ispfs, 5, 69
istdev, 13, 34, 81, 194, 207, 249, 276, 279
istrg, 57
isumtally, 193
itall, 4, 24, 51, 190, 197, 201, 204, 209, 212, 215, 218,
223, 226, 229, 232, 235, 238, 240, 244, 248,
277
itetra, 53
itetvol, 53
itstep, 51

INDEX

ityp, 162, 164
iunr, 56
iunrst, 59
ivoxel, 53, 55, 138
iwwbias, 39, 163, 245
izst, 68, 146, 152
JAM, 2, 10, 11, 13, 36
JAMQMD, 4, 5, 7, 10, 36
JAMQMD2, 4
JENDL-4.0, 5, 7, 13, 14, 38, 109, 280
JENDL-4.0/HE, 1
JENDL/PD-2004, 13
jmout, 51
JQMD, 4, 11, 29, 36, 40
JQMD-2.0, 8, 11, 36, 279

289

line connection, 183line thickness, 191
lineal energy, 230
Linux, 16, 21, 140, 273, 277
log, 168
lost particle, 54
lpolar, 59
Lynch’s formula, 44

Mac, 16, 18, 140, 273, 277
macro body, 13, 112, 114, 125
magnetic field, 41, 46, 51
magnetic field map, 148
make, 272
makefile, 9, 272–274
MARS-PF, 55
marspf.in, 55
K/X, 113
mass, 185, 217
K/Y, 113
mass density, 110
K/Z, 113
mass ratio, 51
kerma, 14, 36
MAT, 126, 134
kerma approximation, 2, 46, 65, 205, 213, 281
mat, 109, 111, 145, 157, 169–171
kf code, 185
matadd, 52, 126, 171
kf-code, 29, 192
material, 109, 190, 195, 205, 213, 216, 220, 224, 227,
230, 233, 236, 243, 259
kmout, 51, 109
material density, 51, 110
knockelec, 238
material name, 189
knoe, 175
material number, 52, 109, 110, 126, 134, 169, 171, 189,
KUROTAMA, 4, 10, 14, 42
197, 226, 235, 238
KX, 113Mathematical expression, 28
KY, 113matinbox, 261
KZ, 113
maxact, 236
l-dst, 259
maxbch, 33, 34, 50, 81, 276, 279
l-phi, 259
maxbnk, 34
l-the, 259
maxcas, 33, 34, 50, 81, 276, 279
l-type, 181, 227
maximum, 93, 94, 114
Landau, 44
maximum value, 183, 184
LAT, 53, 126, 132, 133, 135–137, 139, 140, 255, 257
Maxwell, 4
LaTeX, 171, 173
MCNP, 51, 270
latmax, 280
mdas, 12, 31, 280
lattice, 13, 68, 126, 131, 134–137, 144, 146, 153, 161, mdbatima, 44
162, 164, 166, 167, 174, 176, 178, 179, 202
mean, 236
lattice coordinate system, 132, 133, 135–137, 178
mesh, 1, 3, 4, 8, 9, 13, 77, 133, 135–137, 162, 177–180,
LET, 205, 211, 227
195, 199, 202, 205, 211, 213, 216, 220, 224,
let, 185, 228
227, 230, 233, 236, 240, 243, 246, 248, 255,
LET mesh, 181
257, 281, 282
letmat, 110, 205, 227, 230, 281
mesh definition, 180–183, 189
letmat1, 211
mesh type, 183letmat2, 211
mesh width, 183, 184level, 40
method, 248
level density, 40
mgf, 146, 152level structure, 178
Microsoft Visual Studio, 273
library, 33, 36, 109, 110mID, 154
LIKE n BUT, 134
MinGW-w64, 272
LIKE n BUT, 126, 134
mingw32-make, 272
lin, 168
minimum, 93, 94, 114
line, 261
minimum value, 183, 184

INDEX

290

mirror, 259
mixture, 109mm, 155
model, 159
Moliere, 44
MorP, 236
mother, 216, 220, 224, 236
MPI, 2, 14, 273–275, 281
MPICH2, 17, 275
mset, 169, 170
MTn, 6
multi-source, 67, 68, 79, 95, 102
multiplier, 13, 14, 168–170, 197, 201, 204muon capture, 41
muon capture reaction, 7, 10
muon interaction, 9
Muon-induced nuclear reaction, 11
muon-induced nuclear reaction, 41
muonic atom cascade, 1mwhere, 39
MWO formula, 42
mxlv, 135
mxspln, 39
n-mesh, 246
na, 11, 98
name, 171, 173
NASA, 42natural, 7, 52
natural abundance, 109
natural isotope, 239naz, 26
ncut, 50, 213, 235, 276
ndata, 218, 240
ndedx, 4, 7, 44
ne, 89–91, 168
nedisp, 44, 54, 282
negative sense, 127
negs, 3, 5, 10, 11, 36, 38, 46, 58, 154, 203, 236, 279
neispl, 60
nesting structure, 135
neutrino, 46
neutron capture, 56
neutron multiplicity, 42
neutron optics, 87, 91
nevap, 40, 65
nfile, 193
ngem, 2, 40
ni, 95nlatcel, 209
nlatmem, 209
NLIB, 109, 110
nlost, 54
nm, 12, 93, 94
NMTC, 44nn, 11, 12, 99
no ionization, 33

no reaction, 33
nocas, 201, 223, 235
nocoh, 57
Node file, 138
non, 146, 154, 173, 179
nonu, 8, 56
noobch, 201, 223, 235
norm, 96
Notepad++, 17
npidk, 41
nrecover, 47
nspred, 3, 5, 10, 44, 54
ntetelem, 53
ntetsurf, 53
ntmax, 81, 83
ntrnore, 46
ntt, 100
nuc, 111
nucdata, 5, 36, 38, 279
nucl, 175
nuclcal.out, 55
nuclear, 223, 238
nuclear data, 51, 109, 110, 219
nuclear reaction calculation mode, 56
nuclear resonance fluorescence, 8, 9, 41
nucleus, 157, 216, 236
nuclide, 29, 95, 109
nudtvar, 3, 250
numb, 57
number, 168
number of group, 184
number of history, 34
nwsors, 52
nx, 77ny, 77nz, 2, 77, 202
o-curr, 200o-type, 100
oa-curr, 199, 200
ob-curr, 200
of-curr, 200
oﬀ, 27
Open MP, 13, 273, 274
OpenMP, 4, 275, 281
OpenMPI, 22
opt, 158
out, 174, 176
outer void, 126
output, 1–3, 5, 9, 11, 35, 78, 133, 187, 199, 200, 205,
206, 213, 220, 223, 226, 233, 238, 255, 257,
259, 282
outtime, 241
P, 113, 133
p-table, 12
p-type, 87, 89–91, 93, 94

INDEX

pairprod, 238
parallel, 276
parallel calculation, 50
parallel computing, 14, 22, 34, 273–275
param.inc, 12, 31, 135, 280
ParaView, 6, 197, 218, 223, 226, 235, 238, 255
part, 3, 8, 157, 161–163, 166, 168–170, 174, 184, 185,
195, 199, 203, 205, 211, 215, 216, 220, 224,
227, 230, 233, 236, 243, 246
particle definition, 184particle density, 12, 51, 110particle identification, 29
pcut, 50, 213, 235, 276
PE, 23, 34, 50, 276
Pearlstein-Niita’s formula, 42
PEGS5, 55phel, 175
phi, 68, 70–72, 75–77, 79, 80
phits.in, 276
phits.out, 31
photo-nuclear, 12, 41
photo-nuclear reaction, 11–13, 280
photoelec, 238
photon, 213
PLIB, 109, 110
pnimul, 9, 41, 280
point, 203
polar, 147
polarization, 147
positive sense, 127
pprd, 175
pre-equilibrium, 40
prob, 236
Processing Element, 34, 50
product, 5proj, 158
Pulse magnet, 46
pulse magnet, 146
PX, 113, 128, 129, 131–137
px, 139
PY, 113, 128, 129, 131–137
py, 139
PZ, 113, 128, 129, 131–137
pz, 139pz0, 74291

r-to, 4, 202
r-type, 180, 183r-z, 1, 8, 177, 179, 180, 195, 199, 202, 205, 213, 216,
220, 224, 227, 230, 233, 236, 281, 282
r0, 2, 70, 75, 155, 248
r1, 2, 70, 72, 73, 75, 211
r2, 73, 75, 211
rad, 196
radiation doses, 168
random number, 34
ratio, 109
rayl, 175
RBE, 230
RCC, 114rdam(i), 56
REC, 13, 114
ref, 174, 176reg, 4, 8, 33, 68, 81, 83, 133, 135–137, 144, 146, 152,
154, 156, 161, 162, 166, 167, 173, 174, 176–
179, 185, 190, 195, 196, 199, 202, 205–207,
211–213, 216, 220, 223, 224, 227, 228, 230,
231, 233, 236, 240, 243, 246, 248, 257, 282
reginbox, 261
region boundary, 189
region error, 54
region mesh, 177
region name, 173, 189
region number, 161, 166, 167, 174, 176, 202
repeated structure, 126, 130–134, 137, 161, 178
resc2, 23
resc3, 23
resfile, 23, 186, 196, 200, 203, 206, 212, 213, 223, 224,
228, 231, 233, 238, 243, 248
residual nuclei, 40
resol, 189, 191, 197, 200, 207, 212, 215, 217, 223, 226,
229, 232, 235, 238, 244, 246, 255, 257, 261
resolution, 189–191
restart calculation, 13, 34, 186, 196, 200, 203, 206, 212,
213, 223, 224, 228, 231, 233, 238, 242, 243,
248, 249, 276
Restricted LET, 44
rev, 281
RHO, 126
RHP, 114
RI-source, 7rijk, 24rijklst, 23
q-type, 98, 99
ring, 203q:, 27
RIsource.ack, 3
qc, 155
RIsource.dat, 95
qp:, 27rn, 71, 72
quadrupole electromagnet, 146
rnok, 57
r, 185, 196, 199, 206, 213, 217, 223, 228, 231, 233, 236 RPP, 114, 140r-from, 4, 202
rpp, 139
r-in, 4, 155, 202
rseed, 34r-mesh, 246
rshow, 33, 173, 189, 191, 196, 207, 215, 223, 226, 229,
r-out, 4, 155, 202, 246, 248, 261
232, 235, 238, 243, 246, 271

292

INDEX

rx, 74
SY, 113ry, 74sy, 41, 68, 80, 82, 83, 192rz, 35, 185, 196, 206, 213, 217, 223, 228, 231, 233, 236 symbol, 29
SZ, 113, 127–129
S, 113sz, 41, 68, 80, 82, 83, 192
s-type, 2–4, 11, 66, 68, 70–77, 79, 80, 83, 248, 249, 282
S (α, β), 110t, 185, 196, 199, 203, 206, 211, 223, 233, 236, 243
sangel, 3, 188, 196, 200, 203, 206, 212, 215, 223, 226, t-e1, 185, 211
228, 231, 233, 238, 255, 257, 261
t-e2, 185, 211
sangel parameter, 188t-eng, 185, 206
Sato’s formula, 42
t-type, 81, 83, 100, 181, 183, 195, 199, 201, 203, 206,
scoring mesh, 177, 179, 180
211, 220, 223, 233, 235, 236, 243, 246
SDM, 40
t0, 100
se-type, 231tab, 26
se-unit, 230
targ, 158
SED, 230
target, 241
sed, 231
tc, 100
send to, 17
td, 100
set, 4, 83
tet, 1, 177, 180
set:, 27, 193, 279
TetGen, 139
sfile, 193
Tetra-mesh, 66
shadow, 261
tetra-mesh, 79
shared memory parallel computing, 13, 251
Tetra.bin, 53
shared-memory parallel computing, 17, 19, 22, 34, 273, tetrahedral geometry, 6, 8
275, 277, 279, 281
tetrahedron, 53, 79
Shen, 42
tetrahedron geometry, 2, 3, 79, 138
simple, 213, 226
tetreg, 79
size, 171, 173
TFILE, 139, 140
SMM, 13, 40, 279
tg-list, 241
SO, 113the, 185, 199
soft error rates, 2, 168
the Moliere theory, 44
sors.f, 101
tim, 162
source, 78, 223
time, 145, 146
source check, 33
time mesh, 181, 195, 199, 203, 220, 233, 236, 243, 246
SPAR, 7, 44
timeevo, 241
special, 216
timeout, 6, 34
specific energy, 230
title, 187, 196, 200, 203, 206, 212, 215, 223, 226, 228,
SPH, 114
231, 233, 238, 240, 243, 248, 255, 257, 261
spin, 82, 147, 192
tmax(i), 8, 39
SQ, 113
TMP, 126, 144
standard output, 55
tmp, 144
star density, 236
tn, 100
statistical uncertainty, 34, 186
totfact, 67, 68, 81, 95
stdcut, 4, 6, 197, 201, 204, 209, 212, 215, 218, 223, 226, track structure mode, 205
229, 232, 235, 238, 240, 244, 248
track-structure mode, 1, 3–5, 25, 36, 55, 154, 238
straggling, 57
transform, 191, 262
sumfactor, 193
transform number, 141
sumtally, 6–10, 28, 33, 193, 243
transmut, 8, 238
surface, 202
TRC, 13, 114
surface definition, 112
TRCL, 68, 126, 134, 262
surface number, 112, 125, 132, 133
trcl, 81, 146, 152, 191, 197, 201, 207, 215, 218, 223,
surface sense, 127
226, 229, 232, 235, 238, 244, 255, 257
surface symbol, 112, 113
trcle, 152
switching energy, 36
trclm, 152swtm(i), 39
triangle prism source, 8
SX, 113
trxcrd.dat, 10
sx, 41, 68, 80, 82, 83, 192
TSFAC, 139, 140

INDEX293

tw, 100
TX, 113
TY, 113typ, 146
TZ, 113

w-wdt, 259
wc1(i), 39, 166
wc2(i), 39, 158
WED, 13, 114
weight cutoﬀ, 166
weight value, 41
U, 68, 126, 130–133, 135–137, 139, 144, 146, 153, 161, weight window, 39, 162
162, 164, 166, 167, 174, 176, 178, 202
Weight Window Bias Generator, 163, 245
udtpara, 3, 250
Weight Window Generator, 163
udtvar, 3, 250
wem, 74
unit, 1, 3, 51, 186, 192, 196, 199, 203, 206, 211, 215, wgt, 68, 80
216, 221, 224, 228, 231, 233, 236, 243
width, 191, 197, 200, 207, 215, 217, 223, 226, 229, 232,
universe, 53, 68, 79, 130, 132, 135–137, 144, 146, 153,
235, 238, 244, 246, 255, 257, 261
161, 162, 164, 166, 167, 174, 176, 202
Windows, 10, 16, 272, 273, 277
user defined cross sections, 158
wm, 155
user definition source, 83
Wobbler magnet, 46, 146
user-defined integer variable, 56
wsurvn, 39
user-defined real variable, 56
wt0, 74
user-defined variable, 27
wupn, 39
usrdfn1.f, 205, 211
wwbg, 246
usrdfn2.f, 205, 211
wwbi, 163
usrdfn3.f, 1
wwg, 243
usrelst, 46
wwi, 162
usrelst1.f, 156
x, 185, 186, 196, 199, 206, 213, 217, 223, 228, 231,
usrelst2.f, 156
233, 236
usresol.f, 1
X-ray, 57
usrmgf3.f, 147
x-txt, 190, 196, 200, 206, 212, 215, 223, 226, 228, 231,
usrmgt, 46
233, 238, 246, 255, 257, 261
usrmgt1.f, 146
x-type, 77, 162, 180, 183, 190
usrmgt2.f, 146
x0, 70–76, 80, 83, 180, 246, 248, 249, 259
usrsors.f, 2, 66, 83
x1, 70, 71, 74–76, 80, 83, 246, 248
usrtally.f, 250
x2, 76
utility, 8
x3, 76val, 257
xlin, 188
value, 257
xlog, 188
Vavilov, 44
xmax, 188
void, 126
xmin, 187
VOL, 126
xnum, 57
vol, 167, 179, 197, 207, 212, 215, 218, 223, 226, 229, xp, 74
232, 235, 238
xq, 74
volmat, 190, 197, 207, 215, 218, 223, 226, 229, 232, xsdir, 55, 109, 280
235, 238
xsdir.jnd, 5
volume, 52, 53, 167, 178, 179, 196, 197, 206, 207, 212, XY, 113
215, 218, 223, 226, 229, 232, 235, 238, 244, xy, 3, 35, 185, 188–190, 196, 199, 206, 213, 217, 223,
257
228, 231, 233, 236, 243, 246, 255, 257, 271
volume and area calculation, 33, 73
xyz, 1, 3, 13, 33, 35, 77, 162, 177, 180, 189, 195, 199,
volume correction, 190
202, 205, 213, 216, 220, 224, 227, 230, 233,
voxel, 53, 136
236, 243, 255, 257, 271, 279, 281, 282
vtkfmt, 197, 207, 215, 218, 223, 226, 235, 238, 255
xz, 196, 206, 213, 217, 223, 228, 231, 233, 236, 243,
vtkout, 197, 207, 215, 218, 223, 226, 235, 238, 255
246, 255, 257, 271
w-ang, 259
w-dst, 259
w-hgt, 259
w-mnh, 259
w-mnw, 259

y, 185, 186, 196, 199, 206, 213, 217, 223, 228, 231, 233,
236
y-txt, 190, 196, 200, 206, 212, 215, 223, 226, 228, 231,
233, 238, 246, 255, 257, 261
y-type, 77, 162, 180, 183, 190

294

y0, 70–76, 80, 83, 180, 246, 248, 259
y1, 70, 71, 74–76, 80, 83, 246, 248
y2, 76y3, 76ylin, 188
ylog, 188
ymax, 188
ymin, 187
yp, 74yq, 74yz, 185, 189, 190, 196, 206, 213, 217, 223, 228, 231,
233, 236, 243, 246, 255, 257, 271
z, 2, 185, 196, 199, 206, 213, 217, 223, 228, 231, 233,
236
z-mesh, 246
z-txt, 190, 196, 200, 206, 212, 215, 223, 226, 228, 231,
233, 238, 246, 257, 261
z-type, 2, 77, 162, 180, 183, 190, 202
z0, 70–76, 80, 83, 246, 248, 259
z1, 70–72, 74–76, 80, 83, 246, 248
z2, 76z3, 76
zlin, 257
zlog, 257
ZP, 113zx, 185, 190

INDEX

PHITS
Ver.2.77
Ver.2.80
Ver.2.80aVer.2.81
Ver.2.82
Ver.2.83
Ver.2.84
Ver.2.85
Ver.2.86
Ver.2.87
Ver.2.88
Ver.2.89
Ver.2.90
Ver.2.91
Ver.2.92
Ver.2.93
Ver.2.94
Ver.2.95
Ver.2.96
Ver.2.97
Ver.3.00
Ver.3.01
Ver.3.02
Ver.3.03
Ver.3.04
Ver.3.05
Ver.3.06
Ver.3.07
Ver.3.08
Ver.3.10

Ver. 3.10 User’s Manual
2015/05/19
2015/09/02
2015/09/16
2015/10/15
2015/12/16
2016/03/03
2016/03/16
2016/05/16
2016/08/23
2016/09/15
2016/09/29
2017/01/11
2017/02/09
2017/02/20
2017/04/18
2017/06/16
2017/06/30
2017/07/21
2017/08/28
2017/09/21
2017/10/04
2017/10/31
2017/12/01
2018/02/01
2018/02/16
2018/03/14
2018/05/29
2018/07/05
2018/08/20
2019/04/03

PH ITS development members：
Koji Niita1 , Tatsuhiko Sato2 , Yosuke Iwamoto2 , Shintaro Hashimoto2,† , Tatsuhiko Ogawa2 ,Takuya Furuta2 , Shinichiro Abe2 , Takeshi Kai2 , Pi-En Tsai2,† , Norihiro Matsuda2 ,Hiroshi Iwase3 , Nobuhiro Shigyo4 , and Lembit Sihver5
1
Research Organization for Information Science & Technology (RIST)
2
Japan Atomic Energy Agency (JAEA)
3High Energy Accelerator Research Organization (KEK)
4
Kyushu University
5
Vienna University of Technology, Austria†
Editors of this user’s manual