search

njoy / NJOY2016

Nuclear data processing with legacy NJOY
https://www.njoy21.io/NJOY2016
Other
98 stars 86 forks source link

Explicit p induced MCNP processing #208

Open jchsublet opened 3 years ago

jchsublet commented 3 years ago

Surfing on the renewed interest in charge particle evaluation and MC processing, I exemplified with explicit s30 p-tendl and NJOY2016.64, with success I admit. However I could not help noticing some new messages in my second acer runs

---message from change---expected xss index ( 22673) greater than current index ( 22668) xss array was padded accordingly

Do I have to worry about this padding? that appears to be more numerical than physical. However if its belong to the original file structure or form it would be a good time to tell.

inO016.txt p-O016.tendl.txt O016chk.pdf run-ace-O016.res.txt

whaeck commented 3 years ago

This might be related to issue #130, for which I introduced the padding check in the change routine. Did consis give you messages about shifting the eprime values? If so, it should not be an issue (there's just zeros where there was previous data that I erased, and MCNP won't even notice). The fact that the index is off by 5 does indicate that it would be this. If not, this might indicate another issue in ACER since we don't have to pad the xss array except in consis for what was done to solve issue #130.

jchsublet commented 3 years ago

And it is appreciated, it may partly be related though as #130 was for n-induced, this one is p-induced. Also I am not entirely sure, has expressed in #130 about the eprime shifting logic (why having it on an mt=5 ??) and on the sense of the text of the messages this brings, have a look

consis.txt

We've corrected the TENDL forms for the n-induced and that transpired automatically to the CP ones, but does that bring peace for the CP? because if it does we have a roadmap for explicit cp-induced