## Description ##

* Added randn function.
* Internal SELU function on C++ layer
* Predict now accepts ndarray as well
* Gluon: Only warn when the blocks are unregistered.
* Better sparse support for gluon
* Gpu memory info via mxnet api call.
* Gluon: Improved block summary.
* Added validation docs for MXNet installation for Perl.
* Flexible perl env for examples.
* Gluon: Custom dtypes for the symbol block.
* Separate eval metric for the epoch level.

## 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](https://issues.apache.org/jira/projects/MXNET/issues) 
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 ###

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


[ Full content available at: 
https://github.com/apache/incubator-mxnet/pull/12739 ]
This message was relayed via gitbox.apache.org for [email protected]

Reply via email to