[enhancement] Find a way to display that workflows are related

[kinow]

In GitLab by @bdepaula on May 31, 2023, 16:20

It would be useful if we could display a workflow, and show other workflows that are related.

For the verification suite AS workflow (https://earth.bsc.es/gitlab/es/auto-s2s), we are considering the option to execute StartR (https://earth.bsc.es/gitlab/es/startR/) but instead of calling ecFlow, to use Autosubmit.

The verification suite workflow would then create multiple workflows, one for each chunk of data (do not confuse with Autosubmit configuration chunks, same name, different meaning).

This means we could have:

• a000 is an autosubmit experiment for the auto-s2s
• a00{1,2,3,4,5,6,7,8,9} are experiments created, and executed within a000

It would be nice if we had a way to store some (meta)data to indicate these workflows are all related. And maybe display links for users to click and navigate between workflows.

Also useful for cleaning up, since we could locate orphan workflows (e.g. a000 and a00{1,2,3,4,5} were deleted, which means we should be good to delete a006, a007, a008, a009).

There is also an issue in Climate DT where a similar use case was mentioned, of a workflow having other workflows that are related to this. And we could also consider that any workflow started with autosubmit run --start_after also has a relationship/link to another workflow.

[kinow]

In GitLab by @bdepaula on May 31, 2023, 16:22

mentioned in issue digital-twins/de_340/workflow#25

[kinow]

In GitLab by @jberlin on Jun 7, 2023, 09:52

Hi @bdepaula , do you mean a way to group a given set of experiments that fulfill a given condition ? that could be very nice

[kinow]

In GitLab by @bdepaula on Jun 7, 2023, 10:23

Exactly @jberlin . In StartR, StartR itself would be running in a workflow A. At some point it would prepare to chunk, create Autosubmit workflows during runtime (e.g. B, C, D), execute the workflows, and collect all the data.

In the Web GUI, it would be nice if we had some way to group A, B, C, D. Ideally, in a way that shows A as the parent, and that B, C, D are children of A.

Maybe we could have to modify Autosubmit too, perhaps adding a way to save in the DB some metadata that connects workflows. Something that can be exposed in the API and then consumed by the GUI's.