3 ms·
Author of the post here - happy to answer any questions.
by gxcode 2y ago
Author of the post here - happy to answer any questions.
- philzook 2y agoBeautiful stuff, great post!
- gxcode 2y agoThank you, really appreciate that.
- beltranaceves 2y agoGreat job! I'm working in a similar blog post and it was fun seeing how you approached it. I was surprised the wasm implementation is fast enough, I was even considering writing webGpu compute shaders for my solver
- dartharva 2y agoOT, but can you share the CSS you're using for your site (the blog)? I love how clean it is.
- gxcode 2y agoI ended up making my own theme, but my starting point was PicoCSS: https://picocss.com https://picocss.com
- exe34 2y agohi, this is brilliant, thank you! I will definitely go through it soon. I have been trying to figure something out for a while but maybe haven't quite found the right paper for it to click just yet - how would you mix this with video feedback in a real robot - do you forward predict the position and then have some means of telling if they overlap in your simulated image and reality? I've tried grounding models like cogvlm and yolo, but often the bounding box is just barely useful to go face something, not actually reach out and pick something. there are grasping datasets, but then I think you still have to train a new model for your given object+gripper pair - so I'm not clear where the MPC part comes in. so I guess I'm just asking for any hints/papers that might make it easier for a beginner to grasp. thanks :-)