Skip to content

Fix validation and type-checking errors in optimizers - #201

Merged
AnderBiguri merged 1 commit into
CambridgeCIA:mainfrom
cslht:fix/optimizer-validation-errors
Aug 6, 2026
Merged

Fix validation and type-checking errors in optimizers#201
AnderBiguri merged 1 commit into
CambridgeCIA:mainfrom
cslht:fix/optimizer-validation-errors

Conversation

@cslht

@cslht cslht commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Four fixes in the optimizers:

  • EquivariantSolver captured loop variables by reference, so all four transforms were the same rotation_270; added i=i so each transform stays distinct.
  • GaussianDenoiserSolver passed (y, outputs) (noisy input vs. denoised output) to the validation function; now (outputs, data) so validation matches the training objective.
  • LIONsolver.check_training_ready had isinstance(x, type) backwards, so wrong-typed attributes were never rejected; now not isinstance(x, expected_type).
  • LIONsolver.test() compared a GPU tensor with a numpy array; added .cpu().numpy() on the prediction.

@AnderBiguri
AnderBiguri merged commit becdd45 into CambridgeCIA:main Aug 6, 2026
1 check passed
cslht11 pushed a commit to cslht11/LION that referenced this pull request Sep 6, 2026
…on-errors

Fix validation and type-checking errors in optimizers
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants