{"id":2865,"date":"2016-07-26T22:04:06","date_gmt":"2016-07-26T22:04:06","guid":{"rendered":"https:\/\/notebooks.dataone.org\/?p=2865"},"modified":"2016-07-26T22:04:06","modified_gmt":"2016-07-26T22:04:06","slug":"week-9-reproducibility-of-script-based-workflows-wrap-up","status":"publish","type":"post","link":"https:\/\/notebooks.dataone.org\/workflow-reproducibility\/week-9-reproducibility-of-script-based-workflows-wrap-up\/","title":{"rendered":"Week 9 : Reproducibility of Script-Based Workflows \u2013 Wrap up"},"content":{"rendered":"
\n

For this week, I kept working on\u00a0reproducing the LIGO script on docker and Reprozip experiment by\u00a0building \u201cLIGO script\u201d container on top existing YW container. \u00a0Additionally, I tried to understand the bridge between Docker and Reprozip which are for sharing dependencies but orthogonal kinds docker, i.e one is for software dependencies; e.g.,for YW or YW demos, Docker will tell what\u00a0you need in terms of software and docker files will tell what is required (also \u201cdocker history\u201d will allow you to see how your container was built). While\u00a0Reprozip captures and reproduces data dependencies which trace which the data files are read, written by a script akin to YW + NW and\u00a0docker container might have all the relevant data, but need Reprozip to determine what files were actually used. This tool may be\u00a0applied\u00a0for a case of Matlab DataONE Toolbox which capture data provenance for Matlab scripts and console commands without the need to modify existing Matlab code.<\/p>\n

This week is also the last week of my internship, therefore I have also started documenting my work that summarize the questions, tasks, and findings of\u00a0prospective and retrospective provenance\u00a0and create some online documentation for each major “work package” I have worked on and checked into Github. I would like to thank my mentors Prof. Bertram, Tim and \u00a0Paolo for giving me an amazing chance\u00a0working on this project as well as the constant guidance and informative\u00a0feedbacks.<\/p>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

For this week, I kept working on\u00a0reproducing the LIGO script on docker and Reprozip experiment by\u00a0building \u201cLIGO script\u201d container on top existing YW container. \u00a0Additionally, I tried to understand the bridge between Docker and Reprozip which are for sharing dependencies but orthogonal kinds docker, i.e one is for software dependencies; Continue reading Week 9 : Reproducibility of Script-Based Workflows \u2013 Wrap up<\/span>→<\/span><\/a><\/p>\n","protected":false},"author":104,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[371],"tags":[],"_links":{"self":[{"href":"https:\/\/notebooks.dataone.org\/wp-json\/wp\/v2\/posts\/2865"}],"collection":[{"href":"https:\/\/notebooks.dataone.org\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/notebooks.dataone.org\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/notebooks.dataone.org\/wp-json\/wp\/v2\/users\/104"}],"replies":[{"embeddable":true,"href":"https:\/\/notebooks.dataone.org\/wp-json\/wp\/v2\/comments?post=2865"}],"version-history":[{"count":2,"href":"https:\/\/notebooks.dataone.org\/wp-json\/wp\/v2\/posts\/2865\/revisions"}],"predecessor-version":[{"id":2867,"href":"https:\/\/notebooks.dataone.org\/wp-json\/wp\/v2\/posts\/2865\/revisions\/2867"}],"wp:attachment":[{"href":"https:\/\/notebooks.dataone.org\/wp-json\/wp\/v2\/media?parent=2865"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/notebooks.dataone.org\/wp-json\/wp\/v2\/categories?post=2865"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/notebooks.dataone.org\/wp-json\/wp\/v2\/tags?post=2865"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}