Changes between Version 1 and Version 2 of PDAF_generate_obs_si


Ignore:
Timestamp:
Feb 9, 2019, 11:26:19 AM (6 years ago)
Author:
lnerger
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • PDAF_generate_obs_si

    v1 v2  
    55The routine is typically called in `assimilate_pdaf` or directly in the model code.
    66
    7 The general aspects of the filter specific routines `PDAF_assimilate_*` are described on the page [ModifyModelforEnsembleIntegration Modification of the model code for the ensemble integration] and its sub-page on [InsertAnalysisStep inserting the analysis step]. The routine is used in the fully-parallel implementation variant of the data assimilation system. When the 'flexible' implementation variant, the routines `PDAF_put_state_*' are used.
     7This routine is used to generate synthetic observations. It is the simple-interface variante of [PDAF_generate_obs], having only a single argument and using predefined names for the call-back routines.
     8The routine bases on the usual implementation strategy for PDAF which is described on the page [ModifyModelforEnsembleIntegration Modification of the model code for the ensemble integration] and its sub-page on [InsertAnalysisStep inserting the analysis step]. The routine is used in the fully-parallel implementation variant of the data assimilation system. When the 'flexible' implementation variant, the routine `PDAF_put_state_generate_obs' is used.
    89
    910The interface is the following:
     
    1415 * `status_pdaf`: The integer status flag. It is zero, if `PDAF_generate_obs_si` is exited without errors.
    1516
    16 The routine calls several user-supplied call-back routines. They are described on the page on [ImplementGeneneratObs implementing the generation of synthetic observations].
     17The routine calls several user-supplied call-back routines. They are described on the page on [ImplementGenenerateObs implementing the generation of synthetic observations].
    1718
    1819It is recommended that the value of `status_pdaf` is checked in the program after PDAF_generate_obs_si is executed. Only if its value is 0 the initialization was successful.