AICCM Comparison Manuscript Artifacts¶
The data/*.json files are summary records only. They are not a complete
article artifact bundle.
For every calculation used for figures or reproducibility, keep the full input and output set beside the manuscript:
executable input script or command file
captured
stdout.txtandstderr.txtvibe-qc
.outand.systemfiles when the runner supports themproperty sidecars such as
.properties.jsonand.population.jsonviewer assets:
.qvf,.cube,.xsf,.molden, and structure filesrendered vibe-view HTML panels for QVF plot/table sections
checksums for every generated output file
Generate the local bundle with:
.venv/bin/python docs/manuscripts/aiccm_comparison/generate_artifacts.py --force
The rendered vibe-view panels use the local vibe-view/src reader and
renderers. If the active venv is missing those lightweight dependencies, install
them before generating:
.venv/bin/python -m pip install 'pydantic>=2.0' 'plotly>=5.18'
The default minimal profile creates one tiny B-side vibe-view smoke case so
the artifact contract can be checked locally. Use --profile visual-only for
the article-size visualization cases, or --profile paper to include benchmark
JSON routes as well. The generated tree is
docs/manuscripts/aiccm_comparison/artifacts/.