7/29/2026 at 12:51:48 AM
Genuine question: how reproducible / usable / verifiable are these architectures from the published documentation? Are they similar to PDF/DWG/PSD specifications, where the format look like an open spec at first sight until you attempt to implement it and realize the crucial implementation details are undocumented?by mickael-kerjean
7/29/2026 at 5:26:20 AM
It's entirely reproducible from the available documentation (which is why you see vLLM, SGLang, MLX etc all racing to produce optimized implementations).(As an aside, this is why the "open weights are not open source" thing is a complete misunderstanding. The weights themselves along with the documentation give you enough to fine tune the LLM. You can't rebuild it from scratch, but you can't do this even with the data anyway (because of randomness!))
by nl
7/29/2026 at 6:37:59 AM
I agree that if you have the weights you can use/train a model with the same architecture, and that you won't get the exact weights on your own due to randomness. But isn't data an extremely important part of your ability to effectively train/finetune? It might be much harder to get close to the level of the open weight model if you don't have the data that made it, which is why I think the open weights vs open source distinction is useful.by FinchNova12
7/29/2026 at 1:05:41 PM
There's more to open source than reproducibility. For instance introspection which is even more important with weights since detection of backdoors in models is NP hard IIRC.by monocasa
7/29/2026 at 7:32:24 AM
Isn’t this a bit like saying “ ‘open object files are not open source’ is a complete misunderstanding” because “You can’t rebuild the executable from scratch, but you can’t do this even with the source code anyway (because of build nondeterminism / compiler versions / etc.)”?by spider-mario
7/29/2026 at 8:35:45 AM
not really, compiling isnt a heuristic problem, it has a lot less randomness involvedby desterothx
7/29/2026 at 7:36:47 PM
there's a reason reproducible builds are a thing and most compilations aren'tby NooneAtAll3
7/29/2026 at 8:58:29 AM
Depends on your compiler. You could have a compiler that deliberately uses randomised algorithms. They are often faster and easier to understand and write.Though in practice you can get all the benefits of both determinism and (that kind of) randomisation by using a PRNG and saving the seed you are using.
It's an open question roughly on par with P vs NP whether true randomisation is ever necessary, or whether PRNGs are enough. So far we haven't found any problem or algorithm where true RNG is necessary and good PRNG ain't enough.
by eru
7/29/2026 at 11:47:20 AM
Also, most (optimizing) compilers ”optimize” the code for a fixed amount of time, leading to better optimized binaries on faster computers. That’s why developers should have as fast computers money can buy!by pcmasterr
7/29/2026 at 8:55:32 AM
> (As an aside, this is why the "open weights are not open source" thing is a complete misunderstanding. The weights themselves along with the documentation give you enough to fine tune the LLM. You can't rebuild it from scratch, but you can't do this even with the data anyway (because of randomness!))They could give you the random seeds? (Assuming you carefully train in such a way to remove other sources of randomness, like concurrent execution.)
by eru
7/29/2026 at 9:14:31 AM
Do AI labs even keep track of seeds? They don't even keep the checkpoints most of the time.by alightsoul
7/29/2026 at 6:10:40 AM
> open weights are not open source" thing is a complete misunderstanding> You can't rebuild it from scratch
There's is extremely clear and misunderstanding-free.
Open weights is not open source.
by esperent
7/29/2026 at 9:22:29 AM
> You can't rebuild it from scratch> It's entirely reproducible from the available documentation
You have a very interesting understanding of "reproducibility", I'll give you that :)
But even with that, there are plenty of technical details (especially in regards to the training process) missing from the tech report that leads to these weights not being reproducible in any sense of that word.
by embedding-shape
7/29/2026 at 9:54:58 AM
> You have a very interesting understanding of "reproducibility", I'll give you that :)He was talking about two different things, hence the parentheses. The architecture is reproducible, not the model weights.
by nvme0n1p1
7/29/2026 at 10:21:21 AM
> The architecture is reproducibleBut what's the point of even saying that? Of course it is, otherwise how is it supposed to run in the runtimes? You cannot release model weights that others can run, without also releasing the model architecture, it's in the code at the very least...
by embedding-shape
7/29/2026 at 11:25:35 AM
Because for other specs it's not the case.The K3 arch can be implemented from the spec.
A PDF reader can not be implemented from the spec.
by nvme0n1p1
7/29/2026 at 11:10:32 AM
the beginning of the arguments was good but the "because of randomness" is wildby davidguetta
7/29/2026 at 1:07:09 AM
Implementing models directly from papers is typically pretty doable (and is of course more straightforward when the full implementation is open sourced). Often there is some amount of specific knowledge, like particular hyperparameters, that is missing and has to be trial and errored by the community, but generally speaking, getting the core model architecture implemented is a reasonable task for most well documented models.Reproducing the exact training run, however, is basically impossible without the original dataset and training pipeline (here meaning all of the code + infra involved in actually executing the pre and post training loops). Also, it would be exorbitantly expensive to do if you weren't also a lab trying to train a similar model.
But you can still scale the architecture down and experiment as a solo researcher using the published research. There are probably some open source implementations already on GitHub for any given big open model release.
by calebkaiser
7/29/2026 at 8:58:24 AM
The exact training run is basically impossible anyway. Randomness plays a role. Even if you fix your RNG seed, in a distributed training scenario like this one some weight updates might come at different times and be included in different update steps. Should have minimal impact on the final outcome, but would still be a different model as some of the weights will differ in the end.by marcyb5st
7/29/2026 at 9:00:02 AM
> Should have minimal impact on the final outcome, [...]I share this expectation. But this is an interesting empiric question that deserves study; even if just to confirm what 'everyone knows'.
by eru
7/29/2026 at 11:53:34 AM
Reproducibility isn’t something that has been considered desirable in many pipelines until recent years.Heck even ffmpeg introduce randomness when stitching together downloaded chunks from youtube. By design.
by pcmasterr
7/29/2026 at 2:01:15 AM
The architectures are high level concepts and the mechanics usually have enough detail for you to try and implement.Transformers are very "mendable" in that you can permute the architecture in crazy or random ways, and still basically always end up with get a coherent LLM. The difference comes down to training efficiency, inference efficiency, and usually minor differences in performance.
Hyperparams and stuff, I mean it's standard to do a sweep anyway.
by dannyw
7/29/2026 at 3:07:28 PM
Good question, it's 100%. I.e., the developers usually share a reference implementation with e.g., Hugging Face transformers to load their weights, and from there on you can read the code and, if you have time, reimplement and check everything. It's actually a great learning exercise where you can self-check whether you reimplemented it correctly by comparing the LLM outputs to the reference implementation. Made a video about that workflow a while back here: https://www.youtube.com/watch?v=TXzQ7PGpO6wby ModelForge
7/29/2026 at 12:55:42 AM
The code is open source, and there probably several different implementations.by GaggiX
7/29/2026 at 7:52:08 AM
[flagged]by pepinal