Fix spinors for orb opt#4923
Merged
Merged
Conversation
ye-luo
approved these changes
Feb 13, 2024
Contributor
|
Test this please |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Please review the developer documentation
on the wiki of this project that contains help and requirements.
Proposed changes
Orbital optimization with spinors had a few issues. First, RotatedSPOs were missing a few spin APIs. Second, once the appropriate APIs were added, there were some sizing issues when spinors were used with DiracDeterminants. This is because DD always passes in data structues sized nelec x nelec, whereas in the case of orb opt the spinorset has OrbitalSetSize > nelec. This is now fixed, and orb opt with spinors should be working
Unit tests were modified or added to in order to check both the missing spin APIs in RotatedSPOs as well as the sizing issues in SpinorSet.
What type(s) of changes does this code introduce?
Delete the items that do not apply
Does this introduce a breaking change?
What systems has this change been tested on?
M1 mac
Checklist
Update the following with a yes where the items apply. If you're unsure about any of them, don't hesitate to ask. This is
simply a reminder of what we are going to look for before merging your code.