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
I have used this repo to build our current drft solution for our team.
I am historizing the dataset using an azure ml tabular dataset by passing the path of my drift loadings in blob. This allows me to query the data over time and plot how the p-values are varying.
However in order to detect if we have drift or not in the overall dataset it is unfair to just look to one feature.
I am using a bonferroni correction: Bland JM, Altman DG: Multiple significance tests: The Bonferroni method. BMJ 1995;310(6973):170.
In the same way that it is implemented in Seldon Core:
# TODO: return both feature-level and batch-level drift predictions by default# values below p-value threshold are driftifdrift_type=='feature':
drift_pred= (p_vals<self.p_val).astype(int)
elifdrift_type=='batch'andself.correction=='bonferroni':
threshold=self.p_val/self.n_featuresdrift_pred=int((p_vals<threshold).any()) # type: ignore[assignment]elifdrift_type=='batch'andself.correction=='fdr':
drift_pred, threshold=fdr(p_vals, q_val=self.p_val) # type: ignore[assignment]else:
raiseValueError('`drift_type` needs to be either `feature` or `batch`.')
Hi,
I have used this repo to build our current drft solution for our team.
I am historizing the dataset using an azure ml tabular dataset by passing the path of my drift loadings in blob. This allows me to query the data over time and plot how the p-values are varying.
However in order to detect if we have drift or not in the overall dataset it is unfair to just look to one feature.
I am using a bonferroni correction: Bland JM, Altman DG: Multiple significance tests: The Bonferroni method. BMJ 1995;310(6973):170.
In the same way that it is implemented in Seldon Core:
Maybe something worth to add to the example!