-
Notifications
You must be signed in to change notification settings - Fork 141
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
add batched evaluateVGLWithSpin to SpinorSet #3730
Conversation
@@ -130,13 +130,13 @@ def val(self,pos): | |||
norm = self.norm() |
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.
I saw above an h5 file was removed. No more needed?
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.
the file wasn't removed, it just got overwritten. The lcao_spinor_test.py writes the h5 file that is read by SPOSetBuilder in the test_MO_spinor.py. When I reran it to add new reference values, it just overwrote that file
Test this please |
Please review the developer documentation
on the wiki of this project that contains help and requirements.
Proposed changes
This PR adds the mw_evaluateVGLWithSpin API for SpinorSet. Similar implementation as the mw_evaluate_notranspose.
I also updated the unit test to check this function, as well as updated the unit test that used LCAO spinors since I overlooked that in the last PR.
I think I probably need to implement a few other SpinorSet mw_ APIs, but still looking through the code to see exactly what is needed. I will add other SpinorSet mw_ calls as needed in future PRs.
Part of #3712
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?
macOSX
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.