`mtrag_federated` partitions one domain by article title, which is round-robin fusion's friendliest case: no collection is ever off-topic for a query, so the guaranteed-slot waste that hurts a real deployment is never exercised. Every fusion conclusion measured on it is therefore provisional. `mtrag_pooled` pools all four MTRAG domains, so a query belongs to one and the rest are genuinely off-topic. `collection_of` gains `alpha`, which now means something: 0 keeps a collection to one domain, 1 ignores the domain and shards titles uniformly. Domains map onto collections proportionally, subdividing by title where there are more collections than domains and grouping where there are fewer. Passage ids are checked for collisions across domains, since gold is uri-keyed and a shared id would make it ambiguous. Claude-Session: https://claude.ai/code/session_01WhudUtZm6qqiuv8Y1sbwSc |
||
|---|---|---|
| .. | ||
| frames.yaml | ||
| hotpotqa.yaml | ||
| mtrag_clapnq.yaml | ||
| mtrag_federated.yaml | ||
| mtrag_pooled.yaml | ||
| orb_multimodal.yaml | ||
| orb_multimodal_nemotron.yaml | ||
| orb_text.yaml | ||
| t2_finqa.yaml | ||