empty Gauss points results issue

[kstn]

Hello

I have the empty Gauss point results field in the output file:

GaussPoints "hex_gauss_legendre_3_element_gp_PARTITION_INDEX" ElemType Hexahedra
Number Of Gauss Points: 27
Natural Coordinates: Given
-0.774597 -0.774597 -0.774597
0 -0.774597 -0.774597
0.774597 -0.774597 -0.774597
-0.774597 0 -0.774597
0 0 -0.774597
0.774597 0 -0.774597
-0.774597 0.774597 -0.774597
0 0.774597 -0.774597
0.774597 0.774597 -0.774597
-0.774597 -0.774597 0
0 -0.774597 0
0.774597 -0.774597 0
-0.774597 0 0
0 0 0
0.774597 0 0
-0.774597 0.774597 0
0 0.774597 0
0.774597 0.774597 0
-0.774597 -0.774597 0.774597
0 -0.774597 0.774597
0.774597 -0.774597 0.774597
-0.774597 0 0.774597
0 0 0.774597
0.774597 0 0.774597
-0.774597 0.774597 0.774597
0 0.774597 0.774597
0.774597 0.774597 0.774597
End GaussPoints
Result "PARTITION_INDEX" "Kratos" 99 Scalar OnGaussPoints "hex_gauss_legendre_3_element_gp_PARTITION_INDEX"
Values
End Values

GiD could read the file, but it generates the error "Couldn't assign GaussPoints 'hex_gauss_legendre_3_element_gp_PARTITION_INDEX' to mesh '__all__'", and subsequently, no Gauss point results from other variable can be read (in this case, STRESSES). It's possible to not write Gauss point table for empty results, but it will affect the logic of other results file. Is there a way to overcome this problem?

In the attachment is the file to reproduce the problem.

BR
Giang

[Michael70]

Hey there!

I'm getting exactly same results. Did you find any solution? I can't really come up with anything.

[miguel]

Hi Giang and Michael,
i've checked the example and i've found the problem:

in the mesh file 'Long_WHL_east_track_with_building_moved_geometry_system_model_99.0001.post.msh'
you've defined following meshes of hexaedra with coordinates but without elements, i.e. empty meshes:

Code: Select all

MESH "Kratos_Hexahedra3D27_Mesh_4" dimension 3 ElemType Hexahedra Nnode 27
Coordinates
316292 690.281 251.799 22.738
(... more coordinates)
End Coordinates
Elements
[color=#FF0000][b](empty !!!)[/b][/color]
End Elements

and

Code: Select all

MESH "Kratos_Hexahedra3D27_Mesh_5" dimension 3 ElemType Hexahedra Nnode 27
Elements
[color=#FF0000][b](empty !!!)[/b][/color]
End Elements

As there are no elements, no hexahedral meshes are created and no gauss points can be assigned to any meshes.

Looking into the results file i've seen that the definition of the gauss points are mixed with the definitions of the results.
When GiD reads the 'hex_gauss_legendre_3_element_gp_PARTITION_INDEX' Gauss points definition, issues an error and misinterprets what comes next in the file, as it tries to read a results defined on a gauss points set that has not been defined...
But previously lread results can be seen, like the DISPLACEMETNS and PARTITION INDEX.

Also some results definitions are empty, like the STRESSES for triangles and hexas. but not for the tetras but as it comes after the gauss point error, it's not read.

Attached you can find your mesh with 1 hexahedra ...

Best,

The GiD Team

[miguel]

The attached file ....

[kstn]

Dear Miguel

Thanks for looking into this problem. If I understand correctly, your solution to this problem is to create an element in the empty hexahedra mesh "Kratos_Hexahedra3D27_Mesh_4". That in general is doable but not natural since we have to search for some nodes and connect them to make an element. The reason this mesh is empty because it's a ghost mesh, i.e mesh containing ghost nodes for synchronization but contribute nothing to the physical boundary value problem. In fact, your solution can be problematic, if the newly created element is coincident with the other element of other process. Then with this, GiD will throw an error when we try to merge the mesh.

I have found a solution myself, by modifying the code I'm using. Basically if the mesh is empty (no elements) then no Gauss point table is printed in the result file. That worked. But it took a while to look in exactly where to modify. That is much better if GiD's already able to eliminate those from beginning. Thanks anyway for your solution.

Giang