| 1 | = obs_op_pdaf = |

| 2 | |

| 3 | The page document the user-supplied call-back routine `obs_op_pdaf`. |

| 4 | |

| 5 | The routine `obs_op_pdaf` (called `U_obs_op` inide the PDAF core routines) is a call-back routine that has to be provided by the user. The routine is used with all global filters. The purpose of the routine is to apply the observation operator to the state vector provided by PDAF when the routine is called. The routine is called during the filter analysis step. |

| 6 | |

| 7 | The interface is the following: |

| 8 | {{{ |

| 9 | SUBROUTINE obs_op_pdaf(step, dim_p, dim_obs_p, state_p, m_state_p) |

| 10 | }}} |

| 11 | with |

| 12 | * `step` : `integer, intent(in)`[[BR]] Current time step |

| 13 | * `dim_p` : `integer, intent(in)`[[BR]] Size of state vector (local part in case of parallel decomposed state) |

| 14 | * `dim_obs_p` : `integer, intent(in)`[[BR]] Size of observation vector |

| 15 | * `state_p` : `real, intent(in), dimension(dim_p)`[[BR]] Model state vector |

| 16 | * `m_state_p` : `real, intent(out), dimension(dim_obs_p)`[[BR]] Observed state vector (i.e. the result after applying the observation operator to `state_p`) |

| 17 | |

| 18 | Notes: |

| 19 | * For 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. |

| 20 | |

| 21 | Hint: |

| 22 | * If domain-decomposition is used and the observation operator involves a global operation, e.g. some global integration, one has to gather the information from the other model domains using MPI communication. |