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.

Sign up for GitHub

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

Jump to bottom

LGBMRegressor uses all threads even though n_jobs=1 #1151

Closed
kasyanovse opened this issue Aug 22, 2023 · 0 comments · Fixed by #1153
Closed

LGBMRegressor uses all threads even though n_jobs=1 #1151

kasyanovse opened this issue Aug 22, 2023 · 0 comments · Fixed by #1153
Assignees
@kasyanovse

Comments

@kasyanovse
Copy link
Collaborator

No description provided.

@kasyanovse kasyanovse changed the title LGBMRegressor uses all threads also if n_jobs=1 LGBMRegressor uses all threads even though n_jobs=1 Aug 22, 2023
@kasyanovse kasyanovse linked a pull request Aug 22, 2023 that will close this issue
Bugfixes #1153
Merged
@kasyanovse kasyanovse self-assigned this Aug 23, 2023
@kasyanovse kasyanovse mentioned this issue Aug 23, 2023
Merged
kasyanovse added a commit that referenced this issue Sep 3, 2023
@kasyanovse
Bugfixes (#1153)
5da1447 
1. Fix #1148 with fixed denominator in CGRU and add test for new code
2. Fix #1151 with set n_jobs=1 for some operations
3. Add initial assumption with AR (#1074), enable AR (#1137)
4. Check and add test in accordance with #739
5. Fix integration test `test_result_changing`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kasyanovse kasyanovse

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Bugfixes aimclub/FEDOT
1 participant
@kasyanovse