Implementing the Analysis Step using the universal interface of PDAF3 with g2l/l2g_state

Overview

This page describes the recommended implementation of the local analysis step using the universal routines of the PDAF3 interface in the variant where the provides routines for transfer between global and local state vectors (g2l_state_pdaf/l2g_state_pdaf) in local filters.

We recommend to only use this variant only for porting previous implementations that used PDAFomi_ interface routines from PDAF2. Otherwise, we recommend to use the implementation using the using the universal routines of the PDAF3 interface.

PDAF3 provides universal routines for the analysis step, which only distinguish whether the online or offline mode is used.

For the analysis step we need different operations related to the observations. These operations are requested by PDAF by call-back routines supplied by the user and provided in the observation modules using PDAF-OMI. The names of the routines that are provided by the user are specified in the call to the assimilation routine PDAF3_assimilate_local.

For completeness we discuss here all user-supplied routines that are specified as arguments in the assimilation routines.

Assimilation routines

PDAF3_assimilate_local

This routine is used both in the fully-parallel and the flexible implementation variants of the data assimilation system. (See the page Modification of the model code for the ensemble integration for these variants)

The interface for the routine PDAF3_assimilate_local contains names for routines that operate on the local analysis domains (marked by the suffix _l). Here, we list the full interface of the routine. Subsequently, the user-supplied routines specified in the call are explained.

The universal interface is the following:

  SUBROUTINE PDAF3_assimilate_local(collect_state_pdaf, distribute_state_pdaf, &
                init_dim_obs_pdafomi, obs_op_pdafomi, &
                init_n_domains_pdaf, init_dim_l_pdaf, init_dim_obs_l_pdafomi, &
                g2l_state_pdaf, l2g_state_pdaf, &
                prepoststep_pdaf, next_observation_pdaf, status)

with the following arguments:

• Routines to transfer between model fields and state vector:
  • collect_state_pdaf:
    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.
  • 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. (The same routine is also used in PDAF_init_forecast.)
• Observation routines using PDAF-OMI:
  • init_dim_obs_pdafomi:
    The name of the user-supplied routine that initializes the observation information and provides the size of observation vector
  • obs_op_pdafomi:
    The name of the user-supplied routine that acts as the observation operator on some state vector
• Routines only used for localization:
  • init_n_domains_pdaf:
    The name of the routine that provides the number of local analysis domains
  • init_dim_l_pdaf:
    The name of the routine that provides the state dimension for a local analysis domain
  • init_dim_obs_l_pdafomi:
    The name of the routine that initializes the size of the observation vector for a local analysis domain and the index arrays used to map between the global state vector and the local state vector.
  • g2l_state_pdaf: The name of the routine that initializes a local state vector from the global state vector
  • l2g_state_pdaf: The name of the routine that initializes the corresponding part of the global state vector from the provided local state vector
• Prepoststep and initialization for next forecast phase
  • prepoststep_pdaf:
    The name of the pre/poststep routine as in PDAF_init_forecast. (The same routine is also used in PDAF_init_forecast.)
  • next_observation_pdaf:
    The name of a user supplied routine that initializes the variables nsteps, timenow, and doexit. (The same routine is also used in PDAF_init_forecast.)
• Status flag
  • status:
    The integer status flag. It is zero, if the routine is exited without errors.

Note:

• The order of the routine names does not show the order in which these routines are executed. See the section on the order of the execution at the bottom of this page.

PDAF3_assim_offline_local

For the offline mode of PDAF, the routine PDAF3_assim_offline_local is used to perform the analysis step. The interface of the routine is identical with that of PDAF3_assimilate_local, except that the user-supplied routines U_distribute_state, U_collect_state and U_next_observation are missing.

The interface is:

  SUBROUTINE PDAF3_assim_offline_local( &
                init_dim_obs_pdafomi, obs_op_pdafomi, &
                init_n_domains_pdaf, init_dim_l_pdaf, init_dim_obs_l_pdafomi, &
                g2l_state_pdaf, l2g_state_pdaf, &
                prepoststep_pdaf, status)

PDAF3_put_state_local

This routine exists for backward-compatibility. In implementations that were done before the release of PDAF V3.0, a 'put_state' routine was used for the flexible parallelization variant and for the offline mode. When the 'flexible' implementation variant is chosen for the assimilation system, the routine. The routine PDAF3_put_state_local allows to port such implemnetations to the PDAF3 interface with minimal changes. The interface of the routine is identical with that of PDAF3_assimilate_local, except that the user-supplied routines U_distribute_state and U_next_observation are missing.

