tch-rs VS neuronika

I wanted to do something like this but then I would miss on proper CUDA acceleration and lose performance compared to using torchlib.

I wrote a forgettable llama implementation for https://github.com/LaurentMazare/tch-rs (pytorch's torchlib rust binding).

I first encountered OCaml's PyTorch bindings because apparently they generate a C wrapper around PyTorch's C++ API, and Rust's PyTorch bindings use OCaml's C wrapper. See: https://github.com/LaurentMazare/tch-rs

You could try looking at the min-GPT example of tch-rs. I'd also strongly suggest watching Karpathy's video to understand what's going on.

If you pefer to see it in code there's a succint gpt implementation here https://github.com/LaurentMazare/tch-rs/blob/main/examples/m...

Rust is fully compatible w/ C bindings, so even Python libraries written in C can be easily set up to work in Rust (and have been). For example, see PyTorch Rust bindings, which actually works faster than in Python because all of the glue code around the C++ API is in Rust instead of Python.

Pytorch

I have looked into this a bit and found some crates which help in loading torchscript models called tch-rs

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

Also you can take a look at neuronika.

There is also https://github.com/neuronika/neuronika

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.