CriterionChoice

data class CriterionChoice(val criterionName: String, val numComponents: Int?, val boundary: ComponentCountBoundary, val stillImprovingAtTop: Boolean)(source)

What one criterion preferred, and whether the range of counts it was given decided that.

A preference at the smallest count fitted is usually a real answer, and a warning on it would be noise. The case worth reporting is narrower: the preference sits at the smallest count while the criterion is still improving at the largest. On a sample of 10,000 production lead times searched over one to six components, BIC preferred one component while still falling at six, and carried to twelve it crossed below the one-component value at ten. The range decided that answer, and isUnfinished says so.

Parameters

criterionName

the criterion's name

numComponents

the count it preferred, or null when no count had a comparable value

boundary

where that count sits in the range fitted

stillImprovingAtTop

whether the criterion improved from the second-largest to the largest count with a comparable value, in its own direction; false with fewer than two such counts

Constructors

Link copied to clipboard
constructor(criterionName: String, numComponents: Int?, boundary: ComponentCountBoundary, stillImprovingAtTop: Boolean)

Types

Link copied to clipboard
object Companion

Properties

Link copied to clipboard
Link copied to clipboard
Link copied to clipboard

True when widening the range could change the preference: it sits at the largest count fitted, or at the smallest while the criterion was still improving at the largest.

Link copied to clipboard
Link copied to clipboard