Polaris *.t16 and *.x16 bug

[Pavel Suk]

Hello, 

  I have doubts about the results in the t16 file when the reflector simulation in Polaris sequence. The fission XS is zero, nu*fission is zero, however the kappa*fission is non zero in the t16 file. Is this the code bug? I cannot confirm it from x16 file, because the x16 file is not readable by the script 'x16convert.exe'. The similar numbers are in the output file in the field of the kappa*absorption, but the numbers are in the kappa*fissio field in the t16 file. This complication creates errors in the PARCS code (when using the GenPMAX script for data preparation).

I would like to ask if is it bug, or should I have to change something in the input file.

If the situation is bug and will be repaired in the next SCALE release, can I zero the values without any other impact?

I am sending the Polaris input file and t16, x16 and output file of the simulation

Thank you for your time and answers
Best Regards,
Pavel 

[Matthew A. Jessee]

Pavel,

We are aware of this inconsistency. Polaris provides a kappaAbsorption and kappaFission cross section value. PARCS and PMAXS files only support a kappaFission value. To accurately account for all energy contributions for the power normalization in the core in PARCS, we place the kappaAbsorption cross section on the kappaFission location in the .t16/x16 file. The easiest solution for now is to zero-out kappaFission in your reflector .t16 files. 

In future versions of SCALE, Polaris, GENPMAXS, we hope to iron out this inconsistency.

Thanks,