Skip to content

v3.33.0

Choose a tag to compare

View all tags
@cboettig cboettig released this 06 Oct 16:29
· 20 commits to main since this release
v3.33.0
97d1479

Exported session report

Download the session as code (#394). Beside Print / PDF, the report now offers the whole session as one runnable file:

  • .R script, one RStudio outline section per question
  • .py script with # %% cells
  • .qmd Quarto document with R chunks
  • .ipynb Jupyter notebook with Python cells

Each query gets its own variable (df1, df2, …). The notebooks include the model's answers as prose between the chunks. Files are embedded in the report, so it stays a single file that works offline.

Data sources (#394). A new section cites each dataset the session queried or showed on the map. Each entry comes from its STAC record: title, producers, sci:citation (or the DOI / cite-as link), license, About and STAC links. The same list ends every downloaded file. Citation quality follows the catalog's metadata; a record with no citation says so.

Speed note. The disclaimer now notes that GLEN runs queries on high-speed servers next to the data, so re-running large queries on a personal computer may be much slower.

Controls, regrouped. The report's controls (Code, Code as, Download, Print) are now a labelled, aligned grid under an Options heading in the left rail, above Contents. Below 1480px they become a panel above the document. The rail previously started off-screen at its old 1360px breakpoint.

Fixes to re-running exported code

These affected every export, not just the new downloads:

  • Anonymous S3 access. The setup block now writes KEY_ID '', SECRET '' explicitly. Without them, DuckDB uses any AWS credentials in the reader's environment (e.g. ~/.Renviron), and the public bucket answers 403 InvalidAccessKeyId.
  • h3 extension. The setup now runs INSTALL h3 FROM community; LOAD h3;, since the agent's queries call h3_* functions.
  • Failed queries shown as results. The export now recognises the MCP server's SQL Error: … as a failure, so failed queries go only to the session log. The same gap in the agent loop is tracked in #395.

Upgrading

No config changes. Apps pick this up by bumping their pin to @v3.33.0. Nothing changes in the live app; only the exported file changes.

Assets 2
Loading