@inproceedings{
 title = {Static compiler analysis for workflow provenance},
 type = {inproceedings},
 year = {2013},
 id = {a0ec3456-18c2-32f1-b103-10d7bd6cd8ad},
 created = {2018-03-05T18:20:23.718Z},
 file_attached = {false},
 profile_id = {42d295c0-0737-38d6-8b43-508cab6ea85d},
 group_id = {9d761a94-2f2d-31ce-a8c3-50aa6d668643},
 last_modified = {2018-03-05T18:20:23.718Z},
 read = {false},
 starred = {false},
 authored = {false},
 confirmed = {false},
 hidden = {false},
 citation_key = {Ghoshal2013a},
 private_publication = {false},
 abstract = {Data provenance is the lineage of an artifact or object. Provenance can provide a basis upon which data can be regenerated, and can be used to determine the quality of both the process and provenance itself. Provenance capture from workflows is comprised of capturing data dependencies as and when a workflow executes. We propose a layered provenance model which identifies and stores provenance at different granularities statically by analyzing the source code of programs. We use this model to capture provenance from both workflows and modules within workflows. This paper contributes a static compile time analysis methodology that includes a logical layered provenance model to convert workflow provenance from black box to white box, where the precise mapping between the inputs and outputs of a task can be known.},
 bibtype = {inproceedings},
 author = {Ghoshal, D. and Chauhan, A. and Plale, B.},
 doi = {10.1145/2534248.2534250},
 booktitle = {Proceedings of WORKS 2013: 8th Workshop on Workflows in Support of Large-Scale Science - Held in conjunction with SC 2013: The International Conference for High Performance Computing, Networking, Storage and Analysis}
}

{"_id":"BFrdCqPff8N8gGbhx","bibbaseid":"ghoshal-chauhan-plale-staticcompileranalysisforworkflowprovenance-2013","downloads":0,"creationDate":"2018-03-12T19:10:27.453Z","title":"Static compiler analysis for workflow provenance","author_short":["Ghoshal, D.","Chauhan, A.","Plale, B."],"year":2013,"bibtype":"inproceedings","biburl":"https://bibbase.org/service/mendeley/42d295c0-0737-38d6-8b43-508cab6ea85d","bibdata":{"title":"Static compiler analysis for workflow provenance","type":"inproceedings","year":"2013","id":"a0ec3456-18c2-32f1-b103-10d7bd6cd8ad","created":"2018-03-05T18:20:23.718Z","file_attached":false,"profile_id":"42d295c0-0737-38d6-8b43-508cab6ea85d","group_id":"9d761a94-2f2d-31ce-a8c3-50aa6d668643","last_modified":"2018-03-05T18:20:23.718Z","read":false,"starred":false,"authored":false,"confirmed":false,"hidden":false,"citation_key":"Ghoshal2013a","private_publication":false,"abstract":"Data provenance is the lineage of an artifact or object. Provenance can provide a basis upon which data can be regenerated, and can be used to determine the quality of both the process and provenance itself. Provenance capture from workflows is comprised of capturing data dependencies as and when a workflow executes. We propose a layered provenance model which identifies and stores provenance at different granularities statically by analyzing the source code of programs. We use this model to capture provenance from both workflows and modules within workflows. This paper contributes a static compile time analysis methodology that includes a logical layered provenance model to convert workflow provenance from black box to white box, where the precise mapping between the inputs and outputs of a task can be known.","bibtype":"inproceedings","author":"Ghoshal, D. and Chauhan, A. and Plale, B.","doi":"10.1145/2534248.2534250","booktitle":"Proceedings of WORKS 2013: 8th Workshop on Workflows in Support of Large-Scale Science - Held in conjunction with SC 2013: The International Conference for High Performance Computing, Networking, Storage and Analysis","bibtex":"@inproceedings{\n title = {Static compiler analysis for workflow provenance},\n type = {inproceedings},\n year = {2013},\n id = {a0ec3456-18c2-32f1-b103-10d7bd6cd8ad},\n created = {2018-03-05T18:20:23.718Z},\n file_attached = {false},\n profile_id = {42d295c0-0737-38d6-8b43-508cab6ea85d},\n group_id = {9d761a94-2f2d-31ce-a8c3-50aa6d668643},\n last_modified = {2018-03-05T18:20:23.718Z},\n read = {false},\n starred = {false},\n authored = {false},\n confirmed = {false},\n hidden = {false},\n citation_key = {Ghoshal2013a},\n private_publication = {false},\n abstract = {Data provenance is the lineage of an artifact or object. Provenance can provide a basis upon which data can be regenerated, and can be used to determine the quality of both the process and provenance itself. Provenance capture from workflows is comprised of capturing data dependencies as and when a workflow executes. We propose a layered provenance model which identifies and stores provenance at different granularities statically by analyzing the source code of programs. We use this model to capture provenance from both workflows and modules within workflows. This paper contributes a static compile time analysis methodology that includes a logical layered provenance model to convert workflow provenance from black box to white box, where the precise mapping between the inputs and outputs of a task can be known.},\n bibtype = {inproceedings},\n author = {Ghoshal, D. and Chauhan, A. and Plale, B.},\n doi = {10.1145/2534248.2534250},\n booktitle = {Proceedings of WORKS 2013: 8th Workshop on Workflows in Support of Large-Scale Science - Held in conjunction with SC 2013: The International Conference for High Performance Computing, Networking, Storage and Analysis}\n}","author_short":["Ghoshal, D.","Chauhan, A.","Plale, B."],"biburl":"https://bibbase.org/service/mendeley/42d295c0-0737-38d6-8b43-508cab6ea85d","bibbaseid":"ghoshal-chauhan-plale-staticcompileranalysisforworkflowprovenance-2013","role":"author","urls":{},"metadata":{"authorlinks":{}},"downloads":0},"search_terms":["static","compiler","analysis","workflow","provenance","ghoshal","chauhan","plale"],"keywords":[],"authorIDs":[],"dataSources":["zgahneP4uAjKbudrQ","ya2CyA73rpZseyrZ8"]}