Skip to content
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

Use stateful solver class in QuTiP 5.0 #119

Open
goerz opened this issue May 26, 2024 · 0 comments
Open

Use stateful solver class in QuTiP 5.0 #119

goerz opened this issue May 26, 2024 · 0 comments
Labels
enhancement New feature or request
Milestone

Comments

@goerz
Copy link
Member

goerz commented May 26, 2024

The example at https://qutip.readthedocs.io/en/v5.0.2/guide/dynamics/dynamics-class.html#stepping-through-the-run seems to indicate that in QuTiP 5.0, it is now possible to step through the propagation timestep-by-timestep, and more importantly, to update the control field after each time step.

This should get around the problem first described in #93, and could a major improvement for the krotov package: The overhead from time propagation with the Krotov-specific "sequential update" has always been the bottleneck for this package. If this can be resolved, the krotov package would become applicable to significantly larger systems. For example, a gate optimization for two transmons (not truncated to two levels) has not been feasible, and the equivalent Python example had to restrict itself to a dramatically simplified setup. If everything with QuTiP 5.0 works as it looks it might, I would think that would enable to krotov package to optimize the "full" example.

Obviously, this depends on compatibility with the new QuTiP version (#116)

@BoxiLi @MatthiKrauss

@goerz goerz added the enhancement New feature or request label May 26, 2024
@goerz goerz added this to the 2.0 milestone May 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant