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
This issue is on behaviour currently present in Alibi Detect Server.
Alibi Detect library expects float input to be float32 type in most cases when numerical data is expected. Currently in alibi-detect-server, e.g. here
float32
seldon-core/components/alibi-detect-server/adserver/ad_model.py
Line 63 in ec06181
np.array
dtype
float64
>>> np.array([1.1, 2.2, 3.3]).dtype dtype('float64')
Some detectors will ignore it but some that relies strongly on Tensorflow will unfortunately fail.
For SC 1.13 that uses AD 0.8.1 this can be worked-around by adding a dummy preprocessing in detector artifact:
preprocess_fn = lambda x: x.astype(np.float32) dd = DetectorClassHere(x_ref=..., preprocess_fn = preprocess_fn, ...)
but this solution is not ideal.
One idea that comes to my mind would be on the server side to do following casting:
int64
int32
SC up to 1.13.0
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
This issue is on behaviour currently present in Alibi Detect Server.
Alibi Detect library expects float input to be
float32
type in most cases when numerical data is expected.Currently in alibi-detect-server, e.g. here
seldon-core/components/alibi-detect-server/adserver/ad_model.py
Line 63 in ec06181
we cast input to
np.array
without specifying thedtype
. This is bad as the default will befloat64
Some detectors will ignore it but some that relies strongly on Tensorflow will unfortunately fail.
For SC 1.13 that uses AD 0.8.1 this can be worked-around by adding a dummy preprocessing in detector artifact:
but this solution is not ideal.
One idea that comes to my mind would be on the server side to do following casting:
float64
-> cast tofloat32
int64
-> cast toint32
Environment
SC up to 1.13.0
The text was updated successfully, but these errors were encountered: