Repository navigation
Assess remaining research value with reproducible controls - #11
5 commits merged into
Conversation
zero-aska
left a comment
There was a problem hiding this comment.
The four probes and the six pinned historical inputs pass on the pinned NumPy 2.5.4 and SciPy 1.18.1 stack.
python3 -m unittest discover -s research/value-assessment-20261112 -p test_check.py
Ran 8 tests OK
python3 -B research/value-assessment-20261112/check.py
PASS four probes and six immutable source hashes
publication_files in publication-manifest.json has 39 entries and 0 hash mismatches. The six inputs/manifest.json files match, including the historical Wave 11/12 sources pinned to 70a1204a. Saved evidence holds the quoted figures: halo mass 83913.96 solar masses, f_trap = 0.9999698959, baryon allotment 13126.04, compactness 4.1869e-11. The caustic pressure proxy goes from 0.0384418 to 0.195252, a factor of 5.08, with modal occupations conserved. closure/independent_checks.py exits 0.
This head changes README.md and leaves the root sums line at the old base hash.
file 9004137d818efd9486f7d1f00acb1431707b4a7182efccf33b27d90085fd33f2
sums 5e882f682fd25e980a7f933668fd177b8136208185095b747dc327bc1806f078 README.md
At this exact head the Documentation Index still contains the stray identifiers.- line, the split mic-Dawn quasar confrontation fragment, and a duplicated CHANGELOG bullet. A clean merge with current main drops those lines and keeps the assessment section. The merged README hashes to 514641650792d3faddf1bdfcdeb8b7b0b8dd66e75d2c9a5d0ad628148534b8fb, and the sums line stays 72606ab3.... git merge-tree reports a README conflict with #8 and a README conflict with #23.
second-review-checks.py exits 1 on CPython 3.12.3. Its replay asserts actual == saved for closure/results.json and observations/results.json. Against the saved Python 3.14.6 artifacts that comparison finds 202 and 124 differences. They are the interpreter label plus last-digit roundoff. The same replays pass check.py, which excludes version labels and uses its stated tolerances. The optional script's exact-equality claim is stronger than what this stack reproduces.
Fixes
- Rebuild the root README so the Documentation Index matches current main plus the assessment section, and set the
SHA256SUMSREADME line to that file. On an otherwise unchanged merge the digest is514641650792d3faddf1bdfcdeb8b7b0b8dd66e75d2c9a5d0ad628148534b8fb. - Make
second-review-checks.pycompare with the same tolerance policy ascheck.py, or state inVALIDATION.mdthat its exact JSON equality is tied to CPython 3.14.6.
|
Continued in #26, which keeps this branch's commits, merges main
|
Add a research value assessment with four reproducible probes, primary-source records, and explicit pursue, park and reject decisions. It retains the Wave 12 halo calculation while rejecting its current identification with a black-hole seed, and defines bounded mechanics, calibration and AeST response tests.
The bundle includes six immutable Wave 11/12 inputs with SHA-256 checks before execution. Its focused workflow runs the assessment checks. Full papers, downloaded archives, API caches and machine-specific build logs are excluded.
Validation: all four probes reproduce saved scientific output locally. Eight comparator and source-integrity tests pass, including rejection of altered small scientific signals. Optional independent review calculations reproduce with SymPy. Report prose, relative links and diff checks pass. The broad Lean build retains separate existing Wave 5/6/7 failures. Human scientific review is pending.
Hosted verification: all four probes and eight tests pass on Ubuntu at commit
7c44e92162320d510b959ebd9ffddbad1b017f5a.The independent review's two publication corrections are included: unsupported halo-to-seed wording and explicit rank-one/pentamode prior art. The scoped chirp-mass proof correction is separate in PR 10.
Refs #5. The proposed action, constraint and response gate remains open.