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
Hi @mahdi259
I think for QuantIdentity the answer is just to use Uint8ActPerTensorFloat when initialising QuantIdentity with optional argument act_quant=Uint8ActPerTensorFloat instead of the default int8 - which you can see here
For weights in e.g. QuantLinear I think it would be less common to use unsigned integers, so I don't think there's a datatype available built-in, but you could experiment with that by extending the Int8 weight data type
Thanks @capnramses . That's it. One more question. I have read ULPPACK paper that performs inner product of unsigned numbers, i.e. unsigned inputs and weights. I agree that it's odd to have unsigned weights. Do you know how they use ULPPACK in networks like ResNet?
Thanks
Hi
Is there any way to specify unsigned quantization in QuantIdentity or QuantLinear?
Thanks
The text was updated successfully, but these errors were encountered: