-
Notifications
You must be signed in to change notification settings - Fork 139
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
Fix excited states in splines when spin-up/down sets are built from the same spin species and occupation is specified on the first sposet #4158
Conversation
…he same spin specie and occupation is specified on the first sposet.
Test this please |
Test this please |
all the reference values for the deterministic tests has been updated. short/long test will be updated following #4162 |
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.
Thanks Ye & Hyeondeok.
I normally make a comment about avoiding these bugs in future, but if the implemented logic and tests are both wrong and consistent with each other there is not much more we can do, except things like having few options and therefore fewer lines and fewer chances for issues.
From the blame this bug looks to have existed for a long time.... |
Test this please |
Proposed changes
I noticed this bug when I tried to delete the implicit sposet sharing by spin-up/down electron.
When spin-up/down sets are built from the same spin specie and the occupation is specified on the first sposet, the spin-up set will be built correctly but the spin-down set will misidentify itself the same as the up set and thus the excited set will be used for both up/down spin electrons. Current test reference numbers are all bad.
@Hyeondeok-Shin
Need to update reference number of all the excited states tests using splines
A quick scan shows examples in the manual load two sets of orbitals from different spin. So it seems fine @Hyeondeok-Shin please double check the manual entries.
What type(s) of changes does this code introduce?
Does this introduce a breaking change?
What systems has this change been tested on?
epyc-server
Checklist