| 162 | | * For sharing through the module 'mod_assimilation', we further initialize and array 'coords_l' containing the coordinates that describe the local domain. These coordinates have to describe one location in space and is used in the OMI observation modules to compute the distance from observations. |
| 163 | | * Any form of local domain is possible as long as it can be describe as a single location. If observations are only horizontally distributes (a common situation with satellite data in the ocean), the local analysis domain can be single vertical column of the model grid. In this case, the size of the state in the local analysis domain will be just the number of vertical grid points at this location and the horizontal coordinates are used in 'coords_l' |
| 164 | | * Further, we recommend to initialize an array containing the indices of the elements of the local state vector in the global (or domain-decomposed) state vector (`id_lstate_in_pstate` in the template |
| | 162 | * For sharing through the module 'mod_assimilation', we further initialize an array 'coords_l' containing the coordinates that describe the local domain. These coordinates have to describe one location in space that is used in the OMI observation modules to compute the distance from observations. |
| | 163 | * Any form of local domain is possible as long as it can be describe as a single location. If observations are only horizontally distributed (a common situation with satellite data in the ocean), the local analysis domain can be a single vertical column of the model grid. In this case, the size of the state in the local analysis domain will be just the number of vertical grid points at this location and the horizontal coordinates are used in 'coords_l' |
| | 164 | * Further, we recommend to initialize an array containing the indices of the elements of the local state vector in the global (or domain-decomposed) state vector (`id_lstate_in_pstate` in the template files). This array is also shared through 'mod_assimilation'. |
