1 / 16

Using Provenance to Support Real-Time Collaborative Design of Workflows

Using Provenance to Support Real-Time Collaborative Design of Workflows. Tommy Ellkvist 1 , Erik Anderson 2 , David Koop 2 , Juliana Freire 2 , and Claudio Silva 2 (1) Link ö ping University (http://www.liu.se) (2) University of Utah (http://www.utah.edu). Outline. Motivation

ramona
Download Presentation

Using Provenance to Support Real-Time Collaborative Design of Workflows

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Using Provenance to Support Real-TimeCollaborative Design of Workflows Tommy Ellkvist1, Erik Anderson2, David Koop2, Juliana Freire2, and Claudio Silva2 (1) Linköping University (http://www.liu.se) (2) University of Utah (http://www.utah.edu)

  2. Outline • Motivation • Workflow evolution • Demo • Architecture • Technical issues • Use cases • Conclusion and Future Work

  3. Collaborative workflow design - example • Scientists at CMOP (Center for Coastal Margin Observation and Prediction) collaborating with researchers at University of Utah • Combine knowledge of visualization with knowledge about data. • An efficient method of workflow specification sharing is needed.

  4. Collaborative workflow design - motivation • Designing workflows can be time consuming • In data analysis and exploration, workflows are iteratively refined • Multiple users, with different expertise, need to collaborate

  5. Current approaches to collaboration

  6. Our Approach: Provenance-enabled synchronous workflow design • Share workflow provenance, not only workflow specifications! • Leverages change-based provenance [Freire et al., IPAW 2006] • Unobtrusive • Does not interfere with the users activities • The user can choose whether to incorporate changes • Immediate • Changes are propagated instantly • You can track other users progress • Automatic • No extra operations need to be performed by the users • Once connected, the synchronization is automatic

  7. Workflow Evolution Workflows Data Products Version Tree

  8. Collaboration using workflow evolution Workflows Version Tree User juliana eranders eranders eranders stevec

  9. Demo

  10. Architecture • MySQL database • VisTrails clients User 1 User 2

  11. Propagating Changes Provenance is monotonic!

  12. Synchronization Algorithm Monotonicity is preserved!

  13. Monotonicity is good: users need not worry about interfering the work of others Can combine workflows from different branches using analogy operation Compute difference between workflow versions Apply difference to other workflow Integrating Branches using Analogy (Scheidegger et al., TVCG 2007)

  14. Collaborative Design as a Teaching Aid • Correcting errors • Highlighting interesting nodes • Suggesting alternate solutions

  15. Collaborative Design in Multi-disciplinary Research • Immediate sharing of workflow specifications • Real-time explorative design between users

  16. Conclusion and Future Work • New mechanism for enabling synchronous collaborative workflow design • Unobtrusive, real-time, automatic • User studies needed • Extend to other domains • Graphics design • Other design tools • Parameter exploration tools

More Related