Skip to content

GenericChangeThreshold relative validation inconsistency #520

@stefandominicus-takealot

Description

The implementation of relative threshold validation doesn't align with the documented/expected behaviour.

From the docs:

Aboslute change is calculated as the value diference between the metrics of the candidate and baseline model, namely, v_c - v_b where v_c denotes the candidate metric value and v_b denotes the baseline value. Relative value is the relative difference between the metric of the candidate and the baseline, namely, v_c/v_b.

However, the implementation instead calculates (v_c - v_b) / v_b, NOT v_c/v_b as the docs very clearly state.

The easiest fix would be to update the docs to correctly describe the implementation, but I'm not sure what the desired behaviour actually is.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions