diff options
| author | Pjotr <wrk@bosa.lan> | 2026-10-15 14:29:49 +0000 |
|---|---|---|
| committer | Pjotr <wrk@bosa.lan> | 2026-10-15 14:29:49 +0000 |
| commit | fcfb9e12d996be1520af74e8521367916d2e8041 (patch) | |
| tree | 3d93c8565cdde3a42a34a2deb8709fff276fa3e7 /test/python/test_traits.py | |
| parent | 7f56f54622c704840c34e2b8f289bdb5220e9975 (diff) | |
| download | genenetwork4-fcfb9e12d996be1520af74e8521367916d2e8041.tar.gz | |
gemma: give each scattered chromosome its own persistent cache dir
--cache-dir "." pointed every scattered job at its own hermetic CWL working directory (fresh under ravanan's --store every run), so gemma-wrapper's cache was never actually reused across requests. Point it instead at <ravanan_cache_dir>/gemma-wrapper-cache/chr-<N>, one persistent directory per chromosome -- not a single shared directory, because gemma-wrapper's cache-hit hash does not vary with --chromosomes, so sharing one directory would let one chromosome's job silently reuse another's cached result. Also drops gwa.cwl's InitialWorkDirRequirement staging hack: since kinship and gwa for the same chromosome now point at the same persistent cache_dir, gemma-wrapper finds the kinship step's archive there directly, no staging needed. Confirmed via a real integration run (BXD fixtures) that gemma-wrapper itself unconditionally re-executes GEMMA regardless of whether a matching cached archive already exists -- --cache-dir is only used to hand results between gemma-wrapper's own pipeline stages within one request, not to skip recomputation across requests. So this fixes a real latent bug (archive-glob collisions once a chromosome's cache directory holds more than one request's output) but does not, on its own, speed up repeated identical requests; verified the direct /compute/gemma path shows the same lack of cross-request speedup.
Diffstat (limited to 'test/python/test_traits.py')
0 files changed, 0 insertions, 0 deletions
