Skip to content
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

Rename CutoffsFamily to CutoffsPseudoPotentialFamily #82

Merged
merged 1 commit into from
May 3, 2021

Conversation

sphuber
Copy link
Contributor

@sphuber sphuber commented May 3, 2021

The CutoffsFamily was introduced in order to properly test the
RecommendedCutoffsMixin. It was even given an entry point but this was
just a requirement for the tests to work and it was never intended to
actually be used in production. However, there now seems an actual
usecase for this class as a substitute for the SsspFamily and
PseudoDojoFamily who also have the mixin and allow recommended cutoffs
to be defined but they come with strict rules and only official sets of
pseudopotentials are supported.

If one wants to create a custom pseudopotential family but still want to
use the recommended cutoff functionality, the PseudoPotentialFamily
base class doesn't suffice but the CutoffsFamily does. Now that we
actually consider the class to be used for production, a more aptly
named class name is required to properly reflect its intended usage.

The `CutoffsFamily` was introduced in order to properly test the
`RecommendedCutoffsMixin`. It was even given an entry point but this was
just a requirement for the tests to work and it was never intended to
actually be used in production. However, there now seems an actual
usecase for this class as a substitute for the `SsspFamily` and
`PseudoDojoFamily` who also have the mixin and allow recommended cutoffs
to be defined but they come with strict rules and only official sets of
pseudopotentials are supported.

If one wants to create a custom pseudopotential family but still want to
use the recommended cutoff functionality, the `PseudoPotentialFamily`
base class doesn't suffice but the `CutoffsFamily` does. Now that we
actually consider the class to be used for production, a more aptly
named class name is required to properly reflect its intended usage.
@sphuber sphuber force-pushed the fix/rename-cutoffs-family branch from feb4044 to 04e9bc9 Compare May 3, 2021 21:48
@sphuber sphuber merged commit 62a3fa4 into master May 3, 2021
@sphuber sphuber deleted the fix/rename-cutoffs-family branch May 3, 2021 21:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant