But her current simulations were lying to her. The numbers were noisy, the convergence was unstable, and the energy barriers looked like a jagged mountain range instead of a smooth pass.
The terminal filled with a waterfall of text—warnings, notes, compiler optimizations, the furious clatter of code becoming machine. Finally, a single line: vasp.5.4.4.tar.gz
She was running VASP—the Vienna Ab initio Simulation Package—version 5.4.2. It was a glorious, powerful fortress of Fortran code, but it had a known bug in its DFT-D3 dispersion correction when handling heavy alkalis. A bug that skewed lithium data by exactly 15 millielectronvolts. A tiny, maddening, paper-ruining error. But her current simulations were lying to her
“Old friend at TU Vienna,” Ben whispered. “They know your work. Said this version fixes the lithium bug. Also, the new block-for Davidson algorithm is savage —cuts runtime by 30%. Unofficially, of course.” Finally, a single line: She was running VASP—the
The bug was dead.
Heart pounding, she loaded her full electrolyte model—4,000 atoms, a complex grain boundary, and 12 wandering lithium ions. She set the INCAR tags, the KPOINTS, the POTCAR. She typed the sacred incantation:
Her breath caught. “How?”