@qtsurfer/api-client
    Preparing search index...

    Type Alias SweepMarginalPoint

    How the objective behaved at one value of one axis. best and mean disagreeing is informative rather than noise: a high best with a poor mean marks a value that only works alongside particular settings of the other axes.

    type SweepMarginalPoint = {
        best?: number;
        count?: number;
        mean?: number;
        value?: unknown;
        worst?: number;
    }
    Index
    best?: number
    count?: number

    Non-aborted runs that used this value.

    mean?: number
    value?: unknown

    The axis value, as it appears in a run's parameters.

    worst?: number