Changes between Version 4 and Version 5 of IncrementalAnalysisUpdates
- Timestamp:
- Aug 21, 2025, 5:03:04 PM (12 days ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
IncrementalAnalysisUpdates
v4 v5 80 80 }}} 81 81 82 82 **Note:** 83 - (Added in the final release of PDAF V3.0): When using the EnOI modes (subtype 10 or 11), one has to set `dim_ens_l=1` and allocate `ens_inc` accordingly. Then `ens_inc` contains a single vector for the increment of the state vector. 83 84 84 85 == Change the IAU configuration == … … 136 137 === PDAF_iau_set_pointer === 137 138 138 With this routine the user can set a pointer to the PDAF-internal array of ensemble increments. This provides direct access to the increment array e.g. to analyze it or to write it into a file for restarting. The routine is different from `PDAF_iau_ set_inc` in that here the user obtains access to the internal IAU array, while in `PDAF_iau_set_inc` one can only overwrite the internal array.139 With this routine the user can set a pointer to the PDAF-internal array of ensemble increments. This provides direct access to the increment array e.g. to analyze it or to write it into a file for restarting. The routine is different from `PDAF_iau_init_inc` in that here the user obtains access to the internal IAU array, while in `PDAF_iau_init_inc` one can only overwrite the internal array. 139 140 140 141 The routine can be called by each single process, but it only provides a pointer to the process-local part of the increment array. For domain-decomposed models, this array only includes the state vector part for the process domain. In addition, it usually only contains a sub-ensemble unless one uses the flexible parallelization mode with a single model task. For the fully parallel mode, the process(es) of a single model task only hold a single ensemble state. … … 157 158 158 159 This routine is a replacement for `PDAF_iau_set_pointer` clarifying that it relates to the increment ensemble array. 159 With this routine the user can set a pointer to the PDAF-internal array of ensemble increments. This provides direct access to the increment array e.g. to analyze it or to write it into a file for restarting. The routine is different from `PDAF_iau_ set_inc` in that here the user obtains access to the internal IAU array, while in `PDAF_iau_set_inc` one can only overwrite the internal array.160 With this routine the user can set a pointer to the PDAF-internal array of ensemble increments. This provides direct access to the increment array e.g. to analyze it or to write it into a file for restarting. The routine is different from `PDAF_iau_init_inc` in that here the user obtains access to the internal IAU array, while in `PDAF_iau_init_inc` one can only overwrite the internal array. 160 161 161 162 The routine can be called by each single process, but it only provides a pointer to the process-local part of the increment array. For domain-decomposed models, this array only includes the state vector part for the process domain. In addition, it usually only contains a sub-ensemble unless one uses the flexible parallelization mode with a single model task. For the fully parallel mode, the process(es) of a single model task only hold a single ensemble state. … … 177 178 (This routine is added in the final PDAF V3.0 release, while it's not present in V3.0beta) 178 179 179 This routine is used in the EnOI modes (subtype 10 and 11) where only the state estimate is integrated. The routine allows the user to set a pointer to the PDAF-internal array of state vector increments. This provides direct access to the increment vector e.g. to analyze it or to write it into a file for restarting. The routine is different from `PDAF_iau_ set_inc` in that here the user obtains access to the internal IAU array, while in `PDAF_iau_set_inc` one can only overwrite the internal array.180 This routine is used in the EnOI modes (subtype 10 and 11) where only the state estimate is integrated. The routine allows the user to set a pointer to the PDAF-internal array of state vector increments. This provides direct access to the increment vector e.g. to analyze it or to write it into a file for restarting. The routine is different from `PDAF_iau_init_inc` in that here the user obtains access to the internal IAU array, while in `PDAF_iau_init_inc` one can only overwrite the internal array. 180 181 181 182 The routine can be called by each single process, but it only provides a pointer to the process-local part of the increment vector. For domain-decomposed models, this array only includes the state vector part for the process domain.