Skip to content

Pebble Tanker model

Description

A computational model for addressing the needs in Criticality Safety Benchmarking data for HALEU fuel Cycle and Transportation.

Executive Summary

An exploratory model, the “Pebble Tanker,” was developed; this model aims to facilitate validation of nuclear criticality safety calculations in the context of industrial-scale transportation of TRISO fuel.

Details

The pebble tanker model uses a hexagonal close-packed (HCP) array of grains within a pebble and an HCP array of pebbles within the Pebble Tanker. The tanker constitutes an array of tubes. A 3x3 array of tubes to transport the PBMR-type TRISO Pebble and a 4x4 array of tubes to transport the HERMES-type TRISO Pebble.

Testing

The model was used in a nuclear criticality safety validation analysis. What this analysis entails is; CSAS6-Shift sequence is used to determine the keff of a system.TSUNAMI-3D-Shift analysis sequence is used for the sensitivities of keff and the nuclide reactions. The sensitivities are calculated using the iterated fission probability (IFP) method. These energy-dependent data are then stored in a sensitivity data file (SDF), which is then used by the TSUNAMI-IP sequence. TSUNAMI-IP calculates the ck values reflecting the shared uncertainty between an application and a benchmark experiment. TSUNAMI-IP also provides insight into the different reaction pairs that contribute to the ck parameter. The ck parameter will reveal the aim; to establish the needs for nuclear criticality safety benchmark. The TSUNAMI-3d was tested with Direct perturbation DP evaluations.

Caveats

The paper analyzes pebble quantities that approach industrial quantities, but by no means are these basic models fully designed transportation packages.

Additional Information

None.

Resolution

The assignee, denoted in parentheses for each stage, shall check the boxes within their stage, assign to the next person when all tasks are complete.

  • 0-proposed (Originator: @voe )
    • added a short description sentence above
  • 1-approved/rejected (QA Coordinator: @c31 )
    • added executive section above
    • created a branch for the model named #pebble_tanker-rev01
  • 2-in progress (Originator)
    • documented model
    • merged model !3 (merged) by @voe with review by @c31 and @6tg
    • merged model sample outputs using SCALE v6.3.1 in !2 (merged) by @voe with review by @c31
    • added/expanded/updated details of the model
  • 3-in staging (QA Coordinator)
    • guidance (yes/no)
    • verified models on master
  • 4-in review (Reviewer)
    • reviewed models, derived data, and documentation
  • 5-final check and merge (QA Coordinator)
    • confirmed QA info, labels, and milestone is correct
    • reviewed model details and data for overall conformance and quality
  • 6-notification and closure (QA Coordinator)
    • mirror updated repository
    • send notification of updates
Edited by Celik, Cihangir