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

ValueError: Imaginary component 4.082076360939105e+125 #103

Open
khansharkhamnida opened this issue Nov 10, 2023 · 14 comments
Open

ValueError: Imaginary component 4.082076360939105e+125 #103

khansharkhamnida opened this issue Nov 10, 2023 · 14 comments

Comments

@khansharkhamnida
Copy link

image

Hello, I've encountered the problem above

@vinesmsuic
Copy link

vinesmsuic commented Nov 13, 2023

scipy has to be 1.11.1 instead of 1.11.2 . Just downgrade it with:

pip install scipy==1.11.1

@zc1023
Copy link

zc1023 commented Nov 15, 2023

scipy has to be 1.11.1 instead of 1.11.2 . Just downgrade it with:

pip install scipy==1.11.1

Thank you!It works!

@1LOVESJohnny
Copy link

scipy has to be 1.11.1 instead of 1.11.2 . Just downgrade it with:

pip install scipy==1.11.1

It saves my day :)

@ElysionHuang
Copy link

scipy has to be 1.11.1 instead of 1.11.2 . Just downgrade it with:

pip install scipy==1.11.1

It does work lol !

@lucascolley
Copy link

It looks like the behaviour change comes from scipy/scipy#17918 in 1.11.2. That was supposed to be a bugfix - does it look like a regression here, or is this repo just relying on the buggy implementation?

@sh190128
Copy link

sh190128 commented Mar 6, 2024

scipy has to be 1.11.1 instead of 1.11.2 . Just downgrade it with:

pip install scipy==1.11.1

niubi!

@wxc522
Copy link

wxc522 commented Apr 3, 2024

scipy has to be 1.11.1 instead of 1.11.2 . Just downgrade it with:

pip install scipy==1.11.1

666

@lucascolley
Copy link

This should be fixed now in SciPy 1.13.0, which was just released. Please try with that SciPy version and let us know if the issue persists.

@davystrong
Copy link

@lucascolley just to confirm, this seems to be fixed now.

@lucascolley
Copy link

thanks @davystrong !

@lucascolley
Copy link

@mseitzer I recommend closing this issue now. You may want to consider:

  • placing a lower bound of 1.13.0 on SciPy
  • blocking scipy versions >=1.11.2, <1.13.0

Or just making the recommended fix of upgrading SciPy more visible.

@adil2414
Copy link

adil2414 commented Jul 7, 2024

3 hr of looking for solution. it worked omagaaaa

@ShoufaChen
Copy link

scipy==1.13.0
numpy==1.26.2

works for me. numpy==1.23.5 does NOT work.

@ChongjianGE
Copy link

scipy==1.13.0
numpy==1.26.2

works for me. numpy==1.23.5 does NOT work.

@ShoufaChen Thanks! It saves my day!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests