Changes between Version 1 and Version 2 of PDAFomi_diag_get_obs

Timestamp:

Mar 23, 2025, 8:31:24 AM (9 days ago)

Author:

lnerger

Comment:

--

PDAFomi_diag_get_obs

@@ -9 +9 @@
 The interface is the following: 
 {{{
-  SUBROUTINE PDAFomi_diag_get_obs(id_obs, dim_obs_diag, ncoord, obs_p_ptr, ocoord_p_ptr)
+  SUBROUTINE PDAFomi_diag_get_obs(id_obs, dim_obs_p_diag, ncoord, obs_p_ptr, ocoord_p_ptr)
 }}}
 with the following arguments:
 {{{
     INTEGER, INTENT(in) :: id_obs                    ! Index of observation type to return
-    INTEGER, INTENT(out) :: dim_obs_diag             ! Observation dimension
+    INTEGER, INTENT(out) :: dim_obs_p_diag           ! Observation dimension
     INTEGER, INTENT(out) :: ncoord                   ! Number of observation dimensions
     REAL, POINTER, INTENT(out) :: obs_p_ptr(:)       ! Pointer to observation vector
@@ -22 +22 @@
 
 **Notes:**
- * In Fortran user code the obsevation pointer should be declared in the form[[BR]] `REAL, POINTER :: obs_p_ptr(:)`[[BR]] It does not need to be allocated
- * In Fortran user code the obsevation pointer should be declared in the form[[BR]] `REAL, POINTER :: ocoord_p_ptr(:,:)`[[BR]] It does not need to be allocated
+ * In case of a parallelized model, the vector obs_p_prt and the array ocoord_p_prt contain the values for the process-sub-domain of the calling processor.
+ * In Fortran user code the obsevation pointer should be declared in the form[[BR]] `REAL, POINTER :: obs_p_ptr(:)`[[BR]] It does not need to be allocated. The target vector has the length `dim_obs_p_diag`.
+ * In Fortran user code the obsevation pointer should be declared in the form[[BR]] `REAL, POINTER :: ocoord_p_ptr(:,:)`[[BR]] It does not need to be allocated. The target array has the size `(ncoord, dim_obs_p_diag)`.
  * If the observation diagnostics have not be activated by using [wiki:PDAFomi_set_obs_diag] the pointers will not be set and `dim_obs_diag=0` and `ncoord=0` will be returned. These values canbe checked before assessing the pinter arrays
  * The array `ocoord_p_ptr(:,:)` is organized as in the observation modules:
    * First index: index of different coordinate directions for observation specified by the second index
-   * Second index: ID of the observation
+   * Second index: index of the observation