Problem
VisualBasilisk separates solver output, render planning, metadata reports, and scientific explanations so that facet-to-Blender work follows an inspectable, repeatable sequence.
VisualBasilisk
A small command-line bridge that makes Basilisk facet exports easier to inspect, plan, render, and trace through explicit manifests and reproducible metadata.
Overview
Contribution
Version 0.3 provides schemas, checks, dry-run render plans, a small Blender smoke path, and metadata reports that keep every visualization input and output accountable.
What the bridge does
The workflow turns a declared set of facet files into checked inputs, deterministic render instructions, and traceable outputs.
- Read compact Basilisk-style facet and surface manifests
- Check frame completeness and manifest consistency
- Generate deterministic dry-run Blender render plans
- Run a minimal headless Blender smoke render for tiny synthetic fixtures
- Write metadata reports that keep inputs, outputs, and scientific scope traceable
Demonstrated workflow
Source, schemas, tests, documentation, and tiny synthetic fixtures demonstrate the end-to-end planning and smoke-render path.
| Implementation | Version 0.3 Python CLI with schemas, tests, and documentation |
|---|---|
| Reference fixtures | Tiny synthetic examples for deterministic workflow checks |
| Render path | Dry-run plans plus one minimal Blender smoke-render route |
| Primary outputs | Checked manifests, deterministic plans, contact sheets, and metadata reports |
| Data boundary | User-supplied solver artifacts stay separate from the versioned workflow |
Demonstrated workflow
Explicit inputs become traceable visualization plans.
Tiny synthetic fixtures exercise manifest checks, deterministic render planning, contact-sheet assembly, and metadata reporting from end to end.