Changes between Version 2 and Version 3 of PDAFomi_assimilate_lnetf_nondiagR
- Timestamp:
- Sep 8, 2024, 4:31:30 PM (5 weeks ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
PDAFomi_assimilate_lnetf_nondiagR
v2 v3 32 32 * `U_l2g_state`: The name of the routine that initializes the corresponding part of the global state vector from the provided local state vector 33 33 * `U_next_observation`: The name of a user supplied routine that initializes the variables `nsteps`, `timenow`, and `doexit`. The same routine is also used in `PDAF_get_state`. 34 * `status`: The integer status flag. It is zero, if `PDAFomi_assimilate_lnetf_nondiagR`is exited without errors.34 * `status`: The integer status flag. It is zero, if this routine is exited without errors. 35 35 36 36 Notes: … … 42 42 The user-supplied call-back routines are described on the page on [ImplementAnalysisLocal implementing the analysis step of the local filters]. 43 43 44 It is recommended that the value of `status_pdaf` is checked in the program after PDAFomi_assimilate_lnetf_nondiagRis executed. Only if its value is 0 the initialization was successful.44 It is recommended that the value of `status_pdaf` is checked in the program after this routine is executed. Only if its value is 0 the initialization was successful. 45 45 46 46 PDAF also has a [PdafSimplifiedInterface Simplified Interface] providing the routine `PDAFomi_assimilate_lnetf_nondiagR_si`. In the simplified interface, the name of the user-supplied routines have predefined names and do not appear in the call to `PDAFomi_assimilate_lnetf_nondiagR_si`. More information on the pre-defined names is provided in the [ImplementAnalysisLocal page on implementing the analysis step of the local filters].