Triton 6.1 XSEC in ARP 6.3

[Brian Elder]

Hi all, I have some BWR Triton cross section files that were generated by a contractor in SCALE 6.1.2. I'm attempting to transition to SCALE 6.3 and it appears that ARP is not properly reading the older binary files. Unfortunately, I do not have access to the Triton input that generated the files; however, I do have a summary report with some details of their generation. The files appear to be working correctly in ARP in SCALE 6.1, however ARP in SCALE 6.3 does not appear to be parsing the files correctly. The files are supposed to have 47 exposure statepoints, however ARP in SCALE 6.3 thinks there are 48 and crashes due to not having enough exposures defined in arpdata.txt. I've tried to evaluate the files using OBIWAN in SCALE 6.3 and it provides obviously invalid output:

$ obiwan view -format=burnups atr_10x10-9_e15_w30.cmbined
         pos   MWd/MTIHM
           1  3.4028e+38
           2  3.4028e+38
           3  3.4028e+38

           ...

          46  3.4028e+38

          47  3.4028e+38
          48  3.4028e+38

Does anyone have any idea as to how I can convert or correct these binary files for 6.3 without having access to the original Triton input?

Thanks in advance,

Brian Elder

[Willem van Rooijen]

Hello,

I don't know whether or not this message is relevant, but just in case. From your explanation, it appears that this is a problem between double precision and single precision data. 

I have never used ARP. An old-fashioned solution is to convert the ARP database to ASCII with the "old" version of SCALE and then convert from ASCII to binary with the "new" version of SCALE. Problem is: I don't know whether or not it is possible to convert ARP libraries from binary to ASCII and back...

Regards,

Namizono

2025年8月19日火曜日 21:08:25 UTC+9 Brian Elder:

[Brian Elder]

Thanks for the reply. I had considered that approach, however the problem I ran into is that the tool used to convert the libraries between ASCII and binary, REORG, doesn't exist past SCALE 6.1, so while I can convert them to ASCII in the old version, I cannot convert them back to a usable format in a newer version.

Thanks,

Brian