Censored algorithm runtime
ID: censored-algorithm-runtime
A censored algorithm runtime is an evaluation that ends without observing the algorithm's actual completion time. A timeout or adaptive capping limit can establish that the run had not finished by the cutoff, supplying right censoring rather than an exact completed runtime. The ParamILS capping analysis uses such elapsed-time information to bound comparisons without finishing every run.[ref]
ParamILS: An Automatic Algorithm Configuration Framework by Frank Hutter and others. Section 4, runtime bounds and stopped evaluations
Write for completion time and for a stopping limit. A simple record iswhere means completion was observed. The event flag is essential: the same stored duration can mean a completed run or only a lower bound on a still-running computation.
For an original example, two completed runs take and seconds and a third is stopped unfinished at seconds. Averaging the stored durations gives seconds, but that is only a lower bound on the mean of the actual completion times. If the third would take seconds, the true mean is seconds. Discarding it entirely gives seconds and removes the difficult run from the comparison.
Keep exact observations, cutoff information and any timeout penalty separate. A penalized benchmark score may deliberately assign a stated cost to a timeout; that score is not an observation of . Estimating completion-time distributions additionally requires assumptions about how stopping limits were chosen, particularly when the limits depend on earlier performance.
New to topics? Read the docs here!