formath commented on issue #7934: Bug of group2ctx? Wrong device placement?
URL:
https://github.com/apache/incubator-mxnet/issues/7934#issuecomment-330759033
`exe = x.bind(mx.gpu(), {}, group2ctx={"a": mx.cpu(), "b": mx.gpu()})` The
default context just indicate this executor run on this
formath commented on issue #7934: Bug of group2ctx? Wrong device placement?
URL:
https://github.com/apache/incubator-mxnet/issues/7934#issuecomment-330759033
`exe = x.bind(mx.gpu(), {}, group2ctx={"a": mx.cpu(), "b": mx.gpu()})` The
default context is just indicate this executor run on
formath commented on issue #7934: Bug of group2ctx? Wrong device placement?
URL:
https://github.com/apache/incubator-mxnet/issues/7934#issuecomment-330749338
Depends on the device id of its first control node or input node. Your op
may not assigned by this.
formath commented on issue #7934: Bug of group2ctx? Wrong device placement?
URL:
https://github.com/apache/incubator-mxnet/issues/7934#issuecomment-330742175
During `PlaceDevice`, if an `op` can't be assigned a device id, its device
id will be set `0`. And to assign a default context is
