Hi, It’s been several days that i am stuck on this problem : “Reason: Error reading MeshValueCollection.” Please do you know how to fix it ? Context: i have just imported my .geo file on fenics (google colabs), then i used this program : !add-apt-repository -y ppa:fenics-packages/fenics !apt-g…

i found my mistake by chance :slight_smile:

I don’t know, but do you think it comes from the definition of my physical groups in the .geo file ? Physical Line(1) = {1} ; Physical Line(2) = {2} ; Physical Line(3) = {20} ; Physical Line(4) = {3} ; Physical Line(5) = {6} ; Physical Line(6) = {19} ; Physical Line(7) = {7} ; Physical Line(8) = {1…

Hi, 1 - You have to follow this procedure : [image] Transitioning from mesh.xml to mesh.xdmf, from dolfin-convert to meshio mesh @Iactor , the problem with your code is your mesh. It is not a connected mesh, and consists of several bits and pieces. In particular, you add …

Thank you so much! This worked finally. I uploaded my .msh file into the colab link, and everything went by smoothly, except a minor replacement of “gmsh:physical” with “gmsh:geometrical” (which looks like arising from version diffs).

Hi, You are talking about these lines ? cell_data = numpy.hstack([mesh.cell_data_dict["gmsh:physical"][key] for key in mesh.cell_data_dict["gmsh:physical"].keys() if key==cell_type]) You changed the both ´gmsh:physical’ ? Or which one did you changed ? The first or the se…

Yes, I changed both of them Is it though? It was throwing an error that “gmsh:physical” not found When I looked into the cell_data_dict, it was named “gmsh:geometrical”, so I changed it. Anyways, I think there might be some updates because of version diffs.

The keys in the cell_data_dict is dependent on how the gmsh mesh has been generated. It is normal to use Physical Line, Physical Surface, Physical Volume to mark domains in gmsh, and they will be found in gmsh:physical. If you do not use Physical Markers gmsh sometimes supplies geometrical markers, …

Hi @dokken , Did you find the solution to this error : Unable to find entity in map I saw many discussions, and one for example with @nschloe , that you had dealing with this issue but no solution on that topics…

In your gmsh model, you should add Physical tags, such as Physical Volume, Physical Surface, Physical Curve. With the GMSH python API, this is done with: gmsh.model.addPhysicalGroup as shown in for instance: Using the GMSH Python API to generate complex meshes | Jørgen S. Dokken Also, please post …

Please reduce your problem to the following: mesh generation script script for converting mesh to xdmf -script reading in the mesh and plotting it (no solving of a PDE required). Just call plot(mesh)

How to use MeshValueCollection?

mesh

visriv February 17, 2021, 7:07pm 4

Hi @rkenko,
I am facing the same error as you.

Can you please point out the mistake you realized?
Thanks in Advance.

Topic		Replies	Views
Unable to read the mesh with meshio mesh	3	1849	September 19, 2019
Read complex geometry using meshio mesh	13	4010	September 18, 2020
Problem with "meshvaluecollection.py" Errors	2	479	June 17, 2022
Meshvaluecollection Errors	0	199	June 17, 2022
What is wrong with my mesh? mesh	12	2028	February 18, 2023

How to use MeshValueCollection?

Related topics