Changes between Version 1 and Version 2 of PDAF3_interface

Timestamp:

Mar 23, 2025, 4:12:19 PM (9 days ago)

Author:

lnerger

Comment:

--

PDAF3_interface

@@ -27 +27 @@
 
 **Notes:** 
- * The routines [wiki:PDAF3_put_state_local] and [wiki:PDAF3_put_state_global] exist for backward-compatibility. Starting with PDAF V3.0, we recommend to use [wiki:PDAF3_assimilate_local]  and [wiki:PDAF3_assimilate_global] 
+ * The routines [wiki:PDAF3_put_state_local] and [wiki:PDAF3_put_state_global] exist for backward-compatibility of the flexible parallelization variant. Starting with PDAF V3.0, we recommend to use [wiki:PDAF3_assimilate_local]  and [wiki:PDAF3_assimilate_global]. See the [wiki:ExternalModelLoop instructions for implementing the flexible parallelization variant] for the updated instructions.
  * One can let PDAF select which of the routines to call. The function [wiki:PDAF_localfilter] allows to switch between the routines as is shown in the tutorial implementations and templates.
 
 **For non-diagonal R matrix**
 
-I the observation error covariance matrix **R** is non-diagonal, one needs to sue different interface routines. These provide direct access to the routines that involved operations with the matrix **R** so that the user can implement these as efficiently as possible given the particular characteristics of **R** in they particular application.
+If the observation error covariance matrix **R** is non-diagonal, one needs to sue different interface routines. These provide direct access to the routines that involved operations with the matrix **R** so that the user can implement these as efficiently as possible given the particular characteristics of **R** in they particular application.
 
 See the [wiki:OMI_nondiagonal_observation_error_covariance_matrices] for information on using non-diagonal **R**-matrices with OMI. The routines are only partly generic depending on the needed observation-specific routine: