Coupling/IO fields (transient variables)

Each coupling/IO field effectively received or provided by the component model from/to its external environment (another model or a disk file) through prism_get or prism_put call in the component code (see sections 5.6.1 and 5.6.2) must be specified by one element `transient' which has the following attributes and sub-elements:

• attribute `local_name': the field name, which must match 2$^{nd}$ argument in the corresponding PSMILe call prism_def_var (see sections 5.4.1); (mandatory);

• attribute `long_name': gives a general description of the variable; (optional)

• element `transient_standard_name': one or more PRISM standard names following the CF convention (if they exist); see section 6.3.3 for details; (mandatory)

• element `physics': a description of the coupling/IO field physical constraints; see section 6.3.3 for details; (optional)

• element `numeric', whose attribute `datatype' gives the coupling/IO field numeric type (either
  xs:real, xs:double, or xs:integer); (mandatory)

• element `intent', which describes if the coupling/IO field will be exported or imported, or both (mandatory). This element contains in its sub-elements all coupling and I/O information (source and/or target, frequency, transformations, interpolation, etc.). The sub-elements of `intent' are:
  • element `output': When the coupling/IO field is exported through a prism_put , this export must be described in one or more elements `output'. The element `output' is described in more details in section 6.5.4.

  • element `input': When the coupling/IO field is imported through a prism_get , this import must be described in one element `input'. The element `input' is described in more details in section 6.5.5.