Name and subject of the action
Last edition: Wikinfo(changed_ts)? by Wikinfo(changed_by)?
The PI is responsible to closely follow the progress of the action, and especially to contact NEMO project manager if the delay on preview (or review) are longer than the 2 weeks expected.
Summary
| Action | Halo Management tool |
|---|---|
| PI(S) | Italo Epicoco, Francesca Mele |
| Digest | This task concerns the development of an Halo Management tool to provide the use of different halo sizes (>2) for some NEMO Kernel that can benefit of it |
| Dependencies | Communications cleanup |
| Branch | source:/NEMO/branches/{YEAR}/dev_r{REV}_{ACTION_NAME} |
| Previewer(s) | TBD |
| Reviewer(s) | TBD |
| Ticket | #2610 |
Description
The halo management tool aims to provide the possibility to use different halo sizes for different NEMO Kernels that can benefit of it, i.e. in the dynspg_ts routine it could be convenient to enlarge the halo region (from 3 up to 5 lines or more) to reduce the communication steps in the time sub-stepping loop.
In a wider halo region the overall communication costs reduce but the computation costs grow. However, the use of an extended halo is required to efficiently use the tiling approach.
The activities carried out this year have been manly linked to the analysis and evaluation of the cost/benefit ratio and bug-fixes.
Implementation
...
Documentation updates
...
Preview
...
Tests
...
Review
...
