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
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
SWIFT
SWIFTsim
Commits
aa623b7a
Commit
aa623b7a
authored
6 years ago
by
Matthieu Schaller
Browse files
Options
Downloads
Patches
Plain Diff
Corrected the documentation to containt the correct directory where to put the 'stop' file.
parent
8d0db572
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/RTD/source/ParameterFiles/parameter_description.rst
+3
-2
3 additions, 2 deletions
doc/RTD/source/ParameterFiles/parameter_description.rst
with
3 additions
and
2 deletions
doc/RTD/source/ParameterFiles/parameter_description.rst
+
3
−
2
View file @
aa623b7a
...
@@ -568,8 +568,9 @@ been activated, the previous set of restart files will be named
...
@@ -568,8 +568,9 @@ been activated, the previous set of restart files will be named
``basename_000000.rst.prev``.
``basename_000000.rst.prev``.
SWIFT can also be stopped by creating an empty file called ``stop`` in the
SWIFT can also be stopped by creating an empty file called ``stop`` in the
directory where the code runs. This will make SWIFT dump a fresh set of restart
directory where the restart files are written (i.e. the directory speicified by
file (irrespective of the specified ``delta_time`` between dumps) and exit
the parameter ``subdir``). This will make SWIFT dump a fresh set of restart file
(irrespective of the specified ``delta_time`` between dumps) and exit
cleanly. One parameter governs this behaviour:
cleanly. One parameter governs this behaviour:
* Number of steps between two checks for the presence of a ``stop`` file:
* Number of steps between two checks for the presence of a ``stop`` file:
...
...
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