why meshes generated by demos/api all wrong?
Hi all, The formats of meshes which are generated by demos/api, like view.py, t1.py... are wrong. For example, source code of view.py,
import gmsh
import sys
gmsh.initialize(sys.argv)
gmsh.option.setNumber("General.Terminal", 1)
# Copied from discrete.py...
gmsh.model.add("test");
gmsh.model.addDiscreteEntity(2, 1)
gmsh.model.mesh.addNodes(2, 1, [1, 2, 3, 4],
[0., 0., 0.,
1., 0., 0.,
1., 1., 0.,
0., 1., 0.])
gmsh.model.mesh.addElements(2, 1, [2], [[1, 2]],
[[1, 2, 3,
1, 3, 4]])
# ... end of copy
# Create a new post-processing view
t = gmsh.view.add("some data")
# add 10 steps of model-based data, on the nodes of the mesh
for step in range(0, 10):
gmsh.view.addModelData(t, step, "test", "NodeData",
[1, 2, 3, 4], # tags of nodes
[[10.],[10.],[12.+step],[13.+step]]) # data, per node
gmsh.view.write(t, "data.msh")
gmsh.finalize()
Gemerate .msh file: python view.py
Open .msh use gmsh: gmsh data.msh
Info : -------------------------------------------------------
Info : Gmsh version : 3.0.5
Info : Build OS : Linux
Info : Build options : Ann Bamg Bfgs Blas(Generic) Blossom C++11 Chaco DIntegration Dlopen Fltk Gmm > Jpeg(Fltk) Kbipack Lapack(Generic) LinuxJoystick MathEx Med Mesh Metis Mmg3d Mpeg Netgen ONELAB ONELABMetamodel OpenCASCADE OpenGL OptHom PETSc Parser Plugins Png(Fltk) Post SLEPc Solver Taucs TetGen/BR Tetgen1.5 Voro3D Zlib
Info : Build date : 20170906
Info : Build host : debian7
Info : Packager : geuzaine
Info : Executable : /home/fan/Softwares/gmsh-3.0.5-Linux/bin/gmsh
Info : Home directory : /home/fan/
Info : Launch date : Sun Jun 16 20:29:48 2019
Info : Command line : gmsh data.msh
Info : -------------------------------------------------------
Info : Reading 'data.msh'...
Info : 1 vertices
Info : 1 elements
Error : Unknown vertex 1 in element 2
Error : Error loading 'data.msh'
Info : Done reading 'data.msh'
Edited by fanyuanhong