List of discussion points for SC 2025¶

This list is supposed to serve as a basis for a first, maybe informal, discussion between the PIs of HAMMOZ

Summary of the current status:

Finland: stand-alone full HAM and its implementations into OpenIFS, EC-Earth and CAMS, in the future stand-alone HAMlite and implementation into km-scale IFS

Oxford: HAMlite with very different code since unnecessary parts of the code have been abandoned. Ported to GPU.

TROPOS: ICON-HAMlite-LAM based on the NextGEMS version of the Oxford group stored in the DKRZ repository. Post- and pre-processing tools stored locally (git repo).

Developments done in ECHAM6-HAM (e.g., tagged tracers, marine organic aerosol emission, mineralogy in the dust scheme) not merged, residing in local repositories at the institutes.

List of questions and issues to be discussed by the SC:

There is a wake-up call needed...
Is there a desire to get the different developments back to a common project (both in the sense of a community and technically in a repository)?
If yes, how much manpower can be allocated to the associated tasks? (Revisit list of tasks that was provided when the responsibility was handed over from ETH to TROPOS. 1.5 FTE at ETH vs 0.5 at the moment)
Is it feasible to organise funding for a project to re-integrate the diverging developments?
Is there a strategy to feed developments back into the common project (incl. on-going ECHAM-HAM devs)? How can we organize ourselves, also technically, to supoort this process of (re-)mirgation?
Is there a desire to keep the MOZ part alive, also with regard to a broader user base, and how should we tackle this (actively contact chemistry modellers)?
How can we make HAMMOZ more independent from or more flexible to react to ICON developments (support CommIn implementation)?