"no collapse operator, using sesolve" message #1047
Comments
This was referenced Jul 16, 2019
|
As #1049 has been merged, I’m going to assume this will be fixed in the next release. Closing. |
goerz
added a commit
to qucontrol/krotov
that referenced
this issue
Aug 3, 2019
All problems introduced in QuTiP 4.4 were worked around, except for qutip/qutip#1047 A fix to qutip/qutip#1047 was merged into QuTiP's master, so presumably the problem will disappear with the next release of QuTiP. This commit specifically excludes QuTiP 4.4.0 from being installed on Travis and AppVeyor. We do not exclude that version in the list of dependencies in setupy.py, because the issue is mostly cosmetic (although it will fail tests). The average user should be OK using krotov with QuTiP 4.4.0 Closes #49
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Since the update to version 4.4, calling
mesolvewithout collapse operators prints a message "no collapse operator, using sesolve" to stdout. Is printing this message really necessary? It breaks our examples for thekrotovpackage, see e.g. the notebook https://krotov.readthedocs.io/en/latest/notebooks/01_example_simple_state_to_state.html, where these messages show up in the notebook when it runs with qutip 4.4. Of course I understand that the message is technically correct, and we could work around the problem inkrotov, but it was nice to be able to usemesolveas a catch-all for either a Schrödinger equation or a master equation. We'd have to start routing different cases tomesolveandsesolvemanually, otherwise. Personally, I would argue that this kind of message should be emitted aslogger.debuginstead ofprint, if at all.The text was updated successfully, but these errors were encountered: