Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added documentation for force flag #259

Merged
merged 3 commits into from
May 13, 2020
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion docs/source/conf.py
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,11 @@

# Sphinx setup
#needs_sphinx = '1.0'
extensions = ['sphinx.ext.autodoc', 'sphinx.ext.ifconfig', 'sphinx.ext.viewcode']
extensions = ['sphinx.ext.autodoc',
'sphinx.ext.ifconfig',
'sphinx.ext.viewcode',
'sphinx.ext.autosectionlabel']
autosectionlabel_maxdepth = 2
templates_path = ['_templates']
source_suffix = '.rst'
#source_encoding = 'utf-8-sig'
Expand Down
23 changes: 13 additions & 10 deletions docs/source/usage.rst
Original file line number Diff line number Diff line change
Expand Up @@ -150,17 +150,16 @@ created manually:
Running your experiment
=======================

Once the laboratory has been created and the experiment has been configured, you
can check that the paths have been correctly specified by running::
Once the laboratory has been created and the experiment has been configured, as
an optioal step you can check that the paths have been correctly specified by
running::

payu setup

This creates the temporary ``work`` directory and is done automatically when
the model is run. If there any errors these can be fixed. ``payu`` will not
run the model if there is an existing ``work`` directory, so this must be
removed like so::

payu sweep
the model is run. If there any errors in the configuration, such as incorrect
or missing paths, these can be fixed. ``payu`` will not run the model if there
is an existing ``work`` directory, so this must be removed (see :ref:`Cleaning up`).

The ``setup`` command will also generate manifest files in the ``manifest``
directory. The manifest files track the executable, input and restart files used
Expand All @@ -175,6 +174,11 @@ Once you are satisfied the configuration is correct, and there is no existing

This will run the model once and store the output in the ```archive``` directory.

Optionally is there is an existing ``work`` directory the ``-f/--force`` flag
will automatically ``sweep`` any existing ``work`` directory::

payu run -f

To continue the simulation from its last point, type ``payu run`` again.

In order to schedule ``N`` successive runs, use the ``-n`` flag::
Expand All @@ -200,8 +204,8 @@ If you have instructed ``payu`` to run for a number of resubmits but for some
reason need to stop a run after the current run has completed create a file
called ``stop_run`` in the control directory.

It is possible to require that a run reproduce an existing run using the ``-r``
flag:
It is possible to require that a run reproduce an existing run using the
``-r/--reproduce`` flag:

payu run -r

Expand Down Expand Up @@ -231,7 +235,6 @@ This will delete the contents of ``work`` and move any model and scheduler logs
into a ``pbs_logs`` directory. Any model output in ``archive`` will not be
deleted.


Deleting an experiment archive
------------------------------

Expand Down