Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

MIT’s latest research just just gave Robots a great new skill to grip delicate yet heavy objects without breaking them. The big problem is robots often cannot pick up heavy but fragile things because gripping hard enough usually means crushing or slipping. A single gripper shape has to do...

1,632,855 görüntüleme • 7 ay önce •via X (Twitter)

0 Yorum

Yorum bulunmuyor

Orijinal gönderinin yorumları burada görünecek

Benzer Videolar

Why did so many languages copy async/await from C#? Anders Hejlsberg(Anders Hejlsberg) - creator of TypeScript, C# & Turbo Pascal - on what they got right with the design: #1 - async/await was designed to solve a common problem in the event-loop model: "A lot of languages are built around cooperative multitasking in the sense that they have an event loop that sits and dispatches events. Then you handle the event and then you yield back to the event handler loop. And it all runs in a single thread cooperatively. The problem with that is if you then want to do some long running work: how do I stop in the middle of this piece of long running work and yield back to the event loop cooperatively? And then when my result is ready, I can come back and continue executing here." #2 - state machines are the solution, but hard to build: "Well, in order to do that in an inverted architecture like that, you have to build a state machine. State machines are notoriously hard for people to implement because you've got to move all of your state off of the stack into objects. And then you have this big case statement that envelopes your entire logic. It's a nightmare to figure out. But, the transformation from serially executing code into a state machine, its continuation-passing-style translation is actually one that you can do in a machine-based fashion." #3 - compilers are good at writing state machines: "You can have the compiler write the state machine if you introduce syntax that allows you to indicate where you want to yield. And that's what await is. Await is basically saying, I want to yield here, and I want to yield this promise, and then when the promise completes, I want you to come back here and continue executing. Then the compiler writes a state machine around it and it actually turns it into this big switch statement and moves all of the state that survives across the await into something that's heap allocated. So it can be brought back. And doing all of that work is something that compilers are great at. And so that was sort of the idea that we have this new style of programming where we're using promises or the equivalent of promises and the ability to yield and then we have callbacks. But trying to write your program in that style, that's also what JavaScript suffered from a lot. It's like all this callback style stuff. With Async and Await, you get the illusion that you're just writing normal sequential code and then the compiler does the painful transformation for you. That turns out to be really useful."

The Pragmatic Engineer

13,258 görüntüleme • 1 ay önce

i watched gemma 4 12b build something genuinely impressive today, and then loop itself to death right in front of me. the full run is in the video, sped up but completely uncut, watch it to the end and you will catch the exact moment it stops building and starts looping right in the middle of the work. the task was clean, build a single file gravity simulator, n-body physics, orbits, collisions, running locally on one 3090 through an agent. and for ten minutes it was a joy to watch. it reached for a symplectic integrator on its own, the correct one, the kind that keeps orbits stable instead of spiralling out. real gravity with softening, proper orbital velocities, momentum conserved on collision. the physics was right. the thing actually worked. then on the very last step, writing a few tests to prove its own code, it fell into a loop. not a crash, a loop. it started repeating itself and would not stop. ten more minutes, thirty four thousand tokens into a single answer, the same fragments over and over, until i killed it myself. so it's not that gemma can't code. it did the hard part beautifully. it cannot finish. it cannot hold a long task together without unravelling, and finishing is the entire job in agentic work. here's the part that stings. i run this exact task, same harness, same card, on the chinese open models, qwen especially, and i never see this. they build it, they test it, they stop. every single time. google has the raw capability, you can see it sitting right there in the code, and then the model loops itself to death on a task a 27b from alibaba finishes clean. open weights, apache 2.0, so much to love on paper. i just need it to know when to stop talking.

Sudo su

39,574 görüntüleme • 2 ay önce

This work makes a humanoid robot do simple parkour moves by looking with a depth camera and choosing the right move on the fly. The big deal is that it turns lots of small human moves into long, real-time robot behavior, without hand-coding every transition or retraining for each new course. A humanoid robot is usually good at steady walking, but it often fails when it has to do fast moves like jumping up, vaulting, or rolling, and then keep going to the next obstacle. The hard part is that you cannot easily collect training data for every possible obstacle shape, distance, and mistake, so robots end up learning a few moves that only work in a narrow setup. This work starts from short clips of real human parkour moves, like stepping over, vaulting, climbing, and rolling. It uses motion matching, which is basically a smart “pick the next clip that fits best right now” search, to stitch those short clips into a long, smooth plan that looks like a human doing a whole course. Then it trains a controller with reinforcement learning (RL), which means the robot learns by trial and error to copy that plan while staying balanced and not falling. After training separate expert controllers for different moves, it compresses them into 1 controller that uses only onboard depth sensing and a simple “go this fast in this direction” command. In real tests on a Unitree G1 humanoid, it can clear multiple obstacles in a row, adapt when obstacles get moved, and climb a wall up to 1.25m.

