-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
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
CVS-160560 nanobindings for keypoint detection and segmentation #258
base: master
Are you sure you want to change the base?
Conversation
static_cast<size_t>(r.anomaly_map.channels())}); | ||
}, | ||
nb::rv_policy::reference_internal) | ||
.def_ro("pred_boxes", &AnomalyResult::pred_boxes) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is cv::Rect
correctly wrapped?
nb::class_<InstanceSegmentationResult, ResultBase>(m, "InstanceSegmentationResult") | ||
.def(nb::init<int64_t, std::shared_ptr<MetaData>>(), nb::arg("frameId") = -1, nb::arg("metaData") = nullptr) | ||
.def_prop_ro( | ||
"feature_vector", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Iseg result also contains a saliency map as a vector of cv::Mat
. Perhaps, it's not that easy to expose but there is a chance a vector of nb::ndarray<uint8_t...
would work here
What does this PR do?
AnomalyDetection, Classification and KeypointDetection can be replaced with python version.
Segmentation and InstanceSegmentation still need work to match python format results.
Fixes # (issue)
Before submitting