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
It's surprising that we specify the parameters for the post-processing transformation as separate options in the predict section of the config, but then specify them in a "sub-table" named post_tfm_kwargs in the eval and learncurve sections
We should change predict to be consistent with the others IMO since we may want to change the semantics of post_tfm_kwargs depending on the model family
The text was updated successfully, but these errors were encountered:
This came up in this related bug:
#697 (comment)
It's surprising that we specify the parameters for the post-processing transformation as separate options in the
predict
section of the config, but then specify them in a "sub-table" namedpost_tfm_kwargs
in theeval
andlearncurve
sectionsWe should change
predict
to be consistent with the others IMO since we may want to change the semantics ofpost_tfm_kwargs
depending on the model familyThe text was updated successfully, but these errors were encountered: