Which load cases make up a combination's result
combination_contributionsLoad Combination Contribution Analyzer, step 2. Splits one or more load combinations' results at a set of items into the load cases that produced them: for every item, output point (beam I/J and intermediate points, plate nodes and centre), component and max/min, the signed contribution of each case, its share of the gross, and the governing permutation written out with factors multiplied down (e.g. 1.35Self weight(ST) + 1.5LM1(MV:max)). Add superposes; an Envelope is resolved to the child that governs at each item (the governing child is counted per envelope); ABS gives |f·R| shares; SRSS energy shares. Moving-load, settlement and response-spectrum cases enter at their max or min end. Construction-stage cases are read at the final stage's last step. Cases are identified by type and name together. EVERY item is recomposed and must match the value CIVIL NX reports for the combination at the same item, part, component and sense — if any does not, the run stops and nothing is reported. Returns per combination: the cases ranked by share of the gross over the run, cases zero everywhere, envelope governing counts, and the critical item (largest |value|) per component and sense with its full breakdown; rows largest |value| first; csv: true stores every row. Tables: BEAM, TRUSS, PLATE (per unit length, local axes), ELASTICLINK, GENLINK, REACTION (supported nodes only — CIVIL NX answers other nodes with a made-up total; zero reaction rows it omits are read as zero), DISPLACEMENT. Items in set syntax (elements 101to148, nodes N1toN20, general links L5, elastic links EL7) and/or structure groups (for node tables: the group's nodes plus the nodes of its elements). Read-only (only /post/TABLE reads). Runs as a job on the website.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"combinations": "<combinations>",
"table": "<table>"
},
"name": "combination_contributions"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| csv | No | Also store every row with every case's contribution as a CSV and return its link. | |
| items | No | Items in set syntax, e.g. "101to148", "N9001toN9006", "EL1toEL10". Typed ids must exist and be of the table's kind; ranges keep only what fits. | |
| sense | No | For max/min-pair combinations: which end(s). Ignored for single-valued ones. | both |
| table | Yes | Which result table to decompose. | |
| units | No | Units to report in (CIVIL NX converts). Default: the model's own. | |
| groups | No | Structure group names to add to the set. | |
| maxRows | No | At most this many rows inline (largest |value| first). | |
| components | No | Components to decompose (table column names, e.g. Moment-y, Shear-z, FZ, DZ, Mxx). Default: all of the table's. | |
| combinations | Yes | One General-tab combination name, or up to 10 decomposed at the same items in the same run. |