# DaCe knowledge transfer

## Which knowledge do we need to transfer

### gt4py.next

- not much to transfer, because doesn't go very deep
- Peter wrote most of the code so far
- later: for optimizations we can learn from DaCe people

### gt4py.cartesian

- graph is in nice structure (GPU-nice)
- building the pipeline + some GT4Py specific optimizations
- ideally we would like to transfer Cartesian optimizations to next
- vertical: is not needed to transfer because we have scan and k-caches are explicit
- horizontal: would be interesting to transfer to gt4py.next's Cartesian

### DaCe orchestration

- `__sdfg__` function in DaCe does the magic, nothing specific in GT4Py

## Who might work on DaCe later?

- Edoardo?
- Prashanth?
- Rico?

## DaCe workshop (May 3rd)

Let's aim for a meeting 1h in 1-3 with
Lex, Torsten, Mauro, Linus, Enrique, Hannes, Edoardo?
to give a deeper update of were we stand, what our plans are etc