Changes between Version 3 and Version 4 of PDAFlocal_overview


Ignore:
Timestamp:
Sep 9, 2024, 4:15:17 PM (2 months ago)
Author:
lnerger
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • PDAFlocal_overview

    v3 v4  
    138138||= En3DVar =|| [wiki:PDAFlocal_assimilate_en3dvar_lestkf] || [wiki:PDAFlocal_put_state_en3dvar_lestkf] ||
    139139||= Hyb3DVar =|| [wiki:PDAFlocal_assimilate_hyb3dvar_lestkf] || [wiki:PDAFlocal_put_state_hyb3dvar_lestkf] ||
     140
     141== Porting to PDAFlocal ==
     142
     143If you like to port you existing code to using PDAFlocal, the steps are the following
     1441. Change the call to the analysis routine from `PDAFomi_` to `PDAFlocalomi_` (or `PDAF_` to `PDAFlocal_` for non-OMI implementations)
     1451. Remove `g2l_state_pdaf` and `l2g_state_pdaf` from the interface of the `PDAFlocalomi_`
     146 routine
     1471. In `init_dim_l_pdaf` ensure that the index array for the mapping between the global and local state vectors is implemented (this should exist if the implementation followed the tutorial and templates where it is the array `id_lstate_in_pstate`).
     1481. Insert the call to `PDAFlocal_set_indices`.
     149
     150After these steps it should be possible to recompile and run. If this was successful, one can safely remove the files holding `g2l_state_pdaf` and `l2g_state_pdaf`.