Skip to content

Conversation

@HKaras
Copy link
Member

@HKaras HKaras commented Jul 1, 2024

Fixes an issue that prevents the grid mode in selregparam.

Now the regparamrange is used to decide if brent or grid algorithum is used.
Closes #476

HKaras added 7 commits June 12, 2024 22:21
Regparam would never build the grid correctly. Now using grid or Brent is automatically determined from number of elements in the regparamrange.
@HKaras HKaras added the bugfix Patches something that isn't working label Jul 1, 2024
@HKaras HKaras added this to the v1.2 milestone Jul 1, 2024
@HKaras HKaras requested a review from stestoll July 1, 2024 14:40
@HKaras HKaras self-assigned this Jul 1, 2024
HKaras added 3 commits July 1, 2024 17:00
The test has been updated. The previous convergence criteria was unreliable and only worked based on a coincidence.
stestoll
stestoll previously approved these changes Jul 1, 2024
@HKaras HKaras merged commit 178249e into JeschkeLab:main Jul 15, 2024
@HKaras HKaras deleted the regparam_grid_bug_fix branch July 15, 2024 11:51
HKaras added a commit to HKaras/DeerLab that referenced this pull request Jul 31, 2024
* Update for 3.12

* Updated workflows and changelog

* Upload to 3.12

* Fix bug in regparam grid search

Regparam would never build the grid correctly. Now using grid or Brent is automatically determined from number of elements in the regparamrange.

* Add extra error messages

* Update changelog

* Updated Example

* Updated test

The test has been updated. The previous convergence criteria was unreliable and only worked based on a coincidence.

* Prepare For Release

* Remove duplicate python version
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bugfix Patches something that isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

L-curve reg param do not work with a regparam search range

2 participants