diff options
| author | Pjotr <wrk@bosa.lan> | 2026-11-09 18:30:52 +0000 |
|---|---|---|
| committer | Pjotr <wrk@bosa.lan> | 2026-11-09 18:30:52 +0000 |
| commit | adb75296ecd9ef24f4abed0f45a6b8f6dd657d9b (patch) | |
| tree | 7e415fd6a3d87156bbf253977796478ae16804af /test/python/test_dev_token.py | |
| parent | eb5320d6f51279acf0b65e5bc9755eec927c93ea (diff) | |
| download | genenetwork4-adb75296ecd9ef24f4abed0f45a6b8f6dd657d9b.tar.gz | |
docs: the skill says fitqtl fits covariates
`/compute/fitqtl` has taken `covariates` since c642f87, and the skill
mentioned it only as a trailing sentence inside the fitqtl bullet -- after
the paragraph that says "both engines", which an assistant skimming for
covariates reads as rqtl-and-gemma. Three changes so the offer is where a
reader looks for it:
* the covariates bullet now names all three endpoints
(`/compute/rqtl`, `/compute/gemma` **and `/compute/fitqtl`**);
* the fitqtl bullet says it in bold, with why it matters (the `additive` is
then the effect *after* conditioning), and adds the consequence that the
LOD no longer matches the scan once a covariate is fitted -- the earlier
wording claimed parity unconditionally;
* the endpoint table gained `POST /compute/{rqtl,gemma,fitqtl}` (it had no
entry at all), and the session outline now includes sizing a peak with
fitqtl when the user asks how much it matters.
Docs only.
Diffstat (limited to 'test/python/test_dev_token.py')
0 files changed, 0 insertions, 0 deletions
