Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
SWIFTsim
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Deploy
Releases
Model registry
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
GitLab community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
SWIFT
SWIFTsim
Commits
a9a55d00
Commit
a9a55d00
authored
Jan 25, 2019
by
Peter W. Draper
Browse files
Options
Downloads
Patches
Plain Diff
Fix spelling
parent
f3a3cea2
No related branches found
No related tags found
1 merge request
!707
Repart by CPU ticks with optional fixed costs
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/RTD/source/ParameterFiles/parameter_description.rst
+5
-5
5 additions, 5 deletions
doc/RTD/source/ParameterFiles/parameter_description.rst
with
5 additions
and
5 deletions
doc/RTD/source/ParameterFiles/parameter_description.rst
+
5
−
5
View file @
a9a55d00
...
...
@@ -458,7 +458,7 @@ using the parameter:
The default level of ``0`` implies no compression and values have to be in the
range :math:`[0-9]`. This integer is passed to the i/o library and used for the
lossless GZIP compression algorithm. Higher values imply higher compression but
loss
-
less GZIP compression algorithm. Higher values imply higher compression but
also more time spent deflating and inflating the data. Note that up until HDF5
1.10.x this option is not available when using the MPI-parallel version of the
i/o routines.
...
...
@@ -500,7 +500,7 @@ Showing all the parameters for a basic hydro test-case, one would have:
int_time_label_on: 0
compression: 3
UnitLength_in_cgs: 1. # Use cm in outputs
UnitMass_in_cgs: 1. # Use grams in outpus
UnitMass_in_cgs: 1. # Use grams in outpu
t
s
UnitVelocity_in_cgs: 1. # Use cm/s in outputs
UnitCurrent_in_cgs: 1. # Use Ampere in outputs
UnitTemp_in_cgs: 1. # Use Kelvin in outputs
...
...
@@ -725,13 +725,13 @@ parameter. The possible values for this are *none*, *fullcosts*, *edgecosts*,
* *edgecosts*
Only use computation weights derived from the running tasks for the e
g
de
Only use computation weights derived from the running tasks for the ed
g
e
weights.
* *memory*
Repeat the initial partition with the current particle positions
rebalancing the memory use.
re
-
balancing the memory use.
* *timecosts*
...
...
@@ -783,7 +783,7 @@ adaptive algorithm is further controlled by the::
parameter, which defines the ratio of inter node communication time to data
redistribution time, in the range 0.00001 to 10000000.0. Lower values give
less data movement during redistributions. The best choice fo
e
r these can only
less data movement during redistributions. The best choice for these can only
be determined by experimentation (the gains are usually small, so not really
recommended).
...
...
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
sign in
to comment