@noctus91 I plan to build it out into a more cohesive benchmark with more scenarios, and it probably needs better physics. I suspect some of the lesser models fail because they can't deal with the table having infinite friction.
@noctus91 It's hastily vibe coded using MuJoCo, since I needed something pretty custom. The interface the agent sees are just three unfamiliar CLI tools; it has to actively request screenshots and figure out how to work the arm without knowing in advance how any of it works.
@CosmicMonad I only have so many characters, you know. But check out the dev branch for a preview. It's a huge number of optimizations and fixes (many of them focused on Ampere), no more FA2 dependency... so much. It's wild. Woo.
@SciumoInc I was asking it to add a test automation feature to a simple chat client, which I guess I could see why it might seem dangerous...? It's a stretch, though. But hard to say what really triggered it.
https://t.co/oxTnWJZN2v
The *only* reason I have been using Android for the last 8 years is the fact that I have control of my device, I can hack on it and write software for it and sideload it without begging anyone for the privilege. As soon as Google's "Close Android" initiative goes into effect, I will buy an iPhone and I won't develop on Android again.
@Google - Don't do this. Turn around. Cancel. Change your mind. Realize that you just made a stupid mistake after one too many beers, and you didn't actually mean it. And you are sorry for the confusion and chaos. Then this will just be a bad memory that fades away - instead of the permanent destruction you are about to inflict to your own platform, and millions of customers. And the major boon you are about to hand to Apple.
@CosmicMonad@TheAhmadOsman Or, actually maybe I was thinking about 35B (:
Yeah, 27B is dense and might benefit a bit more from TP. I do plan on adding it soon though, just currently doing the Gemma4 side quest.
@CosmicMonad@TheAhmadOsman The reason is time, really. Priorities, you know. It has 3B active parameters so TP can only do so much given the sync overhead it adds. The model is rarely compute-bound and, being mostly linear attn, that stays true at very long context lengths as well.
1/n I topped the HuggingFace Open LLM Leaderboard without changing a single weight.
No training. No merging. No gradient descent.
I duplicated 7 middle layers of Qwen2-72B and stitched it back together.
This is the story of LLM Neuroanatomy π§΅
@Pirat_Nation@BubbaGde No, that's the paper the blog post cites. It sounds like a different method because they make a bunch of new claims not mentioned in the paper (about it being 8x faster, etc.) but they don't cite any other sources.
@GoogleResearch I wish the paper would elaborate a bit on the "zero overhead" claim. Storage overhead, sure, but what are the specific circumstances where adding a whole extra dΓd rotation and codebook quant has no impact on performance, such that you get speedup equal to the bandwidth savings?
@QuixiAI@sarlev_@XiaomiMiMo Sadly not supported yet. We're waiting for Tri Dao to review/merge PR #1819 for attn sinks in FA2. One of these days, I'm sure (π)
Other than that, 96 GB would still be a tight fit. Could be usable at a little over 2 bpw, though.