-
-
Notifications
You must be signed in to change notification settings - Fork 131
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
change parsing of the input in einsum #579
Conversation
Codecov Report
@@ Coverage Diff @@
## master #579 +/- ##
==========================================
- Coverage 92.19% 92.16% -0.04%
==========================================
Files 20 20
Lines 3204 3304 +100
==========================================
+ Hits 2954 3045 +91
- Misses 250 259 +9 |
Seems like a formatting fail -- Perhaps update Also, there are a lot of lines missing from coverage, more comprehensive tests would be appreciated. |
Ok, I will add more tests |
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.
One last change!
Thanks, @HadrienNU for the improvement! |
After testing the implemented einsum (many thanks for implementing), it turns out that the ellipsis were not working (and they are used by xarray dot function, my primary motivation for making this work). So in this commit there is an added function _parse_einsum input that is borrowed from numpy with the only change that operand are not cast to numpy array but are left untouched.