Data dump every n cycle

New ideas for code development
Post Reply
Peter Wolniewicz
Posts: 135
Joined: Mon Dec 13, 2010 5:50 pm

Data dump every n cycle

Post by Peter Wolniewicz » Fri Dec 31, 2010 3:53 pm

Hi! In mcnp you can dump the results from every "n" cycle iteration to the output file. This is convenient if one wants to check error propagation or result oscillations versus simulation time. I think the command in mcnp is PRDMP... Maybe this feature could be included?


cheers

Peter

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

Re: Data dump every n cycle

Post by Jaakko Leppänen » Fri Dec 31, 2010 4:08 pm

Actually, Serpent does this every 50 cycles. The number is currently fixed, but I can add it as user variable in the next update.
- Jaakko

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

Re: Data dump every n cycle

Post by Andy_Turner » Mon Apr 25, 2016 10:04 am

Did this ever happen? This would be useful.

Does it collect detector data from all MPI tasks every 50 cycles?
This would explain why there is more penalty for small batches when using large mesh detectors.
- Andy Turner, CCFE

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

Re: Data dump every n cycle

Post by Jaakko Leppänen » Wed Apr 27, 2016 7:03 pm

There is parameter "set outp" that sets the printing interval. The parameter controls only when the output routines are called. Data from MPI tasks is always collected at the end of the transport simulation.
- Jaakko

Post Reply