Hiya - I have a couple of tasks which will be run in both R1 and “normal” dependency cycles.
- In one case task configuration is likely to be identical
- In the other, the task configuration is likely to change a little
For straight cylc tasks/scripts, I can see that it would likely be sensible for me to follow the Varying Behaviour By Cycle Point example in the suite design guide.
I’m less clear about what approach is sensible when the tasks are rose apps.
At the moment I’m thinking of just duplicating these:
suite.rc [run_time][[my_app_cold]pointing to
suite.rc [run_time][[my_app]pointing to
But is there a cleverer, DRY-er way, e.g. using inheritance as above?
Ask as while I can see that (especially in “different task config” case) I may not be able to escape duplicating the ~largely-similar-but-slightly-different configuration interfaces (
rose-meta.conf), I’d like to be able to avoid duplicating other aspects (e.g. identical
my_script.py present in both