Max number of burnup steps in t6-depl

67 views
Skip to first unread message

Bruce Patton

unread,
Oct 19, 2020, 10:52:07 PM10/19/20
to SCALE Users Group
Is there a maximum number of burnup steps for triton 3d (t6-depl)? I have a case that runs fine and then just stops. It has a lot of small burnup steps.  I could not find anything in the scale-6.2.4 manual that gave a specific number, but I remember the old GeeWhiz gui had a fixed number of burnup steps ( I seem to recall about a 100).

Rike Bostelmann

unread,
Oct 20, 2020, 1:10:44 PM10/20/20
to SCALE Users Group
Hi Bruce, 

I am not aware of any maximum number of burnup steps in TRITON. If there is, we should catch it at the time of the input processing. Can you post the error message you are seeing?

A possible explanation of this behavior could be that you are running out of memory. Is it possible to re-run the case and observe the memory footprint during the steps before it stops?

Could you otherwise post your input file?

Thanks,
Rike

Bruce Patton

unread,
Oct 22, 2020, 9:48:20 AM10/22/20
to SCALE Users Group
Rike,

I sent you the files.  I think you are right about the memory issue. I tried just a single lattice cell with periodic boundary conditions and it ran the 10 years,  if I collapsed the 2.5 hrs burn/day at 5 days/week into a single burn.  I will try the single cell with the more detailed daily burn to see if it can handle the larger number of burnup steps.

Thanks,
Bruce

Rike Bostelmann

unread,
Oct 22, 2020, 11:32:07 AM10/22/20
to SCALE Users Group
Hi Bruce,

Thank you for the update.
I started the calculation based on the input you posted earlier. So far it is running fine, but I am only at 216.06 days. I will let it run until the end to see if I observe anything particular. 

Thanks,
Rike

Rike Bostelmann

unread,
Oct 24, 2020, 11:58:27 AM10/24/20
to SCALE Users Group
Hi Bruce,

To follow up on the calculation: I successfully ran your 1year input with SCALE 6.3 beta 12 (the beta version I understood you are using). It completed without any error message. 
Have you had success with your re-runs or observed if the previous calculation stopped because of memory? 

Thanks,
Rike

Reply all
Reply to author
Forward
0 new messages