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

What to do for underdetermined problems? #1150

Closed
jseabold opened this issue Oct 25, 2013 · 2 comments
Closed

What to do for underdetermined problems? #1150

jseabold opened this issue Oct 25, 2013 · 2 comments

Comments

@jseabold
Copy link
Member

What to do for the linear OLS models when k > nobs? See #1046, for example.

@josef-pkt
Copy link
Member

I'm slowly tending towards the view that we should issue a lot more warnings or exceptions by default, that can be overridden with an option.

k == nobs
Example in least trimmed squares LTS, the articles I read where starting with an exactly identified system (nobs = k_params). In my branch I used one additional observation, nobs = k_params + 1.
Similar Theil-Sen #557 would also use exactly identified.

Another case would be when we start with regularization. But this would need special handling than just doing the pinv regularization. (sklearn case with k > nobs)

@josef-pkt josef-pkt modified the milestones: 0.6, 0.7 Aug 17, 2014
@josef-pkt josef-pkt modified the milestones: 0.8, 0.7 Jul 17, 2015
@jseabold
Copy link
Member Author

Not actionable. We have regularization now. Can add issues for specific cases.

@bashtage bashtage modified the milestones: 0.8, 0.13 Sep 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants