Port parity
Several methods here have two implementations: the authors' original and its QSM.rs port. A parity check runs both on the same data and checks they still agree as closely as when the limits were set. Released checks what users get: the latest QSMxT release. Development checks QSMxT and QSM.rs as they are now, before their next release.
Tested: QSMxT
(),
the binary the release ships, with QSM.rs
as it pins it (not run yet).
No QSMxT release is known yet.
A release does not change, so it is checked once, and again only when a pair's original or its settings change. A failure is that release's result. Not in means the release has no such command or option yet. This is an older release: its results as recorded.
Tested: QSMxT main
with qsm-core at QSM.rs main
.
Nothing recorded yet.
A check is stale when the original's image changed, QSM.rs changed the port's source
files or its Cargo.lock, QSMxT changed how it runs the step or its
Cargo.lock, the pair's limits changed, or it failed. It does not expire with age.
Status as of .
Release history
Each QSMxT release's result per pair, newest first. Pick a release to see its full table.
| Algorithm | |
|---|---|
| — | |
| No release has been checked yet. |
No original to check against
These QSM.rs methods have no original code to compare with, so they have no parity check; QSM.rs tests them against known answers instead.
- :
How the checks run, the two tracks, the limits, and how to rerun one: docs/parity.md. The history behind these tables: parity/results.json.