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
Analysis Refactoring - Part 2 #1795
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
More fine work - the positive difference in readability between the two still makes me very happy!
// Normalise by A site population | ||
dAxisAngleNormaliser.normaliseDivide(double(a.sites().size())); | ||
// Normalise by B site population density | ||
dAxisAngleNormaliser.normaliseDivide(double(b.sites().size()) / targetConfiguration_->box()->volume()); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking at all these uses of the DataNormaliserND
classes it feels more and more like we should rename them to reflect what they are actually doing, and that is (for the most part) just "operating" on data. Normalisation to a value or to spherical shell are specific examples of operations, but normaliseDivide
is actually just divide
in reality. As a follow-on issue I'd suggest we do a rename of the classes to DataOperatorND
which can contain both the specific functions (e.g. normaliseTo
and normaliseBySphericalShell
) as well as generics like divide()
and multiply()
.
Co-authored-by: Tristan Youngs <tristan.youngs@stfc.ac.uk>
Co-authored-by: Tristan Youngs <tristan.youngs@stfc.ac.uk>
This PR continues work towards #1769, following on from #1789.
Addresses the following:
angle
angle
system testaxisAngle
axisAngle
system testdAngle