With 24 GB laptop GPUs getting harder to find, we squeezed our ฯ0.5 rollout stack from about 22 GB of VRAM to 11.2 GB.
New from @castorhat: the two fixes, and the 16 GB cards it runs on now. https://t.co/N1oynHK4MH
"Imagine if you're testing a robot policy on a hundred thousand dollar humanoid robot and it breaks. Then that's it."
@vivekgr92 of @agilityrobotics earlier this month on our RoboCon Physical AI Salon panel, From Lab to Deployment: https://t.co/fTtuyiR7TQ
His point:
Both repos are open source:
yamulator (sim) https://t.co/Gpf69r6Npi
prism-pi (rollout stack) https://t.co/Syfh1SiQfJ
We'll have another demo running at #CoRL2026 in Austin. Come see it at Booth #1100 ๐
This is our ฯ0.5 demo running live at #IROS2026 last month on a different YAM rig than the one its training data came from.
It had to work in a crowded and loud convention hall none of us had seen before, with people walking around the arms all day.
@castorhat broke down what it took to get it working in our new three-part series ๐
@TheHumanoidHub The API abstraction changes who can deploy a policy. Natural-language prompting without task-specific data significantly lowers setup cost.
Thank you to Boston Venture Connect for hosting, and to @Microsoft, Midas Capital, and COGITO for partnering.
The work starts after the demo. Good to spend an afternoon in Cambridge with people building past it.
A demo isn't the milestone. A customer who's happy because you solved a real problem is.
That was @castorhat's first point on the "Beyond the Demo: Building AI Businesses" panel at Boston Venture Connect's Greater China AI Showcase in Cambridge last week.
Check existing hardware before you build your own.
Custom hardware still costs serious time and money, and off-the-shelf robots and platforms often do the job. Our IROS demo ran on two off-the-shelf YAM arms.