Skip to content
This repository has been archived by the owner on Nov 17, 2023. It is now read-only.

Check list for more operators #3198

Closed
3 tasks
mli opened this issue Sep 2, 2016 · 1 comment
Closed
3 tasks

Check list for more operators #3198

mli opened this issue Sep 2, 2016 · 1 comment

Comments

@mli
Copy link
Member

mli commented Sep 2, 2016

Lacking of operators is the major disadvantage of MXNet comparing to other frameworks. The current multidimensional array interface follows the numpy.ndarray convention. See this tutorial for a quick overview.

Now we are going to add the rest numpy operators into MXNet, and also fix the existing operators if their are different to the according ones in numpy.

I grabbed numpy's routines from this page. The comparison to MXNet's operators will be listed in a few following issues.

For an operator, there are 4 states

  • v : already done, and it is consistent to numpy
  • p : partially done. the part should be fixed is on the comments
  • x : not exists, need to add into mxnet
  • = : not exists, but will not support in a short time
  • ? : not sure whether x or =, leave for discussion
    We will use separate issues to track each operator category. The schedule is
  • survey the current status, and which operators should be added or fixed.
  • examples codes to implement new operators
  • assign jobs to contributors

Also some related tasks:

  • better operator documents
  • better unittest
  • improve neural network related operators
@tqchen
Copy link
Member

tqchen commented Oct 19, 2017

close on stale issue

@tqchen tqchen closed this as completed Oct 19, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants