Say what the cell-mass test proves, and what it does not
Soul: a constant erf passes it. It is one necessary property, not correctness. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
parent
f3aae704e9
commit
cc71f17b7b
1 changed files with 5 additions and 3 deletions
|
|
@ -494,9 +494,11 @@ public sealed class MathTests
|
|||
}
|
||||
}
|
||||
|
||||
// The consumer-level property that actually matters: fire control turns adjacent erf
|
||||
// values into a cell's probability mass, so a backward step in erf would show up as a
|
||||
// negative mass. Soul checked these geometries clean: 16/64/256/1024/4096 cells over
|
||||
// One property the consumer needs, not the whole of correctness: fire control turns
|
||||
// adjacent erf values into a cell's probability mass, so a backward step in erf would
|
||||
// show up as a negative mass. An erf that returned a constant would pass this and is
|
||||
// caught by ErfMatchesReferenceValues instead.
|
||||
// Soul checked these geometries clean: 16/64/256/1024/4096 cells over
|
||||
// +-4 sigma, plus a tight 1 sigma spread and a very tight 0.25 sigma spread.
|
||||
[Theory]
|
||||
[InlineData(16, 4f)]
|
||||
|
|
|
|||
Loading…
Reference in a new issue