Commit 4934829b authored by apuiggro's avatar apuiggro 🤙🏽
Browse files

Provenance for the Loading and Aggregation module + rocrate provenance when...

Provenance for the Loading and Aggregation module + rocrate provenance when executing jobs with autosubmit

Started polishing the provenance functions for the Loading module

Changes to prov_dataset.R

Modified conf files. Added 'modelling_center' item

Fixed duplicities in the conf files

Modifications in provenance for the Loading module

Modifications in the prov_Loading inner functions

Advanced to include provenance in paralel executions

Merged branch to run SUNSET with MN5

Temporal Extent for Subseasonal data, fixed some buggs to execute split recipes with nord3v2 and mn5

Creation of rocrate feature + provenance fix

Feature to create rocrate.yml when requested in the recipe

New job to transfer provenance to the autosubmits experiment folder + creation of rocrate.yml

Added more functionalities to prov_aggregation.R

Use case 4 for provenance generation with autosubmit

Minor change in the .Rmd

Added adecuate picture in use case 4

Fixed some issues

Added provenance feature to Anomalies and Skill modules

Fixed issues with HUB

Run jobs in MN5 with provenance

Minor changes to do merge request

Gitignore files

Preparing merge request·

Removed some files

Fixed minor issues

Fixed some issues with Aggregation

Fixed minor issues

Fixed another issue

Fixed another issue

Minor changes use case

Fix in the use case

Remove provenance graph generation

Fix typo

Started fixing the Use Case + Removed provenance parameter in auto_conf, not needed anymore

Minor changes

Change on the recipe template

Minor changes

Fixed some issue with the atomic_recipes. Added Provenance key to some of them

Fixed some issued after rebasing

fixed more issues with rebase

more changes after rebase

same as before

fixed some space issues
parent 7c487d19
Pipeline #20348 passed with stage
in 16 minutes and 5 seconds
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment