-
Notifications
You must be signed in to change notification settings - Fork 8
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
Previous fix was wrong. Re-fixed #51
Conversation
@scemama would it be possible to add a regression/unit test for this functionality? I feel like it's something that is easy to break and hard to catch. |
@q-posev I detected it running |
@scemama we do run these functions on GAMESS->TREXIO output. Does this bug occur after spherical to cartesian conversion? We have PySCF and ORCA outputs that undergo that in the testing CI. |
I just added a test. |
@scemama I fixed the tests. Should we include qmckl in the test environment to accelerate the check-mos executions? I can use the latest released tarball to build the qmckl python api |
I am afraid that adding the qmckl dependency and compiling it will take as much time as the check-mos.... maybe we can just reduce the number of integration grid points. Even with 30 points, i think we can detect if someting is wrong |
Yes i also thought that the compilation will be slow. If only someone would make a Python package for qmckl... 😀 I actually increased the number of points in this MR and fixed the error thresholds for each file. This is the first attempt to address issue #12 but ideally it would be nice to store some converted trexio files as a ref somewhere and do a more rigorous check of converters using these ref files. |
The normalization was not applied at the proper place in the previous commit. I fixed it.