# Accuracy in Geobegin

**URL:** <https://fluka-forum.web.cern.ch/t/accuracy-in-geobegin/8179>\
**Category:** Geometry and Materials\
**Created:** [19 February 2026 23:07 UTC](https://fluka-forum.web.cern.ch/t/accuracy-in-geobegin/8179 "2026-02-19T23:07:16Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![mhartmann](https://fluka-forum.web.cern.ch/letter_avatar_proxy/v4/letter/m/b5e925/32.png) [@mhartmann](https://fluka-forum.web.cern.ch/u/mhartmann)\
**Post date:** [17 February 2026 20:49 UTC](https://fluka-forum.web.cern.ch/t/accuracy-in-geobegin/8179/1 "2026-02-17T20:49:13Z")

</div>

Sorry to disturb but even after fixing these the error persists, I attach the out file and err file. It is basically saying there is a small error (which I cannot see neither in the geoviewer nor elsewhere)…but it aborts when there are multiple calls for the same error. Is there any way to run this and avoid such issues? I attach the input. If I try to optimise all regions the location of the offending plane/point changes but then the run still stops after completing 5 cycles. I have also tried copying the x y z of one plane into the nearest one without success…

Sometimes by zooming in maybe 100 times, a white region is found which I think is just an artifact from the small scale. Is there any point of increasing the accuracy parameter?

[monet.inp](https://fluka-forum.web.cern.ch/uploads/short-url/fLHjSuZTAir1lyxWeZQjLloZbSM.inp) (1.4 MB)

[monet.flair](https://fluka-forum.web.cern.ch/uploads/short-url/vwmpJbfqu84uSMissk13bu9llua.flair) (2.3 MB)

[monet004.err](https://fluka-forum.web.cern.ch/uploads/short-url/47dlrumIQpiBnUE2NPdsxJlOGKQ.err) (570.4 KB)

it completes 5 cycles and then finishes with errors

EDIT: It runs by setting accuracy to 0.01..Does this sound reasonable ?

 ![msrdc_mHFXhxNpxH](https://fluka-forum.web.cern.ch/uploads/default/original/2X/7/7e1ae59a1ada07ba25a4dbf96d40593447cd2892.png)

---

<div class="post-metadata">

**Author:** ![mhartmann](https://fluka-forum.web.cern.ch/letter_avatar_proxy/v4/letter/m/b5e925/32.png) [@mhartmann](https://fluka-forum.web.cern.ch/u/mhartmann)\
**Post date:** [19 February 2026 23:07 UTC](https://fluka-forum.web.cern.ch/t/accuracy-in-geobegin/8179/2 "2026-02-19T23:07:17Z")

</div>

Hi everyone!

I attach a post related to another question on forum. See log and err files. They are basically saying there is a small error (which I cannot see neither in the geoviewer nor elsewhere)…but it aborts when there are multiple calls for the same error. Is there any way to run this and avoid such issues? I attach the input. If I try to optimise all regions the location of the offending plane/point changes but then the run still stops after completing 5 cycles. I have also tried copying the x y z of one plane into the nearest one without success…

Sometimes by zooming in maybe 100 times, a white region is found which I think is just an artifact from the small scale. Is there any point of increasing the accuracy parameter?

[monet.inp](https://fluka-forum.web.cern.ch/uploads/short-url/fLHjSuZTAir1lyxWeZQjLloZbSM.inp) (1.4 MB)

[monet.flair](https://fluka-forum.web.cern.ch/uploads/short-url/vwmpJbfqu84uSMissk13bu9llua.flair) (2.3 MB)

[monet004.err](https://fluka-forum.web.cern.ch/uploads/short-url/47dlrumIQpiBnUE2NPdsxJlOGKQ.err) (570.4 KB)

it completes 5 cycles and then finishes with errors

EDIT: It runs by setting accuracy to 0.01..Does this sound reasonable ?

---

<div class="post-metadata">

**Author:** ![dcalzola](https://fluka-forum.web.cern.ch/letter_avatar_proxy/v4/letter/d/b782af/32.png) [@dcalzola](https://fluka-forum.web.cern.ch/u/dcalzola)\
**Post date:** [21 February 2026 12:56 UTC](https://fluka-forum.web.cern.ch/t/accuracy-in-geobegin/8179/4 "2026-02-21T12:56:56Z")

</div>

Hi Marco,

Increasing the accuracy parameter is only a temporary fix that masks the underlying issue. As previously discussed in other threads, this approach can become problematic, especially in the case of detailed geometries: [Geometry Errors with Lattices - #2](https://fluka-forum.web.cern.ch/t/geometry-errors-with-lattices/4479/2)

In your `.err` file, you can identify where most particles are encountering problems. I would recommend starting the debugging process from there.

Another possible source of issues could be touching bodies (e.g., coincident planes), although a definitive answer cannot be provided a priori. Occasionally, some spurious geometry precision errors may appear, but the code is able to recover from them.

Good luck with your geometry!  
Cheers,  
Daniele.

---

<div class="post-metadata">

**Author:** ![mhartmann](https://fluka-forum.web.cern.ch/letter_avatar_proxy/v4/letter/m/b5e925/32.png) [@mhartmann](https://fluka-forum.web.cern.ch/u/mhartmann)\
**Post date:** [23 February 2026 01:19 UTC](https://fluka-forum.web.cern.ch/t/accuracy-in-geobegin/8179/6 "2026-02-23T01:19:44Z")

</div>

Hi Daniele,

Thanks! I believe I’ve solved it by setting the NY of several PLA to 0 instead of 1E-17 and by coinciding several planes. It can run on both Flair3.4/Fluka4.5.1 and on Flair2.3/Fluka2025.1. However on a cluster it still fails with segmentation fault (“Seed file not accepted: or corrupted…” and “2 Segmentation fault (core dumped) ${EXE} 2\> $LOGF \> $LOGF fluka run”).

I attach my final input if ever you want to check. Thanks!

[monet1.inp](https://fluka-forum.web.cern.ch/uploads/short-url/oCj7K1byajaXLPqxR3xarvNdHOD.inp) (1.2 MB)

[monet1.flair](https://fluka-forum.web.cern.ch/uploads/short-url/4LZ0g1D4FUs8xUmtOIwavcPNNnn.flair) (2.2 MB)

Best wishes,  
Marco

---

<div class="post-metadata">

**Author:** ![dcalzola](https://fluka-forum.web.cern.ch/letter_avatar_proxy/v4/letter/d/b782af/32.png) [@dcalzola](https://fluka-forum.web.cern.ch/u/dcalzola)\
**Post date:** [27 February 2026 13:18 UTC](https://fluka-forum.web.cern.ch/t/accuracy-in-geobegin/8179/7 "2026-02-27T13:18:14Z")

</div>

Hello Marco,

I am working in parallel to your new question ([Geometry failure without patent user errors](https://fluka-forum.web.cern.ch/t/geometry-failure-without-patent-user-errors/8190)), so I do not know how much updated is this geometry.

Unfortunately I am not able to reproduce your error. Possibly the answer is in the logfile, or in the configuration of your cluster. If you are unable to fix this issue, please open a new thread with all the relevant files.

Cheers,  
Daniele

---

<div class="post-metadata">

**Author:** ![mhartmann](https://fluka-forum.web.cern.ch/letter_avatar_proxy/v4/letter/m/b5e925/32.png) [@mhartmann](https://fluka-forum.web.cern.ch/u/mhartmann)\
**Post date:** [27 February 2026 19:28 UTC](https://fluka-forum.web.cern.ch/t/accuracy-in-geobegin/8179/8 "2026-02-27T19:28:47Z")

</div>

Hi Daniele,

Thanks for your reply! I’ll make a new thread then – I’ll add the log+input files too!

Best wishes,  
Marco

---

<div class="post-metadata">

**Author:** ![horvathd](https://fluka-forum.web.cern.ch/user_avatar/fluka-forum.web.cern.ch/horvathd/32/10584_2.png) [@horvathd](https://fluka-forum.web.cern.ch/u/horvathd)\
**Post date:** [13 March 2026 09:10 UTC](https://fluka-forum.web.cern.ch/t/accuracy-in-geobegin/8179/9 "2026-03-13T09:10:32Z")

</div>


