[Paper] SLAI T-Rex: Full-Parameter Post-training of the DeepSeek-V4 Family on Ascend SuperPOD
Summary
A team published a technical report, an arXiv listing, and a public repository describing how they ran full-parameter post-training of a trillion-scale mixture-of-experts model family on Huawei Ascend NPU hardware rather than the GPU clusters most large training stacks assume. The work is organized as a layered set of optimizations: how the model is split across devices, how computation and communication are overlapped so the network stops stalling the chips, and how the low-level kernels are executed. They report a substantial gain in hardware utilization over the open baseline recipe while keeping training stable.
On top of that infrastructure, the same group built continued pretraining and supervised fine-tuning pipelines aimed at operations research problems, combining collected domain material with synthetic optimization documents whose answers were checked by a solver. The resulting fine-tuned model is reported to lead the comparison set on zero-shot problem solving, ahead of both a commercial small model and the base model it was trained from. All figures are the authors' own; nothing here was reproduced by AIOTruth.
Why it matters
Two things in this report change the map for anyone trying to be found and represented accurately by AI systems. First, the training data that mattered most here was solver-verified: synthetic documents kept only when a program could confirm the answer. That is the direction domain-specific model building is moving, and it means content whose claims can be checked mechanically has a path into model weights that unverifiable marketing prose does not. Second, credible frontier-scale post-training running outside the GPU ecosystem widens the set of models that will end up answering questions about brands. Visibility work that samples only the familiar handful of Western assistants will increasingly miss regionally trained and domain-specialized models that were tuned on entirely different corpora, and those models are the ones that will describe you inside vertical tools.
Source
- github.com/SLAI-AITP/SLAI-T-Rex the item itself, published by r/LocalLLaMA, created by pmttyji
- arxiv.org/abs/2607.20145 Original dataset with disclosed methods
- github.com/features/copilot Public source code or repository, first party
- reddit.com/r/LocalLLaMA/comments/1v47kqc/paper_slai_trex_fullparameter_posttraining_of_thewhere AIOTruth found it
What was checked
- read the item page (200)
- https://docs.github.com/en/search-github/github-code-search/understanding-github-code-search-syntax: does not mention the item, tier 6 (Public source code or repository)
- https://github.com/SLAI-AITP/SLAI-T-Rex/tree/main/docs: does not mention the item, tier 6 (Public source code or repository)
- https://github.com/SLAI-AITP/SLAI-T-Rex/tree/main/docs: does not mention the item, tier 6 (Public source code or repository)
- https://arxiv.org/abs/2607.20145: supports the item, tier 5 (Original dataset with disclosed methods)
- https://github.com/SLAI-AITP/SLAI-T-Rex: supports the item, tier 6 (Public source code or repository)
- https://github.com/features/copilot: supports the item, tier 6 (Public source code or repository)
Limitations
- Reddit engagement is a discovery signal here, not evidence that the claim is correct.
AIOTruth judgment
Evidence status is Supported: the claims trace to an arXiv submission and a first party public repository under the authors' own organization, not to a secondhand writeup. That combination of a disclosed method and released code is why the evidence and originality dimensions scored at the top of the range, and the usefulness score reflects that the optimization approach and the verified-synthetic-data recipe are both reusable by other teams. Relevance scored lower because this is training infrastructure and domain fine-tuning work, one step removed from the discovery and citation practices this site tracks, and the connection has to be drawn rather than read off the page. The performance and utilization numbers remain self-reported and unreproduced, and the Reddit thread that surfaced the item is a discovery signal, not confirmation that the results hold.
How this score was calculated
| Dimension | Weight | Score | What produced it |
|---|---|---|---|
| AIO relevance | 30% | 5 | rag; 3 scope question(s) matched |
| Usefulness | 30% | 9 | 2 artifact(s), 2 actionable marker(s), 1 measured figure(s) |
| Evidence | 25% | 9 | Original dataset with disclosed methods; 3 verified source(s) across 2 domain(s) |
| Originality | 15% | 9 | carries original testing or data; closest archive match 0 |
aioRelevance x 0.30 + usefulness x 0.30 + evidence x 0.25 + originality x 0.15. The rubric is published in full on the Editorial Method page. Scoring is deterministic: the same item scores the same on every run.
Read the source Open the source
Found something wrong here? AIOTruth corrects material errors openly. Have something we should review? Submit a find.