Cleanup remove_distant_points function. #3012
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
I was looking through the source code to understand what the
DFT_REMOVE_DISTANT_POINTS
keyword does, and realized I could not understand what theremove_distant_points
function was doing. I also suspect that that code was partly wrong.This PR cleans up that function so that it now does what it should.
However, it is also evident that the logic of this function is not optimal. Instead of checking if any nucleus is within the maximal spatial extent of the basis set, one should check if any nucleus is within the extent of that nucleus' basis functions. This is just a drive-by commit, as I don't think it's worthwhile to spend time on Psi4's quadrature code, since IntegratorXX and GauXC offer a reusable solution that could be used also in Psi4 with significant negative LOCs.
User API & Changelog headlines
Dev notes & details
Questions
Checklist
Status