-
Notifications
You must be signed in to change notification settings - Fork 54
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
diag() and diagonal() feature #412
Conversation
Codecov Report
@@ Coverage Diff @@
## master #412 +/- ##
==========================================
+ Coverage 98.02% 98.05% +0.03%
==========================================
Files 55 55
Lines 11066 11285 +219
==========================================
+ Hits 10847 11066 +219
Misses 219 219
Continue to review full report at Codecov.
|
I also made some small changes in the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the logic here looks good, only minor things to change.
…han upper bound (numpy returns empty array) and cleaned up code
tests failing, bump |
# Conflicts: # heat/core/manipulations.py # heat/core/tests/test_manipulations.py
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I merge the branch #420 into this to get the correctly working unit test.
Please merge that branch before this one.
Description
This PR targets issue #242.
The returned array of
diag()
in case of creating a diagonal array, will be split the same as the input array (split=None
orsplit=0
).Type of change
Select relevant options.
Are all split configurations tested and accounted for?
[x] yes - [ ] no
Does this change require a documentation update outside of the changes proposed?
[ ] yes [x] no
Does this change modify the behaviour of other functions?
[ ] yes [x] no
Are there code practices which require justification?
[ ] yes [x] no