-
Notifications
You must be signed in to change notification settings - Fork 70
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
Changes to MOOSE checkpoints prevent MRAD model restarts #369
Comments
@GiudGiud Is this the expected behavior of the new app version? I recently used the INL HPC blue_crab-opt compiled on 3/15/2024 for a different problem and the checkpoint files of the child app are generated as usual. |
We should still be able to generate sub-app checkpoints with |
Tag @YaqiWang |
I believe we've been moving towards having the main app handling all the restart, even if the main input file is "changing" from before-restart to after-restart. |
BTW, @GiudGiud helped me get this running, but obviously this is not the ideal fix. This is
This will generate checkpoint files for the SubApp. |
Bug Description
The
checkpoint = true
inHPMR_thermal_ss.i
used to write a directory calledHPMR_dfem_griffin_ss_out_bison0_cp
with checkpoint files. With the recent changes to MOOSE checkpoints, it appears only the master input app can write checkpoint files.Steps to Reproduce
Obtain the latest version of Dire Wolf and MOOSE. Run the steady state case,
HPMR_dfem_griffin_ss.i
as normal. When the simulation finishes, look inHPMR_dfem_griffin_ss_out_bison0_cp
, notice there are 0 files. You will be unable to run the null transient, or any other simulation relying on restarts.As a comparison to show new functionality, add
checkpoint = true
to[Outputs]
inHPMR_dfem_griffin_ss.i
. Run the steady state case. Look at the two output directoriesHPMR_dfem_griffin_ss_out_cp
andHPMR_dfem_griffin_ss_out_bison0_cp
. You will see the checkpoints in the former directory, and not the latter.It is not as trivial as just using the master app checkpoint files. The neutronics and conduction meshs are different, with different BCs. I did not create the mesh, but I'm guessing some changes might need to be made, hence tagging the model creators.
Impact
Trying to use a copy of MRAD for another application. I can't progress much further right now.
Tagging: @miaoyinb @nstauff @GiudGiud @markdehart
The text was updated successfully, but these errors were encountered: