Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
O
OpenFOAM-plus
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Model registry
Monitor
Incidents
Analyze
Value stream analytics
Contributor 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
This is an archived project. Repository and other project resources are read-only.
Show more breadcrumbs
Development
OpenFOAM-plus
Commits
1de9019d
Commit
1de9019d
authored
8 years ago
by
mattijs
Browse files
Options
Downloads
Patches
Plain Diff
ENH: controlDict: extended comment
parent
2238b3bf
No related branches found
No related tags found
1 merge request
!85
Pstream: added maxCommsSize setting to do (unstructured) parallel transfers in blocks.
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
etc/controlDict
+9
-0
9 additions, 0 deletions
etc/controlDict
with
9 additions
and
0 deletions
etc/controlDict
+
9
−
0
View file @
1de9019d
...
...
@@ -62,6 +62,15 @@ OptimisationSwitches
floatTransfer 0;
nProcsSimpleSum 0;
// Optional max size (bytes) for unstructured data exchanges. In some
// phases of OpenFOAM it can send over very large data chunks
// (e.g. in parallel load balancing) and some Pstream implementations have
// problems with this. Setting this variable > 0 indicates that the
// data exchange needs to be done in multiple passes, each of maxCommsSize.
// This is not switched on by default since it requires an additional
// global reduction, even if multi-pass is not needed)
maxCommsSize 0;
// Force dumping (at next timestep) upon signal (-1 to disable)
writeNowSignal -1; // 10;
...
...
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