Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug for Ensight format import #82

Closed
YohannEude opened this issue May 14, 2021 · 1 comment
Closed

Bug for Ensight format import #82

YohannEude opened this issue May 14, 2021 · 1 comment

Comments

@YohannEude
Copy link
Contributor

Hi,

I currently try to use an Ensight mesh with CS 7.1 alpha (from 15 Apr) and I have some problem to keep the groups.
So, I did the following tests to try to understand if the problem comes from my mesh (OpenFOAM one) :

  • I created a box with 3 groups and I meshed it in salome

  • I exported the mesh with the med format

  • I did a prepro (from the med mesh) in CS and export the result in Ensight (the MESH_GROUP.case has well all the groups inside)
    Then,

  • I used the previous MESH_GROUP.case as an input mesh in CS and redo the prepro and CS forget the groups.
    I have the following error message:

    Remark: no vertex ids given
    --> impossible to merge EnSight "parts",
    so the following "parts" are ignored.

So it seems there is a problem with the Ensight format to load a mesh because the MESH_GROUP.case has everything (vol and groups). Do you have any idea?

Thank you for your help,

Cheers,

Yohann

@YvanFournier
Copy link
Contributor

Hello,

Yes, we can only import mesh groups with the EnSight format when global vertex ids are given. Which is not the case when sub-meshes are exported by code_saturne, due to the way postprocessing is handled. Without those ids, we cannot compare faces in different parts, so cannot import groups (a geometrical option would be posssible but risky in case of thins walls).

The EnSight format is actually designed for post-processing, not mesh input. So the logic for importing groups is a "bonus" using a code_saturne-specific logic, but does not handle all cases.

So to check groups with an OpenFoam mesh, another solution is needed. I would recommend first trying to visualize it under SALOME. The probable cause of the issue is the faces with groups do not use the same vertex ids and are thus "isolated faces". The run_solver.log file should warn you about this and the "mesh check mode" of code_saturne places those faces in a separate EnSight part.

If this is the case, you can try to merge vertices under SALOME. Another last-resort option is to use and adapt the user-defined function example from cs_user_mesh-groups_from_free_faces.c, which will use mesh location and interpolation to project the groups from isolated faces on the actual mesh faces.

If this is not the case, check if the group names appear in the preprocessor.log or are already lost at that stage.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants