Not sure why this is hitting the home page right now but people may also be interested in Mujoco Playground [1] which is the latest RL environment wrapper of mujoco, implementing both classic deepmind-control benchmarks, and some very new interesting ones!
The physics engine I'm using is called MuJoCo. And if you're wondering why I didn't write my own physics engine, it's basically because I don't have 20 years.
nestorD 18 hours ago [-]
It's what put MuJoCo on my radar recently! But I was surprised to not see him do any kind of gradient descent to optimize his hyperparameters. MuJoCo has a JAX backend so it should be fairly straightforward.
petters 17 hours ago [-]
He is much better at building hardware than he is writing software.
KeplerBoy 16 hours ago [-]
He seems pretty damn good at both.
lpribis 12 hours ago [-]
I'm pretty sure he has used gradient descent in previous videos to optimize systems, maybe this time it was just easier to hand tune rather than set up an optimization feedback harness around MuJoCo.
prathje 23 hours ago [-]
That the calibration got the simulation so close to reality was quite impressive.
cachius 22 hours ago [-]
Though he had to resort to manual calibration. I always find he has interesting problems for domain experts and would like to see him team up with one. Also with programmers for faster programs than self taught python.
Izikiel43 21 hours ago [-]
The guy has a masters in compsci and mechanical engineering, he has done both python and c++ afaik for his projects
ghusbands 15 hours ago [-]
In the video in question, he doesn't seem able to choose a good scoring function for the stochastic solver (even over multiple weeks), seemingly choosing a linear sum of distances (see 8:50) between simulation and reality. That's a mistake that not even an undergraduate should make. He needs some domain experts.
Izikiel43 7 hours ago [-]
I did comp sci, I sucked at this stuff, and I have a masters.
Low level stuff? Os? Distributed systems? Multithreaded code? Now that’s more on my alley
liuliu 16 hours ago [-]
I think the parent comment is specifically addressing why the black box (or stochastic?) optimizer he used not working.
prathje 23 hours ago [-]
We are using MuJoCo to train a G1 humanoid robot right now. The best thing is that we do not need to fight with NVIDIA software and that it runs on macOS.
While we have people's attention here, we're also working on an official browser-based interactive viewer that allows people to specify a URL to their own model and share a link.
This makes me so happy and excited! Often my mind wanders into the unknown, imagining what would happy to X if it did this? Would it have friction, etc?
I am looking forward to a way I can easily describe a scenario and have an LLM build a legitimate simulation for it. No more hypothetical talk! Next best thing to actual experimentation (can be a useful tool in convincing others to join you/support you in said real experiment - “see? I tested it in a simulation and it behaves exactly that way! We need to try this..”).
v9v 21 hours ago [-]
One thing to be mindful of is that you can get a simulation to behave in (almost) any way you want if you set the parameters right, so you should take care to understand the assumptions that you're baking into your sim before taking its results as gospel.
gspr 20 hours ago [-]
> what would happy to X if it did this? Would it have friction, etc?
MuJoCo does not simulate at a scale where you can discover whether something has friction or not. Friction is a parameter to MuJoCo's simulations.
ai_fry_ur_brain 22 hours ago [-]
Build things yourself. Using LLMs doesnt help you understand anything, they will just give you an annoying case of dunning kruger. Using them will only make you retart-d
whatever1 17 hours ago [-]
Wait what's new ? This is an established library
xingyi_dev 23 hours ago [-]
[dead]
fleahunter 18 hours ago [-]
[dead]
Rendered at 10:19:38 GMT+0000 (Coordinated Universal Time) with Vercel.
[1] https://playground.mujoco.org/
The physics engine I'm using is called MuJoCo. And if you're wondering why I didn't write my own physics engine, it's basically because I don't have 20 years.
Low level stuff? Os? Distributed systems? Multithreaded code? Now that’s more on my alley
PS: I just finished a first draft for agentic skills around working with MuJoCo in Python. Feel free to check them out here: https://github.com/prathje/agentic_mujoco_skills
Very early experimental prototype at the moment, doesn't work super well on phones yet, but you can try it at https://saran-t.github.io/mujoco/?model=https://raw.githubus...
It'll be relocated to live.mujoco.org over the next few days.
https://github.com/saucesaft/differential_policies/
https://github.com/newton-physics/newton
I am looking forward to a way I can easily describe a scenario and have an LLM build a legitimate simulation for it. No more hypothetical talk! Next best thing to actual experimentation (can be a useful tool in convincing others to join you/support you in said real experiment - “see? I tested it in a simulation and it behaves exactly that way! We need to try this..”).
MuJoCo does not simulate at a scale where you can discover whether something has friction or not. Friction is a parameter to MuJoCo's simulations.