Skip to main content

warm_rung_max_iter

Function warm_rung_max_iter 

Source
pub fn warm_rung_max_iter(
    fallback_live: bool,
    previous_point_iterations: usize,
    caller_max_iter: Index,
) -> Option<Index>
Expand description

The max_iter a warm-started continuation rung runs under, or None to leave the caller’s.

warm_rung_budget is safe only because a rung that reaches it is re-solved cold by mu_strategy_fallback. Where that retry will not run (fallback_live false: the caller switched it off, or named a mu_strategy), the budget would be a hard stop that cuts a slow but converging rung and abandons the schedule, so there is none.

previous_point_iterations is what the attempt that produced the previous rung’s point took, not everything its call spent: after a capped rung is rescued (500 + 124 on ieee300_reserve_q98), ten times the total clamps to the caller’s max_iter and leaves the next rung unbudgeted.