Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Handle ops between FDGrid and Python functions #458
base: develop
Are you sure you want to change the base?
Handle ops between FDGrid and Python functions #458
Changes from 1 commit
b1d5e2f
31b357e
84c644d
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
A couple of things:
FData
are callables too. What should happen if we do ops betweenFData
with different domains? And between twoFDataGrid
with the same domain and differentgrid_points
? (we could lose commutativity in this case!) And between aFDataGrid
and aFDataBasis
with the same domain?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.
2/3. This is true, it's now fixed.
Callable
is after testing forFDataGrid
. That way all your concerns are tackled by theFDataGrid
handler.[1] https://stackoverflow.com/questions/35215161/most-efficient-way-to-map-function-over-numpy-array
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.
Also, I don't think this will ever be a hot path, so I wouldn't necessarily spend too much time thinking about micro-optimizing this.
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.
Sorry for the delay.
I didn't mean to use
np.vectorize
, but to assume that theother
function accepts an array as input and return the array as output. This way, it would be very efficient for ufuncs likenp.sqrt
ornp.sin
, or functions created composing these, as they perform the iteration in C code, probably using SIMD instructions for further performance.I would first try passing the array of coordinates, and if that fails pass the coordinates as different parameters for the efficiency reasons explained above.
Ok, so for now
FDataGrid
is special, and twoFDataGrid
s with different domains cannot be operated together. If a user wants that they can always uselambda x: my_fdatagrid(x)
instead. We can also change this behaviour in the future if we found a reasonable way to support it.