Qualification Status¶

Relaxation algorithm and lane matrix¶

Unsupported heterogeneous CUDA material payloads and unsupported adaptive/tableau combinations fail capability checks; no lane silently substitutes Heun, CPU execution, another minimizer, or a looser physical model.

Evidence basis¶

The relaxation promotion is backed by the managed production benchmark (39 comparison pairs, 21/21 required coverage), managed native source/operator/energy-derivative contracts, and CPU/GPU consistency 6/6 rows / 3/3 pairs. The public method pages under Relaxation document the per-algorithm contracts this matrix summarizes.

Frozen-spins qualification¶

frozen_spins constraints are implemented via the typed FrozenSpins contract in API and planner inputs, and they are governed by docs/validation/frozen-spins-v1-scope.yaml (scope_revision: 1, product_version: frozen_spins.v1).

Feature coverage is tracked in a separate lane-agnostic gate path with dedicated scopes and test sets, including:

• selector and membership behavior;

• reference mode semantics (capture_current_at_activation, initial_state, explicit_field_asset);

• empty/inactive selection policy;

• stage activation semantics, resume portability, and visualization support.

Operationally this is exercised through dedicated commands (for example just verify-frozen-spins-qualification and scope/gate companions) rather than by inference from the relaxation matrix.

Frozen-spins kwalifikacja — układ jednolitego wpisu (kod + Python + bibliografia)¶

import fullmag as fm
from fullmag.model.constraints import FrozenSpins
from fullmag.model.selection import in_region_selection

nm = 1.0e-9
study = fm.study("frozen_constructor_example")
study.engine("fdm")
study.device("cpu", precision="double")
study.mode("strict")
study.objects.mesh.defaults(cell_size=(2 * nm, 2 * nm, 2 * nm))
body = study.geometry(fm.Box(40 * nm, 20 * nm, 4 * nm), name="film")
body.Ms = 800.0e3
body.Aex = 13.0e-12
body.m = fm.texture.uniform(1.0, 0.0, 0.0)
study.stages.add_run(stage_id="run", until=1.0e-12)

# Direct constructor (public source class contract)
frozen = FrozenSpins(
    id="film_frozen",
    selector=in_region_selection("film", "all"),
    reference="capture_current_at_activation",
    membership=None,
    empty_selection="error",
    inactive_selection="warn_and_intersect",
)

import fullmag as fm

nm = 1.0e-9
study = fm.study("frozen_region_example")
study.engine("fdm")
study.device("cpu", precision="double")
study.mode("strict")
study.objects.mesh.defaults(cell_size=(2 * nm, 2 * nm, 2 * nm))
film = study.geometry(fm.Box(40 * nm, 20 * nm, 4 * nm), name="film")
film.Ms = 800.0e3
film.Aex = 13.0e-12
film.m = fm.texture.uniform(1.0, 0.0, 0.0)
film_region = film.add_region("core", fm.Box(20 * nm, 20 * nm, 4 * nm))
frozen_region = film_region.freeze_spins(
    id="film_frozen_region",
    reference="capture_current_at_activation",
    membership="snapshot_at_activation",
    stage_ids=("run",),
)
study.stages.add_run(stage_id="run", until=1.0e-12)

Per-interaction support matrices¶

Physics and numerical terminal pages own their four-lane FDM/FEM CPU/GPU support and qualification matrices. Those are the authoritative support status for an interaction; do not use the relaxation table above to claim an interaction is validated outside relaxation. Start from:

• Physical Interactions — canonical interaction pages;

• Numerical Methods — method and solver-lane realizations.

Not yet qualified¶

• Time-domain NIST SP4 reversal (artifact not_evaluated / unvalidated).

• GPU strict-residency and hosted CPU/GPU field parity rerun in the CUDA-visible runtime.

• Full FDM↔FEM cross-backend comparison matrix.

• Frozen-spins lane-agnostic qualification and artifact promotion are tracked by their dedicated frozen-spins gates and are not implied by this relaxation table.

These remain open until their dedicated gates pass with recorded artifacts.

Control Room crosswalk¶

Validation pages are inspection-only in Control Room. The UI may expose runtime metadata, fields, tables, or reports for inspection, but it does not create a qualification claim. TODO: frontend support applies to validation workflow authoring and report publication unless a specific control is named. See Control Room capability register.

Python/API crosswalk¶

Validation is not a standalone Python constructor unless the linked case page names one. Reproduce the exact case, inputs, device, precision, and receipt described by the page; use the referenced API pages for callable signatures.

Physics and bibliography scope¶

The page either states the governing benchmark model or delegates it to the linked physics/numerical-methods page. Any missing derivation is a documented boundary, not an implicit equation. Bibliography and source evidence remain the authoritative references listed by the validation case.

Source-code index¶

• No standalone implementation function is introduced by this validation page. Source evidence is the exact API, managed recipe, runtime manifest, and receipt named by the validation case.