Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
gmsh
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Larry Price
gmsh
Commits
2bbe5a0c
Commit
2bbe5a0c
authored
24 years ago
by
Christophe Geuzaine
Browse files
Options
Downloads
Patches
Plain Diff
*** empty log message ***
parent
8d0332ea
No related branches found
No related tags found
No related merge requests found
Changes
3
Show whitespace changes
Inline
Side-by-side
Showing
3 changed files
Parser/Gmsh.y
+4
-4
4 additions, 4 deletions
Parser/Gmsh.y
Unix/CbOptions.cpp
+2
-1
2 additions, 1 deletion
Unix/CbOptions.cpp
demos/FORMATS
+29
-6
29 additions, 6 deletions
demos/FORMATS
with
35 additions
and
11 deletions
Parser/Gmsh.y
+
4
−
4
View file @
2bbe5a0c
%{ /* $Id: Gmsh.y,v 1.1
1
2000-12-04
09:51:51
geuzaine Exp $ */
%{ /* $Id: Gmsh.y,v 1.1
2
2000-12-04
11:28:33
geuzaine Exp $ */
#include <stdarg.h>
...
...
@@ -1305,9 +1305,9 @@ Coherence :
}
;
/* -------------
C O L
O
R
S
------------- */
/* -------------
--
O P T I
O
N
S
-------------
--
*/
Options :
tColor '{' ColorSections '}'
...
...
This diff is collapsed.
Click to expand it.
Unix/CbOptions.cpp
+
2
−
1
View file @
2bbe5a0c
/* $Id: CbOptions.cpp,v 1.
7
2000-1
1-26 15:43:48
geuzaine Exp $ */
/* $Id: CbOptions.cpp,v 1.
8
2000-1
2-04 11:28:37
geuzaine Exp $ */
#include
"Gmsh.h"
#include
"GmshUI.h"
...
...
@@ -107,6 +107,7 @@ void OptionsCb (Widget w, XtPointer client_data, XtPointer call_data){
CTX
.
r
[
0
],
CTX
.
r
[
1
],
CTX
.
r
[
2
],
CTX
.
t
[
0
],
CTX
.
t
[
1
],
CTX
.
t
[
2
],
CTX
.
s
[
0
],
CTX
.
s
[
1
],
CTX
.
s
[
2
]);
PrintContext
(
&
CTX
,
stderr
);
break
;
/* print */
...
...
This diff is collapsed.
Click to expand it.
demos/FORMATS
+
29
−
6
View file @
2bbe5a0c
...
...
@@ -38,7 +38,7 @@ Gmsh Mesh File Format
Gmsh Ascii Post-Processing File Format
======================================
A
ny
post-processing file is divided in several sections: one
A post-processing file is divided in several sections: one
format section (enclosed between $PostFormat/$EndPostFormat) and
(possibly multiple) post-processing views (enclosed between
$View/$EndView pairs).
...
...
@@ -83,10 +83,27 @@ Gmsh Ascii Post-Processing File Format
scalar points, vector points, tensor points, scalar lines, vector lines,
tensor lines, scalar triangles, vector triangles, tensor triangles,
scalar tetrahedra, vector tetrahedra and tensor tetrahedra.
- 'SP-values' is a list of double precision numbers:
the three first represent the corrdinates of the point
the 'nb-time-step' following
Gmsh Binary Post-Processing File Format
=======================================
The binary post-processing file format is the same as the ascii file format,
except that:
- the format field is the following
$PostFormat
version-number 1
$EndPostFormat
- all double precision vectors ('time-step-values', 'SP-values', 'VP-values', etc.)
are written in binary format
- AND there is an additional integer written before the 'time-step-values', and
which contains the value '1'. This integer serves as a test for little/big endian
detection.
Here is an example, of C code to write the binary format:
int one=1;
fprintf(file, "$View /* %s */\n", name);
...
...
@@ -96,17 +113,23 @@ Gmsh Binary Post-Processing File Format
fwrite(&One, sizeof(int), 1, PostStream);
Parsed View Format
==================
Gmsh Parsed Post-Processing Format
==================================
For testing purposes (or with very small data sets), there is an additional,
post-processing format which is parsed by the same grammar analyser as the
geometry. You can thus for example embed small post-processing views into your
geometrical descriptions.
View "name" {
type
of
element (list
of
coordinates) {list
of
values} ;
type
_
of
_
element (list
_
of
_
coordinates) {list
_
of
_
values} ;
...
}
12 base objects can be displayed:
type
of
element list
of
coordinates list
of
values
type
_
of
_
element list
_
of
_
coordinates list
_
of
_
values
--------------------------------------------------------------------------------
scalar point SP 3 1 * nb time steps
vector point VP 3 3 * nb time steps
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment