Open up WASM notebook to explore a dataset from calkit.io. If good, click save button to solidify it in the project pipeline along with its environment.
Good first use case could be the buildkite dataset in clima-perf. Would be a nice use case for DuckDB. If we get an interesting result we'd like to use for the answer to a question, we can save it as such. We can also save the result either way by putting into the pipeline. Should we launch marimo to do this, or build in our own SQL interface?
Open up WASM notebook to explore a dataset from calkit.io. If good, click save button to solidify it in the project pipeline along with its environment.
Good first use case could be the
buildkitedataset inclima-perf. Would be a nice use case for DuckDB. If we get an interesting result we'd like to use for the answer to a question, we can save it as such. We can also save the result either way by putting into the pipeline. Should we launch marimo to do this, or build in our own SQL interface?