1) Things suitable for outsourcing to ACH
a|) Utility routines to build GDB objects (Thomas Johnson) - not EIRENE specific! Just theatraeders for instance (for all EIRENE geometry types).
b) Interpolation and extaction routnes.
2) Basically B2.5-EIRENE is IMASIfied from the fluid side for output. Still, there are variables in EIRENE worth IMASification, not seeable from the B2.5 IDSs
a) statistical vaiances
b) all, what is ouside the B2 grid (extended grid and more).
c) CRM internal data
d) Emission data with EIRENE resolution (processes, lines, cells, etc)
e) Particular processes, surfaces etc. defined inside EIRENE
f) metadata specific for EIRENE (code library node)
g) make IMAS from base files describing geometry
k) provide conversion tools for grid types (e.g. quadragular to thriangular)
3) EIRENE as an NGM should be IMASified independent on B2.5
a) keep B2.5 IDSs as a basis for other fluid codes (starting with SOLEDGE3X). Flag where generalisation is needed.
b) Start trasforming common variables between B2.5 and EIRENE into IMAS (long term!!)
==> Best to do after the streamlining and total version merge!
==> Data structure developed by streamling should keep in mind future IMASification.
c) Start with IMAS input for EIRENE
==> adding cortesian velocity componets
==> incorporate ways to use the machine description DB