Add support for YAC3
ICON will soon change over to YAC3.
In YAC3, the coupling definitions are made either in a YAML configuration file or at runtime (before the sync_def()
/ search()
call).
We either
-
(A) have to translate the hiopy-coupling-config to a YAC-YAML-config (instead of XML) -
(B) have to implement runtime configuration of the coupling
Note that hiopy-simple-coupling format uses the havelist / wantlist approach with uinque variable names, while YAC (both 2 and 3) requires the explicit definition of source-target pairs.
While (A) might fit easier in the current configuration-workflow, (B) might eventuall simplify configuration. We might even have to switch over to (B) at some point, as YAC3 supports multiple coupling configuration sources and so we might not even have access to the full configuration set anymore.
Edited by Tobias Koelling