next up previous
Next: Input data files Up: OASIS3 auxiliary data files Previous: Grid data files


Coupling restart files

At the beginning of a coupled run, some coupling fields may have to be initially read from their coupling restart file (see section 4.8). If needed, these files are also automatically updated by the last prism_put_proto call of the run (see section 4.6.1) . To force the writing of the field in its coupling restart file, one can use the routine prism_put_restart_proto (see section 4.6.3). The name of the coupling restart file is given by the 6th character string on the first configuring line for each field in the namcouple (see section 5.3). Coupling fields coming from different models cannot be in the same coupling restart files, but for each model, there can be an arbitrary number of fields written in one coupling restart file. Note that in the NONE techniques, output files with the same format are also created for writing the resulting field after transformation.

In the coupling restart files, the fields must be single or double precision REAL arrays (depending on PSMILe and OASIS3 compilation options) and, as the grid data files, must be dimensioned (nx, ny), where nx and ny are the grid first and second dimension, except for fields given on Unstructured ('U') and Reduced ('Dí) grid, for which the arrays are dimensioned (nbr_pts,1), where nbr_pts is the total number of grid points. The shape and orientation of each restart field (and of the corresponding coupling fields exchanged during the simulation) must be coherent with the shape of its grid data arrays. The exceptions are for A, B, G, L, Z, or Y grids for which the field may be oriented from North to South and/or from East to West, in which case, INVERT transformation will have to be used - see section 6.3.

Both binary and NetCDF formats are supported; for NetCDF file the suffix .nc is not mandatory. If the coupling restart file for the first field is in NetCDF format, OASIS3 will assume that all coupling restart files (and output files for NONE communication techniques) are NetCDF[*].

In the NetCDF restart files, the field arrays must have the source symbolic name indicated in the namcouple (see section 5.3).

In binary restart file, each field is written in the following way:

        ...
        WRITE(LU) array_name
        WRITE(LU) restartdata
        ...
where


next up previous
Next: Input data files Up: OASIS3 auxiliary data files Previous: Grid data files
Reinhard Budich 2004-12-22