VizierDB
/
paper-2019-CIDR
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

fixed 2 typos

master
Juliana Freire 2020-02-10 02:02:46 -05:00
parent 756fb1b614
commit 5369620c4e
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

BIN
PDF-versions/vizier-CIDR-cameraready.pdf
View File

Binary file not shown.

4
sections/system.tex
View File

@ -76,7 +76,7 @@ For example, the workflow cell in \Cref{fig:wfVsDFCells} reads from datasets \ls
The workflow API, illustrated in \Cref{fig:wfVsDFCells}.a, targets cells where only collecting coarse-grained provenance information is presently feasible.
This includes \texttt{Python} and \texttt{Scala} cells, which implement Turing-complete languages; as well as cells like \texttt{Load Dataset} that manipulate entire datasets.
To discourage out-of-band communication between cells (which hinders reproducibility), as well as to avoid remote code execution attacks when Vizier is run in a public setting, workflow cells are executed in an isolated environment.
Vizier presently supports execution in an fresh interpreter instance (for efficiency) or a docker container (for safety).
Vizier presently supports execution in a fresh interpreter instance (for efficiency) or a docker container (for safety).
Vizier's workflow API is designed accordingly, providing three operations: \emph{Read dataset} (copy a named dataset from Vizier to the isolated execution environment), \emph{Checkpoint dataset} (copy an updated version of a dataset back to Vizier), and \textit{Create dataset} (allocate a new dataset in Vizier).
A more efficient asynchronous, paged version of the \emph{read} operation is also available, and the \emph{Create dataset} operation can optionally initialize a dataset from a URL, S3 Bucket, or Google Sheet to avoid unnecessary copies.
@ -115,7 +115,7 @@ The result is a version graph, a tree-like structure that shows the notebook's e
Under typical usage, edits are applied to a leaf of the tree to create chains of edits.
Editing a prior version of the notebook creates a \emph{branch} in the version history.
Vizier requires users to explicitly name branches when they are created; This explicit branch management makes it easier for users to follow the intent of a notebook's creator.
Vizier requires users to explicitly name branches when they are created. This explicit branch management makes it easier for users to follow the intent of a notebook's creator.
Internally however, each notebook version is identified by a 2-tuple consisting of a randomly generated, unique branch identifier and a monotonically increasing notebook version number.