Due to recent updates, all users are required to create an Altair One account to login to the RapidMiner community. Click the Register button to create your account using the same email that you have previously used to login to the RapidMiner community. This will ensure that any previously created content will be synced to your Altair One account. Once you login, you will be asked to provide a username that identifies you to other Community users. Email us at Community with questions.
Rapidminer studio detects pandas module but is unable to load it
Hello everyone,
I am trying to set up the python scripting operator and installed Anaconda 3.7. I used the specific python binary to enter the path to python.exe in the base environment.
When I test the path, I get an error message that pandas module is detected but is unable to load.I already reinstalled Anaconda and separately reinstalled the pandas module, still no change in the error message.
The error log set to "Finest" gives me these messages:
I am trying to set up the python scripting operator and installed Anaconda 3.7. I used the specific python binary to enter the path to python.exe in the base environment.
When I test the path, I get an error message that pandas module is detected but is unable to load.I already reinstalled Anaconda and separately reinstalled the pandas module, still no change in the error message.
The error log set to "Finest" gives me these messages:
Jun 28, 2019 10:15:41 PM com.rapidminer.extension.pythonscripting.operator.scripting.python.PythonProcessBuilder getPathPrefix
FINEST: Python executable C:\Users\****\AppData\Local\Continuum\anaconda3\python.exe detected and it is not a Conda installation.
Jun 28, 2019 10:15:41 PM com.rapidminer.extension.pythonscripting.operator.scripting.python.PythonProcessBuilder start
FINEST: Starting Python process C:\Users\****\AppData\Local\Continuum\anaconda3\python.exe using PATH=C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Users\****\AppData\Local\Microsoft\WindowsApps;
Jun 28, 2019 10:15:42 PM com.rapidminer.extension.pythonscripting.operator.scripting.python.PythonSetupTester scriptingSetupTest
WARNING: Pandas module detected, but the extension is unable to load it. Check your installation.
Jun 28, 2019 10:15:42 PM com.rapidminer.extension.pythonscripting.operator.scripting.python.PythonProcessBuilder getPathPrefix
FINEST: Python executable C:\Users\****\AppData\Local\Continuum\anaconda3\python.exe detected and it is not a Conda installation.
Jun 28, 2019 10:15:42 PM com.rapidminer.extension.pythonscripting.operator.scripting.python.PythonProcessBuilder start
FINEST: Starting Python process C:\Users\****\AppData\Local\Continuum\anaconda3\python.exe using PATH=C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Users\****\AppData\Local\Microsoft\WindowsApps;
Jun 28, 2019 10:15:42 PM com.rapidminer.extension.pythonscripting.operator.scripting.python.PythonSetupTester scriptingSetupTest
FINEST: Tested Python executable: C:\Users\****\AppData\Local\Continuum\anaconda3\python.exe
@varunm1
@varunm1
Tagged:
2
Best Answer
-
hughesfleming68 Member Posts: 323 UnicornI have this problem on one machine but not another. The quick fix is to create an environment with Python 3.6.8 and install Pandas and then set Rapidminer to use that. If I try and use my main 3.7 environment which I use all the time with Pycharm, I get the error. I am not sure why the 3.6.8 env works and the 3.7 doesn't. This is most likely a path problem on this particular machine as I do have a working Rapidminer and Anaconda Python 3.7 running in a different office.7
Answers
MarlaBot
if you want to use Anaconda, you can choose in Settings >> Preferences... >> Python Scripting the conda (anaconda) option as a package manager, then select your desired environment (the base, in your case, which is the default). (If Anaconda is not found, add the main Anaconda and the Anaconda\bin directory to the search paths in the same settings tab first.) This should solve your problem.
Let me know, if you have still problems with Anaconda 3.7.
Bence Tamás
https://community.rapidminer.com/discussion/54673/pandas-module-was-not-found
The root cause for this is usually that Conda does not find its DLLs when RapidMiner calls it. Recent Conda versions need a different path setup.
Python Scripting Extension 9.3.1 brings all kinds of heuristics to avoid any similar issues for Windows Anaconda installations.
Please let us know if you experience any issue with that version.
Best,
Peter
this did work for me. thank you
***
Unsupported Pandas version
The current version 1.0.3 of the pandas module for python is not supported.
Please make sure that the pandas module for Python has at least version 0.12.0.
***
How do I resolve this? How do I get pandas 0.12.0 and install it, if it is still available?
Are there other workarounds to this problem? I have downgraded my Anaconda from 3.7 to 3.6 in an attempt to fix this. Nonetheless, the problem still exists ...
Have you tried to update RapidMiner to the last official version (RapidMiner 9.6) ?
Regards,
Lionel
In this case, uninstall Pandas 1.0.3 and install Pandas 1.0.0.
If the error still persists, uninstall Pandas 1.0.0 and install Pandas 0.25.3
Regards,
Lionel
The operator before this, Execute Python, worked ok. It could detect the presence of 0.25.3 when I clicked the test button.
However, the Keras Model operator now displays the error message as:
The Pandas module for Python was not found.
How do I solve this?
It seems to me that the RapidMiner's extension "Keras" is no longer maintained. That's why there is some bugs like that from my point of view.
Can you instead :
- use the new Deep Learning extension (to install from the MarketPlace)
OR
- Build your Keras model manually in a Execute Python operator using Python code.
Regards,
Lionel
yes, unfortunately Keras is not maintained the same way as Python Scripting extension is maintained. The latter keeps adapting to the changes the rapidly evolving Python ecosystem dictates.
My guess is that the cause for the error is the same described above in my comment:
"The root cause for this is usually that Conda does not find its DLLs when RapidMiner calls it. Recent Conda versions need a different path setup. Python Scripting Extension 9.3.1 brings all kinds of heuristics to avoid any similar issues for Windows Anaconda installations."
Keras extension calls out to Python, but it does not sets the PATH environment variable the way how Conda requires it to find its dependencies.
I suggest to follow @lionelderkrikor's recommendations.
(If you still want to give a last try to the Keras extension and you are using Windows, you may potentially solve it this way: try to add these subfolders into the PATH environment variable before starting RapidMiner: <conda_home>/Library/mingw-w64/bin, <conda_home>/Library/usr/bin, <conda_home>/Library/bin, <conda_home>/Scripts, <conda_home>/bin, where you use the conda install path instead of <conda_home>.)
Best,
Peter