Summary
Charts from data the model already has.
Separating the save from the render is what makes it workable: the table goes in once, and after that each new view of it costs only a specification.
What it is
A visualization endpoint for aggregated data. A table is saved under a name, then rendered from a Vega-Lite specification — returning either a base64 PNG or a message carrying the complete specification with the data merged in, depending on how the server was started.
What you get
- A table of aggregated data saved under a name for later use
- A saved table rendered from a Vega-Lite specification
- The output shape chosen at startup: a PNG image, or the specification with the data in it
Requirements
Uv to run it. A flag on the launch command decides between png and text output, and has to be set before the client starts.