Confirmation
Options for the optional confirmation stage run after all members of a concurrent solver run complete. Members can return "best" solutions estimated with different precision (different replication counts, different luck), so picking the winner from point estimates alone favors noise. The confirmation stage re-evaluates the top candidates with common random numbers and picks the winner from the confirmed estimates — standard ranking-and-selection hygiene.
Parameters
the number of best candidate solutions to confirm; must be at least 1
the number of replications for each confirmed candidate; must be at least 1
Properties
True when both screening parameters are set, so the screening stage runs.
The overall confidence used when testing response-constraint feasibility during selection, matching Solver.recommendationCILevel so that confirmation and the solvers agree about which solutions count as feasible.
The replications per candidate used by the screening stage. Null (the default) disables screening; it must be supplied exactly when screenK is.
The rule used to rank candidates and to pick the winner. Null (the default) uses FeasibilityFirstComparator at recommendationCILevel, which is what the solvers themselves use, so confirmation and search agree about what "best" means.