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
Currently, SKLL does not correctly deal with numbers in scientific notation when specified in parameter grids. The main problem is how PyYAML is, by default, set up to accept floating point numbers. We use yaml.load to read in the param grids when parsing the config file. To wit, consider the following example with the same config parameter grid expressed with and without scientific notation:
So we need to get PyYAML to do the right thing by explicitly patching its floating point resolver, e.g., as shown here since it's clear that PyYAML won't fix the problem itself.
The text was updated successfully, but these errors were encountered:
Actually, may be we can just switch to ruamel.yaml which is an up-to-date and in-development replacement for PyYAML that also has a conda package in the defaults channel.
Currently, SKLL does not correctly deal with numbers in scientific notation when specified in parameter grids. The main problem is how PyYAML is, by default, set up to accept floating point numbers. We use
yaml.load
to read in the param grids when parsing the config file. To wit, consider the following example with the same config parameter grid expressed with and without scientific notation:You have to basically specify the above list in a particular version of the scientific notation:
So we need to get PyYAML to do the right thing by explicitly patching its floating point resolver, e.g., as shown here since it's clear that PyYAML won't fix the problem itself.
The text was updated successfully, but these errors were encountered: