Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

evaluate / eval_metric.py #1

Merged
merged 2 commits into from
Mar 16, 2019
Merged

evaluate / eval_metric.py #1

merged 2 commits into from
Mar 16, 2019

Conversation

sunrongda
Copy link
Owner

Description

(Brief description on what this PR is about)
image
image

Checklist

Essentials

Please feel free to remove inapplicable items for your PR.

  • The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
  • Changes are complete (i.e. I finished coding on this PR)
  • All changes have test coverage:
  • Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
  • Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
  • Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
  • Code is well-documented:
  • For user-facing API changes, API doc string has been updated.
  • For new C++ functions in header files, their functionalities and arguments are documented.
  • For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
  • Check the API doc at http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
  • To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

  • Feature1, tests, (and when applicable, API doc)
  • Feature2, tests, (and when applicable, API doc)

Comments

  • If this change is a backward incompatible change, why must this change be made.
  • Interesting edge cases to note here

ifeherva and others added 2 commits March 15, 2019 21:05
…s well. (#14321)

* nd.moveaxis now accepts negative indices and sequence of ints as well.

* Retrigger CI

* retrigger CI

* Retriever

* Retrigger CI

* Retrigger CI

* Retrigger CI, hope for success

* Update test_ndarray.py

* Let’s try to retrigger CI again.

* Retrigger CI

* Disable the new testcase to track bugs

* enable some new testcases

* Update test_ndarray.py

* Update test_ndarray.py
* Add repr for SymbolBlock

* Add a test

* Correct self.cached_graph

* Address review comments
@sunrongda sunrongda merged commit 7ce47c2 into sunrongda:master Mar 16, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants