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)
Details
- Page properties
-
- Content
-
... ... @@ -8,7 +8,6 @@ 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 - 12 12 == Standards == 13 13 14 14 The [[W3C PROV standard>>https://www.w3.org/TR/2013/NOTE-prov-overview-20130430/||rel="noopener noreferrer" target="_blank"]] provides a data model and related tools for provenance interchange on the web. The following diagram shows the three base classes of the PROV data model: Entity, Activity, and Agent. These three classes form the basis for the representation of provenance in the EBRAINS Knowledge Graph: every node in the KG has a type which is a subclass of one of these base classes. ... ... @@ -19,8 +19,22 @@ 19 19 20 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 21 +[[image:Workflow provenance in the EBRAINS KG-2.png||alt="KG schema for data analysis"]] 22 + 23 +[[image:Workflow provenance in the EBRAINS KG.png||alt="KG schema for simulation"]] 24 + 25 +(note that the diagrams do not show Agents; the person who launched each analysis/simulation activity is linked to the activity with a ##wasAssociatedWith## connection). 26 + 27 +(% class="box warningmessage" %) 28 +((( 29 +TODO: insert or link to the detailed schemas for each type 30 +))) 31 + 22 22 == Tools for automated capture of provenance == 23 23 34 + 35 +Issues to discuss: 36 + 24 24 * on different systems: 25 25 ** HPC systems 26 26 ** neuromorphic systems ... ... @@ -31,8 +31,17 @@ 31 31 32 32 == Communication between computer systems and the KG == 33 33 34 - * localcache and synchronization?47 +Two issues arise: 35 35 49 +(i) fine-grained provenance information may need to be obtained on compute nodes, which may not have network access; 50 + 51 +(ii) failures of provenance upload should not cause the workflows to fail; 52 + 53 +An overall solution for both of these issues would perhaps involve a local cache and later synchronization. 54 + 36 36 == User interfaces for browsing, visualizing, and searching provenance information == 37 37 38 - 57 +(% class="box infomessage" %) 58 +((( 59 +DISCUSSION NEEDED: integrate visualization of prov information into KG Search UI, and/or develop separate app? 60 +)))