openvax / topiary / 33405901859

91%

master: 93%

push

github

Keep both versions when one LENS tool appears twice (#208) (#210)

* Keep both versions when one LENS tool appears twice

Keying binding columns on (tool, metric) fixed the version-brittleness
in #206 but left the emitted name - {tool}_{kind}_{field} - with no room
for a version. A table carrying netmhcpan_4.1b.aff_nm and
netmhcpan_4.2.aff_nm produced netmhcpan_affinity_value twice, one
version's values were dropped, and Metadata.models kept only one.
topiary said nothing: the only signal was a pandas duplicate-column
warning later, which does not name the predictor that lost its values,
and to_long() raised, so a consumer could not route around it. Closes

When one tool appears with several versions its columns are qualified -
netmhcpan_4.1b_affinity_value - following the convention to_wide already
uses for the same situation, and topiary warns naming the tool and the
versions. A file with one version per tool is unchanged, warning
included.

Also fixes an older, LENS-independent gap that this exposed: to_wide
appends the version to the model key on collision, but from_wide set
prediction_method_name to the whole key and left predictor_version NaN,
so a round trip produced a method named "netmhcpan_4.1b" with no version
and Affinity["netmhcpan", "4.2"] matched nothing. to_wide now records
the qualified keys in its metadata and from_wide reverses the encoding.

Claude-Session: https://claude.ai/code/session_01BAUqjqDDPXaTdtUDJqapJG

* Address review: real collisions only, explicit key map, version guard

Review of the #208 fix found two defects in it.

Version drift within a file split the predictor. The collision test was
"two version strings appeared for this tool", so a file spelling one
run's version inconsistently across metrics (netmhcpan_4.1b.aff_nm
beside netmhcpan_4.1.score_ba) was qualified into two half-populated
predictors — undoing #206. The test is now whether two versions claim
the same output column.

from_wide guessed at the encoding.... (continued)

55 of 57 new or added lines in 4 files covered. (96.49%)

5562 of 6119 relevant lines covered (90.9%)

2.73 hits per line