-
Notifications
You must be signed in to change notification settings - Fork 71
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
problem with adding to numpy.float64, ufunc issue? #2
Comments
The left operand gets the first shot at implementing the operation. Only if it fails does the right operand attempt with its I don't have a good idea offhand how to get around this. |
thanks very much for the info. is it clear to you that the operator change would cause this? the a similar question is raised in this SO post. after looking at their suggestions the they also suggest to subclassing |
so if the left hand operator fails, the right operand attempt with its |
arsenovic@bd3bb72 . . . embarrasing |
@arsenovic is this now fixed or still a problem? |
i think we can close |
i am working on changing the operators (on this branch) to match those in galgebra: ie
&
->*
and from*
->|
however, i am getting some strange behavior which i dont undertand, which seems to be related to some operator overloads with numpy dtypes. it appears as though the
float64.__add__
is taking precedence over cliffordsMultiVector.__radd__
. not sure why the operator changes created this problem.@moble, @rkern perhaps you all have some ideas on how to solve this?
here is demo of error,
https://gist.github.com/13b0ee10dde76817c79aab567b682efa
The text was updated successfully, but these errors were encountered: