Benchmark Summary Header
What is known about a benchmark experiment before its first problem runs.
A sink needs this to open a record it can append to. It deliberately excludes everything that only exists once cells have run — solver configurations, traces, results — since the point of streaming is to write those as they arrive rather than at the end.
Parameters
the experiment's name
the number of macro-replications this experiment runs
the per-cell replication budget
the confirmation stage's finalist count; null when confirmation is off
the confirmation stage's replications per candidate; null when confirmation is off
the verification replication count; null when verification is off
the number of problems the experiment covers, counting any a resumed run skips, so the record describes the study rather than this pass over it
solver case label to its description
when the experiment's run() began
whether the experiment is capturing iteration traces
whether the experiment is capturing solver-specific state