Changes between Version 3 and Version 4 of PDAF_gather_obs_f2

Timestamp:

Dec 20, 2017, 5:54:10 PM (7 years ago)

Author:

lnerger

Comment:

--

PDAF_gather_obs_f2

@@ -14 +14 @@
 }}}
 with the following arguments:
- * `coords_obs_p` : `real, intent(in)`[[BR]] Process-local observation coordinates array
- * `coords_obs_f` : `real, intent(out)`[[BR]] Full observation coordinates array
+ * `coords_obs_p` : `real, intent(in), dimension(nrows, dim_obs_p)`[[BR]] Process-local observation coordinates array
+ * `coords_obs_f` : `real, intent(out), dimension(nrows, dim_obs_f)`[[BR]] Full observation coordinates array
  * `nrows` : `integer, intent(in)`[[BR]] Number of rows in observation coordinates array
  * `status` : `integer, intent(out)`[[BR]] Status flag (0 for no error)
 
 Notes:
- * The routine `PDAF_gather_dim_obs_f` has to be called once before using `PDAF_gather_obs_f` because it internally initializes the local observation dimensions for gathering. The most recent call to `PDAF_gather_dim_obs_f` defines the dimensions used here.
+ * The routine `PDAF_gather_dim_obs_f` has to be called once before using `PDAF_gather_obs_f` because it internally initializes the local observation dimensions for gathering. The most recent call to `PDAF_gather_dim_obs_f` defines the dimensions `dim_obs_p` and `dim_obs_f` used here.
  * The routine is used for a coordinate array which stores in each column the coordinates of one observation. Thus for a two-dimensional case, the size of `coords_obs_p` is `(2, dim_obs_p)` and `nrows=2` is used in the call to `PDAF_gather_obs_f2`.
  * If the coordindates are stored so that each row of `coords_obs_p` holds the coordinates of one observation the routine `PDAF_gather_obs_f` should be applied separate for each column to gather the full coordinates array.