Changes between Version 2 and Version 3 of PDAF_init_forecast


Ignore:
Timestamp:
Mar 6, 2026, 1:08:47 PM (17 hours ago)
Author:
lnerger
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • PDAF_init_forecast

    v2 v3  
    77The routine `PDAF_init_forecast` has the purpose to initialize the model fields to be propagated from the array holding the ensemble states. In addition, the routine initializes the information on how many time steps have to be performed in the upcoming forecast phase the information, and an exit flag indicating whether further model integrations have to be computed. These variables are used internally in PDAF and can be retrieved by the user by calling [wiki:PDAF_get_fcst_info].
    88
    9 The interface of `PDAF_init_forecast` is the following:
     9The interface is the following:
    1010{{{
    11   SUBROUTINE PDAF_init_forecast(U_next_observation, U_distribute_state, &
    12                             U_prepoststep, status)
     11  SUBROUTINE PDAF_init_forecast(next_observation_pdaf, distribute_state_pdaf, &
     12                            prepoststep_pdaf, status)
    1313}}}
    1414with the following arguments:
    15  * `U_next_observation`: The name of a user supplied routine that initializes the variables `nsteps`, `timenow`, and `doexit`
    16  * `U_distribute_state`: The name of a user supplied routine that initializes the model fields from the array holding the ensemble of model state vectors
    17  * `U_prepoststep`: The name of a user supplied routine that is called before and after the analysis step. Here the user has the possibility to access the state ensemble and can e.g. compute estimated variances or can write the ensemble states the state estimate into files.
     15 * `next_observation_pdaf`: The name of a user supplied routine that initializes the variables `nsteps`, `timenow`, and `doexit`
     16 * `distribute_state_pdaf`: The name of a user supplied routine that initializes the model fields from the array holding the ensemble of model state vectors
     17 * `prepoststep_pdaf`: The name of a user supplied routine that is called before and after the analysis step. Here the user has the possibility to access the state ensemble and can e.g. compute estimated variances or can write the ensemble states the state estimate into files.
    1818 * `status`: The integer status flag. It is zero, if the routine is exited without errors.
    1919
    20 The specifications of the user-supplied routines (`U_next_observation`, `U_distribute_state`, `U_prepoststep`) are documented on the page on [InsertAnalysisStep inserting the analysis step].
     20The specifications of the user-supplied routines (`next_observation_pdaf`, `distribute_state_pdaf`, `prepoststep_pdaf`) are documented on the page on [ImplementAnalysisPDAF3Universal inserting the analysis step].