Implemented final two binary ops, added default params for functionality

[connorgoggins]

Description

Added implementation for reshape_like and choose_element_0index in opperf, as well as supporting variables in rules/default_params.py.

Checklist

Essentials

Please feel free to remove inapplicable items for your PR.

• Changes are complete (i.e. I finished coding on this PR)
• All changes have test coverage
• Code is well-documented
• To the best of my knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

• M benchmark/opperf/nd_operations/binary_operators.py
• M benchmark/opperf/utils/op_registry_utils.py
• M benchmark/opperf/rules/default_params.py
• M benchmark/opperf/opperf.py

[ChaiBapchya]

LGTM! Thanks for your first contribution! More to come!

[ChaiBapchya]

Please add results seen on CPU/GPU for reference.
Did you run opperf for all operators after this change?

[ChaiBapchya]

A gist link with the results would do

[connorgoggins]

@ChaiBapchya https://gist.github.com/connorgoggins/294f55595311c3b811662af08a787f2a

[ChaiBapchya]

Also you could run the opperf utility by specifying the file format and name of the file
That is the results file I am referring to. Not the stdoutput.
Results file will spit out forward/backward time, memory consumption etc.

[access2rohit]

@mxnet-label-bot update [pr-awaiting-review]

[ChaiBapchya]

Also it would make sense to add results for

1. Individual operator test (of the 2 added ops)
2. Group of operator test (binary_op in this case)
3. Full OpPerf test (as mentioned in my previous comment)

Just to ensure it is fool-proof.

[connorgoggins]

Individual operator test (GPU): https://gist.github.com/connorgoggins/c74272c24c1e627a6db3709c1b17ee1d
Individual operator test (CPU): https://gist.github.com/connorgoggins/5e86b4a5def363eb2d791592296cd607

Group of operator test - all binary ops (GPU): https://gist.github.com/connorgoggins/948e5cb3d13ff53bfd6b4279abe28d4f
Group of operator test - all binary ops (CPU): https://gist.github.com/connorgoggins/0a5fb08543d164fce68e3c5006b0b264

Full OpPerf test (GPU)*: https://gist.github.com/connorgoggins/cceb63a3d2d17e36a7f26ed7c0c75505
Full OpPerf test (CPU): https://gist.github.com/connorgoggins/1e88cbd6764a74fc2f72b4eb5b7f022a

*Note: couldn't run sorting/searching ops tests in the full test on GPU because they exceeded the device memory of my p2.8xl instance. Will do another run on a p2.16xl to get those results, but regardless my implementation of these two binary operators has no bearing on the logic of sorting/searching ops.

[ChaiBapchya]

Let's add ElementwiseSum op too

https://mxnet.incubator.apache.org/api/python/docs/api/ndarray/ndarray.html#mxnet.ndarray.ElementWiseSum

[connorgoggins]

Full OpPerf test (CPU): https://gist.github.com/connorgoggins/d39b9adc63c3efabe81cfac34c5dfe1a

[apeforest]

Thanks for your contribution!

[ChaiBapchya]

Not in this PR but in one of the other 3 PRs that you have open you can add yourself to the Contributors.md file
Welcome to the group!! @connorgoggins

[ChaiBapchya]

Incorrect way to rebase @connorgoggins

First get your master branch updated

git remote add upstream https://github.com/apache/incubator-mxnet
git checkout master
git fetch upstream master
git merge upstream/master
git push origin master

Once your fork master is sync'ed with remote master, rebase your branch on master

git checkout <branchname>
git rebase master
git push origin <branchname>

Let me know if this works!