Restart feature in 2.1.17

This category replaces the missing input manual
Tian
Posts: 18
Joined: Mon Mar 10, 2014 1:19 pm
Security question 1: No
Security question 2: 92

Re: Restart feature in 2.1.17

Post by Tian » Tue Sep 22, 2015 12:10 pm

Hi,

Just a small question about restarting, I have add a line

Code: Select all

set rfw 1 test
in the input, however I have got the error massage
Fatal error in function StoreComposition:

Unable to open file for writing
I am using version 2.1.23. What might be wrong? Thank you.

User avatar
Jaakko Leppänen
Site Admin
Posts: 2387
Joined: Thu Mar 18, 2010 10:43 pm
Security question 2: 0
Location: Espoo, Finland
Contact:

Re: Restart feature in 2.1.17

Post by Jaakko Leppänen » Thu Sep 24, 2015 10:15 am

Looks like Serpent is unable to write the restart file. Have you checked the permission in the directory where the calculation is run? Is it possible that you are running out of disk space?
- Jaakko

Andy_Turner
Posts: 18
Joined: Tue Jan 12, 2016 11:38 am
Security question 1: No
Security question 2: 92

Re: Restart feature in 2.1.17

Post by Andy_Turner » Thu Mar 24, 2016 1:26 pm

Can this feature be used to restart from an interrupted calculation? e.g. like in MCNP, doing 'mcnp r=old_runtpe c'
- Andy Turner, CCFE

User avatar
Jaakko Leppänen
Site Admin
Posts: 2387
Joined: Thu Mar 18, 2010 10:43 pm
Security question 2: 0
Location: Espoo, Finland
Contact:

Re: Restart feature in 2.1.17

Post by Jaakko Leppänen » Fri Mar 25, 2016 12:15 am

Yes, basically you can go back to the last completed burnup step (provided that the writing of the restart file was enabled).
- Jaakko

Andy_Turner
Posts: 18
Joined: Tue Jan 12, 2016 11:38 am
Security question 1: No
Security question 2: 92

Re: Restart feature in 2.1.17

Post by Andy_Turner » Tue Mar 29, 2016 12:34 pm

Jaakko Leppänen wrote:Yes, basically you can go back to the last completed burnup step (provided that the writing of the restart file was enabled).
Sorry I meant during a normal transport run, whether it is possible to continue a neutron transport calculation run that was terminated prematurely, or perhaps you want to run more histories for example...
- Andy Turner, CCFE

User avatar
Jaakko Leppänen
Site Admin
Posts: 2387
Joined: Thu Mar 18, 2010 10:43 pm
Security question 2: 0
Location: Espoo, Finland
Contact:

Re: Restart feature in 2.1.17

Post by Jaakko Leppänen » Tue Mar 29, 2016 6:02 pm

Unfortunately, no.
- Jaakko

Andy_Turner
Posts: 18
Joined: Tue Jan 12, 2016 11:38 am
Security question 1: No
Security question 2: 92

Re: Restart feature in 2.1.17

Post by Andy_Turner » Thu Mar 31, 2016 12:39 pm

Jaakko Leppänen wrote:Unfortunately, no.
Oh okay. Feature request? ;)

I understand Serpent2 was designed with an ethos on scalability, to run on large clusters. If there is indeed a goal to do large-scale fixed source problems (once variance reduction is implemented) then we would be talking about using 100's of cores for many weeks. In these cases you would definitely need a binary dump and capability to restart/extend/complete a job from last dump (redundancy against node failure, flexibility, practicality, difficult to know how many NPS is needed before you commence the run etc).

Thanks

Andy
- Andy Turner, CCFE

satkinson
Posts: 23
Joined: Thu Apr 09, 2015 6:14 pm
Security question 1: No
Security question 2: 92

Re: Restart feature in 2.1.17

Post by satkinson » Thu Jul 07, 2016 7:57 pm

Hi Jaakko,

The restart feature seems to only work on bu's greater than 0.1 MWd/kgU. In this case restarting with 0.177 works, however 0.088 does not and it produces the error below.

Restart file "restartfile" contains the following burnup points:

0 : BU = 0.000 MWd/kgu, time = 0.00000E+00 days
1 : BU = 0.088 MWd/kgu, time = 1.00000E+00 days (closest point)
2 : BU = 0.177 MWd/kgu, time = 2.00000E+00 days


***** Thu Jul 7 17:40:05 2016

Input error:

Burnup point 0.088 MWd/kgU not found in restart file

Cheers,

Satkinson

User avatar
Jaakko Leppänen
Site Admin
Posts: 2387
Joined: Thu Mar 18, 2010 10:43 pm
Security question 2: 0
Location: Espoo, Finland
Contact:

Re: Restart feature in 2.1.17

Post by Jaakko Leppänen » Thu Jul 07, 2016 10:47 pm

Do you get this error with 2.1.26 or with some older update?

A quick solution might be to use the burn time instead of burnup (negative entry in the rfr card).

You can also use "set rfr idx 1" which should give you the first burnup point (this feature has probably not been described anywhere).

In any case, the routine not finding a burnup point < 0.1 is clearly a problem that should be fixed.
- Jaakko

satkinson
Posts: 23
Joined: Thu Apr 09, 2015 6:14 pm
Security question 1: No
Security question 2: 92

Re: Restart feature in 2.1.17

Post by satkinson » Fri Jul 08, 2016 11:39 am

Hi Jaakko,

This was found using 2.1.26.

Thanks for the work around.

Satkinson

Post Reply