Moving workflow to python/yaml
We are discussing a refactoring on the medium-term of the globo workflow. Some ideas for the refactoring here below:
- Switch to python/yaml for all the scripts
- Use jinjja for templates (or alternative)
- Remove globo_configure.sh to have a single script for compilation
- Have flags as command line arguments (lamp, nemo)
- Set of resolutions to be recompiled from yaml files but also to have the possibility to compile them from command line
- globoresolution.sh to yaml
- Machine-dependent yaml file with all the options for each platform? Do we need the template for the platform? Quite complicated but on the long term
- Remove the idt, extra, postproc but keep geo and preglobo
- Add debug compilation flag
Edited by Paolo Davini