You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Traceback (most recent call last):
File "/home/janvanrijn/projects/openml-python-contrib/openmlcontrib/testjan.py", line 24, in <module>
run = openml.runs.run_model_on_task(task, flow)
File "/home/janvanrijn/projects/openml-python/openml/runs/functions.py", line 50, in run_model_on_task
add_local_measures=add_local_measures)
File "/home/janvanrijn/projects/openml-python/openml/runs/functions.py", line 129, in run_flow_on_task
run.parameter_settings = OpenMLRun._parse_parameters(flow)
File "/home/janvanrijn/projects/openml-python/openml/runs/run.py", line 455, in _parse_parameters
True, flow.flow_id)
File "/home/janvanrijn/projects/openml-python/openml/runs/run.py", line 402, in extract_parameters
sorted(expected_parameters| expected_components), sorted(model_parameters)))
ValueError: Parameters of the model do not match the parameters expected by the flow:
expected flow parameters: ['classifier', 'imputation', 'memory', 'onehot', 'steps']
model parameters: ['classifier', 'imputation', 'memory', 'onehot', 'steps', 'variancethreshold']
But as we support the passthrough now, what do you think about actively forbidden the None to make the behavior consistent and to keep that step in the pipeline?
We have taken the decision to not provide support None as an estimator placeholder, from the OpenML end, and encourage users to use 'drop' or 'passthrough' wherever sklearn supports so.
This has been implemented in #866.
Activity
janvanrijn commentedon Jun 19, 2018
Current Outcome:
What would be the expected outcome?
mfeurer commentedon Jun 20, 2018
The
variancethresholdshould be part of the expected flow parameters.Neeratyoy commentedon Nov 12, 2019
Using sklearn version
0.21.3, using the modified exampled from above as mentioned below, the error doesn't seem to occur.Also,
flow.parametersdoes contain variancethreshold as null in the serialized string.Can this issue be closed or am I missing something?
mfeurer commentedon Nov 12, 2019
I don't think you're missing anything.
But as we support the passthrough now, what do you think about actively forbidden the
Noneto make the behavior consistent and to keep that step in the pipeline?Neeratyoy commentedon Nov 12, 2019
Sure.
I'll see if I can add it to #866.
mfeurer commentedon Nov 12, 2019
That would be great!
Neeratyoy commentedon Nov 15, 2019
We have taken the decision to not provide support None as an estimator placeholder, from the OpenML end, and encourage users to use 'drop' or 'passthrough' wherever sklearn supports so.
This has been implemented in #866.