Changes between Version 1 and Version 2 of PDAF_init_forecast
- Timestamp:
- May 24, 2025, 2:41:12 PM (8 days ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
PDAF_init_forecast
v1 v2 1 1 = PDAF_init_forecast = 2 2 3 This page documents the routine `PDAF_init_forecast` of PDAF. The routine was introduced with PDAF V3.0 as a replacement of `PDAF_get_state` . The new name `PDAF_init_forecast` is intended to make the purpose of the routine clearer.3 This page documents the routine `PDAF_init_forecast` of PDAF. The routine was introduced with PDAF V3.0 as a replacement of `PDAF_get_state`, with a reduced number of arguments. 4 4 5 5 The routine `PDAF_init_forecast` has to be called once at the end of the initialization of PDAF. Usually, the call will be part of the routine `init_pdaf` that was discussed on the [InitPdaf page on initializing PDAF]. 6 6 7 The 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 provides the information on how many time steps have to be performed in the upcoming forecast phase. The routine can also initialize the information, whether further model integrations have to be computed. For the fully-parallel implementation variant, the number of time steps is used inside PDAF, while the flag on further model integrations is not used.7 The 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]. 8 8 9 9 The interface of `PDAF_init_forecast` is the following: 10 10 {{{ 11 SUBROUTINE PDAF_init_forecast( nsteps, timenow, doexit,U_next_observation, U_distribute_state, &11 SUBROUTINE PDAF_init_forecast(U_next_observation, U_distribute_state, & 12 12 U_prepoststep, status) 13 13 }}} 14 14 with the following arguments: 15 * `nsteps`: An integer specifying upon exit the number of time steps to be performed16 * `timenow`: A real specifying upon exit the current model time. (This value is usually not used in the fully-parallel implemenation variant)17 * `doexit`: An integer variable defining whether the assimilation process is completed. For compatibility 1 should be used for exit, 0 for continuing. (This value is not used in the fully-parallel implemenation variant)18 15 * `U_next_observation`: The name of a user supplied routine that initializes the variables `nsteps`, `timenow`, and `doexit` 19 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