[G-API] Support FP16 input precision for IE backend#20490
[G-API] Support FP16 input precision for IE backend#20490alalek merged 3 commits intoopencv:masterfrom
Conversation
…port-fp16-input-precision
|
@mpashchenkov Could you have a look ? |
|
@TolyaTalamanov, Should wrapIE contain HANDLE(16F) variant? |
| case CV_8U: return IE::Precision::U8; | ||
| case CV_32S: return IE::Precision::I32; | ||
| case CV_32F: return IE::Precision::FP32; | ||
| case CV_16F: return IE::Precision::FP16; |
There was a problem hiding this comment.
@alalek Could you explain what is the CV_16F actually mean ?
I'm a bit confused, because cv::convertFp16 function returns CV_16S depth.
There was a problem hiding this comment.
Discussed locally, thanks!
There was a problem hiding this comment.
Please share this info here for the history.
There was a problem hiding this comment.
Dedicated cv::convertFp16 call is deprecated and is going to be replaced with common .convertTo() call.
Done |
dmatveev
left a comment
There was a problem hiding this comment.
Ok with the change but can this be tested in any form?
GPU/CPU plugins don't work with |
|
@alalek Can we merge it ? |
…recision [G-API] Support FP16 input precision for IE backend * Support fp16 input precision IE backend * Add support to wrapIE
…nput-precision [G-API] Support FP16 input precision for IE backend * Support fp16 input precision IE backend * Add support to wrapIE
Pull Request Readiness Checklist
See details at https://github.com/opencv/opencv/wiki/How_to_contribute#making-a-good-pull-request
Patch to opencv_extra has the same branch name.
Build configuration