Hello,
I have doubts about the results of the homogenized data prepared for the stainless steel reflector in Polaris. I am preparing data via Triton also and when I perform a calculation of a model with almost a full reflector made from stainless steel, the differences from Triton are large. Especially when the multiplication factor of the homogenized data preparation model is compared, the discrepancies can be up to 1150 pcm.
I am attaching the files here:
Rad2 models consist of water and stainless steel block and the discrepancy between Triton and Polaris is approximately 175 pcm in multiplication.
Rad3 models are mainly made from stainless steel and the discrepancy between Triton and Polaris is more than 1300 pcm in multiplication of the model.
This discrepancy produces macro data that affects full core calculation up to 30 ppm of boron (small core).
I am not able to find errors in the Rad3 cases (when you compare the files with Rad2, you will see that there are just different labels and dimensions of the stainless steel).
I am also writing this confusion because a few years ago I found similar behavior in the CASL Vera code that uses also the MoC. The CASL Vera calculated the multiplication factor of the core with the stainless steel reflector wrongly (in comparison to the Serpent code). When the amount of stainless steel decreased. The results were in good consistency.
Do you have any idea how to set up the Polaris to obtain proper XS data?
The XS data obtained from Triton works in the full core model correctly and the multiplication and power distribution are consistent with the reference full core Serpent model.
Thanks, Pavel
Hi Matthew,
I hope you are doing well. We have resolved the issue related to boundary conditions in the SCALE Polaris calculation two years ago.
As I understand it, Polaris currently uses mirror boundary conditions in all directions for both geometries (fuel-only and fuel + reflector). Is there any possibility to modify the boundary conditions in the fuel + reflector model? If not, is this feature planned to be implemented in a future SCALE Polaris release?
Thank you in advance.
Best regards,