---
# System prepended metadata

title: Software infrastructure for EXCLAIM blue track
tags: [functional cycle 12]

---

# Software infrastructure for EXCLAIM blue track

###### tags: `functional cycle 12`


Developers: Jonas (C2SM), Abishek

Appetite: half cycle?

## Background


By "blue track", we mean the version of `icon-exclaim` that is based on Fortran + OpenACC, with the exception of the dycore, which will feature ICON4Py stencils. i.e. The main dycore driver itself will be based on Fortran + ACC, but with wrapper calls to ICON4Py stencils. The wrapper calls may be replaced by DSL preprocessor directives in the coming months.

In the near future, we will similarly replace the tracer advection, microphysics and turbulence components with their ICON4Py equivalents.

![](https://i.imgur.com/DZjM1yV.png)




## Goals

- Establish software dependencies for running the blue track on Daint
- Establish CI pipelines for Daint
- Incorporate Spack in the build process





## Tasks

- [ ] Install dependencies on Daint, now only Tsa. **(C2SM?)**
    - [ ] Install Python 3.10 and 3.8 (for Dusk/Dawn)
    - [ ] Okay to move from GCC 8.3.0 -> GCC 9.3.0?
- [ ] Better Spack build process
- [ ] Setup jenkins CI for Daint (save for last)
    - [ ] CI for nightly and PR builds + tests
    - [ ] CI for probtest reference data generation

## Future goals:
- Remove dusk/dawn
    - move and clean some dawn headers
    - use spack everywhere
- Establish software on Manali
