Week 9 – The road ahead

As mentioned last week, we’d like to develop our own tool to capture provenance information of digital notebooks, so writing an iPython extension is good choice. An iPython extension is like an user defined library, and defined APIs can be registered that they can be invoked in the notebook as functions. So following Continue reading Week 9 – The road ahead

Week 8 – Notebook provenance

As we’re approaching the end of this summer project, it’s time to think about the end game. We’re targeting to study the provenance of notebooks and we choose iPython notebook as a use case and we studied NoWorkflow system in detail, so it’s natural to combine these two together. Since Continue reading Week 8 – Notebook provenance

Week 7 – Provenance questions

Let’s continue on the front of capturing provenance information on the Python script that visualizes a NetCDF file, using NoWorkflow system. In previous blogs, I mentioned that NoWorkflow provenance has three types: definition, development and execution. For execution provenance, only function activation and file access information are captured, there is not very Continue reading Week 7 – Provenance questions

Week 3 – Capturing provenance

The goal of this week is implementing the use cases identified last week, running NoWorklfow system on it and analyzing the result. Implementing the first use case (MsTMIP script in Matlab) is a little bit challenging because 1). making exactly mapping from Matlab to Python is difficult and time-consuming or Continue reading Week 3 – Capturing provenance

Week 1 Report – Getting started

We’re targeting to study provenance in digital notebooks, i.e. iPython. IPython notebook is an a web-based interactive computational environment for Python programming. One of our group members along with other collaborators has created a tool called “NoWorkflow”, which intends to capture script provenance of a Python script. During the joint section of Continue reading Week 1 Report – Getting started