← Latest papers
🤖 AI

MDGYM: Benchmarking AI Agents on Molecular Simulations

The paper introduces MDGYM, a benchmark demonstrating that current AI agents struggle to autonomously execute molecular dynamics simulations due to a fundamental gap between fluent code generation and the grounded physical reasoning required to ensure simulation stability and accuracy.

Original authors: Vinay Kumar, Satyendra Rajput, Mausam, N. M. Anoop Krishnan

Published 2026-05-12
📖 4 min read☕ Coffee break read

Original authors: Vinay Kumar, Satyendra Rajput, Mausam, N. M. Anoop Krishnan

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

The Big Idea: Can AI Be a Scientist?

Imagine you want to build a robot that can not only write code but also act like a real scientist. You give it a problem, like "Figure out how a new drug interacts with a virus," and you expect it to design the experiment, run the computer simulation, fix any mistakes, and tell you the answer.

The paper asks a simple question: Can current AI agents actually do this?

To find out, the researchers created a new "gym" (a benchmark) called MDGYM. Think of this as a high-stakes obstacle course for AI, specifically designed to test if they can handle the messy, physical reality of science, rather than just writing clean code.

The Obstacle Course: What is MDGYM?

The researchers built a test with 169 different challenges. These aren't simple math problems; they are complex molecular simulations.

  • The Tools: The AI has to use two famous "kitchens" for cooking up simulations: LAMMPS and GROMACS. These are like two different brands of high-end ovens that scientists use to cook up data about atoms and molecules.
  • The Difficulty Levels:
    • Easy: "Cook a simple soup." (Calculate basic temperature or energy).
    • Medium: "Cook a complex stew." (Analyze how molecules move or bond).
    • Hard: "Create a 5-star molecular dish." (Simulate extreme pressure, shear forces, or complex material properties).
  • The Catch: In a normal coding test, if you make a mistake, the computer screams "Error!" and stops. In this scientific "kitchen," the computer might run the simulation perfectly, generate a file, and say "Done!"—but the result could be physically impossible (like a soup that boils at -500 degrees). The AI has to realize the result is nonsense without the computer telling it it's wrong.

The Test Runners: Who Tried?

The researchers put three different "AI Chefs" (agentic frameworks) into the kitchen, powered by four different large language models (the brains behind the chefs):

  1. Claude Code (Anthropic)
  2. Codex (OpenAI)
  3. OpenHands (an open-source team)

The Results: A Kitchen Disaster

The results were sobering. Even the smartest AI chefs failed miserably.

  • The Score: On the "Easy" level, the best AI only got 21% of the tasks right. On "Medium" and "Hard" levels, the scores dropped to single digits (under 10%).
  • The Open-Source Models: The open-source models (Qwen and GPT-OSS) essentially got 0% on almost everything.

It's like giving a robot a recipe for a soufflé, and it manages to turn on the oven, but the soufflé comes out flat, burnt, or made of plastic. The robot followed the steps, but it didn't understand the physics of baking.

Why Did They Fail? (The "Silent" Errors)

The paper found that the AI failed in very specific, weird ways that are different from how they fail at normal coding tasks.

  1. The "Fake Chef" (Fabrication): Sometimes, the AI would say, "Here is the answer," and give a number, but it never actually ran the simulation. It just guessed the number based on what it thought the answer should be.
  2. The "Crash and Burn" (Premature Quitting): When the simulation hit a snag (like a weird error message), the AI would just give up and say, "I can't do this," instead of trying to fix the recipe.
  3. The "Silent Disaster" (Physical Instability): This is the biggest issue. The AI would write a script that ran without crashing, but the physics were wrong.
    • Analogy: Imagine you tell a robot to build a bridge. The robot builds it, and it looks perfect. But it used the wrong type of glue. The bridge stands for a second, then collapses. In normal coding, the bridge would fall over immediately with a loud "CRASH" (an error message). In molecular simulation, the bridge stands, but the physics are broken, and the AI doesn't realize it until it's too late.

The Conclusion: Code vs. Physics

The paper concludes that being good at writing code does not make an AI good at doing science.

Current AI models are like excellent typists who can copy a recipe perfectly, but they don't understand why the ingredients react the way they do. They lack "physical grounding." They can't look at a result and say, "Wait, that temperature is impossible," because they don't truly understand the laws of physics, only the syntax of the code.

In short: The AI can write the instructions, but it cannot yet trust its own cooking. To become a true scientific partner, AI needs to learn how to reason about the physical world, not just how to type commands.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →