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
Fixed #971 turned off joblib when n_jobs == 1
#985
Conversation
Codecov ReportBase: 77.43% // Head: 77.43% // No change to project coverage 👍
Additional details and impacted files@@ Coverage Diff @@
## master #985 +/- ##
=======================================
Coverage 77.43% 77.43%
=======================================
Files 198 198
Lines 11165 11165
Branches 1406 1406
=======================================
Hits 8646 8646
Misses 2305 2305
Partials 214 214
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
I will fix this in the upcoming days. |
@rasbt |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks a lot, that looks great! Neat & clean solution!
Was just testing the code and it definitely improved the startup time. When I am trying an example like import numpy as np
from sklearn.linear_model import LogisticRegression
from mlxtend.feature_selection import ExhaustiveFeatureSelector as EFS
seed = 0
X = np.random.rand(10000, 10) # 10k samples, with 10 features
y = np.random.choice([0, 1], size=10000)
model = LogisticRegression()
efs1 = EFS(model,
min_features=1,
max_features=10,
scoring='accuracy',
print_progress=True,
n_jobs=1,
cv=5)
efs1 = efs1.fit(X, y)
print('Best accuracy score: %.2f' % efs1.best_score_)
print('Best subset (indices):', efs1.best_idx_)
print('Best subset (corresponding names):', efs1.best_feature_names_) it still seems to be a bit stuck though. I.e., it would not show any output for like 2-3 min and then iterate through the 1k possibilities in like 1 sec. I wonder if that's an issue with the EDIT: No worries, it was a computer issue. It works perfectly now. Actually it solves the problem. Before, a user could not see the progress printed to the command line until all combinations were evaluated. Now, you get the feedback immediately if |
Thanks for the info :) |
This PR fixes issue #971
Performance Code
Computing Time
main
: 103 sec