vizier-scala
vizier-scala copied to clipboard
VizierDB
The Vizier kernel-free notebook programming environment
**What pain point is this feature intended to address? Please describe.** It takes more time when building a new workflow and choosing appropriate variable/table names, to have to rename certain...
**What pain point is this feature intended to address? Please describe.** When writing scala code cells, it's occasionally useful, when debugging, to display a sample of a generated dataset (i.e.,...
**What pain point is this feature intended to address? Please describe.** Error reporting in scala cells **sucks**. Parse errors are incredibly uninformative, and when exceptions are reported, it's not entirely...
**What pain point is this feature intended to address? Please describe.** In some circumstances, it is convenient to be able to see multiple artifacts simultaneously (e.g., plots, or dataframes). Yes,...
**Describe the bug** 
**What pain point is this feature intended to address? Please describe.** Workflows can get repetitive, with the same sequence of cells getting invoked multiple times. This can make workflows harder...
Several folks have now requested something to highlight the evolution / provenance of a given dataset. The details would have to be discussed, but at a minimum, this would contain...
**Describe the bug** `df(colName)` breaks if `colName` needs to be quoted. The new `DataFrameOps` is cleaner. Unfortunately, this patten is used throughout the entire codebase. We need an audit to...
Instead of taking up regular screen real estate, move the documentation list to the Help menu.
This is the result of our branch history on our notebook. It seems that the timeline of the changes is wrong or has a way of sorting itself that doesn't...
