AW: NO RANDOM FILE

Hi Lawrence,

it could be the case that the message "NO RANDOM FILE" is slightly
misleading. This is the reason why the program eventually aborted but it
might not be the primary reason. You should carefully check the .log
file (at the top!!!) and the .out at the end for additional error
messages. You might find a useful hint in the messages printed before
the final abort message which is related to the random number generator.
For example:

In addition to verify that the abort is not linked to a corrupted FLUKA
installation, which I actually would doubt, you can try to run the
example.inp file which is included in the FLUKA distribution. If this
file runs fine then it's a strong hint that the error is related to your
input file. As a general remark I would suggest to attach the respective
input files to your message sent to the discussion list. Otherwise it is
virtually impossible to give a more specific answer as there can be very
subtle errors in the input which might trigger sometimes misleading
abort messages. For example:
http://www.fluka.org/web_archive/earchive/new-fluka-discuss/0528.html

Cheers
Chris

________________________________

Von: Lawrence Mhatiwa [mailto:lawrencemhatiwa_at_hotmail.com]
Gesendet: Mo 16.03.2009 19:11
An: fluka-discuss_at_fluka.org; Chris Theis; Markus Brugger
Betreff: NO RANDOM FILE

Dear Fluka Users

I have a problem in working with copied files.eg if the original file is
called fluka1.inp and after copying it to another file say
fluka2.inp.The copied file(fluka2.inp) does not run though there is no
difference in the two file except the name and usrbin options.The error
file generated from running a copied input file has the following
message 'Abort called from FLRM64 reason NO RANDOM FILE run stop!' STOP
NO RANDOM FILE.

Meanwhile the first file(fluka1.inp) was running.Its obvious there is a
problem with Random number generation.
I wolud appreciate your help in solving this situation.
Lawrence
Received on Tue Mar 17 2009 - 14:12:45 CET