This repository has been archived by the owner on Apr 17, 2023. It is now read-only.
Don't apply activations on export in classification #83
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The motivation is that d-o-r, POT, OpenVINO task and Model API classification components don't expect activated output from IR, so we had wrong confidence results of classification and simply wrong results of multilabel classification in OV tasks / POT. As soon as we remove d-o-r and related code, we can use activated output on the export sage again.