# Pyfr import mesh with Ennova

**URL:** <https://pyfr.discourse.group/t/pyfr-import-mesh-with-ennova/235>\
**Category:** General\
**Created:** [29 March 2019 14:04 UTC](https://pyfr.discourse.group/t/pyfr-import-mesh-with-ennova/235 "2019-03-29T14:04:12Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Douglas\_Fontes](https://avatars.discourse-cdn.com/v4/letter/d/51bf81/32.png) [@Douglas\_Fontes](https://pyfr.discourse.group/u/Douglas_Fontes)\
**Post date:** [29 March 2019 14:04 UTC](https://pyfr.discourse.group/t/pyfr-import-mesh-with-ennova/235/1 "2019-03-29T14:04:12Z")

</div>

Hello,

I am trying to use Ennova software to generate meshes for PyFR. However, Ennova does not export gmsh mesh. So, I export the mesh to .vtk format, then I use gmsh to convert .vtk mesh to .msh mesh. Despite all these conversions, PyFR is not being able to read this .msh mesh. I am sending you the error and the .msh file. Please, could you help me?

Thank you in advance.

[PyFR.zip](https://pyfr.discourse.group/uploads/short-url/inaH898fPonJAhZfKBhJApJjgeF.zip) (1.38 MB)

---

<div class="post-metadata">

**Author:** ![nnunn](https://avatars.discourse-cdn.com/v4/letter/n/c89c15/32.png) [@nnunn](https://pyfr.discourse.group/u/nnunn)\
**Post date:** [2 April 2019 10:50 UTC](https://pyfr.discourse.group/t/pyfr-import-mesh-with-ennova/235/2 "2019-04-02T10:50:19Z")

</div>

Hi Douglas,

In the `$PhysicalNames` section of your test mesh, the “fluid” region has “ **physical entity number** ” = 3:

```auto
$PhysicalNames

4
2 0 "outlet/face"
2 1 "walls/face"
2 2 "inlet/face"
3 **3**" **fluid**"
$EndPhysicalNames

```

But in the $Elements section of the mesh (from line 88655), both the quad and hex elements are assigned a “ **physical entity number** ” = 0.

I think this means that in \_split\_fluid(), the fluid (hex) elements are getting grouped with the boundary (quad) faces.  
End result is that there are no fluid elements defined after the call to \_split\_fluid().  
Looks like the necessary element info is getting lost in translation?

Nigel
