diff options
| author | Pjotr <wrk@bosa.lan> | 2026-11-05 11:51:08 +0000 |
|---|---|---|
| committer | Pjotr <wrk@bosa.lan> | 2026-11-05 11:51:08 +0000 |
| commit | ff67b720f3d0c74739d8b8b657ac2e96bf171a1b (patch) | |
| tree | 611b7e39c97bf9168537835cd15267028a4e7f86 /test/python | |
| parent | b4ea4e3aaa9735c4d4342b98e3692cce52a40220 (diff) | |
| download | genenetwork4-ff67b720f3d0c74739d8b8b657ac2e96bf171a1b.tar.gz | |
gemma: key the gemma-wrapper cache dir by input set
The cache dir was keyed by chromosome only and shared across requests, so a request with different inputs (another trait, or another snps or genotype file) left a second *-gemma-cXX.tar.xz in the same chr-N dir. gemma-wrapper names those archives by a content hash, so the workflow's single-File glob output binding then matched more than one path and the step failed -- silently, since ravanan's user-error only logs when %log-level is set, which never happens inside a generated job script. Key the cache root by a hash of the input set (genotype path and size, snps contents, trait values, lmm) as well as by chromosome, so repeated identical requests still hit gemma-wrapper's cache while different input sets cannot see each other's archives. chromosomes_in reads the snps file, so it now takes the already-read contents (chromosomes_from) to avoid reading it twice. cwl/README.md: describe the two-part keying, and note that a node needs a writable HOME -- ravanan forwards the submitting process's HOME into the job (as sbatch would) and gemma-wrapper writes its lock file there.
Diffstat (limited to 'test/python')
0 files changed, 0 insertions, 0 deletions
