Skip to content

Add track and max_outer to solve_nnqp_eq for API symmetry with solve_nnqp #20

Description

@tschm

Subcategory: Code structure / API completeness — feature gap (not a defect)
Source: rhiza_quality assessment

Problem

After aligning the inner argument between the two entry points, solve_nnqp_eq still lacks two parameters that solve_nnqp exposes:

  • track — record the free-set trajectory in Result.traj
  • max_outer — cap on outer steps (returns the current iterate with converged=False when hit)

The underlying _active_set_loop already supports both (the solve_nnqp_eq call site just doesn't forward them), so this is a small, mechanical symmetry fix.

Where

  • src/nncg/solver.pysolve_nnqp_eq signature and its _active_set_loop(...) call (currently omits track / max_outer)

Done when

solve_nnqp_eq accepts track: bool = False and max_outer: int | None = None, forwards both to _active_set_loop, with docstrings updated and tests covering the trajectory-recording and outer-cap paths (keeping coverage at 100%).

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions