The goal for this component is to generate an RO-Crate that links together all the elements involved in a specific execution of the IAS pDT (datasets, parameters, model, logfiles, outputs...).
Recap of the Invasive Alien Species (IAS) pDT work so far:
Development work has been happening at UFZ's IAS-Workflows repo (private), to be transferred to BioDT's GitHub at some point
The pDT's components and workflows are structured around the TwinEco framework. We agreed that RO-Crates would fit well as an Indexer component (responsible for drawing the connections between all the different pieces)
At the code level, these workflows are implemented through Pydoit, a Python CLI task management & automation tool
Given the level of detail we want to achieve, the Workflow Run Crate Profiles are a good way of capturing the different types of workflows and associated metadata
The integration between Pydoit and The Workflow Run Crate profile will be developed on this Pydidit repo
We can start testing things out on LUMI in October. Until then, we can work with some lightweight example. We can use the idea of the house plant which gets increasingly upgraded with sensors and automated watering as a "digital twin toy example".
The goal for this component is to generate an RO-Crate that links together all the elements involved in a specific execution of the IAS pDT (datasets, parameters, model, logfiles, outputs...).
Recap of the Invasive Alien Species (IAS) pDT work so far:
We can start testing things out on LUMI in October. Until then, we can work with some lightweight example. We can use the idea of the house plant which gets increasingly upgraded with sensors and automated watering as a "digital twin toy example".