FLUKA zones maximum

Geometry and Materials
1

Hi,

What is the maximum number of zones per region ?

Best wishes,
Marco

2

Here is my input files – the maximum zones are 130 in region T_block

Also what is this symbol (indicated)

Thank you !

arie.inp (1.4 MB)

arie.flair (4.3 KB)

symbol_fluka
symbol_fluka878×155 36.4 KB

4

Hi Marco,

Typically, the hard limit on the geometry side concerns the number of regions. There is no strict limit on the number of zones, provided they fit in memory.

The symbol you mention is simply a newline character (as can be seen directly in the .inp input file).

Allow me to make a few comments:

  1. Your geometry contains some deprecated bodies (e.g. BOX). I understand that your strategy was to decompose them and use infinite bodies to build up the geometry. If you choose to follow this approach, you should at least comment out the BOX body. A more stable alternative would be to use ROT-DEFI and transformations.
  2. In the MATERIAL definitions, you do not leave WHAT(2) (Am) empty for all cards. This is incorrect and will not work.
  3. You can use the flair :rocket:Optimize button to optimize your regions. When I tried doing so, I noticed that some small errors are generated, but these can be easily corrected afterwards. This greatly simplifies the zone definitions.

Cheers,
Daniele

5

Hi Daniele,

Thanks for the comments! Indeed the strategy was as for 1) I also now exploded+optimised the wedges so that should not be a problem. As for the material….I think this is a new issue in Flair 3.4, I have not encountered this in 2.3

Best wishes,
Marco

6

Not really: this is a well intended measure taken from FLUKA-4.4.0 (released on February 2024) onward, as pointed out in the RELEASE-NOTES:

  • The (already discouraged) use of WHAT(2) in the MATERIAL card (material atomic weight) has been deprecated due to frequent inadvertent misuse as mass number. Should your inputs have this field filled, please clear it, or refer to the manual to intentionally overwrite default values.

Flair just warns you about the actual FLUKA expectation.

7

I still get a time-out when removing the WHAT(2), I attach my input as well as log and out files…what could be the issue?

monet001.out (6.1 MB)

monet001.log (471 Bytes)

monet.inp (1.4 MB)

monet.flair (2.3 MB)

8

oh I realised there were 2 cards with the same unit bin…maybe that’s why

9

Not at all. The .log indicates an issue with a COMPOUND card, which in turn is due to your U235 and U238 MATERIAL definitions, where you forgot to indicate the Z value. By the way, these come in addition to U_235 and U_238… Moreover, note that your Eu-151 and Eu-153 MATERIAL cards miss the A value (which is not the Am value to be removed!), hence each of them invokes natural isotopic composition.
After fixing the above, your input still does not run properly due to geometry issues.

12

A post was merged into an existing topic: Accuracy in Geobegin