Changes between Version 2 and Version 3 of PDAF_set_debug_flag

Timestamp:

Jun 10, 2025, 9:21:51 AM (7 days ago)

Author:

lnerger

Comment:

--

PDAF_set_debug_flag

@@ -17 +17 @@
 
 '''Notes: '''
- * To enable syntax checking one can include the interface defintion from 'PDAF_interfaces_module'. For this one has to use-include the routine by 
-{{{
-  USE PDAF_interfaces_module, only: PDAF_set_debug_flag
-}}}
  * For the localized filters, we recommend to activate the debugging only for single local analysis domain. Thus one can select some value of `domain_p`, e.g. in `init_dim_l_pdaf` and then call `PDAF_set_debug_flag` using `debugval=domain_p`, thus
 {{{
@@ -34 +30 @@
  * For the global filters only the first 6 elements of state vectors are shown in order to keep the outputs compact.
  * When implementing an application with PDAF it can be useful to activate the debug output in `init_pdaf` so that debug output from `PDAF_init` is shown. In particular one can see whether the input parameters or ensemble states have their correct values inside PDAF. If this is not the case, it might be that PDAF and the use code are compiled with different precision of the floating point (REAL) variables. 
+ * For PDAF 2: To enable syntax checking one can include the interface defintion from 'PDAF_interfaces_module'. For this one has to use-include the routine by 
+{{{
+  USE PDAF_interfaces_module, only: PDAF_set_debug_flag
+}}}