Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

ml-sharp 🤝 FLUX.2 klein Inspired by 大雄, I’ve trained a LoRA for klein 9b that can repair 3D views from ml-sharp, fixing geometry issues and restoring original details. Weights: I will share the demo + inference code soon!

31,632 Aufrufe • vor 7 Monaten •via X (Twitter)

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

Holy shit… someone just made machine learning click. Not static diagrams. Not math-heavy PDFs. Not black-box training. Real algorithms — training step-by-step — visually. It’s called Machine Learning Visualized and it lets you watch models learn in real time. Here’s why this is different: Instead of dumping theory first, it shows optimization happening live: • gradients moving • weights updating • decision boundaries shifting • loss decreasing • models converging You literally see learning happen. Everything is built from first principles: • Gradient Descent • Logistic Regression • Perceptron • PCA • K-Means • Neural Networks • Backpropagation No magic. Just math → code → visualization. Each chapter is a Jupyter notebook that derives the math then implements it then animates training. So you can watch: • neural nets shape decision surfaces • PCA rotate feature space • K-means clusters form live • gradient descent find minima • sigmoid reshape boundaries • backprop update weights step-by-step This solves a huge problem: Most ML resources teach: math → code → ??? → trained model This shows: math → code → learning process → result Which means you finally understand: • why gradients matter • how weights evolve • what loss landscapes look like • how convergence actually happens • why deep nets learn non-linear functions Even better: You can open any notebook modify parameters and watch behavior change instantly. Learning ML becomes interactive. Not passive. Not abstract. Not confusing. Just… visible. Perfect for: • beginners learning ML • devs moving into AI • interview prep • teaching concepts • understanding backprop • visual learners • building intuition This is the kind of resource that makes neural networks finally “click”. Link: We’re moving from: reading about ML → watching ML learn That’s a big shift. Because once you can see training, you stop memorizing… and start understanding. AI education just got visual.

Suryansh Tiwari

132,607 Aufrufe • vor 5 Monaten

I created a demo of a bioautomation system that uses LLMs, Opentrons, and lua to create a dynamic programming environment for cloud labs or robot/human clusters. It can reason about its own code based off of lab measurements. Most importantly, I actually fucking implemented it, and it is open source. Took about 4 days for this rough draft, and it is very much a draft. The user inputs their task, the system creates code, and then executes it. The code defines control flow from data generated in the lab. Not only can it create code, but it can reason about things that could have gone wrong, run analysis using an internal sandbox, and then create new code based off of that analysis for execution. Timestamps: 0:00 - intro and code generation 3:04 - homebrewed replacement for Opentrons API for running all this code 5:26 - dynamic control flow using data 6:10 - LLM reasoning about a biological protocol and fixing it 10:15 - rant on the future of cloud labs and bioautomation I made this as a demo for how I think we should be thinking about building and scaling biology. I believe we can encode the tacit knowledge of a laboratory into the knowledge of an LLM, that we can do reinforcement learning off of results it creates, and that we must do that by leveraging a sufficient quantity of unique, useful, verifiable protocols. That doesn't come from just doing drug screens - it comes from doing basic everyday experiments and doing them well. Through the elimination of tacit knowledge necessary to physically operate a lab + proper batching + models writing code, I think we can make building biotechnology 10x-100x cheaper and easier than it is nowadays.

Keoni Gandall

21,412 Aufrufe • vor 1 Jahr

WOW. 😳 Apple just quietly won the 3D maps war at WWDC. Gaussian Splatting is coming to Apple Maps Flyover this fall. Apple Maps Flyover covers 300+ cities. Until yesterday, every single one was built on standard drone photogrammetry. The technology captures photos from the air and reconstructs 3D geometry from them. Gaussian Splatting does not reconstruct geometry. It represents the scene as millions of tiny 3D ellipsoids, each one carrying its own color and opacity information based on how light actually behaves in that location. The output is not a mesh model. It is a field of light. When you move through it, it does not crumble at the edges. The detail holds because it was never geometry to begin with. Apple has been hiring for this for years. Their SHARP model, published in research last year, generates photorealistic 3D scenes from a single image in under a second. Google has more sensor data than anyone. More Street View cars, more satellites, more capture history. On navigation accuracy and geodata depth, Google Maps is still ahead by most measures. But fidelity in 3D city rendering is a different competition, and Apple just set a bar in that. Most people will experience this in the fall without knowing the name of the technology. They will open Flyover, look at a city they know, and notice it looks different. Real, not rendered. That is the moment Gaussian Splatting stops being a research term and becomes something a billion people use. Bookmark this. It will look prescient by October.

Shruti

19,832 Aufrufe • vor 3 Monaten

As I promised yesterday, I'll briefly explain LoRA training and share a workflow I made so you can do it quickly. First, let me answer a very common question: 'Why train LoRAs when we have such advanced models?' Even though we have incredibly advanced models now (like NBP), we still can't always get them to do specific things we want. Simplest example: the spritesheet LoRA I made the other day. I generated 1000 images with Nano Banana and only 100 were what I wanted. The LoRA I trained using those 100 images gives me nearly 100% consistent results. Second point is cost and speed. With LoRA, we can cut costs by 4-5x. And while doing that, we're generating 4-5x faster. How many images do you need for a good LoRA? This depends on your LoRA's complexity. For example, when I training the spritesheet LoRA, even though I used 100 images, I didn't include buildings in the training data, so this LoRA doesn't work for buildings. So think about your LoRA's use cases and add examples for as many use cases as possible to improve quality. What are paired images and how to train LoRAs for image-editing? When training LoRAs for image editing on fal, we call each edit example paired images - one with _start suffix, one with _end suffix. For example, if you're training a background remove LoRA, the unedited original photo will be your '_start' image. The image with background removed will be the '_end' image. Simply put: images we want to edit or use as reference get _start, target images we want to achieve get '_end'. Important: save both images with the same name. Like image332_start.jpg and image332_end.jpg. This way the system knows which images pair together. What about training LoRAs for models with multiple image inputs? Same logic. We still use _start and _end suffixes, but with one difference. Since there are multiple input images, we can number them: _start, _start1, _start2. Example: start images, 1st image = Woman portrait (image35_start.jpg) 2nd image = Glasses photo (image35_start1.jpg) 3rd image = Hat photo (image35_start2.jpg) Output image = portrait of woman wearing glasses and hat (image35_end.jpg) Can we do more detailed captioning? Yes. Similarly, you can improve training quality by creating a txt file for each set with the caption inside. Example: create image35.txt and write: 'Recreate the image by putting the glasses from the second image and the hat from the third image on the woman in the first image.' What are Steps? How many should I use? What's Learning Rate? Steps determines how many times the model sees and processes your training data (your images). Each step, the model learns a bit more. But as steps increase, so does the risk of overfitting. So there's no real default. But for a simpler LoRA with 20 paired images, 1000 steps is ideal. Here's a metaphor for the Steps and Learning Rate relationship: Imagine you have a balloon. Our goal is to inflate it to the optimal size. Steps = How many times we blow into the balloon Learning rate = How hard we blow each time If we blow too softly, we need to blow many more times. If we blow too hard, we risk popping it quickly and can't reach optimal size. Of course training won't explode, but it won't work as intended because it wasn't trained optimally. Training's done, now what? Once training's complete, you'll have a safetensors file. Every model you train on fal has a LoRA inference endpoint. In that inference, add your safetensors file link to the LoRA url input, and you can use your LoRA. Thanks for the read! The workflow in the video: If I forgot anything, let me know in the replies.

ilker

15,192 Aufrufe • vor 7 Monaten