71–76 of 76 posts
Earlier quoted context omitted.
You can configure so they don't save their output, then the ipynb diffs will be readable.
Makes me wonder if you could split an ipynb into an in and out file, then add /*.out to .gitignore.
Slightly tangent, but has anyone figured out a good solution for version controlling jupyter notebooks? The closest thing that we've found has been to use the notebook percent format in a simple .py file [0][1]. It plays with git much nicer than an .ipynb and it is still interactive enough for rapid prototyping. However, it would be nice to have some first-class support from Jupyter on this. [0] https://jupytext.read…
Earlier quoted context omitted.
Makes me wonder if you could split an ipynb into an in and out file, then add /*.out to .gitignore.
I like this idea, but seems a little backwards. Normally you commit the _source_ and omit the _artifacts_ haha.
Earlier quoted context omitted.
In essence, yes. Ninja is based around the idea of reproducable science: a given execution of a notebook is immutable and accessible consistently. It writes out cell outputs depending on their mimetype (this is included in Jupyter Notebook metadata). It writes out all declared variables, per-cell, and makes them accessible in several formats (for pre-alpha, as JSON objects). It then exposes all of these via our web s…
I'm glad to see that you can link to the execution of a particular cell. Just to clarify, if the cell had the execution for the Age of a particular person, I don't know if the link to the cell is of the age of that person as of the particular day and time when it was executed, or if is stored in an unevaluated form, the execution would yield an age dependent upon the calculation and using "Now" as the value that is c…
We're enabling re-triggering notebooks soon, which will allow things like scheduled and parameterized executions, and those will be eagerly evaluated as well.
Earlier quoted context omitted.
I like this idea, but seems a little backwards. Normally you commit the _source_ and omit the _artifacts_ haha.
That's what they are saying? Doesn't seem backwards to me.
Earlier quoted context omitted.
You can configure so they don't save their output, then the ipynb diffs will be readable.
Makes me wonder if you could split an ipynb into an in and out file, then add /*.out to .gitignore.