check
check: 5 implementations from 6 papers ran on one shared input (census 2026-09-22, battery b986f7e04d79); they produced 4 distinct outputs across 4 buckets, one shared input per bucket.
Identical values to six decimals (the recorded digest) on the shared input are agreement on those inputs, not equivalence. Implementations are compared only within one bucket, the positional (rank, kind, dtype) of each array argument; the argument name is not part of the key because the harness draws the shared array from (rank, kind) and casts it to the dtype, whatever the name; each bucket's shared input is fixed by that key, so members of one bucket saw bitwise-identical inputs under their own scalar arguments. A cluster is the set of members whose recorded output digest is identical. Nothing here says which computation a paper's method intended, and nothing reproduces a paper's results.
Not compared, and not in the tables or the counts above:
- Every examined implementation of this name that took an array argument ran on the shared input.
- 2 more implementations from 2 papers took no array argument and ran only on their own fixture arguments; no shared input existed for them, so they are not compared (on 2 the recorded shared-output digest is the own-fixture digest).
- Every compared output was digested.
Bucket 1 of 4: arg 1: rank 2, kind float, dtype float32
2 implementations from 3 papers share this bucket (rank, kind, dtype of each array argument, positional; each member's recorded signature, argument name included, is shown under it); 1 distinct output, largest cluster first. Values are the first 8 of the recorded output, flattened.
| Cluster (same digest to six decimals) | Members | Shared output on this bucket's input |
|---|---|---|
| 2 implementations 3 papers d7bd5ceec8a6 recorded values identical |
algorithms/happo_trainer.py 9589eca5 recorded input:2/float/float32 src/algo/r_mappo/hdd_net.py 48291050 recorded input:2/float/float32 |
[1.80263, -1.53378, 0.476053, -0.690887, -0.902849, -1.03047, -0.662761, 0.572889, …] shape [4, 8] · float32 · Tensor |
Bucket 2 of 4: arg 1: rank 1, kind float, dtype float32
1 implementation from 1 paper share this bucket (rank, kind, dtype of each array argument, positional; each member's recorded signature, argument name included, is shown under it); 1 distinct output, largest cluster first. Values are the first 8 of the recorded output, flattened.
| Cluster (same digest to six decimals) | Members | Shared output on this bucket's input |
|---|---|---|
| 1 implementation 1 paper 7602a99aa949 |
ood_detection.py cc7e84fa recorded x:1/float/float32 |
[-0.903889, 0.157131, 0.897612, -0.762196, -0.176256, 0.0530317, -1.62844, -0.177533] shape [8] · float32 · Tensor |
Bucket 3 of 4: arg 1: rank 1, kind float, dtype float64
1 implementation from 1 paper share this bucket (rank, kind, dtype of each array argument, positional; each member's recorded signature, argument name included, is shown under it); 1 distinct output, largest cluster first. Values are the first 8 of the recorded output, flattened.
| Cluster (same digest to six decimals) | Members | Shared output on this bucket's input |
|---|---|---|
| 1 implementation 1 paper af5570f5a181 |
src/experiments/metric_validation.py 434a3e71 recorded arr:1/float/float64 |
[0] shape [] · bool |
Bucket 4 of 4: arg 1: rank 2, kind float, dtype float64
1 implementation from 1 paper share this bucket (rank, kind, dtype of each array argument, positional; each member's recorded signature, argument name included, is shown under it); 1 distinct output, largest cluster first. Values are the first 8 of the recorded output, flattened.
| Cluster (same digest to six decimals) | Members | Shared output on this bucket's input |
|---|---|---|
| 1 implementation 1 paper 6c3c396ed6b5 |
ReLU_normal/cvx_train_normal.py b8bf3dc7 recorded X:2/float/float64 |
[1] shape [] · bool |
Identical values to six decimals (the recorded digest) on the shared input are agreement on those inputs, not equivalence; where a cluster's members carry recorded values, the largest difference among them is shown under the cluster. Paper titles are the archive's archive 2025-07-28 where the paper is in the archive and the graph's where it was added by Syntology; papers with no page here are shown by their recorded paper id only. A paper count above the implementation count means one implementation (one code sha) is held from several papers' repositories and counts once. Per-sample status, licence and fingerprint records for each paper are on its paper page. JSON twin: /census/check.json.
Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections