Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Are we ndarray yet? #597
Are we ndarray yet? #597
Comments
|
Going through all of these issues, I have starting to think at broader challenges which should probably fall under
|
|
I've started taking a crack at einsum here. The implementation I have there has multiple issues (performance and otherwise) and is not at all ready for production, but is apparently correct. I'm actively working on improving the implementation. There's a web frontend that uses the crate as a WASM module deployed here. |
|
The front-end is what I dreamed I could have when I started to use |
|
After reading through the implementations/documentation in numpy and opt_einsum, I'm writing the base cases to handle a single operand or a pair of operands and then I'll write a function that takes the general case along with a pre-specified path and iterates along the path using the base cases. Last will come an independent function (or functions) to optimize the path given the operand sizes. |
|
I published a beta version of my crate to crates.io. It still has some issues but it's far enough along that you are welcome to give it a spin. There is a minimal example (and more in the tests/benches) at the crate repo where you should feel free to open any issues - we can move the discussion there. |
Purpose
The idea behind this collection is to provide an index to easily navigate all currently open ndarray's issues which are immediately actionable.
This is meant to be a good starting point for new contributors (e.g. what should I work on?) and it can also help existing contributors to identify trends and hot areas. I have pinned it using GitHub's new feature, so that it doesn't get lost (and stale).
Given that we have ~100 open issues (and more are opened every day), you are very welcome contributing to this taxonomy effort either commenting on this issue or editing it directly (if you have permissions to do so).
I am only adding to this tracker things I can easily understand/where enough context is provided in the issue - if I left something along the way, feel free to add it and to provide more info on it.
New functionality
Documentation
ndarray's types in a public API (Similar toVec<T>vs&[T]considerations)Feature parity
np.kron) (Issue: #652 PR: #690)Interop / Finer-grained control
Implement ascontiguousarray() or contiguous() method (Issue: #532)shrink_to_fitmethod (Issue: #427)Ergonomics
multislice_axis!macro (Issue: #593)New constructor method for 2D arrays from an iterator of 1D arrays/vectors (Issue: #539)(#609)ArrawViewas custom Dynamically Sized Type (Issue: #538)Quality of life
Arbitrarytrait forArray(Issue: #596)ArcArray1andArcArray2(Issue: #661)Runrustfmton the project and add it to the CI pipeline (PR: #608)Runclippyon the project and take care of the linter warnings (PR: #642)Other
Cloneelements instackandselect(Issue: #269)Improvements
Documentation
ndarray-examplesAxisNewType pattern rationale (Issue: #564)astype(Issues: #493 , #525)Zip/azipwith failing examples (Issue: #453)Error messages / Debugging
Better formatting withDebugfor arrays (Issue: #398, PR: #606)Sharp API edges/corner cases
Avoid panicking for zero-length axis inmap_axis/map_axis_mut(Issue: #579)Core
ChangeArrayBase.ptrtoNonNulltype (Issue: #434 PR: #683)Performance
sum_3_azip(Issue: #561)