challenges in managing implicit and abstract provenance
play

Challenges in managing implicit and abstract provenance data: - PowerPoint PPT Presentation

Workshop on the Theory and Practice of Provenance 2011 Challenges in managing implicit and abstract provenance data: experiences with ProvManager Anderson Marinho, Marta Mattoso, Cludia Werner, Vanessa Braganholo, Leonardo Murta


  1. Workshop on the Theory and Practice of Provenance 2011 Challenges in managing implicit and abstract provenance data: 
 experiences with ProvManager 
 Anderson Marinho, Marta Mattoso, Cláudia Werner, Vanessa Braganholo, Leonardo Murta Federal University of Rio de Janeiro (UFRJ), Brazil Fluminense Federal University (UFF), Brazil

  2. Problem/Motivation • Some challenges in managing provenance • Which provenance data should be gathered? • Open Provenance Model is a possible solution • How to capture provenance data? • Three levels: Workflow, Operating System, Activity • How to manage provenance in workflows that are executed by different execution environments (distributed environments)? 2

  3. ProvManager - Overview of provenance gathering strategy [SWF 2009; IPAW, 2010] 3. Obtain the adapted workflow specifications 6. Provenance data sent ProvManager by the activities 2. Publish the workflow specifications 1. Collect the workflow specifications from SWfMS 4. Load the adapted workflow Taverna specifications in the SWfMS 5. Run VisTrails Kepler Scientist Experiment 3

  4. Workflow instrumentation Original A B workflow 4

  5. Workflow instrumentation Original A B workflow Instrumenting A PGA PGA B PGA PGA PGA workflow 5

  6. Workflow instrumentation Original A B workflow Instrumenting A PGA PGA B PGA PGA PGA workflow A’ B’ Wrapping A B PGA PGA PGA activities 6

  7. Workflow instrumentation Original A B workflow Instrumenting A PGA PGA B PGA PGA PGA workflow A’ B’ Wrapping A B PGA PGA PGA activities Adapted A’ B’ workflow 7

  8. There are still some problems… • Implicit provenance data • Difficulty in gathering provenance data when these are not explicitly declared in the workflow specification • Lack of higher provenance abstraction levels • Concrete workflow related provenance data are not enough to help scientists in the experiment analysis • Some scientists may not be used to such information 8

  9. Implicit provenance data SWfMS domain “C:\res.zip” {1,3,5} “C:\data” B D A C OS domain img.jpg res.zip C:\data 9

  10. Lack of higher provenance abstraction levels C onceptual Abstract C oncrete Analysis of Movements of P rosim P latform Problem : scientist does not easily relate data from one abstraction level to the other Questions such as “what is the result data of the ‘analysis of platform movements’ activity?” can not be easily answered 10

  11. Some ideas… • Implicit data • Adopt a OS level provenance gathering mechanism to work together with the PGA in the ProvManager • There is a similar initiative in VisTrails (Koop et al. (2010)) • Lack of higher provenance abstraction levels • Create a “conceptual provenance data” model • Salayandia and da Silva (2010) propose something similar • Map this model to the existing “concrete provenance data” 11

  12. Workshop on the Theory and Practice of Provenance 2011 Challenges in managing implicit and abstract provenance data: 
 experiences with ProvManager 
 Anderson Marinho, Marta Mattoso, Cláudia Werner, Vanessa Braganholo, Leonardo Murta Federal University of Rio de Janeiro (UFRJ), Brazil Fluminense Federal University (UFF), Brazil

Download Presentation
Download Policy: The content available on the website is offered to you 'AS IS' for your personal information and use only. It cannot be commercialized, licensed, or distributed on other websites without prior consent from the author. To download a presentation, simply click this link. If you encounter any difficulties during the download process, it's possible that the publisher has removed the file from their server.

Recommend


More recommend