-
Notifications
You must be signed in to change notification settings - Fork 86
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
Need Help with Some Error Messages #248
Comments
Most of these appear to be ENDF formatting issues. I'll parse the file in ENDFtk, our new ENDF reader to see if this reader picks up the same issues. The Pb205 and Pr141 might indicate other issues that I'll have to look into more. I'll try to get back to you on this somewhere next week. |
Thanks for taking a look. I don't have a trained eye for this sort of thing, but I'm not surprised. Everyone loves to say they use ENDF format, but devils and details. |
@herter4171 exactly and well phrased, NJOY has broad shoulders but most of the above are in fact ENDF form/format and interpretation issues, some already (Pr141) acted upon by the JENDL-5 team [ @whaeck the above error text do not always correspond to the one I had, but the target list seems to do !! Au198: error in endf illegal TAB1, nbt(nr)/=np for mf/mt = 6/ 5 Removing the implicit (above 20 MeV) mt=5 mf3&mf6 on those targets save the day for reactor applications @whaeck the error in endf illegal TAB1, nbt(nr)/=np for mf/mt = 6/ 5 or 6/ 0 is weird on the above cases, nr max is 20 and np the number of points !! could it means memory overlap, as the endf file has already been read to create the pendf Also what about the fact that on say JENDL-5 U235, PREPRO-2021 warn me to linearise the multiplicity in mf6/mt5 that must be INT = 2, NJOY does not |
Any movement on this? I'll see where I get with downloading newer JENDL, but I'm pretty sure most of the errors will remain. |
@herter4171 for you the solution is to remove, prior to processing, the mt=5 mf3&mf6 blocks (I did it, you need help to do it?), then the Acer errors vanish. Those sections of the files are not relevant for your applications, as they relate and only partially to partial channels occurring above 20 MeV neutron incident energy. ENDF-6 format manual: mt=5 (z,anything) Sum of all reactions not given explicitly in another MT number. This is a partial reaction to be added to obtain MT=1. Each particle can be identified and its multiplicity given in File 6. |
I haven't had time to look into this in detail. I'll try to take some time today. |
I started looking at the Pr-141 error which is related to the unresolved resonance treatment in UNRESR. These are my findings for this evaluation:
I believe that the upper limit of the unresolved resonance region has been erroneously set to 160 keV instead of 100 keV. This is something we have seen in the past (it is a rare thing though). Setting the upper limit of the unresolved energy region to 100 keV in the evaluation fixes the issue. The JENDL5 library provides an errata page where a corrected evaluation is available: https://wwwndc.jaea.go.jp/jendl/j5/JENDL-5_Errata.html |
We are trying to incorporate JENDL 5 into our collection of nuclear data libraries (NDLs). Basically, I was handed some tooling to wrap going from the library source files to a proper NDL using NJOY to evaluate at our temperatures, which I then overhauled to align with how we handle code. I worked around the NJOY parts, because I don't really know what they're doing and have never been a proper user of NJOY.
While we've used NJOY21 for other libraries with no fuss, our original problem had support guiding us to NJOY2016. Using the
develop
branch got rid of most of our original 171 errors due to a known bug fix, but 53 isotopes are still failing on us. I've been told they aren't mission critical, but we will rest easier and not have to explain as much if we can whittle this list down to single digits, ideally. I'm not sure if any platform details beyond us using Linux will help, but I'll be happy to provide further details as needed.Summary of Error Messages
Since GitHub doesn't like tarballs, the inputs and outputs for these isotopes are available for download here, and the password is
YRa4jXgMAKbx
. Also, in my haste, I tarballed the current directory, so you will want to extract in an empty subdirectory. I wanted to have the cases be runnable, but the wrapper code didn't keep all of the tape files by default. If other files are needed to help diagnose, please let me know, and I'll do my best to furnish them.The text was updated successfully, but these errors were encountered: