forked from idaholab/magpie
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Refactor neutronics pka generators to include averaged number densiti…
…es as input. Add documentation (idaholab#302)
- Loading branch information
Sebastian Schunert
committed
Jun 5, 2018
1 parent
6da5ec7
commit 4d9a84a
Showing
11 changed files
with
125 additions
and
98 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,8 @@ | ||
|
||
@inproceedings{SchunertTREATHeatSource, | ||
author={S. Schunert and others}, | ||
title={{Heat Source Characterization In A TREAT Fuel Particle Using Coupled Neutronics Binary Collision Monte-Carlo Calculations}}, | ||
booktitle={{M\&C 2017 International Conference on Mathematics \& Computational Methods Applied to Nuclear Science \& Engineering}}, | ||
month={April, | ||
year={2017} | ||
} |
38 changes: 25 additions & 13 deletions
38
doc/content/documentation/systems/UserObjects/PKAFissionFragmentNeutronics.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,19 +1,31 @@ | ||
<!-- MOOSE Documentation Stub: Remove this when content is added. --> | ||
|
||
# PKAFissionFragmentNeutronics | ||
|
||
!alert construction title=Undocumented Class | ||
The PKAFissionFragmentNeutronics has not been documented, if you would like to contribute to MOOSE by | ||
writing documentation, please see [/generate.md]. The content contained on this page explains | ||
the typical documentation associated with a MooseObject; however, what is contained is ultimately | ||
determined by what is necessary to make the documentation clear for users. | ||
|
||
!syntax description /UserObjects/PKAFissionFragmentNeutronics | ||
`PKAFissionFragmentNeutronics` generates primary knock-on atoms (PKA) originating | ||
from fission reactions. The difference to PKAFissionFragmentEmpirical is that | ||
it uses isotopic fission rates computed by neutronics calculations and ENDF data | ||
for sampling fission product species. | ||
|
||
!syntax parameters /UserObjects/PKAFissionFragmentNeutronics | ||
The partial fission rate for isotope $$i$$ is denoted by $$F_i(\vec{r}, \vec{rho})$$. | ||
It is computed by: | ||
$$$ F_i(\vec{r}, \vec{rho}) = \sum\limits_{g=1}^G N_i(\vec{r},\vec{rho})\sigma_{f,g,i} \phi_g(\vec{r}),$$$ | ||
where $$\vec{r}$$ is the location in the macroscopic, neutronics domain and $$\vec{\rho}$$ | ||
is the location in the microscopic domain. These two locations are separated because their | ||
scale is significantly separated by 3-4 orders of magnitude. Changes with $$\vec{r}$$ are | ||
understood to be smooth changes of the average composition of the microscopic domain (orders of centimeters), while changes with $$\vec{\rho}$$ captures compositional changes between grains on the microscopic domain, i.e. on the orders of micro-meters. The notation of separating the spatial dependence into two scales follows homogenization theory. $$N_i$$ is the number density of isotope $$i$$, $$\sigma_{f,g,i}$$ is the microscopic fission cross section of isotope $$i$$ in group $$g$$, and $$\phi_g$$ is the scalar flux in group $$g$$. | ||
|
||
!syntax inputs /UserObjects/PKAFissionFragmentNeutronics | ||
Denoting the microscopic domain as $$\Omega_m$$ located at $$\vec{r}_m$$, we can define a slowly varying average of the number densities: | ||
$$$ N_i(\vec{r}) = \frac{1}{\Omega_m} \int_{\Omega_m} N_i(\vec{r},\vec{rho}) d\vec{\rho}. $$$ | ||
$$N_i(\vec{r})$$ is the number density provided to neutronics calculations. The nuclide fission rates computed by the neutronics calculation is consequently the slowly varying average | ||
given by: | ||
$$$ F_i (\vec{r}) = \sum\limits_{g=1}^G N_i(\vec{r})\sigma_{f,g,i}.$$$ | ||
The `PKAFissionFragmentNeutronics` accepts the values of $F_i (\vec{r}_m)$ as the `partial_reaction_rates` parameter. In addition, it accepts the values of $$N_i(\vec{r}_m)$$ | ||
as the `averaged_number_densities` parameter. | ||
|
||
!syntax children /UserObjects/PKAFissionFragmentNeutronics | ||
The fission rate density at a location in the microscopic domain is computed by: | ||
$$$ F_i (\vec{r}_m, \vec{\rho}) = \frac{N_i(\vec{r}_m, \vec{\rho})}{N_i(\vec{r}_m)} F_i(\vec{r}_m), $$$ | ||
where $$ N_i(\vec{r}_m, \vec{\rho}) $$ are the number densities provided by the rasterizer. | ||
|
||
!bibtex bibliography | ||
The expected number of fissions in a mesh element with index $j$ and volume $$V_j$$ is given by: | ||
$$$ C_i = \Delta t \int_{V_j} F_i (\vec{r}_m, \vec{\rho}) d\vec{\rho}. $$$ | ||
Non-integer results are rounded up with a probability of the $$ C_i - \text{int}(C_i) $$; otherwise | ||
rounded down. Two PKAs are created from each fission event. The algorithm for sampling their type, energy, and direction of motion is described in [cite:SchunertTREATHeatSource]. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters