Repository navigation
Fix for non-zero CDF start points in incoherent inelastic data #2290
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
Merged
Merged
Changes from 1 commit
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev
Previous commit
Fix wording of comments
- Loading branch information
commit 6a0d5043030cffd791b0500e6eecdf11be3fb02b
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
I never realized this! Do you have an example of a particular library/nuclide/reaction/distribution for which this happens?
Uh oh!
There was an error while loading. Please reload this page.
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.
So this is actually a common occurrence as well (though not systematically the case as with the CDFs). In ENFB/B-VIII.0, I have seen warnings from PapillonNDL about this for important evaluations like H-H2O (all temperatures), D-D2O (all temperatures), O-D2O (all temperatures), and several other materials as well. I don't think it happens for every single incident/outgoing energy pair, but it certainly happens at least once in each of those evaluations. PapillonNDL stops reading the ACE file after the first error, so its hard for me to say with certainty how prevalent it is. When bench marking PapillonNDL, I don't believe I ever noticed a statistical difference with OpenMC due to my sorting of the angles, but this is still less than ideal, as smearing assumes that they are sorted. If you want, I have programs which directly sample the distributions, either from PapillonNDL or OpenMC, and then a script which gets the p-value of the energy and angle distributions to compare.
Another issue I noticed with the ENDF/B-VII.1 ACE files is that the scattering angles where sometimes larger than 1, or less than -1 (this happens in the ligher water TSL for sure). This was a bug in not-so-old versions of NJOY, but has since been fixed. I added a check for this to PapillonNDL, and because of that, I simply can't use the older ENDF/B-VII.0 ACE files that were distributed with MCNP for example. Currently, I don't see a check for this in the OpenMC processing. There isn't really a good solution for this problem, other than re-processing the evaluation with the newer version of NJOY. Do you want me to add a check for this @paulromano ? It might cause people problems if they want to generate HDF5 files from these older ACE files, but maybe this is better than letting them use physically invalid data ?
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.
I should specify, when I mention ENDF/B-VIII.0 here, these are the ACE files made from lib80x, distributed by LANL.
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.
Re: the check for values outside of [-1,1], perhaps the best thing to do would be to add a warning so that at least we're letting the user know they may be dealing with bad data. That doesn't necessarily need to be done as part of this PR though.