Batch Completed Comparison Source
Scenario-host adapter that exposes a completed scenario sweep — the RunResult.BatchCompleted surfaced through whichever controller owns lastResult — as a ComparisonDataSourceIfc for the comparison analyzer UI.
Each scenario in result becomes one ExperimentRow. The experiment's response set is the union of names recorded across its ReplicationCompleted snapshots:
WithinRepStatTableDatarows → ResponseCategory.OBSERVATION. The bridge does not separately tag observation vs time-weighted responses in within-rep records; the discrimination would require joining through the model-element table, which is only available to the (future) database adapter.WithinRepCounterStatTableDatarows → ResponseCategory.COUNTER.
observations returns per-replication values in rep_id order: for response statistics, the average field; for counters, the last_value field (the running count at end of replication).
Lookup is by experiment.exp_name — the authoritative scenario identifier the substrate populates from Model.experimentName, which the orchestrator sets from ScenarioSpec.name.
Properties
Functions
All experiments available for comparison from this source, in source-natural order (commit order for scenarios, execution order for design points, table order for DB loads). Empty when the source has no experiments.
Per-replication observations for the given experimentName / responseName pair. Returns null when the experiment did not record that response, when the experiment is unknown, or when no per-replication data is available (counters that record only an end-of-replication count are surfaced as last_value and still return a one-value-per-rep array). Empty array is reserved for "experiment recorded the response but produced no values" — vanishingly rare in practice but worth distinguishing from "no recording at all".