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
In 0.1.9a0, and by inspection, also in master, the docstring for TPOTEstimator.max_eval_time_mins indicates that a float, including float("inf") is accepted, and also documents a default value that doesn't match the default set in the __init__() signature. Defaults should be ideally be auto-detected via mkdocs or similar infrastructure, not entered / maintained by busy & distractible humans. It also appears that the default is masking an internal problem in how this value is processed.
I've verified on the LOC just prior to creating a TPOTEstimator (first line of output below) that my max_eval_time_mins is float("inf"), but I still get an error. It appears that the default parameter value in __init__() is likely masking an internal inconsistency in how this is treated. There's a similarly misleading docstring re: default value for max_time_mins though I haven't explicitly tested that.
It seems likely that similar documentation maintenance issues are pervasive within the codebase, though I haven't taken the time to explicitly verify.
The text was updated successfully, but these errors were encountered:
chimaerase
changed the title
Misleading docstrings for TPOTEstimater.max_eval_time_mins & max_time_mins
Misleading docstrings for TPOTEstimator.max_eval_time_mins & max_time_minsFeb 12, 2025
In
0.1.9a0
, and by inspection, also inmaster
, the docstring forTPOTEstimator.max_eval_time_mins
indicates that afloat
, includingfloat("inf")
is accepted, and also documents a default value that doesn't match the default set in the__init__()
signature. Defaults should be ideally be auto-detected viamkdocs
or similar infrastructure, not entered / maintained by busy & distractible humans. It also appears that the default is masking an internal problem in how this value is processed.I've verified on the LOC just prior to creating a
TPOTEstimator
(first line of output below) that mymax_eval_time_mins
isfloat("inf")
, but I still get an error. It appears that the default parameter value in__init__()
is likely masking an internal inconsistency in how this is treated. There's a similarly misleading docstring re: default value formax_time_mins
though I haven't explicitly tested that.It seems likely that similar documentation maintenance issues are pervasive within the codebase, though I haven't taken the time to explicitly verify.
The text was updated successfully, but these errors were encountered: