Skip to content

SemanticCompute v1.10.4

Choose a tag to compare

@entertrainment entertrainment released this 28 Aug 10:39
· 1 commit to main since this release

SemanticCompute v1.10.4 — the mirrored BatchedCorrelation binding

One family variant, shipped alone so the verified 1.10.3 stayed frozen. Built to a consumer's falsifiable
acceptance criterion, which is the family's test, verbatim.

Added

crossCorrelationBatchMirrored — the shared reference on a (unshifted), each per-row signal shifted:
the single-pair consumer convention, batched. This is the binding perfusion Tmax needs (one shared AIF against
per-voxel TACs, peak at +delay), and the one the original binding cannot express: the two differ by the sign of
τ, only τ ≥ 0 is evaluated, and the keyword-invited substitution silently returns argmax 0 for every voxel —
asked for independently by two consumers who both hit exactly that.

  • Acceptance criterion, passing: every row bit-identical (==, not tolerance) to
    CorrelationReference.crossCorrelation(a: sharedReference, b: signal_j, numLags:).
  • The consumer's pinned delay-convention test ships batched: shared AIF = bump(6), signal row d = bump(6+d),
    row d's argmax == d for every d.
  • The footgun is an executable demonstration in the same test: the original binding on identical data pins
    every argmax to 0 — asserted, so the reason this variant exists is falsifiable.
  • GPU parity is the family's own stated bar (default float; expected cause: FMA drift in the dot product,
    measured ≤1.7×10⁻⁶). The adopting consumer explicitly declined trading FMA away: an integer-lag argmax cannot
    move at that delta except on a pathological tie. The bit-identity guarantee is the CPU convention, which is
    what an SLParityContract.bitExact adoption gate should gate.

Verification

1099 tests across 238 suites, green. Compile sweep: 340 programs across 199 lowerings, 0 failed.

Upgrade note

A running MCP server keeps the binary it started with: publish, reinstall, restart the client. sc_version's
buildCommit is the proof of what you are talking to.

Assets

macOS binaries are universal (arm64 + x86_64), Developer-ID signed and notarised. Linux binaries are provided
for x86_64 and arm64, statically linked. Verify any download against SHA256SUMS.txt.