Source-first Basilisk VOF/facet-to-Blender bridge for explicit manifests, dry-run render planning, tiny synthetic fixture checks, and reproducible metadata reports.
VisualBasilisk separates solver output, render planning, metadata reports, and scientific explanations. The goal is a small inspectable bridge from Basilisk-style facet exports to Blender-oriented visualization workflows without bundling simulations or large media.
The public repository is a modest v0.3 source snapshot. It includes schemas, tests, tiny synthetic fixtures, and documentation for keeping raw solver artifacts out of GitHub-visible project pages.
The useful product is the source workflow: check manifests, plan rendering, and keep scientific scope explicit.
This step supports reproducible inspection of visualization inputs without turning images into unsupported scientific claims.
This step supports reproducible inspection of visualization inputs without turning images into unsupported scientific claims.
This step supports reproducible inspection of visualization inputs without turning images into unsupported scientific claims.
This step supports reproducible inspection of visualization inputs without turning images into unsupported scientific claims.
This step supports reproducible inspection of visualization inputs without turning images into unsupported scientific claims.
The v0.3 source snapshot includes code, schemas, tests, documentation, and synthetic fixtures. No package or container is distributed.
| Repository | Public source-first v0.3 snapshot |
|---|---|
| Fixture policy | Tiny synthetic examples only |
| Render path | Dry-run plans plus one minimal Blender smoke-render route |
| Distribution | Source and documentation; no package, container, or release |
| Site status | Public project page |
| Scientific status | No validation, production-CFD, or fit-readiness claim |
The tool organizes visualization inputs and render plans; it does not create or validate scientific results.
The next development step is a small real Basilisk-derived fixture with explicit input semantics and tests. Until then, the source examples remain synthetic.