-
Notifications
You must be signed in to change notification settings - Fork 195
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
stress errors reported during fitting and at end should be consistent #442
Comments
Is it just the name? That this is really virial/atom? |
If so then the printed units are wrong, so that needs to be fixed instead (using consistent units) |
Pretty sure it's Line 60 in dee204f
update() in the same file does in Lines 423 to 425 in dee204f
But I think we'll need @ilyes319 to confirm. And I'd strongly urge never to store an actual total stress / n_atoms. That's just not meaningful. |
See #443 |
this is fixed in dev |
The error report during fitting reports
RMSE_stress_per_atom
, and it clearly differs in value from theRMSE Stress (Virials) / meV / A (A^3)
column of the final report table (see below). I think we should just stop ever reporting (by default, at least) single atom stress contributions, because they seem to be normalized very weirdly (i.e. divided by total volume, so they're sub-intensive - only the sum over all atoms is intensive). Also, calling them "per atom" is confusing to me, as I assume that means "divided by n_atoms", rather than from each atom.vs.
The text was updated successfully, but these errors were encountered: