40 research outputs found
Implementation of muon pair production in PHITS and verification by comparing with the muon shielding experiment at SLAC
We implemented a model of muon pair production through a real photon in PHITS
and compared our calculations with data of the muon shielding experiment
conducted at SLAC to verify the validity of the implemented model. Our
predictions of the muon fluence induced by electrons are in good agreement with
the experimental data. To understand the known differences between the
calculations of the muon fluence, which have been determined using other
Monte-Carlo codes, we quantitatively evaluate the fluctuations in the
Monte-Carlo results due to systematic errors in multiple Coulomb scattering,
differences in the approximation methods and energy loss models, and whether
incoherent production is considered.Comment: 16 pages, 8 figure
High dose rate 192Ir brachytherapy source model Monte Carlo dosimetry: mHDR-v2 and mHDR-v2r.
After 2010, the source model of the microSelectron HDR Afterloader System was slightly modified from the previous model. Granero et al. named the modified source model "mHDR-v2r (revised model mHDR-v2)" and the previous model "mHDR-v2". They concluded that the dosimetric differences arising from the dimensional changes between the mHDR-v2 and mHDR-v2r designs were negligible at almost all locations (within 0.5% for r ≥ 0.25 cm), the two-dimensional anisotropy function difference between the two sources is found 2.1% at r = 1.0 cm when compared with the results of the other experimental group. To confirm this difference, we performed a full Monte Carlo simulation without energy-fluence approximation. This is useful near the radiation source where charged-particle equilibrium does not hold. The two-dimensional anisotropy function of the TG-43U1 dataset showed a few percent difference between the mHDR-v2r and mHDR-v2 sources. There was no agreement in the immediate vicinity of the source (0.10 cm and 0.25 cm), when compared to Granero et al. in mHDR-v2r sources. The differences in these two-dimensional anisotropy functions were identified
Recommended from our members
The EGS5 Code System
In the nineteen years since EGS4 was released, it has been used in a wide variety of applications, particularly in medical physics, radiation measurement studies, and industrial development. Every new user and every new application bring new challenges for Monte Carlo code designers, and code refinements and bug fixes eventually result in a code that becomes difficult to maintain. Several of the code modifications represented significant advances in electron and photon transport physics, and required a more substantial invocation than code patching. Moreover, the arcane MORTRAN3[48] computer language of EGS4, was highest on the complaint list of the users of EGS4. The size of the EGS4 user base is difficult to measure, as there never existed a formal user registration process. However, some idea of the numbers may be gleaned from the number of EGS4 manuals that were produced and distributed at SLAC: almost three thousand. Consequently, the EGS5 project was undertaken. It was decided to employ the FORTRAN 77 compiler, yet include as much as possible, the structural beauty and power of MORTRAN3. This report consists of four chapters and several appendices. Chapter 1 is an introduction to EGS5 and to this report in general. We suggest that you read it. Chapter 2 is a major update of similar chapters in the old EGS4 report[126] (SLAC-265) and the old EGS3 report[61] (SLAC-210), in which all the details of the old physics (i.e., models which were carried over from EGS4) and the new physics are gathered together. The descriptions of the new physics are extensive, and not for the faint of heart. Detailed knowledge of the contents of Chapter 2 is not essential in order to use EGS, but sophisticated users should be aware of its contents. In particular, details of the restrictions on the range of applicability of EGS are dispersed throughout the chapter. First-time users of EGS should skip Chapter 2 and come back to it later if necessary. With the release of the EGS4 version, a deliberate attempt was made to present example problems in order to help the user ''get started'', and we follow that spirit in this report. A series of elementary tutorial user codes are presented in Chapter 3, with more sophisticated sample user codes described in Chapter 4. Novice EGS users will find it helpful to read through the initial sections of the EGS5 User Manual (provided in Appendix B of this report), proceeding then to work through the tutorials in Chapter 3. The User Manuals and other materials found in the appendices contain detailed flow charts, variable lists, and subprogram descriptions of EGS5 and PEGS. Included are step-by-step instructions for developing basic EGS5 user codes and for accessing all of the physics options available in EGS5 and PEGS. Once acquainted with the basic structure of EGS5, users should find the appendices the most frequently consulted sections of this report
Comparison of the radial dose functions.
(a) 0 cm ≤ r ≤ 0.5 cm. (b) 0 cm ≤ r ≤ 10 cm. The standard error is added at r = 4 cm.</p
Fig 13 -
(a) Comparison of 2D anisotropy functions at distances of 1.0 cm. (b) The ratio of 2D anisotropy functions to mHDR-v2r source at 1.0 cm. The error bar at 58° is derived from the relationship between mHDR-v2r and mHDR-v2, while the error bar at 158° is derived from the relationship between mHDR-v2r and Daskalov et al.</p
Fig 12 -
(a) Comparison of 2D anisotropy functions at distances of 0.50 cm. (b) The ratio of 2D anisotropy functions to mHDR-v2r source at 0.50 cm. The error bar at 58° is derived from the relationship between mHDR-v2r and mHDR-v2, while the error bar at 158° is derived from the relationship between mHDR-v2r and Daskalov et al.</p
Schematic designs of <sup>192</sup>Ir sources.
Dimensions are given in mm. (a) mHDR-v2 source. Shapes and dimensions are according to Daskalov et al. [7](Fig 1(b)). (b) mHDR-v2r source. Shapes and dimensions are according to Granero et al. [9] (Fig 1).</p