...
| Volet |
|---|
SPS_launch r.run_in_parallel sps.sh |
You can copy the scripts from the following directory:
| Volet |
|---|
| cp -p ~winger/SPS/v_6.1.1/Scripts_latest_version/* ~/SPS/v_6.1.1/Scripts |
Executable
The following is a recipe to create your own executable:
...
c) Clone the SPS Git repository you want to start from, for example:
| Volet |
|---|
Original version from RPN: Modified UQAM version including FLake & CLASS: |
Then change into 'sps' directory that came with the clone:
...
You can check the progress of an SPS simulation the same way as for GEM by executing 'u.tail' on the model listing under ~/listings/${TRUE_HOST}:
| Volet |
|---|
| u.tail model_listing |
Note that model listings will not - yet - get archived at the and of a job as done in GEM!
Restart / Continue a simulation
First, make sure all previous model output has been moved to the archive directory. To do that, go into your config file directory and execute the post pocessing script with:
| Volet |
|---|
| bash SPS_pp_job.sh |
Then resubmit the simulation from the last initial condition output you have with:
| Volet |
|---|
| SPS_lance -JOB_startdate YYYY MM DD hh |
Where "YYYY MM DD hh" is the start date and hour of the job you want to start within the whole simulation, which is probably the date of your last initial condition output.