Development page

Please only use the pages that are directly linked from the start page and within the Implementation Guide

Pages linked here are under development

EGU 2023

MarDATA_DA_2024

New for PDAF V3

IncrementalAnalysisUpdates

PDAF_iau_init

PDAF_iau_init_inc

PDAF_iau_reset

PDAF_iau_set_weights

PDAF_iau_set_pointer

PDAF_iau_add_inc

PDAF_set_iparam

PDAF_set_rparam

PDAF_localfilter

PDAF_local_type

PDAFomi_set_localize_covar

PDAF_diag_ensmean PDAF_diag_stddev_nopmi PDAF_diag_stddev PDAF_diag_variance_nompi PDAF_diag_variance

PDAF_diag_compute_moments

PDAFomi_set_obs_diag PDAFomi_diag_nobs PDAFomi_diag_dimobs PDAFomi_diag_get_obs PDAFomi_diag_get_HXmean PDAFomi_diag_get_HX PDAFomi_diag_obs_rmsd PDAFomi_diag_stats

Porting to PDAF-3

• PDAF_interfaces_module now named PDAF; mandatory to use
• subtype=5 for specifying the offline mode was removed; use PDAF_set_offline_mode
• additional parameter in PDAF_assimilate_lnetf and PDAF_put_state_lnetf
• porting from PDAFomi to PDAF3 for global filters: Just change the name of the routine
• porting from PDAFlocalomi to PDAF3 for local filters: Just change the name of the routine
• porting from PDAFomi to PDAF3 for local filters: The PDAF3 interface uses PDAFlocal so that the routines g2l_state_pdaf and l2g_state_pdaf are not present. Follow the implementation guide for init_dim_l to initialize the information for PDAFlocal
• porting from classical PDAF interface with fully specification of all call-back routines: See implementation guide (PDAF3 uses both PDAF-OMI and PDAF-local to provide compact interfaces)
• porting from PDAFomi or PDAFlocalomi for 3D-Var: Change the name of the routine
• check subtype: 0 and 1 are unchanged; for others: 2=>10, 3=>11, 4=>2, 6=>3, 7=>4
• the option to run the offline mode as 'subtype=5' was removed. It is now require to call "PDAF_set_offline_mode"