# Graphical artefacts in 2D view using umesh card

**URL:** <https://fluka-forum.web.cern.ch/t/graphical-artefacts-in-2d-view-using-umesh-card/8396>\
**Category:** Geometry and Materials\
**Created:** [22 May 2026 12:53 UTC](https://fluka-forum.web.cern.ch/t/graphical-artefacts-in-2d-view-using-umesh-card/8396 "2026-05-22T12:53:51Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![lars.eggimann](https://fluka-forum.web.cern.ch/letter_avatar_proxy/v4/letter/l/fbc32d/32.png) [@lars.eggimann](https://fluka-forum.web.cern.ch/u/lars.eggimann)\
**Post date:** [22 May 2026 12:53 UTC](https://fluka-forum.web.cern.ch/t/graphical-artefacts-in-2d-view-using-umesh-card/8396/1 "2026-05-22T12:53:52Z")

</div>

### Versions

_FLUKA_: 4-5.2  
_Flair_: 3.4-5.3

### Description

Hello again, I have another question regarding the mesh import to flair:  
I import a CAD drawing via the UMESH card, using the new `FLUKA_mesh_fix.py` to convert and fix the geometry. The resulting geometry looks good in the 3D view, but the 2D views show some weirdness (artefacts) and I was wondering how to fix this or if this is even a problem. If I zoom in enough on the 2D view the artefacts vanish. I also checked the geometry with `gmsh` GUI and also there the geometry seems fine.

 ![image](https://fluka-forum.web.cern.ch/uploads/default/original/2X/5/5c1d9200a11a67a091073820b7e7b678aaf6c6ad.jpeg)

I tried different arguments for the converter script including `--occ` and `--fix` etc. but all of them show some form of aretfacting in the 2D views.

Maybe this is not a problem at all and just a visual glitch, I would like to verify nonetheless. Any help is greatly appreciated. 🙂

### Input files

[inputfiles\_and\_geometry.zip](https://fluka-forum.web.cern.ch/uploads/short-url/z4PRSbCv48qwf2IXAajgIZJtQSz.zip) (359.8 KB)

---

<div class="post-metadata">

**Author:** ![vorodin](https://fluka-forum.web.cern.ch/letter_avatar_proxy/v4/letter/v/848f3c/32.png) [@vorodin](https://fluka-forum.web.cern.ch/u/vorodin)\
**Post date:** [22 May 2026 14:47 UTC](https://fluka-forum.web.cern.ch/t/graphical-artefacts-in-2d-view-using-umesh-card/8396/2 "2026-05-22T14:47:08Z")

</div>

Hello,

It’s not really an issue, simply a way how Flair renders tetrahedrals bisect by section plane in viewport, sometimes because of limitation in numerical precision.

Actual artifacts will look like presence of tetrahedrals of material A inside region where material B is assigned.

Cheers,  
Volodymyr

---

<div class="post-metadata">

**Author:** ![lars.eggimann](https://fluka-forum.web.cern.ch/letter_avatar_proxy/v4/letter/l/fbc32d/32.png) [@lars.eggimann](https://fluka-forum.web.cern.ch/u/lars.eggimann)\
**Post date:** [22 May 2026 15:38 UTC](https://fluka-forum.web.cern.ch/t/graphical-artefacts-in-2d-view-using-umesh-card/8396/3 "2026-05-22T15:38:30Z")

</div>

Ah I see, so nothing to worry about! Thank you!

If you don’t mind, I have another similar question:  
I have a lot of `overlap ERROR` in my geom-viever, I assume it is due to the conversion from `.stp` to the `.abaq` file that I get some overlap between the individual parts. However when I run the simulation I get no errors. Is this something I can fix, maybe try other arguments for the conversion script?

 ![image](https://fluka-forum.web.cern.ch/uploads/default/original/2X/3/33d9765979b78286d3b1b561fe2525f428832d42.jpeg)

---

<div class="post-metadata">

**Author:** ![vorodin](https://fluka-forum.web.cern.ch/letter_avatar_proxy/v4/letter/v/848f3c/32.png) [@vorodin](https://fluka-forum.web.cern.ch/u/vorodin)\
**Post date:** [22 May 2026 16:18 UTC](https://fluka-forum.web.cern.ch/t/graphical-artefacts-in-2d-view-using-umesh-card/8396/4 "2026-05-22T16:18:55Z")

</div>

Yes, it might happen due to meshing closely located parts. Common tolerance value for overlaps in CAD and meshing tools is ~1e-6 since in reality it’s really hard to manufacture parts with precision \< 1 um. Instead, a tolerance requested by FLUKA is ~1e-8–1e-10.

There is an option in the script that may fix overlaps, but I deliberately disabled it since Gmsh algorithm was not very robust for complex geometries.

You would need to use a different meshing tool (Ansys/Cubit) to create a so called **shared topology** to generate **conformal mesh**.. But this will require much more time and fine-tuning meshing options in these programs.

These issues are usually tolerated by FLUKA, and introduce quite small uncertainty, few orders less than 1% (depends on mesh resolution).

---

<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:** [10 June 2026 06:35 UTC](https://fluka-forum.web.cern.ch/t/graphical-artefacts-in-2d-view-using-umesh-card/8396/5 "2026-06-10T06:35:08Z")

</div>


