-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mismatch Graphite Matrix between HP-MR Inputs #537
Comments
sounds good. Let's regold. Please ping me if you need help with regolding HPC-tested inputs |
gambka
added a commit
to gambka/virtual_test_bed
that referenced
this issue
Mar 26, 2025
gambka
added a commit
to gambka/virtual_test_bed
that referenced
this issue
Mar 26, 2025
gambka
added a commit
to gambka/virtual_test_bed
that referenced
this issue
Mar 26, 2025
gambka
added a commit
to gambka/virtual_test_bed
that referenced
this issue
Mar 27, 2025
elementx54
added a commit
to elementx54/virtual_test_bed
that referenced
this issue
Mar 31, 2025
Other microreactor input files need to used the `IG_110` grade of graphite. This changes all of the inputs to use the same type of graphite grade. Closes idaholab#537
elementx54
added a commit
to elementx54/virtual_test_bed
that referenced
this issue
Mar 31, 2025
Other microreactor input files need to used the `IG_110` grade of graphite. This changes all of the inputs to use the same type of graphite grade. Closes idaholab#537
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Reason
Due to some changes in BISON's
GraphiteThermalMatrix
, a review of the graphite compact material properties for the HP-MR found that the type was not consistent. As such, changing the models to usegraphite_grade = IG_110
is desired.Design
The inputs for mrad will be changed to use the same compact graphite as the "hpmr_assembley/main.i".
Impact
The simulation results will most likely be changed slightly. However, the changes in BISON would have necessitated this change anyway.
The text was updated successfully, but these errors were encountered: