You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In general, permanents, I think, can be applied to non-square matrices. The determinants too can be applied (except that they are always zero). There is this assert statement that requires the matrix to be square.
I can see why the Geminal.permanent can be a static method and that in the case of APIG, we will always only have permanents of square matrices.
I guess I'm just wondering if this needs to be moved to a "math" location. And if it does, then we should maybe remove the square matrix restriction.
The text was updated successfully, but these errors were encountered:
1. Make ftol and xtol arguments for newton() for inxcreased fine-tuning
2. Change test/test_newton.py to reflect change #1.
3. Organize test/test_newton.py into separated functions with purposeful names.
If we're looking at this module as a fancy-CI/Projected Schr. Equation module, then the permanent is one of these "f(C)" functions that determines the form of the wavefunction. For this reason, it might make sense to leave all "f(C)" functions inside their wavefunction class. This would include the permanent function.
In general, permanents, I think, can be applied to non-square matrices. The determinants too can be applied (except that they are always zero). There is this assert statement that requires the matrix to be square.
I can see why the Geminal.permanent can be a static method and that in the case of APIG, we will always only have permanents of square matrices.
I guess I'm just wondering if this needs to be moved to a "math" location. And if it does, then we should maybe remove the square matrix restriction.
The text was updated successfully, but these errors were encountered: