neuronika VS autograph

Also perhaps comparing to Neuronika.

how does it compare with https://github.com/spearow/juice, https://github.com/neuronika/neuronika and https://github.com/spearow/juice?

Check where and how this struct is used. https://github.com/neuronika/neuronika/blob/variable-rework/neuronika-variable/src/history.rs

I have a question: as the maintainer of [neuronika](https://github.com/neuronika/neuronika), a crate that offers dynamic neural network and auto-differentiation with dynamic graphs, I'm looking at a future possible feature for such framework consisting in the possibility of compiling models, getting thus rid of the "dynamic" part, which is not always needed. This would speed the inference and training times quite a bit.

If you like autograd you will love neuronika

After reading most of the book, I wanted to get my hands dirty. My initial idea was to build a small machine learning framework but I deemed it to be too difficult if not impossible for me at the time. (Now, neuronika would have something to say). When gathering the bibliography for my thesis, I recalled to have stumbled upon a particular algorithm, t-SNE, whom I liked very much. I found the idea behind it to be very clever and elegant (t-SNE it's still one of my favorite algorithms, together with backprop and SOM, I find manifold learning fascinating in general). "So be it", I said, and I began writing a mess of a code, that was basically a translation of the C++ implementation. Boy was it bad.

me and a colleague of mine are developing neuronika

I'm working on a machine learning library https://github.com/charles-r-earp/autograph implemented in Rust that uses rust-gpu to compile Rust compute shaders to spirv, and then gfx_hal to target metal and dx12. Training performance is currently about 2x slower than pytorch (cuda) on my laptop but I've made significant progress recently and I am targeting 1.5x. While rust-gpu itself has it's own restrictions, it does support inline spirv assembly, which provides direct access to operations not provided in its std lib, thus it's lower level than GLSL. For example, it should be possible to target cuda tensor cores via cooperative matrix operations (I believe Metal supports these as well but this may not be implemented in spirv-cross and certainly isn't in naga). Once I have things a bit more stabilized I'd like to provide more examples, like porting from cuda / opencl, but I'm still figuring out patterns like how to work with 16 and 8 bit types in a nice and portable way.

autograph v0.1.0

Working on autograph, for machine learning and neural networks. Unlike CUDA / HIP it's threadsafe, but doesn't expose low level things like multiple streams. Most of the shaders are glsl but I'm now using rust_gpu for pure rust gpu code.

Maybe not for learning but as inspiration I have to plug this amazing effort for ML with (vulkan) shaders: https://github.com/charles-r-earp/autograph

Maybe you'd be interested in checking out my library, https://github.com/charles-r-earp/autograph?