跳到主要內容
AI News HubLIVE
更多
站內改寫1 分鐘閱讀

待翻譯:The Sequence AI of the Week #908: You Need to Learn About Gemini Robotics

文章摘要

AI 服務暫時不可用,以下為來源摘要,待恢復後補全翻譯:Google put a walking humanoid inside a single policy, published the reasoning half as an API, and kept the motor half behind a partner gate. The numbers explain why.

來源TheSequence作者: Jesus Rodriguez
待翻譯:The Sequence AI of the Week #908: You Need to Learn About Gemini Robotics
回報錯誤

更正管道尚未開通,可先複製下方文章資訊留存。

查看更正說明
直接讀正文

AI 服務暫時不可用,以下為來源正文,待恢復後補全翻譯。

The demo carrying this entire release is boring on purpose. You ask Apptronik’s Apollo 2 to put the watering can into the green bin on the bottom shelf. It walks to the table, picks up the can, takes a few steps to the shelves, and places it where you asked. Nothing in that sentence sounds hard until you remember what the previous Gemini Robotics models actually were. They were a torso bolted to a fixed base doing tabletop work. If there were legs, they belonged to somebody else’s controller. Walking is not the interesting part. Boston Dynamics solved walking years ago with hand-tuned controllers and a lot of hydraulics. The interesting part is that the walking and the grasping came out of the same policy, conditioned on the same language instruction. Locomotion stopped being a subsystem you call and became part of the action space you predict. That is the real news in Gemini Robotics 2, and it is a bigger deal than the b-roll makes it look. Three models, two access tiers Read more

展開要點與分析

文章情報

工程師中級

要點

  • AI 服務暫時不可用,系統已先保留來源內容與降級後設資料。
  • Google put a walking humanoid inside a single policy, published the reasoning half as an API, and kept the motor half behind a partner gate. The numbers explain why.

要點與分析由自動化流程生成,可能有誤,請結合原始來源核實。