Difference between revisions of "Gmsh"
From ONELAB
| Line 1: | Line 1: | ||
[http://geuz.org/getdp Gmsh] contains the ONELAB server, but is also a native ONELAB client for geometry, meshing and post-processing. | [http://geuz.org/getdp Gmsh] contains the ONELAB server, but is also a native ONELAB client for geometry, meshing and post-processing. | ||
| − | Any input file ('''.geo''', '''.pos''', scripts) read by Gmsh can be instrumented to interact with the ONELAB server. The syntax is | + | Any input file ('''.geo''', '''.pos''', scripts) read by Gmsh can be [[ONELAB_Syntax_for_Gmsh_and_GetDP|instrumented to interact with the ONELAB server]]. |
| + | |||
| + | The syntax is the same as the one used by [[GetDP]], which allows to write common parameter files for both Gmsh and GetDP. | ||
See for example [[Electric Machines]] to see how both codes can be seamlessly controlled without data duplication. | See for example [[Electric Machines]] to see how both codes can be seamlessly controlled without data duplication. | ||
Revision as of 10:12, 14 September 2013
Gmsh contains the ONELAB server, but is also a native ONELAB client for geometry, meshing and post-processing.
Any input file (.geo, .pos, scripts) read by Gmsh can be instrumented to interact with the ONELAB server.
The syntax is the same as the one used by GetDP, which allows to write common parameter files for both Gmsh and GetDP.
See for example Electric Machines to see how both codes can be seamlessly controlled without data duplication.
