Skip to content

Can't read .msh file in -M module #842

@kimauth

Description

@kimauth

Describe the bug

I get a segmentation fault when trying to read in a .msh file on my M1 Mac (macOS 14.4.1).
Neper version: tried both 4.8.2 and 4.5.0
gmsh --version: tried 4.11.1 and 4.13

To Reproduce
Minimum working example trying to read in a mesh that was produced by neper itself (msh format 2.2):

neper -T -dim 2 -n 3 -format tess
neper -M n3-id1.tess -dim 2 -format msh
$ neper -M n3-id1.tess,n3-id1.msh -dim 2 -format msh -o test_mesh_reading

========================    N   e   p   e   r    =======================
Info   : A software package for polycrystal generation and meshing.
Info   : Version 4.8.2
Info   : Built with: gsl|muparser|opengjk|openmp|nlopt|libscotch (full)
Info   : Running on 8 threads.
Info   : <https://neper.info>
Info   : Copyright (C) 2003-2022, and GNU GPL'd, by Romain Quey.
Info   : No initialization file found (`/Users/auth/.neperrc').
Info   : ---------------------------------------------------------------
Info   : MODULE  -M loaded with arguments:
Info   : [ini file] (none)
Info   : [com line] n3-id1.tess,n3-id1.msh -dim 2 -format msh -o
         test_mesh_reading
Info   : ---------------------------------------------------------------
Info   : Reading input data...
Info   :   - Reading arguments...
Info   : Loading input data...
Info   :   - Loading tessellation...
Info   :     [i] Parsing file `n3-id1.tess'...
Info   :     [i] Parsed file `n3-id1.tess'.
Info   :   - Loading mesh...
Info   :     [i] Parsing file `n3-id1.msh'...
Info   :     [i] Parsed file `n3-id1.msh'.
Info   :   - Reconstructing topology...
Info   : Meshing...
Info   :   - Preparing... zsh: segmentation fault  neper -M n3-id1.tess,n3-id1.msh -dim 2 -format msh -o test_mesh_reading

Context
Ultimately the goal is to generate a tessalation, manipulate the mesh in gmsh in order to obtain a mesh that is refined in the grain boundaries and then read the manipulated mesh back into neper in order to insert cohesive elements along the grain boundaries. This workflow used to work a few years ago, but unfortunately I don't know the software versions that I used then anymore.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions