2006 Second IEEE International Conference on E-Science and Grid Computing (E-Science'06) 2006
DOI: 10.1109/e-science.2006.261098
|View full text |Cite
|
Sign up to set email alerts
|

Managing Large-Scale Workflow Execution from Resource Provisioning to Provenance Tracking: The CyberShake Example

Abstract: This paper discusses the process of building an environment where large-scale, complex, scientific analysis can be scheduled onto a heterogeneous collection of computational and storage resources. The example application is the Southern California Earthquake Center (SCEC) CyberShake project, an analysis designed to compute probabilistic seismic hazard curves for sites in the Los Angeles area. We explain which software tools were used to build to the system, describe their functionality and interactions. We sho… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
58
0

Year Published

2006
2006
2016
2016

Publication Types

Select...
6
3
1

Relationship

2
8

Authors

Journals

citations
Cited by 65 publications
(58 citation statements)
references
References 22 publications
0
58
0
Order By: Relevance
“…Gravitational Wave Observatory. CyberShake [92] is used by the Southern California Earthquake Center to characterize earth quake hazards in a region. The workflow jobs are in the Directed Acyclic Graph in XML (DAX) format and generated the using the workflow generator from [25].…”
Section: Job Schedulingmentioning
confidence: 99%
“…Gravitational Wave Observatory. CyberShake [92] is used by the Southern California Earthquake Center to characterize earth quake hazards in a region. The workflow jobs are in the Directed Acyclic Graph in XML (DAX) format and generated the using the workflow generator from [25].…”
Section: Job Schedulingmentioning
confidence: 99%
“…On the other hand, the focus of this paper is effectively retrieving information from hierarchical workflows and presenting it to the user according to specified keywords. There is also research on how to effectively execute a specific type of workflow in various circumstances [39,24,18,23]. These are orthogonal problems of defining query results on workflow hierarchies, as individual execution methods of a workflow hierarchy do not affect the specification of views on the workflow hierarchy, hence do not affect the definition of query results and the algorithms to generate query results.…”
Section: Queries For Evaluationmentioning
confidence: 99%
“…In such cases we can use Wings and Pegasus to iteratively instantiate and map the workflow. Figure 5 shows the interaction between Wings and Pegasus when instantiating a workflow in an earthquake science application CyberShake [9]. Initially the first portion of the workflow is instantiated by Wings and sent to Pegasus for mapping.…”
Section: Figure 4: a Schematic Of A Portal For Workflowbased Applicatmentioning
confidence: 99%