Skip to content
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

Allow for optional cross sections #167

Open
smpark7 opened this issue Sep 8, 2021 · 0 comments
Open

Allow for optional cross sections #167

smpark7 opened this issue Sep 8, 2021 · 0 comments

Comments

@smpark7
Copy link
Collaborator

smpark7 commented Sep 8, 2021

GenericMoltresMaterial and MoltresJsonMaterial currently require all types of neutronics material data (BETA_EFF, CHIT, CHIP, CHID, DIFFCOEF, FISS, INVV, KAPPA, LAMBDA, NSF, NUBAR, REMXS, SP0) regardless of whether they're used in a particular problem.

For example, a steady-state criticality problem without delayed neutrons does not use delayed neutron data (BETA_EFF, CHID, LAMBDA), but the Material objects require users to provide that data. This issue occurs when users wish to use their own neutronics data for such problems instead of parsing a Serpent 2 or SCALE output file with our dedicated python script. The current workaround involves providing said data files filled with meaningless numbers.

This issue can be closed when the Material objects have flags for different types of reactor simulations that determine which neutronics data Moltres requires.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Moltres
  
new
Development

No branches or pull requests

1 participant