1 | <model name="fldproper" title="Coupling fields properties" layout="flat"> |
---|
2 | <desc> |
---|
3 | Please enter the coupling period, the name of the restart files and the status for |
---|
4 | the different coupling fields, selecting the different rows available. |
---|
5 | If you have many fields, it is possible to propagate the properties of one field |
---|
6 | to the others using the button "copy". |
---|
7 | The "load" button is useless for the OASIS3-MCT application.[] |
---|
8 | A blue (?), located at the right bottom of this window, gives more information on the data to fill up, specially on the |
---|
9 | INPUT and OUTPUT field properties. |
---|
10 | </desc> |
---|
11 | </model> |
---|
12 | |
---|
13 | <model name="cplrststatus" title="Coupling fields properties" layout="flat"> |
---|
14 | <multiple name="crs" title="Coupling period, restarts, status" require="field_names_list" custom_label="Fields" size="1.5;1.5"> |
---|
15 | <param name="cpl" title="Coupling or IO period in s (integer)" type="integer" /> |
---|
16 | <param name="restart" title="Restart file (NetCDF)" type="string" /> |
---|
17 | <choice name="status" title="Status" type="string" default="exported"> |
---|
18 | <option value="exported" title="EXPORTED"/> |
---|
19 | <option value="expout" title="EXPOUT"/> |
---|
20 | <option value="input" title="INPUT"/> |
---|
21 | <option value="output" title="OUTPUT"/> |
---|
22 | </choice> |
---|
23 | </multiple> |
---|
24 | <docu> |
---|
25 | [section=NetCDF Restart files] |
---|
26 | The name of the coupling restart file for the field is mandatory even if no coupling restart file is effectively used. [] |
---|
27 | |
---|
28 | More information on the restart files can be found in the User Guide section 2.10 and section 5.2. |
---|
29 | |
---|
30 | [section=Status of the fields] |
---|
31 | [item=EXPORTED:] The field is exchanged between component models and transformed by OASIS3-MC |
---|
32 | [item=EXPOUT:] The field is exchanged, transformed and also written to two debug NetCDF files (after LOCTRANS and BLASOLD before |
---|
33 | remapping and after all transformations after remapping). |
---|
34 | [item=INPUT:] The field is read in from the input file by the target model. |
---|
35 | [item=OUTPUT:] The field is written out to an output debug NetCDF file by the source model. |
---|
36 | |
---|
37 | More information is available in section 3.3 of the User Guide. |
---|
38 | |
---|
39 | <docuold> |
---|
40 | [section=NetCDF Restart files] |
---|
41 | The name of the coupling restart file for the field is mandatory even if no coupling restart file is effectively used. [] |
---|
42 | |
---|
43 | At the beginning of a coupled run, some coupling fields may have to be initially read from their coupling restart |
---|
44 | file on their source grid. When needed, these files are also automatically updated by the last active oasis_put |
---|
45 | call of the run. Warning: the date is not written or read to/from the restart file; therefore, the |
---|
46 | user has to make sure that the appropriate coupling restart file is present in the working directory. The coupling |
---|
47 | restart files must follow the NetCDF format. [] |
---|
48 | |
---|
49 | Coupling fields coming from different models cannot be in the same coupling restart files, |
---|
50 | but for each model, there can be an arbitrary number of fields written in one coupling restart file. The only exception |
---|
51 | is when a coupling field sent by a source component model is associated with more than one target field and model; |
---|
52 | in that case, if coupling restart files are required, it is mandatory to specify different files for the different fields. [] |
---|
53 | |
---|
54 | In the coupling restart files, the fields must be provided on the source grid in single or double precision REAL arrays and, |
---|
55 | as the grid data files, must be dimensioned (nx, ny), where nx and ny are the grid first and second dimension. The shape and |
---|
56 | orientation of each restart field (and of the corresponding coupling fields exchanged during the simulation) must be coherent |
---|
57 | with the shape of its grid data arrays. [] |
---|
58 | |
---|
59 | The coupling restart files are also used automatically by OASIS3-MCT to allow partial LOCTRANS time transformation |
---|
60 | to be saved at the end of a run for exact restart at the start of the next run. For that reason, coupling restart |
---|
61 | filenames are now required for all namcouple transformations that use LOCTRANS (with non INSTANT values). |
---|
62 | |
---|
63 | [section=Status of the fields] |
---|
64 | The field may be : [] |
---|
65 | - EXPORTED: exchanged between component models and transformed by OASIS3-MCT [] |
---|
66 | - EXPOUT: exchanged, transformed and also written to two debug NetCDF files, one before the sending action in |
---|
67 | the source model below the oasis_put call (after local transformations LOCTRANS and BLASOLD if present), and one |
---|
68 | after the receiving action in the target model below the oasis_get call (after all transformations). EXPOUT should |
---|
69 | be used when debugging the coupled model only. The name of the debug NetCDF file (one per field) is automatically |
---|
70 | defined based on the field and component model names. [] |
---|
71 | - INPUT: read in from the input file by the target model below the oasis_get call at appropriate times corresponding |
---|
72 | to the input period indicated by the user in the namcouple. [] |
---|
73 | - OUTPUT: written out to an output debug NetCDF file by the source model below the oasis_put call, after local |
---|
74 | transformations LOCTRANS and BLASOLD, at appropriate times corresponding to the output period indicated by |
---|
75 | the user in the configuration file. |
---|
76 | </docuold> |
---|
77 | </docu> |
---|
78 | </model> |
---|
79 | |
---|
80 | |
---|
81 | |
---|
82 | |
---|
83 | |
---|
84 | |
---|
85 | |
---|