PyDSTool does not run on Anaconda

[clas]

Hmmm....

I just installed PyDSTool on Anaconda.

I get the following odd error message...

In [1]: from PyDSTool import *

RuntimeError Traceback (most recent call last)
<ipython-input-1-bc4dc4d8a139> in <module>
----> 1 from PyDSTool import *</module></ipython-input-1-bc4dc4d8a139>

~/anaconda3/envs/test/lib/python3.6/site-packages/PyDSTool/init.py in <module>
74 assert len(vernums) > 0
75 if vernums[1] < 5:
---> 76 raise RuntimeError("SciPy v0.5.1 or above is required")
77 del digits, vernums, temp_str
78 </module>

RuntimeError: SciPy v0.5.1 or above is required

---

I have SciPy 1.2.1.

What is happening here?

[clas]

ok. I installed the "beta" version from github and it works...

[Mohammadreza Dorvash]

Hi,

I have the same problem you encountered a few days ago. I installed PyDSTool and get the the "SciPy v0.5.1 or above is required" error.
I ran the .py file of my own project and several other projects with all three of these environments:
1- anaconda/spyder
2- the MacOS terminal
3- IDLE

I get the "SciPy" massage with the first two and "No module named PyDSTool" with IDLE.

I reinstalled PyDSTool by all these methods:
1- conda install
2- pip install
3- git clone
4- directly downloading the files from github and manually running the setup.py file

None of these installation methods had any effect on the errors I get. How did you solve your problem?

[clas]

A bit different. I grabbed the latest version which after looking through files noted that scipy issue was fixed. So I did (in anaconda...)
pip install git+https://github.com/robclewley/pydstool.git
and it works fine.
Clas

Clas A. Jacobson1010 Horizon WayCT 06084 860 783 0074 (home)
jacobsonclas@sbcglobal.net

On Friday, April 26, 2019, 5:40:37 AM EDT, Mohammadreza Dorvash <dorvashmr@users.sourceforge.net> wrote:

Hi,

I have the same problem you encountered a few days ago. I installed PyDSTool and get the the "SciPy v0.5.1 or above is required" error.
I ran the .py file of my own project and several other projects with all three of these environments:
1- anaconda/spyder
2- the MacOS terminal
3- IDLE

I get the "SciPy" massage with the first two and "No module named PyDSTool" with IDLE.

I reinstalled PyDSTool by all these methods:
1- conda install
2- pip install
3- git clone
4- directly downloading the files from github and manually running the setup.py file

None of these installation methods had any effect on the errors I get. How did you solve your problem?

PyDSTool does not run on Anaconda

Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/pydstool/discussion/472291/

To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

[clas]

A bit different. I grabbed the latest version which after looking through files noted that scipy issue was fixed. So I did (in anaconda...)

pip install git+https://github.com/robclewley/pydstool.git

and it works fine.

"Works fine."

• I cannot get the Radau integrators to work. I looked at all the old posts that I could find and nothing seemed to to indicate how to fix this. I'm running this under Ubuntu 18.04 in Anaconda.

• The Dopri sorta work. I run them and they fail. I then move the .so files from the temp directory (which I saw in some post that I cannot locate again...from Rob) into the parent and re-run and its fine. Odd, annoying but it does run.

Hope thie helps. Great package.

[Mohammadreza Dorvash]

Well, I found the following link very helpful in solving the problem with SciPyversion. Apparently, when they were coding PyDSTool they did not think about the fact that SciPy might release versions higher than 1.0.0!!!!!!!!!!

https://stackoverflow.com/questions/49369299/pydstool-do-not-recognize-scipy-version

The problem is in the __init__.py file, line 76.

Additionally, one might the following link to install the PyDSTool:

pip install git+https://github.com/tkf/pydstool.git

TKF tried to address the issue by changing a few things in the setup.py file; however, if this does not work, changing the line 76 of the __init__.py will probably be a viable choice.