| 8 | {{{ |
| 9 | SUBROUTINE distribute_state_pdaf(dim_p, state_p) |
| 10 | }}} |
| 11 | with |
| 12 | * `dim_p` : `integer, intent(in)`[[BR]] Size of the provided state vector |
| 13 | * `state_p`: `real, intent(inout), dimension(dim_p)`[[BR]] State vector for process-local model sub-domain |
| 14 | |
| 15 | Notes: |
| 16 | * When the routine is called a state vector `state_p` and its size `dim_p` are provided. As the user has defined how the model fields are stored in the state vector, one can initialize the model fields from this information. |
| 17 | * If the model is not parallelized, `state_p` will contain a full state vector. If the model is parallelized using domain decomposition, `state_p` will contain the part of the state vector that corresponds to the model sub-domain for the calling process. |
| 18 | * The operations performed in `distribute_state_pdaf` and `collect_state_pdaf` are the inverse operations of each other. |
| 19 | * The routine is executed by all processes that belong to model tasks. |
| 20 | |
| 21 | Some hints: |
| 22 | * If the state vector does not include all model fields, it can be useful to keep a separate array to store those additional fields. This array has to be kept separate from PDAF, but can be defined using a module like `mod_assimilation`. |
| 23 | |