From: Giuseppe Battistoni (Giuseppe.Battistoni@mi.infn.it)
Date: Wed Sep 26 2007 - 13:27:38 CEST
A) there is one clean way inside the source routine.
If there, subject to the conditions that you will impose, you
put NOMORE = 1 then FLUKA will make a clean end of run.
B) Sometimes, in other routines, I use a different way:
1) I include the common (CASLIM) which contains the number of running
event, NCASE, and the maximum number of requested events, NCASES.
2) whan I want to stop FLUKA I just put NCASE = NCASES.
In this way FLUKA understands that the required number of histories
has been processed and stops
On Wed, 26 Sep 2007, Vadim Talanov wrote:
> Dear FLUKA experts,
> sorry for a maybe naive question but - is there a recommended effective way to
> stop a FLUKA run during the execution of the program from within a USER
> subroutine? "Effective" means not just an execution of a STOP statement
> somewhere at some condition but rather some way to tell the program that it's
> time to stop calculations, collect statistics, write output files etc. and exit
> NORMALLY right now.
> One can presume that there may be several ways to accomplish this, and I am just
> wondering which one is recommended by the authors?
> Sorry once again if this case has been already covered somewhere,
> Kind regards, Vadim
This archive was generated by hypermail 2.1.6 : Wed Sep 26 2007 - 13:54:28 CEST