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
As reported by one of our students, the tabular dataset returned by the search CV tool is populating the list differently as documented earlier in many ML tutorials. Do we know what needs to be changed in the tool parameter selection to make the search CV tool run? I remember we used to get a list of all hyperparameters and then we could select those whose values need to be optimized.
I tried a few ways to make it work - by changing tool's version, using different options in Choose a parameter name (with current value) but the jobs are failing. Do you know what should be the correct setting, then I will update the tutorials accordingly. I am not sure if this is a bug or it has been formatted like this (above image).
As reported by one of our students, the tabular dataset returned by the search CV tool is populating the list differently as documented earlier in many ML tutorials. Do we know what needs to be changed in the tool parameter selection to make the search CV tool run? I remember we used to get a list of all hyperparameters and then we could select those whose values need to be optimized.
I tried a few ways to make it work - by changing tool's version, using different options in
Choose a parameter name (with current value)
but the jobs are failing. Do you know what should be the correct setting, then I will update the tutorials accordingly. I am not sure if this is a bug or it has been formatted like this (above image).The hyperparameters were listed previously as:
.
link to the history: https://usegalaxy.eu/u/kumara/h/age-prediction
It could be related to the method here:
Galaxy-ML/galaxy_ml/utils.py
Line 456 in d662fc5
I think parameters should be listed that currently do not
ping @qiagu Any ideas/hint how to fix this?
Thanks a lot!
The text was updated successfully, but these errors were encountered: