Package-level declarations
Types
The results database for benchmark experiments: SQLite by default (via the SQLiteDb base), holding the tables described by the table-data classes of this package.
Re-runs the confirmation stage of a finished benchmark against stored results, under a different selection rule, without re-running the search.
One row per (experiment, problem) confirmation stage: how many candidates were ranked, how many of them were confidently response-feasible at the confirmation's CI level, and whether the selection was therefore degenerate.
One row per confirmed finalist of a problem's confirmation stage: the finalist's point, its CRN-confirmed estimates, and whether it won.
One row per benchmark experiment. Experiment ids are assigned by the database (max + 1), so re-running an experiment — for example a trace-enabled rerun of a problem — appends into the same database under a new id.
One row per (run, iteration, state name) of a captured trace (opt-in): the cell solver's algorithm-specific state for that iteration.
One row per captured iteration of a run's trace (opt-in): the cumulative requested replications and the best penalized objective so far. Iteration 0 is the initialized state. Keyed by run id, so a trace-enabled rerun lands in the same database next to earlier trace-free experiments.
One point of performance-profile data: the fraction of a solver case's (problem, macro-replication) cells that reached the solve threshold within the given fraction of the replication budget.
One row per (experiment, problem, response constraint): the constraint as the problem defines it. Without these rows the database records what a run achieved but not what it had to meet, so answering "was every verified winner feasible?" meant hand-coding the constraint table from the specification and joining it externally. With them the question is a single join and the archive is self-describing.
One problem's replayed selection.
One row per problem per experiment: identity, shape (dimension, orientation, constraints), the reference solution when one exists, the gap basis the runs were measured against, and the problem's winning point.
One row per (run, response constraint): the cell best's estimate for the constrained response, by how much the constraint is violated, the one-sided upper confidence limit, and whether that constraint on its own can be declared feasible.
One row per (run, response): the cell best's estimate for every response of the problem, the objective included.
One row per benchmark cell: one solver case run once (one macro-replication) on one problem under the experiment's budget. numReplicationsRequested is the actual budget consumption used to normalize cross-algorithm comparisons.
The flattened configuration properties of a solver case, read from the first solver instance the case actually created during the experiment — the configuration that ran, not what was assumed.
One row per solver case per experiment; the case's parameters live in tblSolverCaseParameter.
One row per response of a problem's verification stage (opt-in): the winning point re-simulated at the experiment's verification replication count.