-
Notifications
You must be signed in to change notification settings - Fork 19
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
MultiFab & Array4 #19
Conversation
A comment by @WeiqunZhang
|
24584b0
to
97b9875
Compare
Windows memory violation: Cannot find any issue on Linux with address + undefined sanitizers so far... (besides #29) update: I used a too-small integer type to store the pointer: numpy/numpy#21248 |
This comment was marked as resolved.
This comment was marked as resolved.
a56a873
to
165f854
Compare
This comment was marked as resolved.
This comment was marked as resolved.
Co-authored-by: Shreyas Ananthan <[email protected]>
Forgot to return in custom lambda methods
Still fails with double free, probably because MFIter survives MultiFab or so
Try again with a newer pybind11 version later?
Implement the `__array_interface__` in Array for.
28c886b
to
4ac3dde
Compare
3D == no component: stride should not matter
This comment was marked as resolved.
This comment was marked as resolved.
Resolved more gentle already, just dead code left.
make sure view & original match after modification
Reimplementation of the successful MFiter concepts from: https://github.com/sayerhs/pyamrex for
MultiFab
, avoiding copies. Reimplementation ofyield
continuations with an iterator.Start new concepts for
Array4
- first via__array_interface__
: #17 / #9 (comment)amrex::Box
indexing semantics by default for everything: index-1
is ghost)asarray
/as_numpy
/as_cupy
functions for non-owning data from it: (numpy
/Python Buffer Interface semantics for everything: index-1
is end of array)Refs.: