# \[Ann\] GmshImport package: GMSH 4.1 file parser

**URL:** <https://discourse.julialang.org/t/ann-gmshimport-package-gmsh-4-1-file-parser/98819>\
**Category:** General Usage\
**Created:** [May 14, 2023, 1:18am UTC](https://discourse.julialang.org/t/ann-gmshimport-package-gmsh-4-1-file-parser/98819 "2023-05-14T01:18:12Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![PetrKryslUCSD](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/petrkryslucsd/32/215825_2.png) [@PetrKryslUCSD](https://discourse.julialang.org/u/PetrKryslUCSD)\
**Post date:** [May 14, 2023, 1:18am UTC](https://discourse.julialang.org/t/ann-gmshimport-package-gmsh-4-1-file-parser/98819/1 "2023-05-14T01:18:12Z")

</div>

Import `.msh` files in the Gmsh 4.1 format. Capability: import node and element blocks.  
Limitation: The element types are limited at the moment to the most common ones.

The imported data are not specific to any particular solver, and it should be easy to use it as you see fit.

---

<div class="post-metadata">

**Author:** ![oheil](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/oheil/32/220745_2.png) [@oheil](https://discourse.julialang.org/u/oheil)\
**Post date:** [May 14, 2023, 8:48am UTC](https://discourse.julialang.org/t/ann-gmshimport-package-gmsh-4-1-file-parser/98819/2 "2023-05-14T08:48:22Z")

</div>

In the spirit of the ongoing discussion here

> [@Fixing Package Fragmentation](https://discourse.julialang.org/t/fixing-package-fragmentation/98712):
>
> Taken from a Slack discussion: I’ve had colleagues comment that fragmentation is currently the only really bad thing of the Julia ecosystem. They miss the numpy/scipy monolithic approach. Now for most package ecosystems the bus factor probably follows some kind of power law, but the vibe I get with Julia is that the relationship between bus factor and popularity (and package complexity, cf. NPM micro-packages) is a lot weaker I do think one actionable thing might be to more loudly mark c…

perhaps you are interested in

> **[JuliaIO](https://github.com/JuliaIO)**
>
> A collection of Julia packages for unified IO infrastructure - JuliaIO

and especially in

> **[GitHub - JuliaIO/FileIO.jl: Main Package for IO, loading all different kind...](https://github.com/JuliaIO/FileIO.jl)**
>
> Main Package for IO, loading all different kind of files - GitHub - JuliaIO/FileIO.jl: Main Package for IO, loading all different kind of files

to register your new package (and maybe more) for FileIO.jl  
Just a hint, I don’t know if this suitable at all for you or for FileIO.jl but perhaps you want to check.

I see ideas like FileIO.jl as the natural (organic) solution to any fragmentation in the Julia ecosystem, despite that I don’t see any fragmentation problems, or better, I just don’t have a fragmentation problem with Julia. It’s just not a problem (for me). Ok, the other discussion…