-
Notifications
You must be signed in to change notification settings - Fork 25
Tallying arbitrary MT number #179
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
Tallying arbitrary MT number #179
Conversation
ChasingNeutrons
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, just the handful of aesthetic things to fix.
NuclearData/ceNeutronData/aceDatabase/aceNeutronNuclide_class.f90
Outdated
Show resolved
Hide resolved
NuclearData/ceNeutronData/aceDatabase/aceNeutronNuclide_class.f90
Outdated
Show resolved
Hide resolved
NuclearData/ceNeutronData/aceDatabase/aceNeutronNuclide_class.f90
Outdated
Show resolved
Hide resolved
| !! NOTE: despite being in the interface, this function only makes sense | ||
| !! for CE. The MG extension returns a fatalError if called | ||
| !! | ||
| function getMTxs(self, MT, p) result(xs) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why can this not work for MG? Can't certain MT numbers be included/excluded?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In a MG material you can only look up the cross sections you provide. Those are legit tally responses, but are not provided by getMTxs (they are looked up from the xss Packages directly). Otherwise, the ENDF MT numbers don't exist in MG.
Adding the capability to micro and macro Responses to get a larger set of MT numbers as input.