Rohan Paul

37,121 görüntüleme • 5 ay önce

Dario Amodei just told software engineers exactly how long they have. Six to twelve months. Amodei: “I have engineers within Anthropic who say I don’t write any code anymore. I just let the model write the code, I edit it, I do the things around it.” The people building the most powerful AI in history have already stopped writing code. That is not a forecast. That is the current working condition inside the lab closest to the frontier. Amodei: “We might be six to 12 months away from when the model is doing most, maybe all, of what SWEs do end-to-end.” The tech industry spent a decade making software engineers its highest-paid, most protected class. That era has a last day now. When a model can execute an entire software build end-to-end, the ability to write syntax stops being a skill. It becomes a credential for a job that no longer exists. Amodei: “And then it’s a question of how fast does that loop close.” That is the sentence everyone skipped. The code was never the hard part. The hard part was everything around it. The model just learned everything around it. Writing the code is already nearly gone. Testing is next. Deployment is next. When all three collapse into a single autonomous execution loop, the machine no longer needs a human in the chain at all. The corporation or sovereign state that closes that loop first does not gain a competitive advantage. It gains a category of speed that biological engineers cannot match, track, or reverse. That is not disruption. That is replacement at a systems level. Amodei is not describing a future disruption. He is describing the current state of his own building. The loop is already closing. The only question is whether you are inside it or outside it when it seals.

Dustin

318,457 görüntüleme • 5 ay önce

A TURING AWARD WINNER STOOD UP AND TOLD A ROOM OF ENGINEERS THAT ALMOST NONE OF THEM DO THE ONE THING THAT ACTUALLY SEPARATES REAL ENGINEERING FROM TYPING, THEY WRITE CODE BUT THEY NEVER WRITE THE BLUEPRINT 56 minutes from Leslie Lamport -- Turing Award winner, creator of the tech behind almost every distributed system on earth. -> His claim: architects draw plans before a brick is laid. Programmers just start coding and hope. That gap is where complex systems quietly break. 04:10 -- A blueprint for software is called a spec. Write what the system must DO before touching how it does it. 10:13 -- Thinking above the code is the skill. The language is just the last, easiest step. 43:23 -- What programmers should really know isn't syntax. It's thinking clearly enough that "done" actually means done. 48:15 -- Thinking is hard, so we skip it. We jump straight to code because typing feels like progress. And this is exactly the wall the new "Loop engineering" hype is about to hit -- people now design loops of agents that write and check code while they walk away. But an unattended loop with no spec just ships broken work faster. Lamport is the missing half: the discipline that makes it safe to leave a loop running at all. You thought the leverage moved into better prompts and better loops. This is the man showing it moved above the code, where almost no one is willing to think. Save this. Read it before you trust a single agent loop ↓

slash1s

15,306 görüntüleme • 21 gün önce

.David Deutsch: "What's currently called AI and AGI are not only different from each other, they are very close to being the exact opposites of each other. The reason is that an AI, current AI is like an AI that diagnoses diseases or an AI that plays chess or an AI that controls a huge factory. Those things have objective functions, that is they have a function that they are designed to maximize and that is why they are used in those particular applications. Or in military terms, you could say the objective is to hit the target. You might say the objective is to hit the target unless some thing specified, but it's a specified thing comes up in which case don't hit the target and so on. This is, as I said, almost the opposite of what humans do when humans think. For a start, the AI has to be obedient, that is it has to actually do the things it is programmed to do, whereas a human is fundamentally disobedient, especially when being creative. When a human plays chess, they are performing a completely different kind of computation. They don't do the same things, they don't investigate the same possibilities that the artificial chess playing machine does, because the artificial one is capable of looking at billions and billions of possibilities, whereas the human can only look at hundreds or something. They are doing something completely different. Another difference is that the human can explain, can write a book later, having become world champion, can write a book saying how I did it, as the computer program that beats the world champion can write no such book, because it has no idea how it did it. It was just following a program. I was doing this and that and that and none of that is illuminating. Also, third thing, the chess player can decide I don't want to play chess anymore, from now on I will play Go or from now on I will play tennis. If commanded to play chess, the functionality will deteriorate completely. Those things are different. What we want in an AGI is that it behaves in a way that cannot be specified in advance, because if you specified it, you would already have the answer. The AGI program has to give unexpected answers, answers to questions we didn't even know how to ask."

