diff options
| author | Pjotr Prins <pjotr.public01@thebird.nl> | 2026-11-16 11:24:26 +0000 |
|---|---|---|
| committer | Pjotr Prins <pjotr.public01@thebird.nl> | 2026-11-16 11:24:26 +0000 |
| commit | 6f48a70b389f712bd5a53bbd7495cb40954a7eaa (patch) | |
| tree | 79ff90186a14815b7f814ce4ea618b35d128d944 /test/python/test_envelope.py | |
| parent | 9ff458ee52079a2385b231f0b7b629170ecfc6a1 (diff) | |
| download | genenetwork4-6f48a70b389f712bd5a53bbd7495cb40954a7eaa.tar.gz | |
cwl: make the ravanan path use the gemma build the wrapper path uses
`(specifications->manifest (list "gemma"))` resolved to Guix's `gemma`, which is 0.98.5 (banner 2021-08-25); gemma-wrapper pins `gemma-gn2`, which is 0.98.6 (banner 2022-08-05). Same source, different build, and the two paths disagreed in beta by ~3e-3 because of it. Now both name `gemma-gn2`. Verified on the job side: the latest runs' own logs report GEMMA 0.98.6 and OpenBLAS 0.3.31, the same pair the wrapper profile resolves to. The remaining difference is smaller and has a different cause, measured rather than guessed: same path, two cold runs: worst |Δbeta| 5.1e-6 (1034/21055 bit-identical) wrapper vs ravanan: worst |Δbeta| 3.1e-3 their kinship matrices: differ by ~1e-5 cell-wise, same 198 individuals So GEMMA is not reproducible run to run under multithreaded BLAS (both contexts report 96 threads), and the kinship matrix amplifies that by roughly two orders of magnitude into beta. Pinning threads on both paths is what would make the parity gate exact; until then 0.005 is the honest tolerance, and scripts/gemma-compare.py now defaults to exact and says which one it is enforcing. Also notes in the comment that a manifest change alone does not take effect: ravanan keys a step on (script, inputs), so it kept reusing step scripts built against the old manifest until the workflow source changed.
Diffstat (limited to 'test/python/test_envelope.py')
0 files changed, 0 insertions, 0 deletions
