Closed paulromano closed 4 years ago
I have not run your input deck, but I am seeing the same issue on our own processing of 10B. We have run this through MCNP and don't get any noticeable problems. We are having other issues with 10B, perhaps they are related. I think there is something wrong with the data, but I'm not sure what it is at the moment.
In any event, regardless of the data, NJOY should produce a valid XSS array.
Ok, good to know I'm not crazy! I see @brown170's name on the file description, so let's blame him.
@jlconlin Have you found out anything more about the 10B issues?
@paulromano I had totally forgotten about this issue. I've been too busy getting ENDF/B-VIII.0 processed.
As noted in #164, there was an error in the original VIII.0 evaluation for B10 (errata here). Recent updates to NJOY also cause it to produce an error with the original evaluation rather than letting it slide through with no errors (but weird values in the ACE file). The fixed B10 evaluation works just fine, so I'll go ahead and close this issue.
I'm trying to process ENDF/B-VIII.0 beta6 using NJOY2016 and I'm running into an issue with B-10. NJOY actually runs fine and generates an ACE file, no problem. Looking at the ACE file, I see that NXS(1) is 82851 implying that the XSS array should be found over (NXS(1) + 3)/4 = 20713 lines. However, the file actually has an additional 12 lines of zeros (mix of floating point and integers) after the required 20713 lines. The end of the file looks like:
where the last value in XSS is actually 8.01e2. So, my question is -- what are all these zeros and why are they there? Is this a valid ACE file or is something wrong? The scripts that I have for parsing ACE files fail on this one in a way that I've never seen before so it makes me a little suspicious.
Here's my input deck for good measure: