Geometry Errors using two UMESH Cards

Versions

FLUKA: 4-5.2
Flair: 3.4-5.4
Operating system: Fedora Linux 44 (Workstation Edition) x86_64
Compiler: GNU Fortran (GCC) 16.1.1 20260515 (Red Hat 16.1.1-2)

Description

I wanted to import two different mesh geometries using the UMESH card. Testing them individually in a seperate “clean” new project showed to me that they work (simple beam onto the geometry).
But somehow when importing them together this fails and i get the following error:

 STOP TOO MANY ERRORS IN GEOMETRY
Note: The following floating-point exceptions are signalling: IEEE_UNDERFLOW_FLAG IEEE_DENORMAL
STOP STOP: FLUKA ABORTED

Looking in the .err file i can see that the error happens in my region number 11, which corresponds to the VOID region according to the .out file:

Region n.       11 VOID

Somehow I was not able to isolate the issue, I tried to remove geometry until the error no longer happens, but somehow even after i only had the vacuum left there was still the too many geometry errors error. I also tried the opposite, starting from clean basic input file and adding my things until i got the error, however then removing this same mesh again did then not fix the error, once i have the error in an input file I was not able to get rid of it … somehow it feels like a bug but i am not confident enough in using fluka and flair to be sure. The behaviour seems inconsistent.

If someone could look at my input files and point me in the right direction (or give some debugging steps) that would help me a greatly!

WCCD_STS.zip (3.0 MB)

EDIT:

after debugging a bit more I noticed that the error only happens once i add the .wccd mesh, so probably there is something with this geometry that is causing trouble.
The weird thing is that the error does not go away when I take out the mesh again … But I dont see how i could debug this?

The input file that no longer works even after removing the mesh:

WCCD_STS_TESTING.zip (3.0 MB)

Hi @lars.eggimann,

I was able to replicate this issue with your input.

Interestingly enough, it happens because of the missing blckbody region around

The navigator, in this case, suggests a very large step for VOID region and ends up in the undefined region

Please let me know if you have any other questions
Volodymyr

Hi @vorodin

First of all thank you very much for the quick and competent reply.

I am glad that you were able to identify the issue. Sadly I don’t quite understand what the problem exactly is and how to fix it?
I think I did define the blackbody around the whole geometry, but not correctly?

Thank you again for all your help!
Lars

Aah now I see! I had assigned aluminum to all the regions for debugging but did not reassing the blackbody to blackhole …
Incredibly stupid mistake I am sorry for wasting your time.

Again thanks for the help!

All the best,
Lars