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.

The partial fission rate for isotope is denoted by . It is computed by:

where is the location in the macroscopic, neutronics domain and 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 are understood to be smooth changes of the average composition of the microscopic domain (orders of centimeters), while changes with 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. is the number density of isotope , is the microscopic fission cross section of isotope in group , and is the scalar flux in group .

Denoting the microscopic domain as located at , we can define a slowly varying average of the number densities:

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:

The PKAFissionFragmentNeutronics accepts the values of as the partial_reaction_rates parameter. The fission rate density in the microscopic domain is computed by:

where , is the site volume that is provided to the MyTRIMRasterizer and is the -th variable provided to the MyTRIMRasterizer's var parameter. Hence, we have:

PKAFissionFragmentNeutronics accepts the values of in the averaged_number_densities parameter.

The expected number of fissions in a mesh element with index and volume is given by:

Non-integer results are rounded up with a probability of the ; 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 Schunert and others (2017).

Input Parameters

  • averaged_number_densitiesThe number density of the species averaged over the domain.

    C++ Type:std::vector<PostprocessorName>

    Unit:(no unit assumed)

    Controllable:No

    Description:The number density of the species averaged over the domain.

  • blockThe list of blocks (ids or names) that this object will be applied

    C++ Type:std::vector<SubdomainName>

    Controllable:No

    Description:The list of blocks (ids or names) that this object will be applied

  • partial_reaction_ratesPartial neutronic reaction rates per unit volume [sum_g xs_{r,g,i} * phi_g], r: reaction type, g: energy group, i: nuclide id.Provide number density as variable in rasterizer!

    C++ Type:std::vector<PostprocessorName>

    Unit:(no unit assumed)

    Controllable:No

    Description:Partial neutronic reaction rates per unit volume [sum_g xs_{r,g,i} * phi_g], r: reaction type, g: energy group, i: nuclide id.Provide number density as variable in rasterizer!

Optional Parameters

  • allow_duplicate_execution_on_initialFalseIn the case where this UserObject is depended upon by an initial condition, allow it to be executed twice during the initial setup (once before the IC and again after mesh adaptivity (if applicable).

    Default:False

    C++ Type:bool

    Controllable:No

    Description:In the case where this UserObject is depended upon by an initial condition, allow it to be executed twice during the initial setup (once before the IC and again after mesh adaptivity (if applicable).

  • execution_order_group0Execution order groups are executed in increasing order (e.g., the lowest number is executed first). Note that negative group numbers may be used to execute groups before the default (0) group. Please refer to the user object documentation for ordering of user object execution within a group.

    Default:0

    C++ Type:int

    Controllable:No

    Description:Execution order groups are executed in increasing order (e.g., the lowest number is executed first). Note that negative group numbers may be used to execute groups before the default (0) group. Please refer to the user object documentation for ordering of user object execution within a group.

  • force_postauxFalseForces the UserObject to be executed in POSTAUX

    Default:False

    C++ Type:bool

    Controllable:No

    Description:Forces the UserObject to be executed in POSTAUX

  • force_preauxFalseForces the UserObject to be executed in PREAUX

    Default:False

    C++ Type:bool

    Controllable:No

    Description:Forces the UserObject to be executed in PREAUX

  • force_preicFalseForces the UserObject to be executed in PREIC during initial setup

    Default:False

    C++ Type:bool

    Controllable:No

    Description:Forces the UserObject to be executed in PREIC during initial setup

Execution Scheduling Parameters

  • control_tagsAdds user-defined labels for accessing object parameters via control logic.

    C++ Type:std::vector<std::string>

    Controllable:No

    Description:Adds user-defined labels for accessing object parameters via control logic.

  • enableTrueSet the enabled status of the MooseObject.

    Default:True

    C++ Type:bool

    Controllable:Yes

    Description:Set the enabled status of the MooseObject.

  • implicitTrueDetermines whether this object is calculated using an implicit or explicit form

    Default:True

    C++ Type:bool

    Controllable:No

    Description:Determines whether this object is calculated using an implicit or explicit form

  • seed0The seed for the master random number generator

    Default:0

    C++ Type:unsigned int

    Controllable:No

    Description:The seed for the master random number generator

  • use_displaced_meshFalseWhether or not this object should use the displaced mesh for computation. Note that in the case this is true but no displacements are provided in the Mesh block the undisplaced mesh will still be used.

    Default:False

    C++ Type:bool

    Controllable:No

    Description:Whether or not this object should use the displaced mesh for computation. Note that in the case this is true but no displacements are provided in the Mesh block the undisplaced mesh will still be used.

Advanced Parameters

  • prop_getter_suffixAn optional suffix parameter that can be appended to any attempt to retrieve/get material properties. The suffix will be prepended with a '_' character.

    C++ Type:MaterialPropertyName

    Unit:(no unit assumed)

    Controllable:No

    Description:An optional suffix parameter that can be appended to any attempt to retrieve/get material properties. The suffix will be prepended with a '_' character.

  • use_interpolated_stateFalseFor the old and older state use projected material properties interpolated at the quadrature points. To set up projection use the ProjectedStatefulMaterialStorageAction.

    Default:False

    C++ Type:bool

    Controllable:No

    Description:For the old and older state use projected material properties interpolated at the quadrature points. To set up projection use the ProjectedStatefulMaterialStorageAction.

Material Property Retrieval Parameters

Input Files

References

  1. S. Schunert and others. Heat Source Characterization In A TREAT Fuel Particle Using Coupled Neutronics Binary Collision Monte-Carlo Calculations. In M&C 2017 International Conference on Mathematics & Computational Methods Applied to Nuclear Science & Engineering. April 2017.[BibTeX]