Deutsch Explains

72,455 görüntüleme • 1 yıl önce

Dr Fei-Fei-Li explains with a simple example how everyday household chores are so extremely difficult for Robots. "If you tell a robot to open the top drawer and watch out for the vase, this is actually a really hard task for robots." because the robot must ground language into the real world. Words like "top", "drawer", and "vase" are abstract. The system has to map them to 3D locations, objects, and relations in a noisy scene. This requires robust perception, object recognition, and spatial reasoning under uncertainty. The robot also lacks human commonsense. "Watch out" implies predicting consequences, estimating clearances, and understanding that vases are fragile. Encoding such priors, like how heavy a drawer is or how a vase might tip, is very complex and difficult without rich world knowledge. Learning the behavior from rewards is tough. The success signal is very sparse here, so naive exploration almost never stumbles on a full success sequence. This makes policy learning sample inefficient and brittle, especially when the environment changes between training and deployment. A sparse reward situation is when the agent only gets a success signal at the very end, and gets little or no feedback along the way. If a robot must open a drawer without hitting a vase, it might get reward only if the drawer ends up open and the vase is intact. Every partial try before that looks the same to the learner, reward equals 0. --- From "DSAI by Dr. Osbert Tay" YT channel

Rohan Paul

342,627 görüntüleme • 8 ay önce

The yen just jumped hard after intervention and everyone is already relaxing like the problem is fixed. That’s the dangerous part. When the yen was getting crushed, everyone stayed alert. Positioning was careful. People were watching every move. Then Japan and the US stepped in, the yen jumped, and the tone flipped almost overnight. Relief showed up. People started talking like the pressure had been handled. That shift is the part that matters. Nothing about the real setup changed. The rate gap is still wide. You can still borrow yen cheap and put that money to work somewhere that pays more. That incentive did not disappear just because two governments defended the currency for a few days. The door is still open. All the intervention did was interrupt the move. It did not close it. Now we are in the quiet stretch. Headlines slow down. The yen stops making dramatic daily swings. And that is usually when people start leaning back into the same trades that created the pressure in the first place. Caution fades. Positioning rebuilds. The market starts testing whether the threat of more intervention is real or just something officials said while the cameras were on. I do not like this phase. A sharp selloff forces people to pay attention. A bounce lets them look away. And once enough people look away, the market does not need a brand new crisis. It only needs the existing pressure to reassert itself. That is why the current calm bothers me more than the original move did. Delayed pressure does not disappear. It waits. And when it stops waiting, it usually does not give much warning. You’re treating this bounce like the problem is solved… or are you watching the part that usually gets people hurt? #Gold $JPY #Kospi

₿Strategy 🟧

16,945 görüntüleme • 3 gün önce

Demis Hassabis confirmed every frontier AI lab is working on recursive self-improvement and in the same sentence said the safety risk of removing humans from the loop entirely keeps him up at night. That combination should stop you. The CEO of Google DeepMind just confirmed that the thing most people treat as a theoretical future risk is already the active focus of every serious lab on earth right now. He explained why it works in coding and math. The feedback loop is fast. You can verify whether an answer is correct almost instantly. You can generate synthetic training data from it. The loop closes quickly and cleanly. Then he said where it breaks down. In biology, chemistry and physics. Any domain where verifying a hypothesis requires a physical experiment in the real world. The loop does not close in seconds. It closes in weeks or months. Geoffrey Hinton said in his Nobel lecture that recursive self-improvement is the development he fears most and that once started it may not be possible to stop. Hassabis is not pushing back on that. He is describing the guardrails labs are building around a process they are already running. Every lab has to think carefully about the safety of a process where no human is in the loop. He said that as a constraint they are navigating right now. The question they are sitting with is how much of it to let run without a human watching. (Watch the full interview on YouTube at Two Minute Papers channel)

Ihtesham Ali

68,231 görüntüleme • 1 ay önce