Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

constrained GLM issues: 1. constrained not satisfied, 2. duplicate/conflicting contrains error thrown #16312

Closed
wendycwong opened this issue Jun 26, 2024 · 2 comments
Assignees
Labels
Milestone

Comments

@wendycwong
Copy link
Contributor

wendycwong commented Jun 26, 2024

Support ticket: https://support.h2o.ai/a/tickets/108488

Issue 1. Constraints are not strictly satisfied;
Issue 2. NPE when specifying beta constraints
Issue 3. Constraints that are not conflicting or duplicated but are detected to be such by the code.

@wendycwong
Copy link
Contributor Author

issues 2/3 are resolved due to bugs in implementation.
issue 1 is due to algorithm arriving at line search failure or arriving at a state where no further progress can be made. When this happens before the constraints are satisfied, we are stuck with solution that do not satisfy all constraints.

wendycwong pushed a commit that referenced this issue Jul 26, 2024
wendycwong added a commit that referenced this issue Aug 9, 2024
* Continue to double check algo.

* fix bug in gradient update.

* implemented various version of IRLSM

* Found GLM original with gradient magnitude change best

* GH-16312: fix wrong error raised by duplicated/conflicted constraints.

* force beta constraint to be satisfied at the end if it is not.

* GH-16312: add assert check to test per Veronika suggestion.

* GH-16312: fix tests after fixing constrained GLM bugs.

* GH-16312: fixed NPE error in checkCoeffsBounds

* GH-16312: fix test failure.

* remove conflicting constraint tests as we currently do not have the capability to do so right now.
* change dataset path from AWS to local
@valenad1 valenad1 modified the milestones: 3.46.0.5, 3.48.0.1 Aug 28, 2024
@valenad1
Copy link
Collaborator

@wendycwong moved milestone to next Major. It was merged to master

valenad1 added a commit that referenced this issue Aug 28, 2024
* ht/first draft

sans:
- 16354: Removed Snyk check and migrated to Privy vulnerability check.
- 16348: Cleaned references to `erin-data` and `h2o-smalldata` buckets.
- 16347: Added sonatype scan to Jenkins scans.
- 16332: (Duplicate) part of 3.46.0.6

* ht/misplaced c/p fix

* ht/added 15989

* Remove #16312 from list. It will be part of major release

---------

Co-authored-by: Adam Valenta <[email protected]>
wendycwong added a commit that referenced this issue Sep 3, 2024
* Continue to double check algo.

* fix bug in gradient update.

* implemented various version of IRLSM

* Found GLM original with gradient magnitude change best

* GH-16312: fix wrong error raised by duplicated/conflicted constraints.

* force beta constraint to be satisfied at the end if it is not.

* GH-16312: add assert check to test per Veronika suggestion.

* GH-16312: fix tests after fixing constrained GLM bugs.

* GH-16312: fixed NPE error in checkCoeffsBounds

* GH-16312: fix test failure.

* remove conflicting constraint tests as we currently do not have the capability to do so right now.
* change dataset path from AWS to local
wendycwong added a commit that referenced this issue Sep 11, 2024
* Continue to double check algo.

* fix bug in gradient update.

* implemented various version of IRLSM

* Found GLM original with gradient magnitude change best

* GH-16312: fix wrong error raised by duplicated/conflicted constraints.

* force beta constraint to be satisfied at the end if it is not.

* GH-16312: add assert check to test per Veronika suggestion.

* GH-16312: fix tests after fixing constrained GLM bugs.

* GH-16312: fixed NPE error in checkCoeffsBounds

* GH-16312: fix test failure.

* remove conflicting constraint tests as we currently do not have the capability to do so right now.
* change dataset path from AWS to local
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants