Skip to content

SEP 49: The TDSE response on native #764

Closed

Description

@jtravs

Tracks SEP 49: The TDSE response on native, and numpy_ref as a slim test reference (on its draft branch until the draft pull request merges; then docs/dev/seps/sep-0049-tdse-native-slim-reference.md on main).

It proposes two phases. First, the TDSE response runs on the native CPU build: native's Adams march evaluates the source through a host source hook, a Python callable that the native session binds and the compiled march calls holding the GIL at each source evaluation. That is an ADR exception to "no Python call in a trial step", limited to this hook; device builds refuse it. Second, numpy_ref becomes a slim test and development reference: the contract arithmetic (linear, source, Runge–Kutta and Adams trials, statistics) and the decision specification (adams_core, rk_core), with no step loop, sessions, groups, batch or registry row, and no longer selectable. Full-run parity becomes native's run replayed on the reference along its own steps, plus decision traces. Estimated cost: about −11.5k source lines, −12k test lines, +0.3k C++ and +0.4k native adapter lines.

Where it stands

What comes next

  • Merge the draft so it can be discussed in the developer documentation.
  • Human and AI reviews of Part I; answer the open questions Q1–Q10 (§12).
  • Acceptance by the maintainers.

To resolve first

Related

Done when

The SEP reaches Final, Rejected, Withdrawn or Superseded, and this issue closes with it. A Deferred SEP keeps it open.

Activity

  1. added
    priority: mediumReal work that should not wait long
    refactorInternal restructuring with no change in behaviour
    area: backendsAcross backends, and numba_cpu
    sepTracks an enhancement proposal (SEP)
    area: tdseThe TDSE response and its atomic providers
    on Nov 12, 2026
  2. added a commit that references this issue on Nov 12, 2026
  3. jtravs commented on Nov 12, 2026

    @jtravs
    ContributorAuthor

    Draft pull request: #765.

  4. changed the title [-]SEP 49: The TDSE response on native, and numpy_ref as a slim test reference[/-] [+]SEP 49: The TDSE response on native[/+] on Nov 12, 2026
  5. jtravs commented on Nov 13, 2026

    @jtravs
    ContributorAuthor

    Done in #771 (merged as 22f886e). SEP 49 is Final and archived: the TDSE response runs on native through the host-source hook, with Pyroraptor always in a worker process (ADR-078). A/B against main: geometric mean 0.986 on 8 cases (limit 1.015); non-TDSE runs bitwise identical on 7 cases with estimate plans. Follow-ups: #777 (strict-FMA checker bound), #785 (GPU TDSE comparison).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area: backendsAcross backends, and numba_cpuarea: tdseThe TDSE response and its atomic providerspriority: mediumReal work that should not wait longrefactorInternal restructuring with no change in behavioursepTracks an enhancement proposal (SEP)

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions