ster pairs merge
Write one pair set out of several, every pair of each in the order named, for a direction fitted across all of them.
Invocation and purpose#
ster pairs merge --pairs <SET> --pairs <SET> [--pairs <SET>...] --trait <NAME> --output <FILE>The unified direction wisent's train-unified-goodness fitted across benchmarks is `ster vector train` on the set this writes. No model is loaded.
Inputs and options#
| Input | Required | Meaning |
|---|---|---|
--pairs <SET> | two or more | A pair set to merge; each passes the validation every pair set passes, and their pairs are written in the order named. |
--trait <NAME> | yes | The trait_name written on the merged set; must not be blank. |
--output <FILE> | yes | Pair-set JSON the merged pairs are written to. |
Output and state#
Writes the merged set as pretty-printed JSON with a trailing newline. Stdout is a pretty JSON document with output and report: the merged trait_name, pair_count, and one sources entry per set with its path, its own trait_name and its pairs. ster request pairs/merge takes {"sources": [...], "traitName": "…", "output": "…"} and answers the same document; Ster Desktop runs it from the Merge action.
Refusals#
- Fewer than two sets are refused as
pairs merge needs at least two pair sets and got <N>, and a blank trait name aspairs merge needs the trait name the merged set is fitted for. - Every source is loaded with the pair-set refusals:
failed to read pair set <PATH>,invalid pair set JSON in <PATH>,pair set <PATH> contains no pairs, andpair set <PATH> contains an empty positive or negative prompt. - Through the request, an empty source path is refused as
pairs merge names an empty pair-set pathand a missing output aspairs merge requires an output path, with status 2 before anything is read.