This is an automated email from the ASF dual-hosted git repository. haoj pushed a change to branch numpy_pr_merge in repository https://gitbox.apache.org/repos/asf/incubator-mxnet.git.
discard 39e3757 Merge branch 'master' into numpy_pr_merge omit c95de90 add numpy op logspace (#15825) omit 38ee854 Numpy compatible vsplit; minor changes to split (#15983) omit ab60e34 numpy eye op (#16132) omit 6913fe2 [Numpy] Numpy compatible dstack (#15871) add 1d4ede3 Add mask target generator operator for Mask-RCNN (#16268) add 8820220 Adds pip requirements file to nightly gpu ci image (#16472) add 1256976 Fix Nightly Tests for Binaries (#16451) add 974327e [Numpy] Numpy compatible dstack (#15871) add 80982ec numpy eye op (#16132) add bf8bd40 Numpy compatible vsplit; minor changes to split (#15983) add 63500c5 add numpy op logspace (#15825) This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (39e3757) \ N -- N -- N refs/heads/numpy_pr_merge (63500c5) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. No new revisions were added by this update. Summary of changes: ci/docker/Dockerfile.build.ubuntu_nightly_gpu | 1 + src/operator/contrib/mrcnn_target-inl.h | 132 ++++++++++++ src/operator/contrib/mrcnn_target.cu | 278 ++++++++++++++++++++++++++ tests/python/unittest/test_operator.py | 57 ++++++ tests/utils/notebook_test/__init__.py | 2 +- 5 files changed, 469 insertions(+), 1 deletion(-) create mode 100644 src/operator/contrib/mrcnn_target-inl.h create mode 100644 src/operator/contrib/mrcnn_target.cu