vcycle-rate
At its defaults it draws convergence factor against grid size, with 2 pre-smoothing sweeps. Three curves against grid size on a logarithmic horizontal axis. Two rise towards one; the third is a flat line near a tenth.
vcycle-rate is one function in lib/figures/multigrid.js —
multigrid — the smoother, the coarse grid, and the rate that does not move. Everything below came out of it during this build, at
arguments taken from the essays rather than invented for this page. A figure here is the
figure a reader meets in an essay, and if the generator changes, this page changes with it.
At its defaults
Drawn even though every essay passes arguments — which on this site is every essay, at 100% of placements since the standard pass. A default nothing exercises is a trap for the next essay to call this with none, and this is the page where a default that has drifted from the figures around it becomes visible.
Three curves against grid size on a logarithmic horizontal axis. Two rise towards one; the third is a flat line near a tenth.
nu: 1
The arguments are the ones A block size is a property of the machine passes. A value drawn at the generator's defaults instead would be a picture no essay asked for and no assertion has been run against.
Three curves against grid size on a logarithmic horizontal axis. Two rise towards one; the third is a flat line near a tenth.
nu: 2
The arguments are the ones A rate that does not notice the size passes. A value drawn at the generator's defaults instead would be a picture no essay asked for and no assertion has been run against.
Three curves against grid size on a logarithmic horizontal axis. Two rise towards one; the third is a flat line near a tenth.
nu: 4
The arguments are the ones A rate that does not notice the size passes. A value drawn at the generator's defaults instead would be a picture no essay asked for and no assertion has been run against.
Three curves against grid size on a logarithmic horizontal axis. Two rise towards one; the third is a flat line near a tenth.
What it checked while drawing
Every figure above asserted its own claims on the way to being drawn, and a claim that failed
would have failed the build rather than drawn a wrong picture. Those assertions used to leave
no trace at all: a passing one returned true and the only evidence the figure had
checked anything was that nothing crashed. The list below is what they actually said, collected
by running this generator with an observer installed — not a description of
what it is believed to check.
16 distinct claims across 4 sets of arguments, grouped below by shape — because most of them are one sentence with a different number in it, and how many separate times that sentence was put to the test is the informative part.
and its factor at n = 15 is well under a third — asserted 4 times
Jacobi at n = 15 contracts at cos(πh) — asserted 4 times
multigrid converges on 15 points — asserted 4 times
between one and four pre-smoothing sweeps
the grid size is one less than a power of two
the V-cycle factor barely moves across a factor of eight in size
while the smoother's climbs
Against the rule
The rule does not apply to it. It factorises nothing, so there is no residual it could be withholding. That is worth stating rather than leaving blank: a site that reported the rule as satisfied by every generator would be counting mostly generators the rule never reached.
Across the library: the rule bites on 52
of 99 generators —
37 print a residual and
15 are exempt with a published reason;
47 factorise nothing.
Read from lib/residual-rule.js, which is the same body the gate enforces from,
and the gate's last check fails the build if this page and it disagree about any generator.
Where it is called
Changing this generator changes every figure on this list. That is what makes the list worth publishing rather than keeping in a check script.
A block size is a property of the machine
Three lines of counting say the best block size is √(M/3). Scanned over every integer at five fast memories, the measured optimum is √M − 2 — exactly, at all five. The count has the right scaling and the wrong constant, low by a factor of 1.56, and the wrong form: the answer is affine in √M rather than proportional to it.
Iterating, instead of factorisingA rate that does not notice the size
The V-cycle reduces the residual by a factor of ten a cycle at fifteen points and at a hundred and twenty-seven. Jacobi on the same four problems goes from 0.981 to 0.9978, climbing towards one. One of those is a constant and the other is an exponent, and that is the whole distinction the field turns on.
Iterating, instead of factorisingThe same problem on a coarser grid
Restriction, the coarse operator and interpolation are three matrices with nine distinct entries between them. Two of the three are each other's transpose, and their product with the fine operator is the coarse discretisation exactly — not approximately, entry for entry, at every level.