math-canonical-curve-on-the-cost-counter

# Draw the field's plain two-curve figure against the algorithm's own cost counter, before any richer diagnostic In algorithms and optimisation the standard result artifact is one plain figure: the field's headline scalar on the ordinate against the algorithm's own implementation-independent cost counter on the abscissa, with every competing method on the same axes as an additional curve or a labelled horizontal reference line. Draw that figure first, alone, in its own panel. Folding it into an eleven-series multi-panel diagnostic destroys it -- a reader has to be able to see one curve sitting below another. Pick the abscissa another group can reproduce on different hardware: iteration index, oracle or function evaluations, node expansions, sample count, instance size, number of agents or items. Wall-clock time is a legitimate second figure and never a substitute for the first; on a shared or loaded machine it is also the axis a referee discounts. For residuals, duality gaps and objective gaps use a logarithmic ordinate across the full decade span, and draw the target tolerance as an annotated horizontal line. State the headline scalar in the paper's own unit on a three-point scale: prior method, your method, and the oracle, human or ideal reference where the field defines one. If the available instances are smaller than the benchmark the claim concerns, run the reduced set anyway, report the achieved-versus-target ratio explicitly, and support it with a scaling curve acro...