about summary refs log tree commit diff
path: root/test/python
diff options
context:
space:
mode:
authorPjotr <wrk@bosa.lan>2026-11-15 12:40:09 +0000
committerPjotr <wrk@bosa.lan>2026-11-15 12:40:09 +0000
commitcb0527d043ac041508f111451392c64fcaf3643c (patch)
treef032da2ca2731e17dcc785ea9c13f34b670ca82d /test/python
parent93d48485ba1b366ae4b161e5f70e70603725db96 (diff)
downloadgenenetwork4-cb0527d043ac041508f111451392c64fcaf3643c.tar.gz
docs: what is missing from genenetwork4, ranked by migration effort
A survey of the three clones side by side (genenetwork1, genenetwork2,
genenetwork3) for functionality that would fit a JSON API, ordered by what
it would cost to migrate rather than by which repo it came from, in three
tiers: S (hours to a day), M (days), L/XL (weeks or a new concept).

Each row says which of GN1/GN2/GN3 carries the feature -- yes, part or no,
established by reading their code -- so a row is not mistaken for something
nobody has ever built. Nine rows are S, eight M, eight L/XL; the S tier is
almost entirely metadata, which is exactly the pattern the size evidence
explains: ProbeSetData 5 314 694 464 rows, LCorrRamin3 127 368 780, SnpAll
79 534 772 and GeneRIF 8 425 all in db_webqtl, so every value-shaped feature
is a query-design problem while every metadata feature is small.

Also lists what genenetwork4 already covers, the recommended order (matrix,
then tissue and literature correlation, then pagination and the dropdown
tree, then the sample-matrix and genotype exports, then partial
correlation), and where each feature lives in each clone.

ASCII only, aligned so the tables read as tables in a monospace view.
Diffstat (limited to 'test/python')
0 files changed, 0 insertions, 0 deletions