-
Notifications
You must be signed in to change notification settings - Fork 138
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
[BUG] Linear regression model predicts NaN values only #3210
Comments
Taking a look |
Any news on this one @b4sjoo? |
@b4sjoo any update on this? |
@dhrubo-os can you please assign this issue to me? |
@rithin-pullela-aws I just assigned to you. Thanks for looking into this. |
Hi @wrigleyDan, experimenting with different optimiser and learning rates results in better model weights and responses. I used ADA_GRAD and got the output between 0 and 1:
Open Search uses Tribuo to perform linear regression, please find this bug report on Tribuo for better explanation. |
For Tribuo's linear regressions, it's probably better to default to using AdaGrad with some reasonable learning rate rather than a constant learning rate SGD as it's very tricky to tune that correctly. We provide a default |
What is the bug?
I trained a linear regression model with 5000 features and apparently when calling the
_predict
API onlyNaN
values are returned.I cannot exclude that I'm using parameters that are not ideal and as a consequence lead to the
NaN
predictions. I unsuccessfully tried smaller learning rates but did not experiment with all available parameters and parameter values.How can one reproduce the bug?
Steps to reproduce the behavior:
What is the expected behavior?
The expected behavior is to receive not only
NaN
values but reasonable predictions, in the given example values between 0 and 1.What is your host/environment?
Do you have any screenshots?
See the linked Gist with a notebook example and the data used as features.
Do you have any additional context?
Initially reported in the #ml OpenSearch Slack channel: https://opensearch.slack.com/archives/C05BGJ1N264/p1731077205560749
The text was updated successfully, but these errors were encountered: