Context Navigation

Changes between Version 16 and Version 17 of ImplementAnalysisseek

v16	v17
85	85	Here, all user-supplied routines are described that are required in the call to `PDAF_assimilate_seek`. For some of the generic routines, we link to the page on [ModifyModelforEnsembleIntegration modifying the model code for the ensemble integration].
86	86
87		To indicate user-supplied routines we use the prefix `U_`. In the t~~emplate directory `templates/` as well as in the example implementation in `testsuite/src/dummymodel_1D` these routines exist without the prefix, but with the extension `_pdaf.F90`~~. In the section titles below we provide the name of the template file in parentheses.
	87	To indicate user-supplied routines we use the prefix `U_`. In the tutorials in `tutorial/` and in the template directory `templates/` these routines exist without the prefix, but with the extension `_pdaf`. The files are named correspondingly. In the section titles below we provide the name of the template file in parentheses.
88	88
89	89	In the subroutine interfaces some variables appear with the suffix `_p`. This suffix indicates that the variable is particular to a model sub-domain, if a domain decomposed model is used. Thus, the value(s) in the variable will be different for different model sub-domains.