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 | Loop fusion (continuation of the 2020WP/HPC-09_epico_Loop_fusion work ) |
|---|---|
| PI(S) | Francesca Mele, Italo Epicoco |
| Digest | Complete the 'loop fusion' optimization tecnique implementation of the remaining routines from the most computing intensive towards the less computing intensive one. |
| Dependencies | Communications cleanup |
| Branch | source:/NEMO/branches/{YEAR}/dev_r{REV}_{ACTION_NAME} |
| Previewer(s) | TBD |
| Reviewer(s) | TBD |
| Ticket | #2608 |
Description
As the loop fusion-optimization depends from the Communications cleanup work, the implementation of this action has been integrated in the NEMO/branches/2021/dev_r14393_HPC-03_Mele_Comm_Cleanup/ branch starting from the changeset [14801].
For the implementation details see https://forge.ipsl.jussieu.fr/nemo/wiki/2021WP/HPC-03_Mele_Comm_Cleanup.
Loop fusion optimization could be considered for the future through automatic code transformation, for example with the use of DSLs.
Implementation
...
Documentation updates
...
Preview
...
Tests
...
Review
...
