Sharp First-Order Lower Bounds for Higher-Order Smooth Nonconvex Optimization
Abstract: We study the deterministic first-order oracle complexity of finding (ε)-stationary points in smooth nonconvex optimization when the objective satisfies higher-order smoothness assumptions. While the classical (ε{-2}) rate is optimal under only Lipschitz gradients, higher-order smoothness leads to accelerated first-order upper bounds, most notably the (ε{-7/4}) rate under Lipschitz Hessians and the (ε{-5/3}) rate under Lipschitz third derivatives. The matching lower bounds, however, have remained open. We resolve this gap by proving a new dimension-free first-order lower bound for higher-order smooth nonconvex functions, valid for every finite smoothness order. In particular, our construction gives a matching (Ω(ε{-7/4})) lower bound in the Hessian-Lipschitz case and a matching (Ω(ε{-5/3})) lower bound in the third-order-smooth regime. The hard instance is based on a \emph{block-chain} mechanism that enforces blockwise oracle revelation while preserving the smoothness structure needed for the scalar hard instance. The lower-bound construction was discovered with the assistance of ChatGPT 5.5 Pro and subsequently verified by the authors.
Paper Prompts
Sign up for free to create and run prompts on this paper using GPT-5.
Top Community Prompts
Explain it Like I'm 14
Explaining “Sharp First-Order Lower Bounds for Higher-Order Smooth Nonconvex Optimization”
1) What is this paper about?
This paper studies how fast any gradient-based algorithm can possibly be, in the worst case, when trying to find an “almost-stationary point” of a bumpy (nonconvex) function. “Gradient-based” means the algorithm only looks at the function’s value and its gradient (the direction of steepest change), not second derivatives or higher.
The big idea: when the function is extra smooth (not just the slope is smooth, but also the curvature and even higher wiggles change smoothly), some algorithms are known to speed up. The paper proves matching “lower bounds,” showing that these faster speeds are the best anyone can do with gradients alone. In short, the known fast rates are optimal.
2) What questions does the paper answer?
The authors ask: if the function is very smooth (for example, the curvature is well-behaved), how many gradient queries are fundamentally necessary to find a point where the gradient is small, say ?
- Without extra smoothness, the best-known (and tight) rate is about queries.
- With smoother curvature (Lipschitz Hessians), the best algorithms achieve about .
- With even smoother third derivatives, the best algorithms achieve about .
The open question: are these faster rates truly the best possible, or could an even smarter gradient method beat them? The paper proves tight lower bounds showing you cannot generally beat those rates.
3) How did they approach it? (Explained simply)
First, some everyday translations:
- Finding an “-stationary point” means finding a spot where the slope is tiny (the gradient’s length is at most ). Think of climbing hills and valleys: a stationary point is where the slope flattens out.
- A “first-order oracle” is like a helper you can ask: “What’s the height of the hill here?” and “Which direction is the steepest slope?” You cannot ask for curvature (second derivatives) directly.
- “Higher-order smoothness” means not only the slope changes smoothly as you move, but also the curvature (and possibly its changes) behave nicely. Imagine a road that is not only smooth but whose bends don’t change suddenly.
What is a lower bound? It’s a proof that no matter how clever your algorithm is (as long as it only uses function values and gradients), there exists a tricky function that forces you to make at least so many queries before you can find a small gradient. This shows a certain speed is impossible to beat in the worst case.
How do they build such a tricky function?
- Think of a maze with levels (phases) connected in a line. To move to the next level, you must discover a specific path in the current level. If your algorithm can only learn by following the gradient (like feeling your way in the dark), it must explore the maze level by level.
- Previous lower bounds used a “chain” of scalar variables—a simple corridor where progress to the last room is slow. But tuning that chain to match the best-known accelerated rates under higher smoothness was hard.
- The paper’s key innovation is a “block-chain” construction (not cryptocurrency!). Each level is now a block (a small group of variables) with:
- an entrance coordinate (like a door you have to open),
- and a hidden readout at the far end (like the exit).
- The trick: the nonconvex “difficulty” (the part of the function that creates the hard-to-reach gradient) is applied not directly to the block’s raw variables, but to a linear combination (a special “readout” of the block). This lets the authors finely control how smooth the function is at higher orders without making the problem easier to solve with gradients.
Analogy:
- Imagine each block as a hallway with an entrance and an exit. You only learn what’s behind the exit after you’ve walked through from the entrance. The gradient guidance will only reveal the next part if you’ve opened doors in order. This slows any gradient method that can only “see” nearby slopes.
- The linear readout is like placing a mirror at the end of the hallway that controls how sharply things appear—fine-tuning how “smooth” the reflections look—without letting you peek around corners too early.
Technically, this ensures:
- The algorithm cannot access the final part (where the gradient could be small) until it has revealed enough of the chain block by block.
- Meanwhile, the function is tuned so its higher derivatives are Lipschitz (well-behaved), matching the desired smoothness assumptions exactly.
“Dimension-free” means this hardness doesn’t disappear in high or low dimensions—the bounds don’t depend on how many variables there are.
4) What did they find, and why is it important?
The authors prove tight, dimension-free lower bounds on the number of gradient queries needed to reach an -stationary point under higher-order smoothness:
- With Lipschitz gradients only (the basic case): the classical lower bound is .
- With Lipschitz Hessians (second derivatives are well-behaved): the lower bound is .
- With Lipschitz third derivatives: the lower bound is .
These match the best-known upper bounds achieved by state-of-the-art first-order (gradient-only) algorithms. So the speedups people have designed are as fast as possible in the worst case—there’s no room for a faster exponent using only gradients.
Why this matters:
- It settles long-standing tiny gaps between what algorithms can do and what theory said might be unavoidable.
- It confirms that once third derivatives are Lipschitz, the “exponent” of the best possible rate saturates at —adding even higher smoothness (fourth, fifth derivatives, etc.) doesn’t buy you a better exponent if you still only use gradients.
- It gives a clear target for algorithm designers: if you want to beat these exponents, you need more than gradients (e.g., second-order information like Hessian-vector products), or different assumptions.
5) What are the implications?
- For practitioners: If your method only uses function values and gradients, you should not expect to do better than about (with Hessian-Lipschitz smoothness) or (with third-derivative Lipschitz smoothness) in the worst case. Algorithms already achieving these rates are near-optimal.
- For theorists: The “block-chain” hard instance is a new tool for building tight lower bounds while carefully controlling higher-order smoothness. It separates the “what you can see” (oracle revelation) from “where the difficulty lives” (the nonconvex readout), allowing finer calibration than past constructions.
- For future work: To surpass these limits, one must either:
- use richer information (like second-order queries), or
- impose stronger or different structural assumptions on the problem, or
- exploit special problem structures (like finite-sum problems, low dimensions, or stochastic settings) in ways not covered by these bounds.
In short: This paper closes a key theoretical gap and shows that the known accelerated rates for gradient-only methods under higher smoothness are exactly optimal.
Knowledge Gaps
Knowledge gaps, limitations, and open questions
Below is a focused list of what the paper leaves uncertain or unexplored, framed as concrete, actionable directions for future work.
- Randomized first-order methods: The lower bound is proved for deterministic algorithms. Does the same exponent (ε{-7/4} for p=2, ε{-5/3} for p≥3) hold against randomized first-order methods? Construct a distribution over rotated/scaled block-chain instances (Yao-style) and prove or refute matching randomized lower bounds.
- Dimension-dependent regimes: The result is dimension-free; it does not quantify the smallest dimension d needed to realize the hard instance at a given (Δ, L1:p, ε). Derive explicit lower bounds that trade off d and ε, and determine whether the ε-exponents can be improved in low dimensions (e.g., to match d-sensitive upper bounds such as O(d{1/4}ε{-13/8})).
- Log-factor optimality for p=3: For Lipschitz third derivatives, best known gradient-only upper bounds have an extra log(1/ε) factor, while the lower bound here does not. Is there a deterministic, gradient-only algorithm achieving O(Δ L1{1/2} L3{1/6} ε{-5/3}) without logarithmic factors? Or are log factors information-theoretically necessary?
- Mixed-oracle trade-offs: The paper addresses purely first-order oracles. Quantify tight lower bounds when a small number of Hessian-vector or higher-order queries are allowed, characterizing the optimal gradient–Hessian trade-off under higher-order smoothness (p≥2), and identifying the exact “few-second-order-queries” thresholds at which the ε-exponent changes.
- Stochastic and finite-sum settings under higher-order smoothness: Extend the block-chain construction to bounded-variance stochastic gradients and finite-sum models with p-smoothness, to obtain tight (dimension-free) sample/gradient lower bounds that mirror the deterministic exponents or reveal genuine stochastic barriers.
- Second-order stationarity with first-order oracles: The paper targets first-order stationarity. What is the optimal first-order oracle complexity for reaching approximate local minima (e.g., (ε, √ε)-second-order stationarity) under Lipschitz Hessian or higher-order smoothness? Can one prove matching lower bounds to complement the known upper bounds?
- Hölder-smooth higher derivatives: The analysis assumes Lipschitz continuity of the p-th derivative (order-1 Hölder). Generalize to Hölder continuity with exponent α∈(0,1] for Dp f, and characterize the exact ε-exponent as a function of (p, α).
- Non-Euclidean geometry and composite objectives: The lower bound is for unconstrained Euclidean problems with gradient-oracle access. Extend to (i) non-Euclidean smoothness (e.g., coordinate-wise or norm-specific smoothness) and mirror-descent oracles, and (ii) composite problems with proximable regularizers and projection/proximal oracles; determine whether the ε-exponents change.
- Robustness to oracle noise/inexact gradients: The hard instance and proof are deterministic with exact gradients. Establish lower bounds under inexact or noisy first-order oracles (e.g., additive or relative errors) and quantify how the ε-exponent degrades with noise level.
- Explicit constants and reliance on ℓq: The lower bound scales with constants ℓq from the scalar potential bounds and unspecified absolute constants (cε, chp, CM, cN). Derive explicit numerical constants or alternative potentials that reduce the dependence on ℓq (which grows super-exponentially in q), enabling sharper non-asymptotic statements.
- Minimal structural assumptions for orthogonal reduction: The extension from zero-respecting to general deterministic methods relies on orthogonal invariance of the function class. Provide a fully explicit distributional reduction and verify its applicability to randomized methods; delineate any function-class restrictions where the reduction fails.
- Tightness for p≥4 in terms of smoothness constants: While the ε-exponent saturates at 5/3 for p≥4, the lower bound uses min_{1≤q≤p}(Lq/ℓq){1/(2q)}. Develop matching upper bounds that adapt to whichever higher-order Lipschitz constant is most favorable (q≥4), validating the exact min-structure on constants, or prove that only L3 governs first-order acceleration.
- Minimal-dimension construction details: The calibrated instance sets d=MN with M≈(L1/Γp){1/2} and N≈ΔΓp/ε2 but does not give a tight lower bound on d as a function of (Δ, L1:p, ε). Specify the minimal d sufficient to achieve the lower bound and prove necessity via dimension-dependent lower bounds.
- Extensions beyond global smoothness: The framework assumes global Lq-Lipschitz bounds. Investigate whether similar lower bounds hold under local smoothness (e.g., smoothness only in a neighborhood of the iterates) or under structural conditions like gradient dominance/PL or Kurdyka–Łojasiewicz inequalities.
- Alternative targets and metrics: The result focuses on gradient-norm stationarity in the Euclidean norm. Establish whether analogous tight bounds hold for other stationarity measures (e.g., projected stationarity, stationarity in other norms) and for different optimization targets (e.g., function suboptimality with nonconvex objectives).
Practical Applications
Immediate Applications
The items below translate the paper’s results into concrete actions practitioners and researchers can take now.
- Optimizer selection and compute budgeting (software/ML/AI)
- What to do: Use the tight exponents ε-7/4 (Hessian-Lipschitz) and ε-5/3 (third-derivative-Lipschitz) as lower bounds on the number of gradient evaluations to plan training time and compute budgets. Prefer methods with Hessian-vector products or quasi-Newton updates when aiming for very small ε.
- Tools/workflows: “Complexity budget calculators” that take rough estimates of Δ, L1, L2, L3 and a target ε to compare first-order vs curvature-aware options; add-ons to PyTorch/JAX/TensorFlow that suggest enabling Hessian-vector products (HVPs) once ε is below a threshold.
- Assumptions/dependencies: Requires coarse estimates of smoothness constants and initial suboptimality Δ; the lower bounds are worst-case and deterministic (noise-free); HVP availability depends on autodiff support and acceptable per-iteration cost.
- Early stopping and target-ε policy (software/ML operations; daily practice)
- What to do: Set stopping criteria and learning-rate schedules around the proven exponents to avoid diminishing returns as ε shrinks. If a workflow cannot exploit HVPs, do not expect asymptotics better than ε-7/4 (if Hessian-Lipschitz holds) and certainly not beyond ε-5/3 even with higher smoothness.
- Tools/workflows: Dashboards that display projected remaining gradients vs ε under the tight exponents; automated alerts that recommend switching to curvature-aware steps or stopping.
- Assumptions/dependencies: Accurate progress tracking toward stationarity; relevance of first-order stationarity to the downstream task (e.g., validation loss correlation).
- Benchmarking and claim auditing for optimizers (software/academic standards)
- What to do: Use the block-chain hard instances as adversarial tests in optimizer suites to verify claims of “faster-than-ε-7/4” first-order acceleration under Hessian-Lipschitzness or “faster-than-ε-5/3” under third-order smoothness.
- Tools/workflows: Incorporate synthetic “block-chain” test generators into open-source benchmarking (e.g., a small library that exposes functions with tunable Δ, L1:Lp); add CI tests that fail if an optimizer purports stronger worst-case rates without additional oracle access or structural assumptions.
- Assumptions/dependencies: Implementations of the hard instances; tests remain deterministic; care with constants and finite-dimension effects.
- Practical smoothness profiling to guide method choice (software/ML/engineering)
- What to do: Approximate L2 via power iteration on Hessian-vector products and track Hessian variation along the trajectory as a proxy for Lipschitz Hessian; if third-derivative estimates are unreliable, default to the Hessian-Lipschitz regime.
- Tools/workflows: Lightweight HVP-based probes scheduled every K steps; “smoothness meter” panels in training logs that inform whether acceleration assumptions plausibly hold.
- Assumptions/dependencies: HVP probes add overhead; L3 is especially hard to estimate—treat estimates as heuristics.
- Reviewer/author checklists and course materials (academia)
- What to do: Adopt checklists that flag any deterministic first-order claim beating ε-7/4 (p=2) or ε-5/3 (p≥3) without extra oracle access or structure; integrate the block-chain construction and saturation result (“no exponent better than 5/3 for p≥3”) into advanced optimization curricula.
- Tools/workflows: Template sections in papers/syllabi explaining oracle model, smoothness order, and compatible rates; reference benchmark scripts.
- Assumptions/dependencies: Community uptake; clear oracle-model statements in submissions.
- Portfolio/planning for nonconvex solvers in engineering applications (robotics, imaging, energy, finance)
- What to do: For pipelines that must reach tight stationarity (e.g., high-precision trajectory optimization, medical image reconstruction, optimal power flow), plan for the lower-bound complexity or adopt curvature-aware routines to reduce exponents and wall-clock time.
- Tools/workflows: RFP/roadmap templates that budget compute using the tight exponents; “switch-to-second-order” gates when projected gradient calls exceed a threshold.
- Assumptions/dependencies: The modeled problem fits the smoothness regime; solver stack supports HVPs or quasi-Newton reliably.
Long-Term Applications
These items require further development, integration, or scaling before broad deployment.
- Automated optimizer selection and orchestration (software/ML platforms)
- What: Platform-level agents that estimate Δ, L1:Lp online, then route jobs between first-order, HVP-based, or higher-order solvers to minimize time-to-ε.
- Potential products: An “optimizer autopilot” for PyTorch/JAX that toggles HVPs, restarts, and preconditioning based on measured smoothness and the paper’s lower-bound-informed thresholds.
- Dependencies: Robust, low-overhead smoothness estimators; reliable cost models for HVPs on diverse hardware; policy logic validated on large workloads.
- Standardized worst-case benchmarking and certification (industry/regulation)
- What: Certification suites requiring demonstration against block-chain-type instances before marketing “accelerated first-order” claims; procurement guidelines that reference the tight exponents for compute planning.
- Potential products: An “Optimization Benchmark Standard” with reference instances and reporting protocols (analogous to MLPerf, but for optimizers).
- Dependencies: Community standards, governance buy-in, and neutral benchmarking bodies.
- Hardware-software co-design for curvature-aware optimization (semiconductors/cloud)
- What: Architectures and kernels optimized for fast HVPs and limited second-order routines, justified by the provable benefits over tight first-order lower bounds at small ε.
- Potential products: Accelerator libraries exposing fast HVP primitives; cloud instances with “curvature-optimized” SKUs bundled with solver stacks.
- Dependencies: Demonstrated end-to-end gains on major workloads; compiler/autodiff integration; cost/performance trade studies.
- Robust smoothness estimation libraries (software/research)
- What: Practical packages to estimate or bound L2 and (coarsely) L3 for large models/problems, enabling reliable entry into the Hessian-Lipschitz or third-order regimes.
- Potential products: “smoothness-probe” libraries with adaptive sampling and statistical guarantees.
- Dependencies: Methodological advances for noisy/stochastic settings; scalable linear-algebra kernels.
- Adversarial curricula for optimizer evaluation (research/ML engineering)
- What: Families of tasks inspired by the block-chain mechanism (layer-by-layer revelation, tail hiding) to stress-test exploration and stationarity in RL/planning and large-scale training.
- Potential products: RL/trajectory-optimization benchmarks that mimic the constructed hardness patterns to reveal optimizer weaknesses.
- Dependencies: Translating worst-case constructions into domain-realistic tasks; ensuring transferability of insights.
- Policy and sustainability analytics (policy/energy/enterprise IT)
- What: Use the tight exponents to model compute and energy consumption as a function of target ε, informing sustainability targets and cost forecasts for large training runs or optimization-heavy analytics.
- Potential products: Dashboards for CIOs/ML Ops that convert ε targets into projected energy/cost with scenario planning (first-order only vs curvature-aware).
- Dependencies: Organizational processes that set accuracy/ε targets; data on carbon intensity and hardware efficiency.
- Research roadmap and AI-assisted theorem discovery practices (academia)
- What: Codify human+AI workflows for lower-bound discovery, extending the paper’s AI-assisted construction to other oracle models (stochastic, finite-sum, distributed) and problem classes.
- Potential products: Open protocols and reproducible “theorem-crafting” notebooks; competitions for new hard-instance designs.
- Dependencies: Community norms for AI-assisted research; tooling and reproducibility infrastructure.
Cross-cutting assumptions and caveats
- Model of computation: Results are for deterministic first-order oracles; stochastic noise, finite-sum structure, or problem-specific geometry can change practical rates.
- Worst-case vs typical-case: The exponents are worst-case tight; many applications see faster empirical convergence. Use the bounds for risk management and guarantees, not as predictions of average behavior.
- Smoothness constants: L1:Lp and Δ are rarely known; practical tools must estimate them coarsely and remain conservative.
- Objective: Bounds are for first-order stationarity (‖∇f(x)‖ ≤ ε), not necessarily for test-set metrics, global minima, or second-order stationarity.
- Costs and constants: Tight exponents do not pin down constant factors; cross-over points where curvature-aware methods win must be measured on target workloads.
Glossary
- acceleration factor: A multiplicative improvement over the baseline gradient-descent rate due to additional smoothness structure. "the acceleration factor imposed by the active higher-order smoothness constraints."
- accelerated gradient: A momentum-based first-order method (e.g., Nesterov’s) that achieves faster convergence on smooth problems. "runs accelerated gradient in regions that behave convexly"
- approximate local minima: Points where the gradient is small and the Hessian is nearly positive semidefinite, within specified tolerances. "find approximate local minima within "
- block-chain mechanism: A constructed hard instance organized into blocks that enforce staged information revelation across iterations. "based on a block-chain mechanism that enforces blockwise oracle revelation"
- block-layer tail-hiding: A property ensuring later components of the instance remain unrevealed until earlier block layers are traversed. "yielding a block-layer tail-hiding property"
- blockwise oracle revelation: The design that forces an algorithm to uncover information one block at a time via oracle queries. "enforces blockwise oracle revelation"
- cubic-regularized subproblems: Local quadratic models augmented with a cubic term to control step sizes in second-order methods. "approximately solve cubic-regularized subproblems"
- “convex until proven guilty” framework: An approach that treats regions as convex unless evidence of nonconvexity is found, using that evidence to make progress. "The accelerated ``convex until proven guilty'' framework"
- deterministic first-order oracle complexity: The minimum number of function/gradient evaluations needed by any deterministic first-order method to reach a target accuracy. "We study the deterministic first-order oracle complexity of finding -stationary points"
- dimension-free: A guarantee or bound that does not depend explicitly on the ambient dimension. "a new dimension-free first-order lower bound"
- first-order oracle: An interface that returns function values and gradients at queried points. "first-order oracle calls"
- first-order zero-chain: A function whose gradient’s support reveals coordinates in a prescribed chain order, enabling lower-bound constructions. "a classical first-order zero-chain"
- Green-kernel: The inverse (or fundamental solution) of a linear operator used to characterize responses like entry-to-suffix coupling. "Green-kernel consequences"
- Hessian-Lipschitz: A smoothness condition where the Hessian varies in a Lipschitz-continuous manner. "In the Hessian-Lipschitz setting"
- Hessian-vector products: Products of the Hessian with a vector, enabling curvature-aware steps without forming the full Hessian. "uses Hessian-vector products to obtain curvature-aware guarantees"
- higher-order smoothness budgets: The available Lipschitz bounds on higher derivatives that constrain algorithm design and lower-bound calibration. "after enforcing the higher-order smoothness budgets"
- initial gap: The initial suboptimality that factors into iteration complexity. "For functions with -Lipschitz gradients and initial gap "
- Lipschitz gradients: A condition that the gradient does not change faster than linearly with distance. "under only Lipschitz gradients"
- Lipschitz th-order derivatives: A condition that the th derivative is globally Lipschitz, controlling higher-order variation. "has -Lipschitz th-order derivatives"
- Lipschitz third derivatives: A smoothness condition requiring the third derivative to be Lipschitz-continuous. "under Lipschitz third derivatives"
- linear observation map: A linear readout applied before a nonconvex potential to decouple smoothness scaling from revelation. "we introduce an additional balancing mechanism by applying the nonconvex potential after a linear observation map"
- lower bound: A provable limit showing that any algorithm requires at least a certain number of oracle calls. "we give a new dimension-free first-order lower-bound construction"
- massive path operator: A shifted path Laplacian combining a mass term and a tridiagonal path structure. "the corresponding massive path operator"
- mass scale: A tuning parameter (e.g., ) that sets the curvature baseline for calibration under smoothness constraints. "the largest mass scale compatible with all derivative Lipschitz constraints"
- minimax: A worst-case optimality notion comparing the best algorithm against the hardest instance. "gives the minimax claim"
- negative-curvature-based gradient methods: Algorithms that exploit directions of negative curvature to escape saddles faster. "negative-curvature-based gradient methods yield "
- nonconvex optimization: Optimization of functions that are not convex, typically featuring saddles and local minima. "smooth nonconvex optimization"
- nontrivial gap regime: The parameter regime where the initial gap is large enough to make the lower bound meaningful. "We assume the nontrivial gap regime in which ."
- operator norm: The maximum amplification factor of a linear/multilinear operator with respect to Euclidean norms. "we write ."
- oracle complexity: The study of how many oracle queries are needed to reach a target guarantee. "We follow the oracle-complexity framework"
- path Laplacian: The tridiagonal matrix encoding a chain (path) graph’s second-difference structure. "be the path Laplacian in tridiagonal form"
- path quadratic: The quadratic form induced by the path Laplacian (and mass), shaping interactions within each block. "the path quadratic forces zero-respecting methods to expose the block one coordinate layer at a time"
- pullback: The composition of a function with a linear map that transfers smoothness properties via operator norms. "Smoothness constraints are stable under such pullbacks"
- quasi-Newton method: A gradient-only method that builds Hessian approximations from gradients to accelerate convergence. "a gradient-only quasi-Newton method"
- q-linear form: A symmetric multilinear map of order used to represent higher derivatives. "viewed as a symmetric -linear form"
- regularized Newton methods: Second-order methods that add regularization to Newton steps for global convergence and complexity guarantees. "Classical trust-region methods and regularized Newton methods"
- residual certificate: A bound showing the gradient must remain large until certain coordinates are revealed, preventing early stationarity. "The following residual certificate is the key point"
- saddle-escaping: Algorithmic techniques or analyses focusing on escaping strict saddle points in nonconvex objectives. "Within the first-order saddle-escaping literature"
- scalar chain: A one-dimensional chain construction linking successive scalar states used in lower-bound hard instances. "We begin by recalling the scalar chain"
- scalar hard instance: A carefully constructed function in one dimension serving as the core of a lower-bound argument. "needed for the scalar hard instance"
- scalar potential: The one-dimensional nonconvex potential applied to each chain state. "be the scalar potential from Eq.~(10)"
- stationarity obstruction: A mechanism ensuring the gradient cannot be small (i.e., stationarity is obstructed) before certain revelations. "turn this residual certificate into an -stationarity obstruction"
- suffix projection: A readout restricted to a suffix of coordinates to separate observation from revelation. "read through a suffix projection"
- suffix readout: The linear readout of the current block’s suffix coordinates used by the nonconvex potential. "the current scalar state is read through a suffix projection" / "the suffix readout "
- tail hiding: Ensuring later (tail) coordinates remain zero/unseen to maintain a gradient lower bound until sufficient iterations pass. "Tail hiding for zero-respecting sequences"
- third-order-smooth regime: The setting where third derivatives are Lipschitz, enabling accelerated first-order rates. "in the third-order-smooth regime"
- trust-region methods: Second-order algorithms that restrict steps to a region where models are reliable, with established complexity. "Classical trust-region methods"
- zero-respecting methods: Algorithms that only activate coordinates that have appeared in past gradients, central to chain-based lower bounds. "A first-order method is zero-respecting"
Collections
Sign up for free to add this paper to one or more collections.