Restart feature in 2.1.17

This category replaces the missing input manual
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 21, 2016 1:03 pm

Hi Jaakko,

I have tried these work around now and they get to the stage when they read the file, however the simulation causes a segmentation fault and crashes.

The stages are;

0 : BU = 0.000 MWd/kgu, time = 0.00000E+00 days
1 : BU = 0.021 MWd/kgu, time = 1.00000E+00 days
2 : BU = 0.643 MWd/kgu, time = 3.10000E+01 days (closest point)

I tried the time version using;

set rfr -31 3rodsinfirststage (31 being the day)

and

set rfr idx 2 3rodsinfirststage

Both give the same segmentation fault.

Cheers,

Satkinson

User avatar
Jaakko Leppänen
Site Admin
Posts: 2380
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 » Mon Jul 25, 2016 10:12 am

Could you send me the entire input by email?
- Jaakko

Peter Wolniewicz
Posts: 135
Joined: Mon Dec 13, 2010 5:50 pm

Re: Restart feature in 2.1.17

Post by Peter Wolniewicz » Thu Jan 26, 2017 1:46 pm

Hi!

Must the geometry be the same using the restart feature? I have an activated material and I want to put it in a different geometry and using the restart feature.

I tried, but I get segmentation fault:

Reading material compositions from restart file...
Segmentation fault (core dumped)

User avatar
Jaakko Leppänen
Site Admin
Posts: 2380
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 Jan 26, 2017 2:44 pm

The geometry doesn't have to be, but the material names must match. In any case you shouldn't get a segfault. Could you try running the calculation in debug mode?
- Jaakko

Peter Wolniewicz
Posts: 135
Joined: Mon Dec 13, 2010 5:50 pm

Re: Restart feature in 2.1.17

Post by Peter Wolniewicz » Thu Jan 26, 2017 3:10 pm

Jaakko Leppänen wrote:The geometry doesn't have to be, but the material names must match. In any case you shouldn't get a segfault. Could you try running the calculation in debug mode?
To run it in debug mode, do I uncomment the debug flag in the Makefile:
#CFLAGS += -DDEBUG
make clean
make all

and then just run the executable as usual i.e,
sss2 input file

Thanks

Peter Wolniewicz
Posts: 135
Joined: Mon Dec 13, 2010 5:50 pm

Re: Restart feature in 2.1.17

Post by Peter Wolniewicz » Thu Jan 26, 2017 3:14 pm

I compiled it in debug mode and I got the same result in terminal:

SUMMARY -- 91 nuclides included in calculation:

- 91 elements with photon interaction data
- Photon energy cut-offs at 1.00E-03 and 100.0 MeV
- 364 transport reactions
- 91 special reactions
- 95.13 Mb of memory allocated for data

Normalizing compositions and processing mixtures...
OK.

Allocating memory for macroscopic cross section data...
OK.

Reading material compositions from restart file...
Segmentation fault (core dumped)

User avatar
Jaakko Leppänen
Site Admin
Posts: 2380
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 » Mon Jan 30, 2017 11:11 am

Which code version are you using?
- Jaakko

Peter Wolniewicz
Posts: 135
Joined: Mon Dec 13, 2010 5:50 pm

Re: Restart feature in 2.1.17

Post by Peter Wolniewicz » Mon Jan 30, 2017 11:24 am

Jaakko Leppänen wrote:Which code version are you using?
Jaakko:

2.1.26

User avatar
Jaakko Leppänen
Site Admin
Posts: 2380
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 » Mon Jan 30, 2017 11:27 am

2.1.27 fixed some problems related to restart files. Could you try with the latest update?
- Jaakko

Peter Wolniewicz
Posts: 135
Joined: Mon Dec 13, 2010 5:50 pm

Re: Restart feature in 2.1.17

Post by Peter Wolniewicz » Mon Jan 30, 2017 3:43 pm

Jaakko Leppänen wrote:2.1.27 fixed some problems related to restart files. Could you try with the latest update?
This fixed my issues!
Thanks

Post Reply