Backend
A numerical study of radius update rules in trust-region algorithms
arXiv cs.NA0 views
arXiv:2610.26134v1 Announce Type: cross Abstract: Part I [arXiv:2606.30202] and Part II establish which trust-region radius update mechanisms can fail and under which hypotheses they must succeed. Neither says where the thresholds sit once a rule runs with real constants, or how the rule interacts with the model Hessian and the subproblem solver. This paper turns them into nine falsifiable claims and settles what it can, on four designed problems where the theory's quantities are computable and on CUTEst, where only aggregate cost is visible. Every mechanism runs in one Julia package written for this study, so two runs differing in one component differ in nothing else. The rule is worth less than the model and more than nothing. Crossing the mechanisms with four model Hessians puts $96.5$ per cent of the variation on the model and $1.6$ on the rule, and the rules separate most under the most accurate model rather than least. Uncapped R-grad is the robust default among the criticality-anchored rules, though the retrospective rule is ahead of it on this collection. No constant escapes the side conditions. For every cap there is a minimiser at which the constraint stays active, and for every anchoring constant a flatness on which escape takes arbitrarily long. The second of these is proved here as well as measured, and the proof uses no property of the model or of the subproblem solution beyond $\|s_k\| \leq \Delta_k$. The radius rule governs the length of the step, and so the cost of a run. The model decides the search direction, and with it whether the run converges at all.
Source:https://arxiv.org/abs/2610.26134PreviousAdvancing the Theory of Sheffer Sequences via Dual Pad\'e Rational ApproximantsNextStructural conditions on trust-region radius updates. Part II: second-order convergence and asymptotic radius behaviour
Related posts
Turn Today’s Messy Notes Into Tomorrow’s Checklist With AI
0dev.to AI
A 763B MoE at "2 Bits": Where the Bytes Really Go in the GSQ-RCO GGUFs, and Why 100% Recovery Sits Inside the Noise
0dev.to AI
How I ship fixes to open-source projects maintainers actually merge (with AI in the loop)
0dev.to AI
Prompt Injection Through Documents: How to Harden an LLM Extraction Pipeline
0dev.to AI
Keeping noindex, the sitemap and the image sitemap in agreement for programmatic pages
0dev.to AI
3 Things in AI You Should Know: Character.AI Files for Bankruptcy
0dev.to AI