apeforest commented on a change in pull request #16215: New ops for RCNN + old
ops improvements for RCNN
URL: https://github.com/apache/incubator-mxnet/pull/16215#discussion_r326471319
##########
File path: src/operator/contrib/bounding_box-inl.h
##########
@@ -787,6 +787,284 @@ void BipartiteMatchingBackward(const nnvm::NodeAttrs&
attrs,
});
}
+
+inline bool BoxEncodeShape(const nnvm::NodeAttrs& attrs,
+ mxnet::ShapeVector *in_attrs,
+ mxnet::ShapeVector *out_attrs) {
+ CHECK_EQ(in_attrs->size(), 6U);
+ CHECK_EQ(out_attrs->size(), 2U);
+ mxnet::TShape& sshape = (*in_attrs)[0];
+ mxnet::TShape& mshape = (*in_attrs)[1];
+ mxnet::TShape& ashape = (*in_attrs)[2];
+ mxnet::TShape& rshape = (*in_attrs)[3];
+
+ CHECK_EQ(sshape.ndim(), 2)
+ << "samples shape must have dim == 2, "
+ << sshape.ndim() << " provided";
+
+ CHECK_GE(mshape.ndim(), 2)
+ << "matches shape must have dim == 2, "
+ << mshape.ndim() << " provided";
+
+ CHECK_GE(ashape.ndim(), 3)
+ << "matches shape must have dim == 3, "
+ << ashape.ndim() << " provided";
+ int ldim = ashape[ashape.ndim() - 1];
+ CHECK_EQ(ldim, 4)
+ << "last dimension of anchors must be 4, "
+ << ldim << " provided";
+
+ CHECK_GE(rshape.ndim(), 3)
+ << "refs shape must have dim == 3, "
+ << ashape.ndim() << " provided";
+ ldim = rshape[rshape.ndim() - 1];
+ CHECK_EQ(ldim, 4)
+ << "last dimension of anchors must be 4, "
+ << ldim << " provided";
+
+ // asign input shape
+ SHAPE_ASSIGN_CHECK(*in_attrs, 4, mshadow::Shape1(4));
+ SHAPE_ASSIGN_CHECK(*in_attrs, 5, mshadow::Shape1(4));
+
+ // assign output shape
+ mxnet::TShape oshape = ashape;
+ SHAPE_ASSIGN_CHECK(*out_attrs, 0, oshape);
+ SHAPE_ASSIGN_CHECK(*out_attrs, 1, oshape);
+ return shape_is_known(oshape);
+}
+
+struct box_encode {
+ template<typename DType>
+ MSHADOW_XINLINE static void Map(int i, DType *out_targets, DType *out_masks,
Review comment:
Can we use `index_t` here for i, m, n in order to support large tensor?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
With regards,
Apache Git Services
