Experiment dependencies
This is a long waited feature (for some niche experiments), but it would be helpful for spin-up executions or experiments making use of different Autosubmit experiments.
There should be a better support in Autosubmit4, but we can start providing a basic one: One experiment could have a DEPENDENCIES/TRIGGER, etc section in expdef.conf
. The user could specify the name of some other experiment_a, that would trigger the start of experiment_b when experiment_a is complete without errors.
The easiest way to proceed, I think, is to define the configuration and afterwards, start both experiments (with two different Autosubmit instances). The dependent experiment would be just waiting until the first one is finished.
The trickiest part would be to retrieve the status from other experiment. Should we use Autosubmit API?
We could progressively introduce more dependencies or triggers, as it is done in other workflow managers as Cylc. For example, to start an experiment after a date/time.
CP needs to run some decadal experiments that would benefit from using this feature, to create initial conditions in one workflow that would be consumed by another one.
@dbeltran @wuruchi who could take charge of this?
Modification to the SPAM Filter