Repository navigation
Conversation
… printed Ising, percolation and Sabra series The slope between scales a < b is at least p/q exactly when (y_b/y_a)^q >= (x_b/x_a)^p, a comparison of integers. scaling-check/ holds the checker, the series with their sources, a verdict table and a README. tests/scaling-check.mjs has known answers, exact ties, a comparison with 80-digit logarithms and four must-fail controls.
…h only new files The percolation window slope over L = 32 to 256 is 1.8727, not 1.8734 (that was close to the table's least-squares fit, 1.8735). The test that claimed to reject 91/48 +- 1/100 used the bracket [1.821, 1.865], which rejects any slope near 91/48. It now uses [9052/4800, 9148/4800] and pins the edge at 23 and 24 thousandths. Tests now pin the smallest accepted half-widths that the README quotes (recomputed with 60-digit decimal logarithms), run table.mjs, check the grid search on a known answer, and check that steps and all pairs always agree. The README says why they agree, gives the Ising per-value errors as 0.4% to 1.4%, states how L'vov et al. fitted their Table I, and says what verify reads. The README.md run-list line and the CI line are dropped: open pull requests edit both files, and tests/scaling-check.mjs now runs table.mjs under npm test.
…e smallest case The README said steps and all pairs always give the same verdict. That holds on exact values only. With error bars every step can fit the bracket while a longer stretch does not. The README now gives the interval form of all pairs (a chain of difference constraints, Dechter, Meiri and Pearl 1991, as stated in Foundation-0/fractals draft pull request 60) and the smallest disagreement case. The test pins that case with its widened twin. The tool is unchanged.
The README now states when the interval form is exact: each box has 0 < L <= U and the bracket is not empty. Without the second condition the pair inequalities can pass while no slope exists. The long paragraph is split, and the case is called a smallest case, with three scales as the fewest that can differ. The test adds a bracket [1/2, 2] that the widened boxes must pass. A swap of p and q in either inequality now fails the suite. Before, every bracket in the section had p equal to q, so that swap stayed green.
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #57
What is added
Five new files. No existing file is edited, so this touches nothing an open pull request touches.
scaling-check/check.mjs:cmpPower(the sign of (y_b/y_a)^q - (x_b/x_a)^p in BigInt),exponentIn(a closed bracket in three modes),exponentInLog2(the same for a printed column of base-2 logarithms),tightestHalfWidth, and an 80-digit logarithm used only by the tests. No dependencies.scaling-check/series.mjs: the five series, each with the script that prints it, the commit (48b923b), the row and the column.scaling-check/table.mjs: prints the verdicts. Withverifyit runscritical/table.mjsandturbulence/table.mjs quickand finds every pinned number again.scaling-check/README.md: what the check certifies and what it does not, and the verdict on each series, including the ones it rejects.tests/scaling-check.mjs: picked up bytests/run.mjswith no change to it.Commands and output
node tests/scaling-check.mjsprints 40 lines marked PASS and ends withall scaling-check checks pass.npm testends withall 9 check file(s) pass. It takes about 45 seconds.node scaling-check/table.mjs verifyends withevery pinned number is in the output of the scripts (source commit 48b923b). It takes about 45 seconds and is not part ofnpm test.node scaling-check/table.mjsprints, for the percolation mass:bracket +-1/100: window rejects, steps rejects, pairs rejectsandsmallest half-width that is accepted (grid 0.001): window 0.024, steps 0.039, pairs 0.039.How each test can fail
A second reviewer made 25 single changes to the checker, the series and the tests, one at a time, and ran the tests on each. 24 do not pass. 23 turn the tests red: among them a dropped tie, a dropped sign, a truncated steps mode, one changed digit in each series, and a changed published exponent. One, a wrong power, makes the test run without end.
One change stays green under
npm test: reading the wrong column for one series inverify. Onlynode scaling-check/table.mjs verifycatches it, and that command is not in CI because it runs the Monte Carlo.The first version of the tests had one vacuous case. Its percolation bracket was not 91/48 plus and minus 1/100, so it would have passed with a slope of exactly 91/48. That case is corrected and the bracket edge is now pinned.
Standing of each statement
npm test. They are about the printed digits only.What a reviewer should look at
scaling-check/is the right place. The repository has no folder for a tool that spans studies, so this follows the study layout: code, a table script, a README and a test file.node scaling-check/table.mjsto both is a one-line follow-up once the open pull requests that edit them have landed.Update, 2026-11-21
The README used to say that the steps and all pairs modes always give the same verdict. That holds on exact values only. With error bars, every step can fit the bracket while a longer stretch does not.
The README now gives the interval form of all pairs and the two conditions under which it decides exactly whether values inside the error bars exist with every step slope in the bracket. This is consistency of a chain of difference constraints (Dechter, Meiri and Pearl 1991). Draft pull request 60 in this repository states and applies it, and this change cites it.
A new test pins a three-scale case where steps pass and all pairs fail, with a widened twin and two brackets that would catch a mistake in the inequality, all in exact integer fractions. The tool's behaviour and its other tests are unchanged. A reviewer broke the new check ten ways on a copy. Nine went red at once, and the tenth led to one more test.
AI assistance
Claude Sonnet 5.5 wrote the code, tests and text. Claude Opus 5.5 reviewed the change, recomputed the verdicts by a second route and ran the 25 single changes. Claude Fable 5.2 directed the work and reran the commands before posting. A human reviews before merge.