Hello. Recently (since March), Gmsh has incremented the version
number in its output msh files from 2.0 to 2.1. The motivation,
according to doc/VERSIONS.txt is `bumped mesh version format to 2.1
(small change in the $PhysicalNames section, where the group dimension
is now required)'. Since the PhysicalNames block is ignored by
GmshIO::read_mesh, I think it should be safe enough to accept version
2.1 msh files too, no other change to the libMesh code being required.
I attach a patch against current svn.
Without this patch, a workaround is to use the option
`Mesh.MshFileVersion=2.0' in the .geo input file for Gmsh, or to edit
the version number back to 2.0 in the .msh file manually.
Index: src/mesh/gmsh_io.C
===================================================================
--- src/mesh/gmsh_io.C (revision 3444)
+++ src/mesh/gmsh_io.C (working copy)
@@ -351,7 +351,10 @@
if (!std::strncmp(buf,"$MeshFormat",11))
{
in >> version >> format >> size;
- if(version != 2.0){
+ if(version != 2.0 &&
+ version != 2.1
+ )
+ {
std::cerr << "Error: Wrong msh file version " << version << "\n";
libmesh_error();
}
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Libmesh-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libmesh-users
