Re: abort call from fluka.

From: Giuseppe Battistoni <>
Date: Sat, 24 Apr 2010 20:26:21 +0200 (CEST)

it's not impossible that you have found a real bug, but in order to
verify in an easier way what is really happening, could you please send as
attachment another file?

We need the random seed written by FLUKA soon before the crash.
You find it in the temporary directory created by the crashed run
and is linked to fort.2
If your run crashed at the 3rd cycle that implies the existance of
an initial seed called ran**003 and in the temporary directory
 the seed we need is called ran**004

Starting a run using this seed allows to reproduce the error condition
at most within 5 min. of CPU plus initialization.

In case it's not available, ran**003 is better than nothing.

Thank you
        Giuseppe Battistoni

On Fri, 23 Apr 2010 wrote:

> Dear all,
> This has reference to my previous mail.
> There I have attached my input file as well as the .out, .err and .log file for
> the crashed cycle. As due to some trouble, only the input file is readable,
> I am attaching the line from the out file, where it calls for abort.
> The line goes like this
> "Abort called from HHFLEV reason STOP:HHFLEV-HADRIV Run stopped! STOP STOP:HHFLEV-HADRIV".
> It ran for the first two cycles without trouble, but from 3rd cycle onwards,
> it crashed. Even restarting this is of no use.
> Any help in this matter will be highly appreciated.
> With Regards,
> S. Chatterjee
> Scientific Officer,
> TLD Unit, BARC
> Variable Energy Cyclotron Centre,
> 1/AF, Bidhannagar,Kolkata-64
> Off:+91-33-23184207
> Fax:+91-33-23346871
Received on Sat Apr 24 2010 - 21:11:31 CEST

This archive was generated by hypermail 2.2.0 : Sat Apr 24 2010 - 21:11:31 CEST