Model-Post-Training

TL;DR for operators For generated engineering code, successful execution should be treated as a feasibility check, not a correctness certificate. In the paper’s 7B ablation, reinforcement learning based only on program validity reaches pass@1 of 0.58 and pass@8 of 0.76. Adding continuous trajectory accuracy raises those figures to 0.71 and 0.84. The mechanism is straightforward. Generated solver code must first run, return the required output shape, and avoid non-finite values. Programs that clear those checks are then graded by how closely their numerical trajectories match hidden references and, where available, how consistent their outputs are with the governing PDE. ...

Compile Once, Train Later: Offline RL Moves Code-Model Verification Upstream Code assistants have a small accounting problem. Not the glamorous kind involving model capability, agentic workflows, or yet another dashboard with a glowing neural blob. The ordinary kind: every time a model proposes code during reinforcement learning, someone—or something—has to run it, test it, score it, and feed that score back into training. ...