...
To create the batch job, use the oifs_run command. This creates a small batch job file ready to submit.
Panel | ||||||
---|---|---|---|---|---|---|
| ||||||
oifs_run -e exptid [-m path-to-master.exe] [-r resolution] [-l namelist] [-s timestep] [-n nproc] [-f fcast len] [-x run number] [-q] For this workshop, the only arguments to use are: -e, -l, -f, -x and -q. Note that the -f argument, the length of the forecast is specified as: dNN, for example d10 means '10 days'. |
Info | ||||
---|---|---|---|---|
| ||||
Use the The command will create a create a file ' Submit this job:
Check the job status:
These forecasts complete in about 15mins. |
Info |
---|
If you get the error message:
|
execute the command:
to correct set the environment. |
Checking the model output
After the qstatu command shows that the job has completed, there will be a 'batch log file' in the pf001 directory:
Code Block | ||||
---|---|---|---|---|
| ||||
oifs_trcray1.o1481792 |
Info | ||
---|---|---|
Using your favourite text editor, check this file to make sure the model has run correctly. It's usually best to start from the bottom of the file and scroll up. If you see:
the model has failed. |
The output from each model run goes into a directory named according to this run number. e.g. the default is 'output1'. So job2 would write the output to 'output2' and so on.
Run number
Each model run has a number. This is '1' by default but can be changed using the -x option to the oifs_run command.
Panel | ||||||
---|---|---|---|---|---|---|
| ||||||
oifs_run -e gc1d -l mynamelist -x 2 -f d5 -q |
Checking job status: qstatu