Changes between Initial Version and Version 1 of ImplementAnalysislenkf


Ignore:
Timestamp:
Dec 3, 2016, 7:05:06 PM (8 years ago)
Author:
lnerger
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ImplementAnalysislenkf

    v1 v1  
     1= Implementation of the Analysis step for the LEnKF (Localized Ensemble Kalman Filter) =
     2
     3{{{
     4#!html
     5<div class="wiki-toc">
     6<h4>Implementation Guide</h4>
     7<ol><li><a href="ImplementationGuide">Main page</a></li>
     8<li><a href="AdaptParallelization">Adaptation of the parallelization</a></li>
     9<li><a href="InitPdaf">Initialization of PDAF</a></li>
     10<li><a href="ModifyModelforEnsembleIntegration">Modifications for ensemble integration</a></li>
     11<li><a href="ImplementationofAnalysisStep">Implementation of the analysis step</a></li>
     12<ol>
     13<li><a href="ImplementAnalysisestkf">Implementation for ESTKF</a></li>
     14<li><a href="ImplementAnalysislestkf">Implementation for LESTKF</a></li>
     15<li><a href="ImplementAnalysisetkf">Implementation for ETKF</a></li>
     16<li><a href="ImplementAnalysisletkf">Implementation for LETKF</a></li>
     17<li><a href="ImplementAnalysisseik">Implementation for SEIK</a></li>
     18<li><a href="ImplementAnalysislseik">Implementation for LSEIK</a></li>
     19<li><a href="ImplementAnalysisseek">Implementation for SEEK</a></li>
     20<li><a href="ImplementAnalysisenkf">Implementation for EnKF</a></li>
     21<li>Implementation for LEnKF</li>
     22<li><a href="ImplementAnalysisnetf">Implementation for NETF</a></li>
     23<li><a href="ImplementAnalysislnetf">Implementation for LNETF</a></li>
     24
     25</ol>
     26<li><a href="AddingMemoryandTimingInformation">Memory and timing information</a></li>
     27</ol>
     28</div>
     29}}}
     30
     31[[PageOutline(2-3,Contents of this page)]]
     32
     33The LEnKF was added with verson 1.12 of PDAF.
     34
     35== Overview ==
     36
     37For the analysis step of the LEnKF different operations related to the observations are needed. These operations are requested by PDAF by calling user-supplied routines. Intentionally, the operations are split into separate routines in order to keep the operations rather elementary. This procedure should simplify the implementation. The names of the required routines are specified in the call to the routine `PDAF_put_state_lenkf` for the fully-parallel implementation (or `PDAF_put_state_lenkf` for the 'flexible' implementation). With regard to the parallelization, all these routines are executed by the filter processes (`filterpe=.true.`) only.
     38
     39For completeness we discuss here all user-supplied routines that are specified in the interface to PDAF_put_state_lenkf. Thus, some of the user-supplied routines that are explained on the page explaining the modification of the model code for the ensemble integration are repeated here.
     40
     41The LEnKF implemented in PDAF follows the original LEnKF by Evensen (1994) including the correction for perturbed observations (Burgers et al. 1998). The LEnKF implemented in PDAF is reviewed by Nerger et al (2005) and described in more detail by Nerger (2004). The localization is covariance lozalization of PH^T and HPH^T as described in Houtekamer & Mitchell (2001) (See the [PublicationsandPresentations page on publications and presentations] for publications and presenations involving and about PDAF)
     42
     43In our studies (Nerger et al. 2005, Nerger et al. 2007), the EnKF showed performance deficiencies compared to the SEIK filter. Due to this, we focused more on the SEIK filter and the ETKF and ESTKF after these comparison studies. For real applications, we generally recommend using ESTKF or ETKF, or their local variants LESTKF or LETKF. However, the EnKF/LEnKF might have a good performance if very large ensemble can be used as this reduces the sampling errors.
     44
     45== `PDAF_assimilate_lenkf` ==
     46
     47The general aspects of the filter specific routines `PDAF_assimilate_*` have been 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 is used, the routines `PDAF_put_state_*' is used as described further below. Here, we list once more the full interface of the routine. Subsequently, the full set of user-supplied routines specified in the call to `PDAF_assimilate_lenkf` is explained.
     48
     49The interface when using the LEnKF is the following:
     50{{{
     51  SUBROUTINE PDAF_assimilate_lenkf(U_collect_state, U_distribute_state, U_init_dim_obs, &
     52                                 U_obs_op, U_init_obs, U_prepoststep, U_localize, &
     53                                 U_add_obs_err, U_init_obscovar, U_next_observation, status)
     54}}}
     55with the following arguments:
     56 * [#U_collect_statecollect_state_pdaf.F90 U_collect_state]: The name of the user-supplied routine that initializes a state vector from the array holding the ensemble of model states from the model fields. This is basically the inverse operation to `U_distribute_state` used in `PDAF_get_state` as well as here.
     57 * [#U_distribute_statedistribute_state_pdaf.F90 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.
     58 * [#U_init_dim_obsinit_dim_obs_pdaf.F90 U_init_dim_obs]: The name of the user-supplied routine that provides the size of observation vector
     59 * [#U_obs_opobs_op_pdaf.F90 U_obs_op]: The name of the user-supplied routine that acts as the observation operator on some state vector
     60 * [#U_init_obsinit_obs_pdaf.F90 U_init_obs]: The name of the user-supplied routine that initializes the vector of observations
     61 * [#U_prepoststepprepoststep_ens_pdaf.F90 U_prepoststep]: The name of the pre/poststep routine as in `PDAF_get_state`
     62 * [#U_localizelocalize_covar_pdaf.F90 U_localize]: Apply covariance localization to the matrices HP and HPH^T^
     63 * [#U_add_obs_erradd_obs_err_pdaf.F90 U_add_obs_err]: The name of the user-supplied routine that adds the observation error covariance matrix to the ensemble covariance matrix projected onto the observation space.
     64 * [#U_init_obscovarinit_obscovar_pdaf.F90 U_init_obscovar]: The name of the user-supplied routine that initializes the observation error covariance matrix.
     65 * [#U_next_observationnext_observation_pdaf.F90 U_next_observation]: The name of a user supplied routine that initializes the variables `nsteps`, `timenow`, and `doexit`. The same routine is also used in `PDAF_get_state`.
     66 * `status`: The integer status flag. It is zero, if `PDAF_assimilate_lenkf` is exited without errors.
     67
     68== `PDAF_put_statel_enkf` ==
     69
     70When the 'flexible' implementation variant is chosen for the assimilation system, the routine `PDAF_put_state_lenkf` has to be used instead of `PDAF_assimilate_lenkf`. The general aspects of the filter specific routines `PDAF_put_state_*` have been described on the page [ModifyModelforEnsembleIntegration Modification of the model code for the ensemble integration]. The interface of the routine is identical with that of `PDAF_assimilate_lenkf` with the exception the specification of the user-supplied routines `U_distribute_state` and `U_next_observation` are missing.
     71
     72The interface when using the LEnKF is the following:
     73{{{
     74  SUBROUTINE PDAF_put_state_lenkf(U_collect_state, U_init_dim_obs, U_obs_op, &
     75                                 U_init_obs, U_prepoststep, U_localize, &
     76                                 U_add_obs_err, U_init_obscovar, status)
     77}}}
     78
     79
     80== User-supplied routines ==
     81
     82Here all user-supplied routines are described that are required in the call to `PDAF_assimilate_lenkf`. For some of the generic routines, we link to the page on [ModifyModelforEnsembleIntegration modifying the model code for the ensemble integration].
     83
     84To indicate user-supplied routines we use the prefix `U_`. In the template directory `templates/` as well as in the example implementation in `testsuite/src/dummymodel_1D` these routines exist without the prefix, but with the extension `_pdaf.F90`. In the section titles below we provide the name of the template file in parentheses.
     85
     86In the subroutine interfaces some variables appear with the suffix `_p`. This suffix indicates that the variable is particular to a model sub-domain, if a domain decomposed model is used. Thus, the value(s) in the variable will be different for different model sub-domains.
     87
     88
     89=== `U_collect_state` (collect_state_pdaf.F90) ===
     90
     91This routine is independent of the filter algorithm used.
     92See the page on [InsertAnalysisStep#U_collect_statecollect_state_pdaf.F90 inserting the analysis step] for the description of this routine.
     93
     94
     95=== `U_distribute_state` (distribute_state_pdaf.F90) ===
     96
     97This routine is independent of the filter algorithm used.
     98See the page on [InsertAnalysisStep#U_distribute_statedistribute_state_pdaf.F90 inserting the analysis step] for the description of this routine.
     99
     100
     101=== `U_init_dim_obs` (init_dim_obs_pdaf.F90) ===
     102
     103This routine is used by all global filter algorithms (SEEK, SEIK, EnKF, ETKF) and by the LEnKF.
     104
     105The interface for this routine is:
     106{{{
     107SUBROUTINE init_dim_obs(step, dim_obs_p)
     108
     109  INTEGER, INTENT(in)  :: step       ! Current time step
     110  INTEGER, INTENT(out) :: dim_obs_p  ! Dimension of observation vector
     111}}}
     112
     113The routine is called at the beginning of each analysis step.  It has to initialize the size `dim_obs_p` of the observation vector according to the current time step. Without parallelization `dim_obs_p` will be the size for the full model domain. When a domain-decomposed model is used, `dim_obs_p` will be the size of the observation vector for the sub-domain of the calling process.
     114
     115Some hints:
     116 * It can be useful to not only determine the size of the observation vector at this point. One can also already gather information about the locations of the observations, which will be used later, e.g. to implement the observation operator. An array for the locations can be defined in a module like `mod_assimilation` of the example implementation.
     117
     118
     119=== `U_obs_op` (obs_op_pdaf.F90) ===
     120
     121This routine is used by all global filter algorithms (SEEK, SEIK, EnKF, ETKF) and the LEnKF.
     122
     123The interface for this routine is:
     124{{{
     125SUBROUTINE obs_op(step, dim_p, dim_obs_p, state_p, m_state_p)
     126
     127  INTEGER, INTENT(in) :: step               ! Currrent time step
     128  INTEGER, INTENT(in) :: dim_p              ! PE-local dimension of state
     129  INTEGER, INTENT(in) :: dim_obs_p          ! Dimension of observed state
     130  REAL, INTENT(in)    :: state_p(dim_p)     ! PE-local model state
     131  REAL, INTENT(out) :: m_state_p(dim_obs_p) ! PE-local observed state
     132}}}
     133
     134The routine is called during the analysis step. It has to perform the operation of the observation operator acting on a state vector that is provided as `state_p`. The observed state has to be returned in `m_state_p`.
     135
     136For a model using domain decomposition, the operation is on the PE-local sub-domain of the model and has to provide the observed sub-state for the PE-local domain.
     137
     138Hint:
     139 * If the observation operator involves a global operation, e.g. some global integration, while using domain-decomposition one has to gather the information from the other model domains using MPI communication.
     140
     141
     142=== `U_init_obs` (init_obs_pdaf.F90) ===
     143
     144This routine is used by all global filter algorithms (SEEK, SEIK, EnKF, ETKF) and the LEnKF.
     145
     146The interface for this routine is:
     147{{{
     148SUBROUTINE init_obs(step, dim_obs_p, observation_p)
     149
     150  INTEGER, INTENT(in) :: step             ! Current time step
     151  INTEGER, INTENT(in) :: dim_obs_p        ! PE-local dimension of obs. vector
     152  REAL, INTENT(out)   :: observation_p(dim_obs_p) ! PE-local observation vector
     153}}}
     154
     155The routine is called during the analysis step.
     156It has to provide the vector of observations in `observation_p` for the current time step.
     157
     158For a model using domain decomposition, the vector of observations that exist on the model sub-domain for the calling process has to be initialized.
     159
     160
     161=== `U_prepoststep` (prepoststep_ens_pdaf.F90) ===
     162
     163The general aspects of this routines have already been described on the [ModifyModelforEnsembleIntegration#U_prepoststepprepoststep_ens_pdaf.F90 page on modifying the model code for the ensemble integration] for the SEIK filter. For completeness, the description is repeated specifically for the EnKF:
     164
     165The interface of the routine is identical for all filters, but sizes can vary. Also, the particular operations that are performed in the routine can be specific for each filter algorithm.
     166
     167The interface for this routine is for the LEnKF
     168{{{
     169SUBROUTINE prepoststep(step, dim_p, dim_ens, dim_ens_p, dim_obs_p, &
     170                       state_p, Uinv, ens_p, flag)
     171
     172  INTEGER, INTENT(in) :: step        ! Current time step
     173                         ! (When the routine is called before the analysis -step is provided.)
     174  INTEGER, INTENT(in) :: dim_p       ! PE-local state dimension
     175  INTEGER, INTENT(in) :: dim_ens     ! Size of state ensemble
     176  INTEGER, INTENT(in) :: dim_ens_p   ! PE-local size of ensemble
     177  INTEGER, INTENT(in) :: dim_obs_p   ! PE-local dimension of observation vector
     178  REAL, INTENT(inout) :: state_p(dim_p) ! PE-local forecast/analysis state
     179                                     ! The array 'state_p' is not generally not initialized in the case of SEIK/EnKF/ETKF.
     180                                     ! It can be used freely in this routine.
     181  REAL, INTENT(inout) :: Uinv(1, 1)  ! Not used not LEnKF
     182  REAL, INTENT(inout) :: ens_p(dim_p, dim_ens)      ! PE-local state ensemble
     183  INTEGER, INTENT(in) :: flag        ! PDAF status flag
     184}}}
     185
     186The routine `U_prepoststep` is called once at the beginning of the assimilation process. In addition, it is called during the assimilation cycles before the analysis step and after the ensemble transformation. The routine is called by all filter processes (that is `filterpe=1`).
     187
     188The routine provides for the user the full access to the ensemble of model states. Thus, user-controlled pre- and post-step operations can be performed.  For example the forecast and the analysis states and ensemble covariance matrix can be analyzed, e.g. by computing the estimated variances. In addition, the estimates can be written to disk.
     189
     190Hint:
     191 * If a user considers to perform adjustments to the estimates (e.g. for balances), this routine is the right place for it.
     192 * Only for the SEEK filter the state vector (`state_p`) is initialized. For all other filters, the array is allocated, but it can be used freely during the execution of `U_prepoststep`.
     193 * The array `Uinv` is not used in the EnKF. Internally to PDAF, it is allocated to be of size (1,1).
     194 * Apart from the size of the array `Uinv`, the interface is identical for all ensemble filters (SEIK/ETKF/EnKF/LSEIK/LETKF/LEnKF). In general it should be possible to use an identical pre/poststep routine for all these filters.
     195 * The interface through which `U_prepoststep` is called does not include the array of smoothed ensembles. In order to access the smoother ensemble array one has to set a pointer to it using a call to the routine `PDAF_get_smootherens` (see page on [AuxiliaryRoutines auxiliary routines])
     196
     197
     198
     199=== `U_localize` (localize_covar_pdaf.F90) ===
     200
     201This routine is only used for the LEnKF.
     202
     203The interface for this routine is:
     204{{{
     205SUBROUTINE U_localize(dim_p, dim_obs, HP, HPH)
     206
     207  INTEGER, INTENT(in) :: dim_p                 ! PE-local state dimension
     208  INTEGER, INTENT(in) :: dim_obs               ! Dimension of global observation vector
     209  REAL, INTENT(inout) :: HP(dim_obs, dim_p)    ! Matrix HP
     210  REAL, INTENT(inout) :: HPH(dim_obs, dim_obs) ! Matrix HPH^T^
     211}}}
     212
     213The routine is called during the analysis step and has to apply the element-wise Schur product for the covariance localization of the two matrices'''HP''' and '''HPH^T^''', which are provided as input/output arguments.
     214
     215Notes:
     216 * In case of a parallelization with domain decomposition, `HP` contains only the columns of the matrix that resides on the model sub-domain of the calling process. The number of rows is that of the global number of observations
     217
     218Hints:
     219 * To compute the localization one can use the routine `PDAF_local_weight` after computing the distance between two elements in the matrix '''HP''' or '''HPH^T^'''.
     220
     221
     222=== `U_add_obs_err` (add_obs_err_pdaf.F90) ===
     223
     224This routine is only used for the EnKF and LEnKF.
     225
     226The interface for this routine is:
     227{{{
     228SUBROUTINE add_obs_err(step, dim_obs, C)
     229
     230  INTEGER, INTENT(in) :: step                ! Current time step
     231  INTEGER, INTENT(in) :: dim_obs             ! Dimension of obs. vector
     232  REAL, INTENT(inout) :: C(dim_obs, dim_obs) ! Matrix to that the observation
     233                                             !    error covariance matrix is added
     234}}}
     235
     236The routine is called during the analysis step. During the analysis step of the LEnKF, the projection of the ensemble covariance onto the observation space is computed. This matrix is provided to the routine as `C_p`. The routine has to add the observation error covariance matrix to `C_p`.
     237
     238The operation is for the global observation space. Thus, it is independent of whether the filter is executed with or without parallelization.
     239
     240Hints:
     241 * The routine does not require that the observation error covariance matrix is added as a full matrix. If the matrix is diagonal, only the diagonal elements have to be added.
     242
     243
     244
     245=== `U_init_obscovar` (init_obscovar_pdaf.F90) ===
     246
     247This routine is only used for the EnKF and LEnKF.
     248
     249The interface for this routine is:
     250{{{
     251SUBROUTINE init_obscovar(step, dim_obs, dim_obs_p, covar, m_state_p, &
     252     isdiag)
     253
     254  INTEGER, INTENT(in) :: step                ! Current time step
     255  INTEGER, INTENT(in) :: dim_obs             ! Dimension of observation vector
     256  INTEGER, INTENT(in) :: dim_obs_p           ! PE-local dimension of observation vector
     257  REAL, INTENT(out) :: covar(dim_obs, dim_obs) ! Observation error covariance matrix
     258  REAL, INTENT(in)  :: m_state_p(dim_obs_p)  ! PE-local observation vector
     259  LOGICAL, INTENT(out) :: isdiag             ! Whether the observation error covar. matrix is diagonal
     260}}}
     261
     262The routine is called during the analysis step and is required for the generation of an ensemble of observations. It has to initialize the global observation error covariance matrix `covar`. In addition, the flag `isdiag` has to be initialized to provide the information, whether the observation error covariance matrix is diagonal.
     263
     264The operation is for the global observation space. Thus, it is independent of whether the filter is executed with or without parallelization.
     265
     266Hints:
     267 * The local observation vector `m_state_p` is provided to the routine for the case that the observation errors are relative to the value of the observation.
     268
     269
     270=== `U_next_observation` (next_observation_pdaf.F90) ===
     271
     272This routine is independent of the filter algorithm used.
     273See the page on [InsertAnalysisStep#U_next_observationnext_observation_pdaf.F90 inserting the analysis step] for the description of this routine.
     274
     275
     276
     277== Execution order of user-supplied routines ==
     278
     279For the :EnKF, the user-supplied routines are essentially executed in the order they are listed in the interface to `PDAF_assimilate_lenkf`. The order can be important as some routines can perform preparatory work for later routines. For example, `U_init_dim_obs` can prepare an index array that provides the information for executing the observation operator in `U_obs_op`.
     280
     281Before the analysis step is called the following routine is executed:
     282 1. [#U_collect_statecollect_state_pdaf.F90 U_collect_state]
     283
     284The analysis step is executed when the ensemble integration of the forecast is completed. During the analysis step the following routines are executed in the given order:
     285 1. [#U_prepoststepprepoststep_ens_pdaf.F90 U_prepoststep] (Call to act on the forecast ensemble, called with negative value of the time step)
     286 1. [#U_init_dim_obsinit_dim_obs_pdaf.F90 U_init_dim_obs]
     287 1. [#U_obs_opobs_op_pdaf.F90 U_obs_op] (`dim_ens` calls: one call for each ensemble member)
     288 1. [#U_localizelocalize_covar_pdaf.F90 U_localize]
     289 1. [#U_add_obs_erradd_obs_err_pdaf.F90 U_add_obs_err]
     290 1. [#U_init_obsinit_obs_pdaf.F90 U_init_obs]
     291 1. [#U_init_obscovarinit_obscovar_pdaf.F90 U_init_obscovar]
     292 1. [#U_obs_opobs_op_pdaf.F90 U_obs_op] (`dim_ens` calls: one call for each ensemble member, repeated to reduce storage)
     293 1. [#U_prepoststepprepoststep_ens_pdaf.F90 U_prepoststep] (Call to act on the analysis ensemble, called with (positive) value of the time step)
     294
     295In case of the routine `PDAF_assimilate_enkf`, the following routines are executed after the analysis step:
     296 1. [#U_distribute_statedistribute_state_pdaf.F90 U_distribute_state]
     297 1. [#U_next_observationnext_observation_pdaf.F90 U_next_observation]
     298