The interface when using one of the local filters is the following:

  SUBROUTINE PDAF3_put_state_local(collect_state_pdaf, &
                init_dim_obs_pdafomi, obs_op_pdafomi, &
                init_n_domains_pdaf, init_dim_l_pdaf, init_dim_obs_l_pdafomi, &
                g2l_state_pdaf, l2g_state_pdaf, &
                prepoststep_pdaf, status)

User-supplied routines

Here, all user-supplied routines are described that are required in the call to PDAF3_assimilate_local, PDAF3_assim_offline_local or PDAF3_put_state_local. For some of the generic routines, we link to the page on modifying the model code for the ensemble integration.

In the subroutine interfaces some variables appear with the suffix _p (short for 'process'). This suffix indicates that the variable is particular to a model sub-domain, if a domain decomposed model is used. In addition, there will be variables with suffix _l (indicating 'local').

Call-back routines that end on _pdaf are regular call-back routines from the core part of PDAF, while call-back routines that end on _pdafomi handle observations within PDAF-OMI.

collect_state_pdaf (collect_state_pdaf.F90)

This routine is independent of the filter algorithm used.

See the page on modifying the model code for the ensemble integration for the description of this routine.

distribute_state_pdaf (distribute_state_pdaf.F90)

This routine is independent of the filter algorithm used.

See the page on modifying the model code for the ensemble integration for the description of this routine.

init_dim_obs_pdafomi (callback_obs_pdafomi.F90)

This is a call-back routine initializing the observation information. The routine just calls a routine from the observation module for each observation type.

See the documentation on callback_obs_pdafomi.F90 for more information.

obs_op_pdafomi (callback_obs_pdafomi.F90)

This is a call-back routine applying the observation operator to the state vector. The routine calls a routine from the observation module for each observation type.

See the documentation on callback_obs_pdafomi.F90 for more information.

init_n_domains_pdaf (init_n_domains_pdaf.F90)

This routine is only used for localization. It is called during the analysis step before the loop over the local analysis domains is entered. It has to provide the number of local analysis domains. In case of a domain-decomposed model, the number of local analysis domain for the model sub-domain of the calling process has to be initialized.

The interface for this routine is:

SUBROUTINE init_n_domains_pdaf(step, n_domains_p)

  INTEGER, INTENT(in)  :: step        ! Current time step
  INTEGER, INTENT(out) :: n_domains_p ! Number of analysis domains for local model sub-domain

Hints:

• As a simple case, if the localization is only performed horizontally, the local analysis domains can be single vertical columns of the model grid. In this case, n_domains_p is simply the number of vertical columns in the process-local model sub-domain.

init_dim_l_pdaf (init_dim_l_pdaf.F90)

This routine is only used for localization.

The interface for this routine is:

SUBROUTINE init_dim_l_pdaf(step, domain_p, dim_l)

  INTEGER, INTENT(in)  :: step        ! Current time step
  INTEGER, INTENT(in)  :: domain_p    ! Current local analysis domain
  INTEGER, INTENT(out) :: dim_l       ! Local state dimension

The routine is called during the loop over the local analysis domains in the analysis step.

It provides in dim_l the dimension of the state vector for the local analysis domain with index domain_p to PDAF.

In the recommended implementation shown in the tutorial and template codes, there are two further initializations:

1. The routine can initialize the index array id_lstate_in_pstate containing the indices of the elements of the local state vector in the global (or domain-decomposed) state vector. This is shared with g2l_state_pdaf and l2g_state_pdaf via the module mod_assimilation. (In the implementation of the analysis using PDAFlocal one would provide this array directly to PDAF)
2. The routine initializes an array coords_l containing the coordinates of the local analysis domain. This is shared with U_init_dim_obs_l_pdafomi via the module mod_assimilation.

Hints:

• The coordinates in coords_l have to describe one location in space that is used for localization to compute the distance from observations.
• The coordinates in coords_l have the same units as those used for the observations
• For geographic distance computations, the unit of the coordinates needs to be radian, thus (0, 2*pi) or (-pi,pi) for longitude and (-pi/2, pi/2) for latitude.
• Any form of local domain is possible as long as it can be describe as a single location.
• If the local domain is a single grid point, dim_l will be the number of model variables at this grid point.
• The local analysis domain can also be a single vertical column of the model grid if observations are only horizontally distributed (a common situation with satellite data in the ocean).
  • In this case, dim_l will be the number of vertical grid points at this location times the number of model fields that exist in the vertical, plus possible variables at e.g. the surface.
  • In this case only the horizontal coordinates are used in coords_l.

Hint for id_lstate_in_pstate:

• The initialization of the index vector id_lstate_to_pstate is analogous to a loop that directly performs the initialization of a local state vector. However, here only the indices are stored. If this looks to complicated, one can implement the indexing directly in g2l_state_pdaf and l2g_state_pdaf. However, this is likely less efficient.

init_dim_obs_l_pdafomi (callback_obs_pdafomi.F90)

