Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
pugs
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
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
code
pugs
Commits
d724e88d
Commit
d724e88d
authored
2 years ago
by
Stéphane Del Pino
Browse files
Options
Downloads
Patches
Plain Diff
Update documentation to deal with item_array and sub_item_array
parent
e7129c30
No related branches found
No related tags found
1 merge request
!166
Feature/item array in pgs
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/userdoc.org
+18
-15
18 additions, 15 deletions
doc/userdoc.org
with
18 additions
and
15 deletions
doc/userdoc.org
+
18
−
15
View file @
d724e88d
...
...
@@ -2831,32 +2831,35 @@ The information produced concerns
This type is used to designate kinds of items (cell, face, edge or node).
***** ~item_value~
***** ~item_value~
and ~item_array~
The type ~item_value~ is an abstract type use to designate arrays of
values defined on the entities of a ~mesh~. Actually, these values are
not associated to the mesh itself but to the *connectivity*. The values
on the entities can be of type ~B~, ~N~, ~Z~, ~R~, ~R^1~, ~R^2~, ~R^3~, ~R^1x1~, ~R^2x2~
and ~R^3x3~. Entities themselves can be cells, faces, edges or nodes.
The types ~item_value~ and ~item_array~ are abstract types use to
designate values or arrays of values defined on each entities of a
~mesh~. Actually, these set of values (or arrays) are not associated to
the mesh itself but to the *connectivity*. The values on the entities
can be of type ~B~, ~N~, ~Z~, ~R~, ~R^1~, ~R^2~, ~R^3~, ~R^1x1~, ~R^2x2~ and
~R^3x3~. Entities themselves can be cells, faces, edges or nodes.
These variables are used to pass data from one function to another.
#+BEGIN_warning
By now, no mathematical operation is defined on ~item_value~ variables.
By now, no mathematical operation is defined on ~item_value~ or
~item_array~ variables.
#+END_warning
Moreover, ~item_value~ variables can be post processed. Observe that
edge or face values cannot be post processed since neither ~VTK~ nor
~Gnuplot~ can handle these data.
~Gnuplot~ can handle these data. Also ~item_raray~ can only be post
processed if array per item contain scalar data ( ~B~, ~N~, ~Z~, ~R~).
***** ~sub_item_value~
***** ~sub_item_value~
and ~sub_item_arrays~
Th
is
abstract type handles values defined on the sub items
of the
items of a ~mesh~. Similarly these
values are attached to a *connectivity*
and not to a mesh. The values associated to
the sub items can be of
type ~B~, ~N~, ~Z~, ~R~, ~R^1~, ~R^2~, ~R^3~, ~R^1x1~, ~R^2x2~
or ~R^3x3~. An example of
~sub_item_value~ is the $\mathbf{C}_{jr}$ vectors
which are defined at each
node of each cell.
Th
ese
abstract type handles values
or arrays
defined on the sub items
of the
items of a ~mesh~. Similarly these
sets of values or arrays are
attached to a *connectivity*
and not to a mesh. The values associated to
the sub items can be of
type ~B~, ~N~, ~Z~, ~R~, ~R^1~, ~R^2~, ~R^3~, ~R^1x1~, ~R^2x2~
or ~R^3x3~. An example of
~sub_item_value~ is the $\mathbf{C}_{jr}$ vectors
which are defined at each
node of each cell.
These variables are used to pass data from one function to
another. They cannot be post processed.
...
...
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