-
Notifications
You must be signed in to change notification settings - Fork 125
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
[ITensors] Fix eigen_perturbation
rank
#1302
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## main #1302 +/- ##
===========================================
- Coverage 84.14% 53.88% -30.26%
===========================================
Files 100 99 -1
Lines 8594 8490 -104
===========================================
- Hits 7231 4575 -2656
- Misses 1363 3915 +2552 ☔ View full report in Codecov by Sentry. |
[test ITensors mps] |
[test ITensors mps] |
Run ITensors mps tests from comment trigger: succeeded ✅ |
1 similar comment
Run ITensors mps tests from comment trigger: succeeded ✅ |
Run ITensors mps tests from comment trigger: succeeded ✅ |
1 similar comment
Run ITensors mps tests from comment trigger: succeeded ✅ |
It appears that #1214 may have caused an issue when non-trivial
eigen_perturbation
is passed tofactorize
, where it is too aggressive about setting an upper bound on the rank of the factorization. This appears to cause issues for the noise term in DMRG, see https://itensor.discourse.group/t/revert-back-to-older-version-of-itensors-jl/1366.Really this logic should not be in
factorize
since it adds this extra complexity and breaks the abstraction offactorize
that it is doing a factorization of the input tensor, but disentangling it will be left for future work.I need to add a minimal test once we confirm this fixes the issue with the noise term.