| 1 | = PDAF_iau_init = |
| 2 | |
| 3 | This page documents the routine `PDAF_iau_init` of PDAF, which was introduced with PDAF V3.0. |
| 4 | |
| 5 | This routine initializes parameters for incremental analysis updating, IAU. It further allocates the array in which the ensmelbe increments are stored. This array exists on all processes that are model tasks |
| 6 | |
| 7 | The routine is usually called in init_pdaf after the initialization of PDAF in PDAF_init. |
| 8 | |
| 9 | |
| 10 | The interface is the following: |
| 11 | {{{ |
| 12 | SUBROUTINE PDAF_iau_init(type_iau, nsteps_iau, flag) |
| 13 | }}} |
| 14 | with the following arguments: |
| 15 | {{{ |
| 16 | INTEGER, INTENT(in) :: type_iau !< Type of IAU |
| 17 | !< (0) no IAU |
| 18 | !< (1) constant increment weight 1/nsteps_iau |
| 19 | !< (2) Linear IAU weight with maximum in middle of IAU period |
| 20 | !< (3) Zero weights for null mode (can be used to apply IAU on user side) |
| 21 | INTEGER, INTENT(in) :: nsteps_iau !< number of time steps in IAU |
| 22 | INTEGER, INTENT(out) :: flag !< Status flag |
| 23 | }}} |
| 24 | |
| 25 | Hints: |
| 26 | * type_iau=2 is linearly increasing and decreasing similar to what is used in the ocean model NEMO. Thi sis usually used if the IAU is applied in re-running over the previous observation phase |
| 27 | * type_iau=3 stores the increment information, but does not apply the increment. This permits to apply the increment in user-provided code. For this `PDAF_iau_set_pointer` can be used to assess the increment array within PDAF. |