We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Measures have a property whether they can return an NA, but also a slot to define the value which is returned instead of an NA....
I am not sure this is of ANY use. MAYBE one can have one concept for this in the superclass, to transform an NA or NAN into a different value.
but having separate options for all metrics seems way too much and confusing
The text was updated successfully, but these errors were encountered:
probably this feature might be reasonable to impute NaNs values.
the docs of the property say: the measure could return a NaN or NA. we likely only want one. NaN.
Might be good to add a sentence in ?Measure that this exists.
we need a test for the interaction between this and the NaN production if in Measure$score has weird NaN producing code #1110
Sorry, something went wrong.
also rename the propery to nan_value
check in mlr3measures that we always produce NaN and not NA
mllg
No branches or pull requests
Measures have a property whether they can return an NA, but also a slot to define the value which is returned instead of an NA....
I am not sure this is of ANY use. MAYBE one can have one concept for this in the superclass, to transform an NA or NAN into a different value.
but having separate options for all metrics seems way too much and confusing
The text was updated successfully, but these errors were encountered: