jetson-inference VS Enzyme

Jetson Nano’s are obsolete and no longer supported; but to answer your question, this might be a good place to start.

I’m trying to do the tutorial, where they retrain the neural network to detect fruits (jetson-inference/pytorch-ssd.md at master · dusty-nv/jetson-inference · GitHub 1)

Jetson-Inference is another amazing resource to get started on. This will allow you to try out a number of neural networks (classification, detection, and segmentation) all with your own data or with sample images included in the repo.

Hello! I'm looking for some pre trained image classification models to use on a Jetson Nano. I already know about the model zoo and the pre trained models included in the https://github.com/dusty-nv/jetson-inference repo. For demonstration purposes, however, I need a model trained on small objects from the context of production, ideally nuts, bolts, and similar small objects. Does anyone happen to know a source for this? Thanks a lot!

> They provide some SSD-Mobilenet-v2 here: https://github.com/dusty-nv/jetson-inference

I was aware of that repository but from taking a cursory look at it I had thought dusty was just converting models from PyTorch to TensorRT, like here[0, 1]. Am I missing something?

> I get 140 fps on a Xavier NX

That really is impressive. Holy shit.

[0]: https://github.com/dusty-nv/jetson-inference/blob/master/doc...

[1]: https://github.com/dusty-nv/jetson-inference/issues/896#issu...

If you have a screen and keyboard and mouse plugged into the Nano, I would recommend starting with Hello AI World on https://github.com/dusty-nv/jetson-inference#hello-ai-world

Well, don't get me wrong. I do like my Jetson Nano. For a hobbyist who likes to tinker with machine learning in their spare time it's definitely a product cool and there are quite a few repositories on Github[0, 1] with sample code.

Unfortunately… that's about it. There is little documentation about

- how to build a custom OS image (necessary if you're thinking about using Jetson as part of your own product, i.e. a large-scale deployment). What proprietary drivers and libraries do I need to install? Nvidia basically says, here's a Ubuntu image with the usual GUI, complete driver stack and everything – take it or leave it. Unfortunately, the GUI alone is eating up a lot of the precious CPU and GPU resources, so using that OS image is no option.

- how deployment works on production modules (as opposed to the non-production module in the Developer Kit)

- what production modules are available in the first place ("Please refer to our partners")

- what wifi dongles are compatible (the most recent Jetson Nano comes w/o wifi)

- how to convert your custom models to TensorRT, what you need to pay attention to etc. (The official docs basically say: Have a look at the following nondescript sample code. Good luck.)

- … (I'm sure I'm forgetting many other things that I've struggled with over the past months)

Anyway. It's not that this information isn't out there somewhere in some blog post, some Github repo or some thread on the Nvidia forums[2]. (Though I have yet to find a reliably working wifi dongle…) But it usually takes you days orweeks to find it. From a product which is supposed to be industry-grade I would have expected more.

[0]: https://github.com/dusty-nv/jetson-inference

https://github.com/dusty-nv/jetson-inference#system-setup

Automatic differentiation is done using https://enzyme.mit.edu/

lattner left google and was the primary reason they chose swift, so they lost interest.

if you're asking from an ML perspective, i believe the original motivation was to incorporate automatic differentiation in the swift compiler. i believe enzyme is the spiritual successor.

https://github.com/EnzymeAD/Enzyme

https://ispc.github.io/ispc.html

For the auto-differentiation when I need performance or memory, I currently use tapenade ( http://tapenade.inria.fr:8080/tapenade/index.jsp ) and/or manually written gradient when I need to fuse some kernel, but Enzyme ( https://enzyme.mit.edu/ ) is also very promising.

MPI for parallelization across machines.

For autodiff, we are currently working again on publishing a new Enzyme (https://enzyme.mit.edu) Frontend for Rust which can also handle pure Rust types, first version should be done in ~ a week.

Have you taken a look at enzymeAD? There is a group porting it to rust.

Enzyme dev here, so take everything I say as being a bit biased:

While, by design Enzyme is able to run very fast by operating within the compiler (see https://proceedings.neurips.cc/paper/2020/file/9332c513ef44b... for details) -- it aggressively prioritizes correctness. Of course that doesn't mean that there aren't bugs (we're only human and its a large codebase [https://github.com/EnzymeAD/Enzyme], especially if you're trying out newly-added features).

Notably, this is where the current rough edges for Julia users are -- Enzyme will throw an error saying it couldn't prove correctness, rather than running (there is a flag for "making a best guess, but that's off by default"). The exception to this is garbage collection, for which you can either run a static analysis, or stick to the "officially supported" subset of Julia that Enzyme specifies.

Incidentally, this is also where being a cross-language tool is really nice -- namely we can see edge cases/bug reports from any LLVM-based language (C/C++, Fortran, Swift, Rust, Python, Julia, etc). So far the biggest code we've handled (and verified correctness for) was O(1million) lines of LLVM from some C++ template hell.

I will also add that while I absolutely love (and will do everything I can to support) Enzyme being used throughout arbitrary Julia code: in addition to exposing a nice user-facing interface for custom rules in the Enzyme Julia bindings like Chris mentioned, some Julia-specific features (such as full garbage collection support) also need handling in Enzyme.jl, before Enzyme can be considered an "all Julia AD" framework. We are of course working on all of these things (and the more the merrier), but there's only a finite amount of time in the day. [^]

[^] Incidentally, this is in contrast to say C++/Fortran/Swift/etc, where Enzyme has much closer to whole-language coverage than Julia -- this isn't anything against GC/Julia/etc, but we just have things on our todo list.

Idk, Enzyme is pretty next gen, all the way down to LLVM code.

https://github.com/EnzymeAD/Enzyme

I'm working on merging my build-tool for (oxide)-enzyme into Enzyme itself. Also looking into improving the documentation.

that seems one of the points of enzyme[1], which was mentioned in the article.

[1] - https://enzyme.mit.edu/

being able in effect do interprocedural cross language analysis seems awesome.