The full experimental pipeline behind Axis5 and the Tier3 v13 definition: from a single database, fits the Axis5 covariance/weight model, determines its thresholds, and classifies every block's Tier3 state and collapse phase, all in one run.
| Location | Included in the DOI 1.7 Zenodo archive (Merutan_DOI1.7.zip) |
|---|---|
| Role | The full experimental pipeline: performs the covariance fitting (from a 1,000,000-block sample), determines Axis5's feature weights and thresholds, and runs Axis5 inference on the same database, all in a single pass. comp_* is computed mean-centered: (xb,i − μi) × wi. |
| Used by | DOI 1.6 and DOI 1.7 — builds analysis_delta, the table that generate_axis5_tier3_full_db.py later joins against to produce axis5_full, the table those reports' Tier3/Axis5 results were queried from. (A further step assembles the full meltan_integrated_viewer_*.duckdb database referenced in DOI 1.7's videos, combining that output with the Axis1 and Axis6 databases from the same pipeline; its schema has been public since DOI 1.0's appendix, though that assembly step itself isn't separately published; see generate_axis5_tier3_full_db.py for how the two relate.) |
| Status | Current, as documented in DOI 1.7 — a different concern entirely from the JOIN-based verification pipeline (create_alignment_db_single.py / import_ground_truth_data.py) that was corrected and replaced. No bug or correction has been published against this script. |
Run interactively, in one pass, against a single database:
tta_delta_results.duckdb), attaches it
read-only as base, and writes all output to a
new analysis_results.duckdb alongside it.delta_phase and a finer
delta_phase_detail.jump_sum_block:
critical / transition / plateau_low / plateau_hi).delta_phase_detail).analysis_delta, plus a
SHA-256 hash of the output database and a short
analysis_results_definition.md recording the
exact Tier3 v13 definition used.
Interactive, with no command-line arguments: running the script
opens a file-picker dialog to choose the base database
(tta_delta_results.duckdb). The output database is
written alongside it, in the same folder, as
analysis_results.duckdb.