grompp should read floats (e.g charge) from data files to double, to avoid accumulating round-off error
On the 3.3M lignocellulose benchmark, gmx grompp warns that total charge is -0.000267. In double precision, it does not warn. Each moleculetype in the topology claims a qtot of zero, so probably this is an accumulation issue.
More generally, we should use double anywhere that we haven't measured that performance is worth improving via running in single, just like every other HPC application.
Avoid grompp charge warning with rounding
Even though the grompp total charge check uses double for summation,
there are rounding errors for each charge when charges are stored
in single precision. Now the charge check rounds the net charge of
molecules to integer when the difference is less than the maximum
possible sum of charge rounding errors.
#2 Updated by Berk Hess about 3 years ago
- Status changed from New to Accepted
- Assignee set to Berk Hess
All charge summation in grompp (and even in mdrun for PME corrections) is done in double precision. So I don't see directly why things differ here between a single and double build. Maybe reading and storing each charge in single precision leads to a difference in the last significant bit of some charges which is visible in the double.
If that is the case, the check in sum_q in topio.cpp should not check against 1e-6, but against something like 0.5*GMX_REAL_MIN*atoms->nr.
#4 Updated by Berk Hess about 3 years ago
- Tracker changed from Feature to Bug
- Status changed from Accepted to Fix uploaded
- Target version set to 2018
- Affected version set to git master
I would say this is a bug, since with PME grompp will generate a warning (not in v2016) and -maxwarn 1 is needed.
I pushed up a change that increases the tolerance for rounding for large molecules. Now we tolerate larger errors for large molecules. The only way to avoid that is reading and storing the charges in double precision in grompp.
#6 Updated by Erik Lindahl about 3 years ago
This is a really old issue. I remember looking into it, and the problem is likely that the individual charges themselves with values like 0.3 cannot be represented exactly in floating-point data (and obviously the error is much larger in single), and then it doesn't help that we perform the summation in double.
#8 Updated by Mark Abraham about 3 years ago
- Subject changed from grompp charge precision leads to incorrect total charge warning to grompp should read floats (e.g charge) from data files to double, to avoid accumulating round-off error
- Status changed from Resolved to Accepted
- Target version changed from 2018 to 2019
Retargeted the remaining part of the task to 2018