-
Notifications
You must be signed in to change notification settings - Fork 16
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
Change the default time evolution method #143
Comments
RK4 is actually more black box than TDVP_PS and TDVP_VMF to get not bad results (of course not the best) for most Hamiltonians. |
Makes sense. However I'd like to add that the step control in TDVP_VMF is a unique advantage. Then it again boils down to the documentation. We should list all the possible schemes and their (dis)advantages. Some of them are published with well-supported data (like the 2020JCP work). Some of them are more empirical. |
I totally agree with you about improving the documentation for all the evolution algorithms. For the current situation, I think we can switch the default algorithm to P&C TD RK (general explicit RK propagator for both time-dependent/independent H), with which the time-step can be controlled adaptively (e.g Cash-Karp45, RKF45). |
I think not if the electronic sites are separated by phonon sites. Maybe this is worth documenting too.
No problem
OK. Could you do it while adding the documentation? I assume you're more familiar with the setup. Honestly I rarely use this method and I'm under the impression that the step-size control for P&C RKF is not particularly reliable. Sometimes the step size simply keeps shrinking to infinitely small in one step. |
That's true in some cases because the error due to time-step is probably overwhelmed by the truncation error in one single step. In this case, weird results will occur. |
Currently, the default time evolution method is
prop_and_compress
, which is not very popular. Maybe it's time to change it to TDVP_PS or TDVP_VMF?The text was updated successfully, but these errors were encountered: