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
Some TorchFX operations are returning a tuple instead of a torch.Tesnor. In case an algorithm requests a statistic from such node nncf will raise an error like tuple has not is_empty method. This affect the yolon11 model, current workaround is the ignored scope with the type of operation which return a tuple:
nncf.IgnoredScope(types=["__getitem__"])
The task is to:
Introduce FXTargetPoint with port_id attr instead of input_port_id
Support FXTargetPoint in each TorchFX transformation
Feature Use Case
No response
Are you going to submit a PR?
Yes I'd like to help by submitting a PR!
The text was updated successfully, but these errors were encountered:
🚀 Feature request
Some TorchFX operations are returning a tuple instead of a
torch.Tesnor
. In case an algorithm requests a statistic from such node nncf will raise an error liketuple has not is_empty method
. This affect theyolon11
model, current workaround is the ignored scope with the type of operation which return a tuple:The task is to:
FXTargetPoint
withport_id
attr instead ofinput_port_id
FXTargetPoint
in each TorchFX transformationFeature Use Case
No response
Are you going to submit a PR?
The text was updated successfully, but these errors were encountered: