正在加载视频...
视频加载失败
Every wondered if we can model motion as a language? can we tokenize this new language? is it useful? Turns out tremendously! 🚀 In out latest #NeurIPS2024 paper on QueST: Self-Supervised Skill Abstractions for Learning Continuous Control, we find that action tokenization matters a lot! We can learn skill... show more
26,218 次观看 • 1 年前 •via X (Twitter)
10 条评论

also a shout out to @LerrelPinto and team for their work on BAKU which is concurrent and equally impressive in terms of thinning the chaff in BC architectures. This is important and their ideas are also very timely. It is exciting to see the field simplify architectures and also simpler latent variable transformer architectures becoming very competitive at multimodal action space modeling.

Also shout out to @zsoltkira @AlexToshev and team for another learned action tokenizer “…show that a learned tokenization allows for sufficient modeling precision, yielding the best performance on downstream tasks. For discrete actions, we demonstrate that semantically aligning these actions with the native output token space of the MLLM leads to the strongest performance. We arrive at these lessons via a thorough study of seven action space adapters…” Learned action tokenization, combined with simplified transformer architectures is scaling very well I’m so glad to see more activity on this question and that too from my next-door neighbor @zsoltkira

100% agree! Tokenizing motion as a language also helps for translating language to motion (IROS 2022) We also have relevant work in BC with action tokens coming up at IROS 2024

thanks for sharing. we will look at it and definitely cite it in the camera ready.

Hi @animesh_garg @MeteAtharva , this is a really interesting paper! Just wanted to share our ICLR 24 paper, MCNN which also previously improved over diffusion policy and other BC baselines. Thanks

This is really good!

I feel the effectiveness attribution of the causal tokenizer design might be wrong. Since the AR transformer generates the tokens auto-regressively (and causally), it's natural to use a causal tokenizer -- otherwise there is a mismatch.

This is fantastic. It's exactly what I'm working on in hardware.

Great to hear that would love to know more how to do that in hardware

Cool but is it really necessary to reduce motion information to a much lower bandwidth information such as language? For humans language is easy to understand but robots can understand trajectories in coordinates. So isn’t language a shortcut here?
