| 55 | | We recommend to use X=3 for optimizing the user routines. The output will look like |
| | 55 | We recommend to use X=3 for optimizing the user routines. With PDAF-OMI, the output will look like |
| | 56 | {{{ |
| | 57 | PDAF PDAF Timing information - call-back routines |
| | 58 | PDAF ---------------------------------------------------- |
| | 59 | PDAF Initialize PDAF: 0.078 s |
| | 60 | PDAF init_ens_pdaf: 0.077 s |
| | 61 | PDAF Ensemble forecast: 0.003 s |
| | 62 | PDAF MPI communication in PDAF: 0.000 s |
| | 63 | PDAF distribute_state_pdaf: 0.001 s |
| | 64 | PDAF collect_state_pdaf: 0.000 s |
| | 65 | PDAF LESTKF analysis: 25.183 s |
| | 66 | PDAF PDAF-internal operations: 24.762 s |
| | 67 | PDAF OMI-internal routines: 0.001 s |
| | 68 | PDAF init_n_domains_pdaf: 0.000 s |
| | 69 | PDAF init_dim_l_pdaf: 0.001 s |
| | 70 | PDAF g2l_state_pdaf: 0.001 s |
| | 71 | PDAF l2g_state_pdaf: 0.014 s |
| | 72 | PDAF Time in OMI observation module routines |
| | 73 | PDAF init_dim_obs_pdafomi: 0.001 s |
| | 74 | PDAF obs_op_pdafomi: 0.003 s |
| | 75 | PDAF init_dim_obs_l_pdafomi: 0.002 s |
| | 76 | PDAF prepoststep_pdaf: 0.017 s |
| | 77 | }}} |
| | 78 | This output will show you in which routine most time is spent. If it is a call-back routine, you have the possibility to check for optimizations to this routine to speed up the computation. If most time is spend inside PDAF, as in the example, you can't further optimize. |
| | 79 | |
| | 80 | The OMI-specific output shown above was introduced with PDAF V2.2.1. In older versions of PDAF, or when OMI is not used, more user-provided call-back routines are used. In this case, the output will look like |
