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
ff998ea8
Commit
ff998ea8
authored
1 month ago
by
Stéphane Del Pino
Browse files
Options
Downloads
Patches
Plain Diff
Add user doc for load_balance:mesh -> mesh
parent
ddb2af50
No related branches found
Branches containing commit
No related tags found
1 merge request
!204
Remove m_cell_global_index from Connectivity
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/userdoc.org
+24
-0
24 additions, 0 deletions
doc/userdoc.org
with
24 additions
and
0 deletions
doc/userdoc.org
+
24
−
0
View file @
ff998ea8
...
...
@@ -3431,6 +3431,30 @@ In this example, we set three arrays defined at all nodes, all the
- ~face_values~ interpolates ~f~ at the centers of the faces of ~m~,
- ~cell_values~ interpolates ~f~ at the centers of the cells of ~m~.
***** ~load_balance:mesh -> mesh~
Creates a new partition of a mesh in parallel (~MPI~).
#+BEGIN_SRC pugs :exports both :results none
import mesh;
let m1:mesh, m1 = cartesianMesh([0,0], [1,1], (10,10));
let m2:mesh, m2 = load_balance(m1);
#+END_SRC
In this example the mesh ~m2~ is a new parallel partition of the mesh
~m1~. This implies that the two meshes, while being identical from the
mathematical point of view, are now different (and are not defined on
a same connectivity: the connectivity is actually balanced).
Discrete functions defined on ~m1~ are *not* implicitly transferred on the
mesh ~m2~! The function ~load_balance:(Vh)->(Vh)~ must be used to perform
mesh and data load balancing.
#+BEGIN_note
To simplify development of large calculations. A sequential call of
this function has the same effect: the mesh and its connectivity are
copied!
#+END_note
***** ~transform: mesh*function -> mesh~
This function allows to compute a new mesh as the transformation of a
...
...
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