Changes for page Provenance of simulation and data analysis workflows
Last modified by adavison on 2022/05/23 22:24
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 1 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,6 +1,6 @@ 1 1 == Introduction == 2 2 3 -Computational provenance is a record of all the steps in a computational scientific workflow, including the code that was run, input data, the computational environment (hardware, OS, compiler versions, library version...), the person who performed each step, and output data.3 +Computational provenance is a record of all the steps in a computational scientific workflow, including the code that was run, input data, the computational environment (hardware, OS, compiler versions, library version...), and output data. 4 4 5 5 Capturing computational provenance facilitates: 6 6 ... ... @@ -8,16 +8,15 @@ 8 8 * management and tracking of workflows/projects by the scientists/engineers involved 9 9 * evaluation/review by other scientists and engineers 10 10 11 + 11 11 12 12 == Standards == 13 13 14 - The [[W3C PROV standard>>https://www.w3.org/TR/2013/NOTE-prov-overview-20130430/||rel="noopener noreferrer" target="_blank"]] provides a datamodeland related tools for provenanceinterchangeonthe web. The following diagram showsthethreebaseclasses of thePROVdata model: Entity,Activity,andAgent. These three classes formthebasis for the representation of provenance in the EBRAINS KnowledgeGraph: every node inthe KG has a type which is a subclassofone of these base classes.15 +Information about the W3C PROV ontology and related tools 15 15 16 -[[image:starting-points.svg||alt="The three Starting Point classes of the W3C PROV ontology and the properties that relate them."]] 17 17 18 18 == Storage of provenance in the Knowledge Graph == 19 19 20 -We present here the current schemas for representing (a) data analysis and (b) simulations in the Knowledge Graph. These schemas will need to be extended to cover neurorobotics simulations, and probably a more explicit representation of pipelines/workflows (the chaining together of multiple analysis / simulation stages) will be needed. 21 21 22 22 == Tools for automated capture of provenance == 23 23 ... ... @@ -33,6 +33,7 @@ 33 33 34 34 * local cache and synchronization? 35 35 35 + 36 36 == User interfaces for browsing, visualizing, and searching provenance information == 37 37 38 38
- Workflow provenance in the EBRAINS KG.svg
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.adavison - Size
-
... ... @@ -1,1 +1,0 @@ 1 -159.5 KB - Content