Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • gmsh gmsh
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 395
    • Issues 395
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 5
    • Merge requests 5
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Model experiments
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gmshgmsh
  • gmshgmsh
  • Issues
  • #1157

Inconsistent MSH format spec

Dear Gmsh developers,

I am the author of MshIO, a stand alone IO library supporting MSH file format in both ASCII and binary, for both version 2.2 and version 4.1. I noticed an inconsistency in the format spec for binary 4.1 on how node/element data are stored. See my original finding here.

In short, the spec stated elementTag and nodeTag is of type size_t, i.e. 8 bytes on my macbook. However, Gmsh 4.7.1 seems to expect int32_t, i.e. 4 bytes, based on trial and error. I appreciate any clarification on how to handle this issue.

best, Qingnan (James) Zhou

Assignee
Assign to
Time tracking