Hi Nick,
If you want to do without rfluka, go through the rfluka script line by line and
implement your replacement one by one. My recommendation is: please use rfluka,
whether on a GRID or not. I can't see any reason why you can't "use rfluka or
anything like that". I was running 5 different Monte Carlo codes on different
GRIDs over a decade ago. Today, the middleware technology is far more friendly
and many glitches have been ironed out.
There should be no problem specific to FLUKA. We follow the generic recipe, for
each job submitted:
- set all necessary environment variables, because the login by the middleware
is usually not the full shell login;
- make sure the executable matches the archi-OS of the executing node, put a
conditional in the job submission script;
- depending on the file system, transfer any necessary files: the executable,
the input file (or user macro file), plus all runtime data files.
The only glitches I can think of would be:
- missing libraries e.g. libxxxxx.so sort of thing, in which case either ask the
administrator of that particular cluster to get the libxxxxx.so available, or
put a conditional in the job submission script;
- the scheduler loses control of some jobs leaving the jobs hanging, unclean
exits etc, which has nothing to do with FLUKA, just a GRID thing.
:) mary
> On 18 January 2015 at 04:57 "Mikhail Polkovnikov <Михаил Полковников>"
> <pmk_at_ihep.ru> wrote:
>
>
> On 15.01.2015 14:38, Nickolay wrote:
> > I want to run my custom exe in GRID, so I can't use rfluka or anything
> > like that.
> >
> > BTW, does anyone know some information on this matter? Is it possible
> > at all (running FLUKA in GRID, I mean), given the fact, that FLUKA
> > relies on lots of auxillary files (those .bin file in $FLUPRO)?
> >
> > Thanks.
> >
> > On 14.01.2015 19:06, Alberto Fasso wrote:
> >> Why don't you want to run the rfluka script?
> >> Have a look at it, and you will see that it does much more than
> >> executing an *.exe file. Among many other necessary things, it
> >> creates the temporary directory where FLUKA is going to run, and
> >> makes sure that all the data files needed by FLUKA are available there.
> >> random.dat is just one of those files.
> >>
> >> Alberto
> >>
> >>
> >> On Wed, 14 Jan 2015, Nickolay wrote:
> >>
> >>> Hello,
> >>>
> >>> I need to run custom made executable (made using FLAIR). So I looked
> >>> into
> >>> rfluka script and, based on its contents, issued a command:
> >>>
> >>> example.exe < example.inp &> log.out
> >>>
> >>> As a result, my program stopped with the following error:
> >>>
> >>> ...
> >>>
> >>> ***** Next control card ***** RANDOMIZ 1.000 0.000 0.000
> >>> 0.000 0.000 0.000
> >>>
> >>> **** No Random file available !!!!!! ****
> >>> Abort called from FLRM64 reason NO RANDOM FILE Run stopped!
> >>> STOP NO RANDOM FILE
> >>>
> >>> I even copied random.dat from $FLUPRO into the directory where I try to
> >>> execute my program but it didn't help.
> >>>
> >>> Could anyone explain me how to run custom made FLUKA executables
> >>> manually?
> >>> (i.e. not using rfluka script)
> >>>
> >>> Thanks.
> >>>
> >>> Best regards,
> >>> Nick
> >>>
> >>>
> >
> > You can manage unsubscription from this mailing list at
> > https://www.fluka.org/fluka.php?id=acc_info
> Hi Nickolay,
>
> Here are links that could be useful.
> Don't sure about the actual state of these projects.
>
> 1. Dr. Niels Bassler's blog:
> http://willworkforscience.blogspot.ru/2012/01/quick-and-dirty-guide-for-parallelizing.html
> 2. AU FLUKA Tools:
> http://sourceforge.net/projects/auflukatools/?source=directory
>
>
> Best regards,
> Mikhail
>
> You can manage unsubscription from this mailing list at
> https://www.fluka.org/fluka.php?id=acc_info
>
You can manage unsubscription from this mailing list at
https://www.fluka.org/fluka.php?id=acc_info
Received on Tue Jan 20 2015 - 12:20:59 CET