tree fbfa75fdeb70512c77292713fe4fbf3ea2c918ec
parent 437d7af6a7bc88d79e8edd6e584a729bac947d5d
author Marc Kupietz <kupietz@ids-mannheim.de> 1788961295 +0200
committer Marc Kupietz <kupietz@ids-mannheim.de> 1788961295 +0200

Say what the imputed flag is about, and how labels become column names

Two things a reader of a multi-VC comparison stumbled over, both matters
of documentation rather than of behaviour.

`imputed` describes the node/collocate pair across all labels, not the
row it stands in, so a row whose own scores are perfectly attested still
carries `imputed = TRUE` when the pair is missing from some other virtual
corpus. That is what makes `filter(!imputed)` drop the pair as a whole,
and it reads as a mistake until said out loud. In a two-corpus analysis
of "Reform" every single flagged row was of that kind. `imputed_<label>`
is the one that speaks about the row.

And the label in `<measure>_<label>` goes through make.names(), so a
corpus called 1976-1980 turns up as logDice_X1976.1980, while the `label`
column and the winner/loser columns keep the name as given. Mapping
between them means applying the same transformation, which the
documentation now shows.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Change-Id: I9b3814107767cebf5c0f6656e71a59b5633c7eb9