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
As a user, I want only the relevant errors surfaced to me and expected behavior to be suppressed.
For now, focus on the KS Test metric (see #129 and #130 for more details)
Expected behavior
Create a new MetricComputationError to be used when there is a mathematical error when computing the metric (eg. when calling scipy or dividing by zero)
For tabular and relational tests compute method:
If there are 0 columns with valid data types, return None and throw a warning. This is not an error; the metric is simply undefined.
Problem Description
As a user, I want only the relevant errors surfaced to me and expected behavior to be suppressed.
For now, focus on the KS Test metric (see #129 and #130 for more details)
Expected behavior
MetricComputationError
to be used when there is a mathematical error when computing the metric (eg. when calling scipy or dividing by zero)For tabular and relational tests
compute
method:None
and throw a warning. This is not an error; the metric is simply undefined.MetricComputationError
MetricComputationError
, show a warning but keep going with the other columnsThe text was updated successfully, but these errors were encountered: