FAILURE MAP
← Case archive

FA-6401 / Discrete calculus / Open access

Inverse linear interpolation · case 01

The interval origin is not removed.

Verified by executionVariant 1 · 4 checks per implementationDownload source bundle ↓JSON ↗

ROOT CAUSE

The interval origin is not removed.

THE FAILURE

The interval origin is not removed.

Unsuccessful approach: Reversing the span sign reverses the parameter direction.

Case contract

Integer sample values and compatible sample-array lengths. Rational results are reduced Fraction strings; spacing is positive unless explicitly stated otherwise. a,b,x are integers; return None when the endpoint interval has zero span. Exact operational definition: str(Fraction(x-a,b-a)) if a!=b else None

Why this case matters

Small exact fixtures expose this error without platform timing, external services, or probabilistic observations. Discrete calculus results depend on the stated convention.

1 / The failure

Exit 1
"""Failure Map reference implementation. Python standard library only."""
import json
import math
import calendar
import statistics
import itertools
from fractions import Fraction
from datetime import date, datetime, timedelta, timezone
from decimal import Decimal, ROUND_HALF_UP, ROUND_DOWN, ROUND_CEILING, ROUND_FLOOR

N = 1
observations = []
def solve(a, b, x):
    return str(Fraction(x,b)) if b else None
def check(label, actual, expected):
    observations.append({"check": label, "actual": actual, "expected": expected, "passed": actual == expected})
check('fixture 1: (2, 10, 4)', solve(*(2, 10, 4)), '1/4')
check('fixture 2: (3, 7, 3)', solve(*(3, 7, 3)), '0')
check('fixture 3: (3, 7, 7)', solve(*(3, 7, 7)), '1')
check('fixture 4: (2, 2, 2)', solve(*(2, 2, 2)), None)
print(json.dumps({"observations": observations, "passed": all(x["passed"] for x in observations)}, ensure_ascii=False))
raise SystemExit(0 if all(x["passed"] for x in observations) else 1)
Boundary fixtureActualExpectedOutcome
fixture 1: (2, 10, 4)2/51/4Failed
fixture 2: (3, 7, 3)3/70Failed
fixture 3: (3, 7, 7)11Passed
fixture 4: (2, 2, 2)1NoneFailed

SHA-256 / c3af5676b751693b1cc1dca09a59cf0afd357ef6c5d592432c8af383fd2efba1

2 / The unsuccessful fix

Exit 1
"""Failure Map reference implementation. Python standard library only."""
import json
import math
import calendar
import statistics
import itertools
from fractions import Fraction
from datetime import date, datetime, timedelta, timezone
from decimal import Decimal, ROUND_HALF_UP, ROUND_DOWN, ROUND_CEILING, ROUND_FLOOR

N = 1
observations = []
def solve(a, b, x):
    return str(Fraction(x-a,a-b)) if a!=b else None
def check(label, actual, expected):
    observations.append({"check": label, "actual": actual, "expected": expected, "passed": actual == expected})
check('fixture 1: (2, 10, 4)', solve(*(2, 10, 4)), '1/4')
check('fixture 2: (3, 7, 3)', solve(*(3, 7, 3)), '0')
check('fixture 3: (3, 7, 7)', solve(*(3, 7, 7)), '1')
check('fixture 4: (2, 2, 2)', solve(*(2, 2, 2)), None)
print(json.dumps({"observations": observations, "passed": all(x["passed"] for x in observations)}, ensure_ascii=False))
raise SystemExit(0 if all(x["passed"] for x in observations) else 1)
Boundary fixtureActualExpectedOutcome
fixture 1: (2, 10, 4)-1/41/4Failed
fixture 2: (3, 7, 3)00Passed
fixture 3: (3, 7, 7)-11Failed
fixture 4: (2, 2, 2)NoneNonePassed

SHA-256 / 2a99541309c849e5b7ef708d5a53b153c296eafc2316923175b5ebf67697b949

HELD IN THE MEMBER ARCHIVE

The verified repair and its recorded checks are member-only.

This mechanism has 4 recorded checks per implementation. The open-access tier publishes the failure and the unsuccessful fix; the repaired source that passes every check, and the observations that prove it, are available to members.

Every case sharing this mechanism uses the same contract and the same repair, so this one record is held back for all of them.

Member access is invitation-based. Sign in with your invited account to inspect the repair.

Sign in to the archive ↗

Verification & scope

This reproducer isolates one failure mechanism. Results cover the supplied fixtures. Variants within a family share a test contract and should remain grouped when constructing evaluation splits. Related mechanisms with a shared evaluation_group must also remain together; these controlled models are not independent production incidents.

Observations recorded using Python 3.12.14 at 2026-09-29T14:38:01.538736+00:00.

Case digest / fa39f8e5a597d4ee7ef9a6499599a0739e74ac28b5a197c604246a2a4c5117d7