rust-ndarray
wgpu
rust-ndarray | wgpu | |
---|---|---|
20 | 195 | |
3,328 | 10,995 | |
2.2% | 3.2% | |
8.2 | 9.9 | |
6 days ago | 1 day ago | |
Rust | Rust | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
rust-ndarray
-
Some Reasons to Avoid Cython
I would love some examples of how to do non-trivial data interop between Rust and Python. My experience is that PyO3/Maturin is excellent when converting between simple datatypes but conversions get difficult when there are non-standard types, e.g. Python Numpy arrays or Rust ndarrays or whatever other custom thing.
Polars seems to have a good model where it uses the Arrow in memory format, which has implementations in Python and Rust, and makes a lot of the ndarray stuff easier. However, if the Rust libraries are not written with Arrow first, they become quite hard to work with. For example, there are many libraries written with https://github.com/rust-ndarray/ndarray, which is challenging to interop with Numpy.
(I am not an expert at all, please correct me if my characterizations are wrong!)
-
Helper crate for working with image data of varying type?
Thanks for sharing. I read this issue on why ndarray does not have a dynamically typed array: https://github.com/rust-ndarray/ndarray/issues/651
-
What is the most efficient way to study Rust for scientific computing applications?
You can get involved with the ndarray project
-
faer 0.8.0 release
Sadly Ndarray does look a little abandoned to me: https://github.com/rust-ndarray/ndarray
-
Status and Future of ndarray?
The date of the last commit of [ndarray](https://github.com/rust-ndarray/ndarray) lies 6 month in the past while many recent issues are open and untouched.
-
How does explicit unrolling differ from iterating through elements one-by-one? (ndarray example)
While looking through ndarrays src, I came across a set of functions that explicitly unroll 8 variables on each iteration of a loop, with the comment eightfold unrolled so that floating point can be vectorized (even with strict floating point accuracy semantics). I don't understand why floats would be affected by unrolling, and in general I'm confused as to how explicit unrolling differs from iterating through each element one by one. I assumed this would be a scenario where the compiler would optimize best anyway, which seems to be confirmed (at least in the context of using iter() rather than for) here. Could anyone give a little context into what this, or any explicit unrolling achieves?
-
Announcing Burn: New Deep Learning framework with CPU & GPU support using the newly stabilized GAT feature
Burn is different: it is built around the Backend trait which encapsulates tensor primitives. Even the reverse mode automatic differentiation is just a backend that wraps another one using the decorator pattern. The goal is to make it very easy to create optimized backends and support different devices and use cases. For now, there are only 3 backends: NdArray (https://github.com/rust-ndarray/ndarray) for a pure rust solution, Tch (https://github.com/LaurentMazare/tch-rs) for an easy access to CUDA and cuDNN optimized operations and the ADBackendDecorator making any backend differentiable. I am now refactoring the internal backend API to make it as easy as possible to plug in new ones.
-
Pure rust implementation for deep learning models
Looks like it's an open request
-
The Illustrated Stable Diffusion
https://github.com/rust-ndarray/ndarray/issues/281
Answer: you can’t with this crate. I implemented a dynamic n-dim solution myself but it uses views of integer indices that get copied to a new array, which have indexes to another flattened array in order to avoid duplication of possibly massive amounts of n-dimensional data; using the crate alone, copying all the array data would be unavoidable.
Ultimately I’ve had to make my own axis shifting and windowing mechanisms. But the crate is still a useful lib and continuing effort.
While I don’t mind getting into the weeds, these kinds of side efforts can really impact context focus so it’s just something to be aware of.
-
Any efficient way of splitting vector?
In principle you're trying to convert between columnar and row-based data layouts, something that happens fairly often in data science. I bet there's some hyper-efficient SIMD magic that could be invoked for these slicing operations (and maybe the iterator solution does exactly that). Might be worth taking a look at how the relevant Rust libraries like ndarray do it.
wgpu
-
GPU Compute in the Browser at the Speed of Native: WebGPU Marching Cubes
Oh look it's subgroup support landing last week: https://github.com/gfx-rs/wgpu/pull/5301
- 3D and 2D: Testing out my cross-platform graphics engine
- Warp Terminal is now available for Linux
- Linux version of Warp terminal is here
-
Building the DirectX shader compiler better than Microsoft?
And wgpu has been doing this for years. Things like descriptor indexing are not exposed to the web but used by Rust (mostly) engines on native.
https://wgpu.rs/
-
New Renderers for GTK
If they used https://wgpu.rs/ they would get directx and metal for free (:
-
Show HN: WebGPU Particles Simulation
IIRC it was delayed multiple times. I think the first intent to ship from chrome was before 100 but they kept pushing it off. Firefox still does not support it. There are projects like wgpu[0] that wrap provide a higher level API and I have used some projects using it with no issues. WFIW I didn't see any issue with OP's demo either.
[0] https://github.com/gfx-rs/wgpu
- Deno 1.39: The Return of WebGPU
-
How do I become a graphics programmer? – A guide from AMD Game Engineering team
wgpu, the Rust WebGPU implementation is the bee's knees. https://wgpu.rs/ You can use it beyond the web.
-
There is anything like wgpu.rs for Zig?
There is anything like wgpu.rs for Zig? wgpu.rs is an abstraction on top of Vulkan, Metal, DirectX, etc...
What are some alternatives?
nalgebra - Linear algebra library for Rust.
vulkano - Safe and rich Rust wrapper around the Vulkan API
Rust-CUDA - Ecosystem of libraries and tools for writing and executing fast GPU code fully in Rust.
tauri - Build smaller, faster, and more secure desktop applications with a web frontend.
image - Encoding and decoding images in Rust
glow - GL on Whatever: a set of bindings to run GL anywhere and avoid target-specific code
neuronika - Tensors and dynamic neural networks in pure Rust.
rust-gpu - 🐉 Making Rust a first-class language and ecosystem for GPU shaders 🚧
utah - Dataframe structure and operations in Rust
bevy - A refreshingly simple data-driven game engine built in Rust
linfa - A Rust machine learning framework.
bgfx - Cross-platform, graphics API agnostic, "Bring Your Own Engine/Framework" style rendering library.