diff options
| author | Pjotr <wrk@bosa.lan> | 2026-11-14 22:58:18 +0000 |
|---|---|---|
| committer | Pjotr <wrk@bosa.lan> | 2026-11-14 22:58:18 +0000 |
| commit | 4d554b02daaea23b60826aa7b3c644baa55376d2 (patch) | |
| tree | b6f3e879d0509bcdad1abd5207b76afa5291925e /test/python | |
| parent | 3a62ef34c127d36fd4e04583349f64eee5de2c6f (diff) | |
| download | genenetwork4-4d554b02daaea23b60826aa7b3c644baa55376d2.tar.gz | |
docs: what GeneNetwork correlates, and what correlation_rust does
Answers the question that blocks duplicating the correlation_rust path: what is actually correlated. Four kinds over three axes -- sample (one trait vs every trait of a dataset, over individuals), tissue (gene vs gene over 26-32 tissue systems), literature (a table lookup in LCorrRamin3, no n at all) and partial (conditioned, GN3 only, async). Records the engine's contract as it is: JSON in, CSV out, one trait per line positionally aligned to x_vals, non-floats dropped pairwise, rows under 4 pairs refused, output sorted by |r| descending with NaNs last, top-N applied afterwards in Python, and no bicor in the engine at all -- which matters because GN3's Python path uses a minimum of 6 and the engine uses 4. Measured read-only against db_webqtl: ProbeSetData 5 314 694 464 rows, PublishData 3 288 638, TissueProbeSetData 90 562 DataIds with 26-32 values each (avg 29.0), LCorrRamin3 127 368 780. Hence no path loads a dataset whole, and the value fetch -- not the arithmetic -- is the cost. Ends with the two shapes a GN4 integration can take (thin: keep the file dance; direct: reuse parser::parse_rows_with_names and Pearson/Spearman in memory) and the four semantics that must be decided either way.
Diffstat (limited to 'test/python')
0 files changed, 0 insertions, 0 deletions
