正在加载视频...
视频加载失败
Performant reinforcement learning is a hard infrastructure and research problem. We’ve recently made on-demand multi-node clusters available and showed how to take advantageous of heterogeneous sampling compute. But there still exists the need for high-fidelity environments, clear and robust reward functions, and tuned training recipes that actually work. Most... show more
12,904 次观看 • 18 天前 •via X (Twitter)
9 条评论

Axiom Bio trains large open models to identify molecules from mass spectrometry data, which requires doing long-context RL. With our training library, they had full control to quickly conduct 64k-context DeepSeek V4.1 Flash runs on 64 B300s.

@AfterQuery curates long horizon data from domain experts for models to be trained on. Using our training library, they were able to kick off autoresearch for models like Kimi and DeepSeek at 256k context length on their existing datasets.

Read more at

love seeing this, post training is turning into a product instead of a research project

Can the training/eval split keep whole customers or workflows out, rather than random steps from the same traces? I’d want to see whether gains survive on an unseen workflow before treating higher reward as better production performance.

For a small team, “own your intelligence” still needs a break-even number: training + failed runs + data cleanup, spread over expected traffic. Cheaper inference can take a while to pay that back. Would love to see that alongside the reward curves.

@andrewdsouza modal's dojo trains llms for ai teams we know a team flagging reward hacking mid training

Long-context runs make debugging reward changes expensive. Saving the environment version, reward code and representative rollout traces with each checkpoint would let teams explain why a score moved, rather than only seeing that it did.

you list clear reward functions as one of the hard parts and the library ships tuned defaults. how does it help when a team's reward function is the thing that's wrong?



