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
c24e3ab6
Commit
c24e3ab6
authored
20 years ago
by
Christophe Geuzaine
Browse files
Options
Downloads
Patches
Plain Diff
add FAQ entry on multi-time-step views
parent
d96ad1ec
Branches
Branches containing commit
Tags
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/FAQ
+26
-1
26 additions, 1 deletion
doc/FAQ
with
26 additions
and
1 deletion
doc/FAQ
+
26
−
1
View file @
c24e3ab6
$Id: FAQ,v 1.5
5
2005-03-
12 22:25:2
4 geuzaine Exp $
$Id: FAQ,v 1.5
6
2005-03-
23 16:53:4
4 geuzaine Exp $
This is the Gmsh FAQ
This is the Gmsh FAQ
...
@@ -366,3 +366,28 @@ There can be several reasons:
...
@@ -366,3 +366,28 @@ There can be several reasons:
In any case, you can automatically remove all empty views with
In any case, you can automatically remove all empty views with
'View->Remove->Empty Views' in the GUI, or with "Delete Empty Views;"
'View->Remove->Empty Views' in the GUI, or with "Delete Empty Views;"
in a script.
in a script.
* 7.13 My code generates data "time step by time step", and thus
cannot easily output Gmsh's multi-time-step post-processing files,
where the values for all the time steps are given per element. How can
I use Gmsh's post-processor in this situation?
Just create one view for each time step: Gmsh can handle an arbitrary
number of views and it can deal with these separate views as
efficiently as with a single multi-time-step view. The only
disadvantage is that the total amount of disk space used is greater
(since the node data is repeated for each time step).
In practice, depending on the size of the data set, you may want to
store all the views in a single file or create one separate file for
each view, which you can then load selectively (and thus reduce the
memory required for the analysis). In any case you can use
'Tools->Options->Post-processing->View links' to apply options to
multiple views at once, and the up and down arrow keys to loop through
(animate) the views (instead of the left and right arrow keys for
multi-time-step views).
Also note that if all the views are based on the same grid, Gmsh can
combine the separate views into a multi-time-step view by using the
'View->Combine->Time Steps' menu, or by using the '-combine' command
line option.
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