Community & Support
Learn
Marketplace
Discussions
Categories
Discussions
General
Platform
Academic
Partner
Regional
User Groups
Documentation
Events
Altair Exchange
Share or Download Projects
Resources
News & Instructions
Programs
YouTube
Employee Resources
This tab can be seen by employees only. Please do not share these resources externally.
Groups
Join a User Group
Support
Altair RISE
A program to recognize and reward our most engaged community members
Nominate Yourself Now!
Home
Discussions
Community Q&A
issues of installing R-extension
winecoding
I followed the R-extension installation guide step-by-step, except the following step,
“Now you can configure RapidMiner. If you click on Next, you will be asked to enter the path to the jri library that has been installed with rJava. This is located in one of the .libpath directories noted above and more exact in <libpath directory>/rJava/jri/. The filename depends on your operating system and is jri.dll on Windows and libjri.so or jri.so on Unix.”
After clicking next, I selected C:\users\suc\Documents\R\win-library\2.15\rJava\jri\jri.dll
I think it should have been C:\users\suc\Documents\R\win-library\2.15\rJava\jri\jri.dll
But looks like there is no way to allow me modify it. I tried to re-install RapidMiner, removing R-extension and re-install R-extension. No matter what I did, it seems that the system just remember this. After I click next, the popup message box always says: Found library in C:\users\suc\Documents\R\win-library\2.15\rJava\jri\jri.dll
Find more posts tagged with
AI Studio
Extensions
R
Installation
Accepted answers
All comments
MariusHelf
Hi,
you can edit the settings in Tools->Preferences->R
Please note that the R architecture must match the RapidMiner architecture, so if you are using 64bit-RapidMiner, you have to choose the 64bit version of rJava. For me it's for example C:\Users\marius\Documents\R\win-library\2.15\rJava\jri\x64\jri.dll
Best, Marius
Quick Links
All Categories
Recent Discussions
Activity
Unanswered
日本語 (Japanese)
한국어(Korean)
Groups