-
Notifications
You must be signed in to change notification settings - Fork 6.8k
[MXNET-978] Higher Order Gradient Support broadcast_to, broadcast_power, power, elemwise_mul and elemwise_sub and add unit test function check check_nth_order_binary #17754
base: master
Are you sure you want to change the base?
Changes from 12 commits
3901e33
a81985c
df83c8c
6ba9f82
159b51a
a63824a
c07f0a6
4730106
7453032
e21363c
555f532
8d849fa
46427f1
5ecfbcf
d47a04a
d4a0efe
923aaf7
6186135
41160f4
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -46,7 +46,15 @@ static const std::vector<std::pair<std::string, std::string>> test_unary_operato | |
|
||
static const std::vector<std::pair<std::string, std::string>> test_binary_operators = { | ||
{ "elemwise_add", "_backward_add" }, | ||
{ "elemwise_mul", "_backward_mul" } | ||
// TODO(Deng, Wenqi): In https://github.com/apache/incubator-mxnet/pull/17754, | ||
// we have changed backward op to graph of ops for computing backward of elemwise_mul, | ||
// but the CoreOpExecutor in tests/cpp/include/test_core_op.h actually has issues | ||
// to support this way even it provides CoreOpExecutor::GetBackward for the case. | ||
// e.g: It actually assumes there is one backward for all kinds of op, but elemwise_mul has two. | ||
// It will get wrong dependency for the second backward in CoreOpExecutor::GetBackwardDependency | ||
// due to "return igrad_entries[0].node;" // and failed to call CoreOpExecutor::bwd_inputs() | ||
// and CoreOpExecutor::bwd_outpuss() due to "CHECK_EQ(backward_.size(), 1U)";. | ||
// { "elemwise_mul", "_backward_mul" } | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I don't know much about this, but I don't think removing an existing test would be a good idea. @apeforest @larroy @sxjscience Would be better people to take the call. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. For more explanation, becaue the failure of the test cases are caused by defects of CoreOpExecutor, I just want a pr to achieve only one task. Maybe we need a other pr or jira to fix the issuee of CoreOpExecutor. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yes. That makes sense. |
||
}; | ||
|
||
template<typename TT> | ||
|
Uh oh!
There was an error while loading. Please reload this page.