-
Notifications
You must be signed in to change notification settings - Fork 65
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
New release request: Flexibility on qutip + scipy extensions (Forschungszentrum Jülich/JSC) #775
Comments
Hello @AlvaroHuanay , thanks for reaching out! I'm afraid this will not be straigthforward because we encountered a severe performance degradation when we first tried to upgrade to Qutip 5 (see #730 for details). There has been no Qutip release since we last tried so I don't expect things to have changed on that front. If I may ask, do you happen to know if you actually need to run emulations on this environment with restricted dependencies? I ask because these conflicts come from the |
Hi @HGSilveri Thank you very much for your quick update. We are trying to get Qutip 4.7.5 on our systems. Nonetheless, we would really appreciate if the extension "scipy==1.13.1" could be added at least to be able to integrate it. Our intention is to have the complete pulser module as we will use both tools. Do you have in mind upgrading to Qutip 5.X for later releases? I ask this based on the coments on #730, #757. Kind regards. |
Hi @AlvaroHuanay, Unfortunately that wouldn't help you much as QuTiP is also incompatible with Scipy>=1.13. QuTiP PR for the restriction on their side: As mentioned in the issues you linked we will have to resolve this, but I don't think we can commit to a timeline immediately. Henrique will know better. Best, |
Hi again @AlvaroHuanay
I'm afraid this won't be possible because Qutip 4.7.6 (the latest and probably last release of Qutip 4) enforces
We will take another crack at this very soon. We can keep you up to date on how it goes but it is indeed not possible to commit to a timeline at the moment. |
Greetings, Thank you both (@awennersteen and @HGSilveri) for the explanation. I contacted our team and we are going to use pulser-core in the meantime. Regarding @HGSilveri last comment:
could you please reach to us when you are able to solve this issue with Qutip 5.X and Scipy 1.13.1? I will stay tunned on your repository as well as Qutip's repository to be aware of it just in case because our intention is being able to use the complete pulser module in our systems for the future. Thank you very much, your comments were very helpful. Kind Regards. |
Hi @AlvaroHuanay ! |
Dear Pulser team,
We are contacting you from Forschungszentrum Jülich. Developing Pulser 1.1.1 for our Stage 2025, we came accross with an incompatibility issue. I would like to ask if it would be possible to make a new Pulser release compatible with the following libraries:
qutip==5.0.4
scipy==1.13.1
The other dependencies you have for Pulser fit perfectly for us. Those are the only extensions we have issues with. The requirements you have in your last release for these extensions are:
qutip~=4.7.5
scipy<1.13
Could you release a new version with these compatibilities?
Any additional information you may need I will be glad to provide you so.
Kind regards.
The text was updated successfully, but these errors were encountered: