diff options
| author | Pjotr <wrk@bosa.lan> | 2026-11-11 15:56:43 +0000 |
|---|---|---|
| committer | Pjotr <wrk@bosa.lan> | 2026-11-11 15:56:43 +0000 |
| commit | 69ff86d7c2125c34d4f8ccce09ed535b532377e2 (patch) | |
| tree | eebf533a09c47af99c98b23365b354b82f18a4bd /test/python/test_mapping_methods.py | |
| parent | cd3e65b6a03827d328aecb88c94406e85e5c161b (diff) | |
| download | genenetwork4-69ff86d7c2125c34d4f8ccce09ed535b532377e2.tar.gz | |
docs: how pve gets deployed, and what the deployed box runs
GEMMA_WRAPPER_CMD is the lever: the profile's gemma-wrapper may be older than the pin, and pointing the variable at the store path is enough -- -pve reaches GEMMA either way, but the per-run .log.txt files where pve lives are only kept beside the archive from 5eb53fa on. Recorded the verified production state too: both processes restarted with gemma-wrapper-1.00-pre1-4.5eb53fa, and POST /compute/gemma for BXD::10001 on the running instance returns pve 0.3125 to 0.9558 over 20 chromosomes -- measured there, not on a fixture.
Diffstat (limited to 'test/python/test_mapping_methods.py')
0 files changed, 0 insertions, 0 deletions
