Linking Abstract Plans of Scientific Experiments to their - PowerPoint PPT Presentation

Linking Abstract Plans of Scientific Experiments to their Corresponding Execution Traces Milan Markovic, Daniel Garijo*, and Peter Edwards University of Aberdeen *University of Southern California

Scientific Workflows • Computational steps and data dependencies that are necessary to carry out a scientific experiment • Beneficial for reproducing previous experiments, improving standardization practices in a research lab and educating students on existing methods

Workflows Abstractions

Current Limitations • Complex plans are usually simplified into less detailed (abstract) workflows • Currently, it is difficult to link between high level workflow specifications and low level execution traces

P-Plan & Prov-O Execution Trace Bundle Plan wasDerivedFrom Input correspondsToVariable Data correspondsToStep Sort Sorted correspondsToVariable Data

Extended P-Plan (EP-Plan) • https://w3id.org/ep-plan • New concepts for linking different abstractions of plans and execution traces • Concepts for additional plan metadata such as constraints, objectives, agents, references to policies, and rationales for individual plan elements • Intended for cross-domain applications

ep-plan:isDecomposedAsPlan Linking Plans ep-plan:isSubPlanOfPlan :SummarizedWf :ExecutedWf & sub-plans (ep-plan:Plan) (ep-plan:Plan) ep-plan: hasPart • Multisteps are :InputFilesVar :File1Var :File2Var decomposed into (ep-plan:MultiVariable) (ep-plan:Variable) (ep-plan:Variable) sub-plans ep-plan:hasInputVariable ep-plan:hasInputVariabe • Multivariables from :AggregateStep :ExecuteWorkflowStep (ep-plan:Step) (ep-plan:MultiStep) more abstract plans ep-plan:hasOutputVariable are linked to ep-plan:hasOutputVariabe :AggregatedDataVar variables in sub- (ep-plan:Variable) :OutputFilesVar plans (ep-plan:MultiVariable) ep-plan:hasInputVariabe :SortStep (ep-plan:Step) ep-plan:hasPart ep-plan:hasOutputVariable ep-plan: :OutputVar :ErrorLogVar isElementOfPlan (ep-plan:Variable) (ep-plan:Variable)

ep-plan: :SummarizedWf :ExecutedWf Linking execution isSubPlanOfPlan (ep-plan:Plan) (ep-plan:Plan) prov:wasDerivedFrom traces prov:wasDerivedFrom :SummarizedExecutionTrace :ExecutionTrace (ep-plan:ExecutionTraceBundle) (ep-plan:ExecutionTraceBundle) prov: • MultiActivities hadMember correpsond to MultiSteps :File1 :File2 :InputFiles (ep-plan:Entity) (ep-plan:Entity) (ep-plan:EntityCollection) • EntityCollecions prov:used prov:used correspond to :Aggregate :WorkflowEcexution MultiVariables (ep-plan:Activity) (ep-plan:MultiActivity) prov:wasGeneratedBy • hadMember relationships prov:wasGeneratedBy :AggregatedData link Entities and (ep-plan:Entity) :OutputFiles EntityCollections (ep-plan:EntityCollection) prov:used between different :Sort (ep-plan:Activity) prov:hadMember abstractions of execution prov:wasGeneratedBy traces ep-plan: :Output :ErrorLog (ep-plan:Entity) (ep-plan:Entity) isElementOfTrace

Future Work • Implementation of EP-Plan vocabulary within the WINGS provenance capture mechanisms • Explore how other concepts supported by EP-Plan (e.g. references to workflow constraints) can be captured within the WINGS platform

Contact & Acknowledgments • milan.markovic@abdn.ac.uk • dgarijo@isi.edu