Changes between Version 257 and Version 258 of LnDevel

Timestamp:

Mar 28, 2025, 7:04:18 PM (4 days ago)

Author:

lnerger

Comment:

--

LnDevel

@@ -100 +100 @@
 **[wiki:PDAF3_interface PDAF3_interface]** (still need to complete...)
 
-[wiki:PDAF3_assimilate_local] !
+[wiki:PDAF3_assimilate] !
 
 [wiki:PDAF3_assimilate_global] !
 
-[wiki:PDAF3_put_state_local] !
+[wiki:PDAF3_put_state] !
 
 [wiki:PDAF3_put_state_global] !
@@ -197 +197 @@
 * Revised setting parameters for PDAF: Before the parameters were all set in the call to PDAF_init. Now there are new routines PDAF_set_iparam and PDAF_set_rparam to set selected parameters, without the need to specify all parameters. These routines make the specification of parameters for PDAF more flexible and can also be used during a run to change parameter values.
 * Revision of the initialization of observations: Now the observations are initialized before the actual analysis step is computed. Also the observartion operator is called before the actual analysis step. This also allows the option to initialize observations before prepoststep_pdaf is called for the forecast ensemble. Related to this the screen output for the observations was revised and is displayed at a different location from before
-* New PDAF3 interface: The selection of possible calls to PDAF*_put_state and PDAF*_assimilate has grown over the years since new functionality, in particular PDAF-OMI and PDAFlocal, required a new interfaces. We now defined a new standard interface PDAF3_assimilate_X and PDAF3_put_state_X, which uses the latest features that were introduced in previous PDAF releases and allow for a minimum number of arguments. The previous routines still exist, but we recommend to change to the new routines. 
+* New PDAF3 interface: The selection of possible calls to PDAF*_put_state and PDAF*_assimilate has grown over the years since new functionality, in particular PDAF-OMI and PDAFlocal, required a new interfaces. We now defined a new standard interface in which a single routine (PDAF3_assimilate) can execute all available filter methods for the case of a diagonal observation error covariance matrix. The routine leverages the latest features that were introduced in previous PDAF releases to allow for a minimum number of arguments. The previous routines still exist, but we recommend to change to the new routines. There is also the routine PDAF3_put_state, which is now mainly recommended when the offline mode is used.
 * New routine PDAF_get_fcst_info: This routine allows to retrieve the return values of PDAF_get_state (nsteps, time, doexit) for the case that PDAF_assimilate routines, which do not return these values, are used.
-* Change for flexible parallelization variant: For this variant it is now possible to use PDAF_assimilate routines, while PDAF_put_state routines had to be called before. Using PDAF_assimilate in combination with 'PDAF_get_fcst_info' is the recommend choice for PDAF V3. Since PDAF_assimilate routines are called at each time step during the forecast phase this allows to easy use of the IAU functionality.
+* Change for flexible parallelization variant: For this variant it is now possible to use PDAF_assimilate, while PDAF_put_state routines had to be called before. Using PDAF_assimilate in combination with 'PDAF_get_fcst_info' is the recommend choice for PDAF V3, but usinf PDAF_put_state is still possible. Since PDAF_assimilate is called at each time step during the forecast phase this allows to easy use of the IAU functionality.
 * New routine PDAFomi_set_localize_covar: This routine is called in the OMI observation module in init_dim_obs_pdafomi. It sets the information for localization in the LEnKF and ENSRF/EAKF methods. (optional for LEnKF) 
 * Calling LEnKF with the common routine PDAF3_assimilate_global: In PDAF 2.3 and before, the LEnKF had its own interface due to the additional call-back routine localize_covar_pdafomi required by this filter. With the new routine PDAFomi_set_localize_covar that is called in the OMI observation module in init_dim_obs_pdafomi the additional user-supplied subroutine localize_covar_pdafomi is no longer required which lowers the amount of implementation work for the user.