Cluster Install Unable to run "-d" option (dpmjet executable)

Versions

FLUKA: 4-5.2
Flair: 3.4-5.4
Operating system: RHEL, Fedora 44
Compiler: gfortran --version: GNU Fortran (GCC) 16.1.1 20260515 (Red Hat 16.1.1-2)

Description

I am working with a sysadmin to build a containerized installation of fluka+flair. The programs function to some degree, but fail in specific scenarios.

After starting a new .flair project with the “basic” template, the run seems to proceed, but then the .err file says “abort called NO RANDOM FILE run stopped!” and FLUKADATA is not set. However, the fluka config appears to point to data properly…“fluka-config --data: /usr/local/fluka/data”.

Ok, so to work around that, I made a simlink to “data/random.dat” in “/usr/local/fluka/”, and that error goes away and it appears to run properly.

For my application, I need to run flukadpm. I have tried to run using flukadpm via command line and flair gui, but either method produces the error that -d is an “illegal option”. From what I can tell, -d is the standard option to run flukadpm ( FLUKA on the command line | The official CERN FLUKA website .m).


everything appears to be normal other than requiring the simlink to random.dat

Input files

Standard “basic” template input

test.inp (944 Bytes)

test.flair (1.5 KB)

Dear Trevor,

Could you show the content of the /usr/local/fluka/Version.tag and the test001.out files, please? Thanks!

One thing, please avoid running simulations in the directory where FLUKA is installed.

Cheers,
David

Dear @tolsen

you have a mixup of versions. You are using an rfluka script from an obsolete version and not the one from the official fluka version.

Thank you for your response. The sysadmin ran a test in the fluka directory after setup, but my tests are running from a sub-directory out of /home/fluka/.

The Version.tag shows the most up-to-date version, 4-5.2.
I have also attached the test001.out file after re-running it.

test001.out (102.0 KB)

Dear Trevor,

Thank you for uploading the files. These are coming from the container, right? Could you check, if the host has also FLUKA installed? Maybe somehow it leaks into the container.

If you like, you could upload the build file for the container so I could try to reproduce the problem.

Cheers,
David