Over the course of the comparisons being done between ALARA and FISPACT-II for FENDL3 validation efforts, one underlying issue has been the mismatching of reference decay libraries. Currently, ALARAJOY inherits its decay methods from EAFLib, necessitating an EAF decay library to be provided. While in principle, FISPACT-II should be able to use EAF decay data as well, the two distributed decay libraries on FISPACT-II's nuclear data GitLab (https://git.oecd-nea.org/fispact/nuclear_data) are UKDD, which are ENDF-formatted. To resolve this, one of two routes could resolve this issue:
- Locate a distribution of EAF-2010 that can be used by FISPACT-II, and have both ALARA and FISPACT-II reference EAF decay data.
- Restructure the decay inheritance for ALARAJOY to allow for ENDF-6 formatted decay data, which should be able to process the UKDD library distributed by FISPACT-II.
If Option 1 is available, this would likely be the preferable option because it would not require any code overhaul, although, it is not clear whether or not such a library distribution is presently available. Otherwise, even if we do include ENDF-6 decay inheritance, it should probably be done as an equal alternative option to the EAF inheritance, so that a user working with ALARAJOY could either provide an ENDF-6 or EAF reference decay library.
Over the course of the comparisons being done between ALARA and FISPACT-II for FENDL3 validation efforts, one underlying issue has been the mismatching of reference decay libraries. Currently,
ALARAJOYinherits its decay methods fromEAFLib, necessitating an EAF decay library to be provided. While in principle, FISPACT-II should be able to use EAF decay data as well, the two distributed decay libraries on FISPACT-II's nuclear data GitLab (https://git.oecd-nea.org/fispact/nuclear_data) are UKDD, which are ENDF-formatted. To resolve this, one of two routes could resolve this issue:If Option 1 is available, this would likely be the preferable option because it would not require any code overhaul, although, it is not clear whether or not such a library distribution is presently available. Otherwise, even if we do include ENDF-6 decay inheritance, it should probably be done as an equal alternative option to the EAF inheritance, so that a user working with ALARAJOY could either provide an ENDF-6 or EAF reference decay library.