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
{{ message }}
Repository navigation
Sweepable Parameter can't handle Russia Format #4634
In that case we need to add culture invariant to whichever parse from /into string in AutoML. Either we stick to one culture preference inside AutoML, or we just use the default culture setting.
Do you remember the story why we add that culture invariant restriction when parsing sweepable params..
I would stick w/ culture invariant for the lifetime of the string. Currently we have culture invariant on the use of the string, but not the creation. Hence this issue being filed.
Using culture invariant helps in various ways:
If we separate the run context (e.g. cluster sweeping) the remote runner machines may be set to English/Russian/etc and needs to share sweep values.
Logging -- lets say we want to aggregate and find the best values for a hyperparamer like LearningRate. We'll be receiving values of 0.1234 and 0,1234.
Activity
justinormont commentedon Jan 7, 2020
I would fix by pushing a culture invariant into the sweepable param:
machinelearning/src/Microsoft.ML.Sweeper/Parameters.cs
Line 140 in b861b5d
LittleLittleCloud commentedon Jan 8, 2020
In that case we need to add culture invariant to whichever parse from /into string in AutoML. Either we stick to one culture preference inside AutoML, or we just use the default culture setting.
Do you remember the story why we add that culture invariant restriction when parsing sweepable params..
justinormont commentedon Jan 8, 2020
I would stick w/ culture invariant for the lifetime of the string. Currently we have culture invariant on the use of the string, but not the creation. Hence this issue being filed.
Using culture invariant helps in various ways:
0.1234and0,1234.LittleLittleCloud commentedon Jan 9, 2020
OK that's convincing, thanks