...
| Info |
|---|
If you get the error message:
execute the command:
to correct set the environment. |
During the course of the model run, files with names ICM*+* will appear in the experiment directory. These are the model output files. There is 1 per output interval. In these experiments the output interval is every 3 hours.
Checking the model output
...
| 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.
If the model fails, there are 2 files to look at in the appropriate 'output' directory:
NODE.001_01 : this is the output from the model as it is running (i.e. all the print/write fortran statements). This is a large file, so in case of errors, start from the bottom up!
oifs.log : this is where the model writes any error messages.
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 |
...