Kan Wu created MXNET-137:
----------------------------
Summary: fix parameters name inconsistent for Proposal OP and
Multi Proposal OP
Key: MXNET-137
URL: https://issues.apache.org/jira/browse/MXNET-137
Project: Apache MXNet
Issue Type: Bug
Reporter: Kan Wu
Hi, there.
There is parameters name inconsistent in Proposal OP and Multi Proposal OP.
Proposal OP:
[cls_prob](https://github.com/apache/incubator-mxnet/blob/master/src/operator/contrib/proposal-inl.h#L160)
vs
[cls_score](https://github.com/apache/incubator-mxnet/blob/master/src/operator/contrib/proposal.cc#L462)
Multi Proposal OP:
[cls_prob](https://github.com/apache/incubator-mxnet/blob/master/src/operator/contrib/multi_proposal-inl.h#L162)
vs
[cls_score](https://github.com/apache/incubator-mxnet/blob/master/src/operator/contrib/multi_proposal.cc#L500)
It seems that the parameter name should be `cls_prob` rather than `cls_score`.
[The parameter
prompt](https://github.com/apache/incubator-mxnet/blob/master/src/operator/contrib/proposal-inl.h#L107)
[Faster R-CNN
example](https://github.com/apache/incubator-mxnet/blob/master/example/rcnn/rcnn/symbol/symbol_resnet.py#L193)
So I replace `cls_score` with `cls_prob`, and I change the parameter name in
the unittest for Proposal OP and Multi Proposal OP.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
