How to include burnup in coupled calculations? #1216
Replies: 1 comment
-
|
Hi @LeonDong1998, we are very close to having this natively supported in Cardinal (you can find details here: #921). In this PR, you can find an in-memory approach for iteratively running (i) Cardinal multiphysics statepoint to predict temperatures and densities and (ii) OpenMC depletion calculations to update composition. Our team is still currently reviewing the capability and hope to have this merged within the next year but at the moment there are a few other developments higher on the task list. We would greatly welcome you using this PR for your needs - the functionality should be present, but we do not yet have any documentation. There is an alternative (equivalent) approach where you can iteratively run Cardinal and OpenMC depletion calculations, but using a file-based approach. With this alternative option, you can (i) run Cardinal as you normally do, outputting a properties.h5 file which contains temperature and density; (ii) loading this file into an OpenMC depletion script that runs just 1 depletion step and outputs a statepoint file with the new composition. You can then repeat these two steps until the end of the depletion cycle, loading data from files. I've attached an example script which shows how to use this. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello everyone!
I have encountered a difficult problem. I want to implement the coupled calculation of MOOSE and openmc burnup using the same time scale. But it seems that burnup calculation can only be done through integrator calculation, and burnup settings cannot be generated into XML files.
I'd like to express my gratitude in advance!
Beta Was this translation helpful? Give feedback.
All reactions