This routine is only used for localization. It is a call-back routine for PDAF-OMI that initializes the local observation vector. The routine calls a routine from the observation module for each observation type.

See the documentation on callback_obs_pdafomi.F90 for more information.

g2l_state_pdaf (g2l_state_pdaf.F90)

The interface for this routine is:

SUBROUTINE g2l_state_pdaf(step, domain_p, dim_p, state_p, dim_l, state_l)

  INTEGER, INTENT(in) :: step           ! Current time step
  INTEGER, INTENT(in) :: domain_p       ! Current local analysis domain
  INTEGER, INTENT(in) :: dim_p          ! State dimension for model sub-domain
  INTEGER, INTENT(in) :: dim_l          ! Local state dimension
  REAL, INTENT(in)    :: state_p(dim_p) ! State vector for model sub-domain 
  REAL, INTENT(out)   :: state_l(dim_l) ! State vector on local analysis domain

The routine is called during the loop over the local analysis domains in the analysis step. It has to provide the local state vector state_l that corresponds to the local analysis domain with index domain_p. Provided to the routine is the state vector state_p. With a domain decomposed model, this is the state for the local model sub-domain.

Hints:

• In the simple case that a local analysis domain is a single vertical column of the model grid, the operation in this routine would be to take out of state_p the data for the vertical column indexed by domain_p.
• We recommend to use the index array id_lstate_in_pstate, which can be initialized in init_dim_l_pdaf. The array holds the indices of the local state vector elements in the global state vector.
• We generally recommend to implement the analysis step using PDAFlocal. In this case the routine g2l_state_pdaf is not present and PDAF performs its operations internally.

l2g_state_pdaf (l2g_state_pdaf.F90)

The interface for this routine is:

SUBROUTINE l2g_state_pdaf(step, domain_p, dim_l, state_l, dim_p, state_p)

  INTEGER, INTENT(in) :: step           ! Current time step
  INTEGER, INTENT(in) :: domain_p       ! Current local analysis domain
  INTEGER, INTENT(in) :: dim_p          ! State dimension for model sub-domain
  INTEGER, INTENT(in) :: dim_l          ! Local state dimension
  REAL, INTENT(in)    :: state_p(dim_p) ! State vector for model sub-domain 
  REAL, INTENT(out)   :: state_l(dim_l) ! State vector on local analysis domain

The routine is called during the loop over the local analysis domains in the analysis step. It has to initialize the part of the global state vector state_p that corresponds to the local analysis domain with index domain_p. Provided to the routine is the state vector state_l for the local analysis domain.

Hints:

• In the simple case that a local analysis domain is a single vertical column of the model grid, the operation in this routine would be to write into state_p the data for the vertical column indexed by domain_p.
• We recommend to use the index array id_lstate_in_pstate, which can be initialized in init_dim_l_pdaf. The array holds the indices of the local state vector elements in the global state vector.
• We generally recommend to implement the analysis step using PDAFlocal. In this case the routine g2l_state_pdaf is not present and PDAF performs its operations internally.

prepoststep_pdaf (prepoststep_ens_pdaf.F90)

The routine has already been described for modifying the model for the ensemble integration and for inserting the analysis step.

See the page on modifying the model code for the ensemble integration for the description of this routine.

next_observation_pdaf (next_observation_pdaf.F90)

This routine is independent of the filter algorithm used.

See the page on modifying the model code for the ensemble integration for the description of this routine.

Execution order of user-supplied routines

The user-supplied routines are executed in the order listed below. The order can be important as some routines can perform preparatory work for routines executed later on during the analysis. For example, in init_dim_l_pdaf we can prepare the index array that provides the information how to localize a global state vector.

Before the analysis step is called the following is executed by PDAF3_assimilate_local and PDAF3_put_state_local:

1. collect_state_pdaf (called once for each ensemble member)
2. prepoststep_pdaf (Call to act on the forecast ensemble, called with negative value of the time step)

At the analysis time, the observations are initialized by the routines:

1. init_dim_obs_pdafomi
2. obs_op_pdafomi (Called dim_ens times; once for each ensemble member)

Now the analysis step is entered and the number of local analysis domain is initialized by calling:

1. init_n_domains_pdaf

In the loop over all local analysis domains, it is executed for each local analysis domain:

1. init_dim_l_pdaf
2. g2l_state_pdaf
3. U_init_dim_obs_l_pdafomi
4. l2g_state_pdaf

After the loop over all local analysis domains, it is executed:

1. prepoststep_pdaf (Call to act on the analysis ensemble, called with (positive) value of the time step)

In case of the routine PDAF3_assimilate_local, the following routines are executed after the analysis step:

1. distribute_state_pdaf
2. next_observation_pdaf