Hi Jperraud,
Only happens running with R.NET.If I start the R gui, the lib paths are good.
After initializing the R engine I issue 3 R commands (one at a time).
- getwd()[report results in log file]
- .libPaths()[report results in log file]
- library(padb)[This loads my custom R package which is installed in user library]
Under R.NET 1.5.0, all 3 commands are successful.
Under R.NET 1.5.5 #2 only reports one directory and #3 fails withError in library(padb) : there is no package called 'padb'
I am in no hurry to upgrade R.NET.Let me know if you need example code.
Thanks,
Rob
From: jperraud [email removed]
Sent: Monday, September 16, 2013 5:45 PM
To: MCALLISTER,ROB (A-Spokane,ex1)
Subject: Re: Problem with version 1.5.5 [rdotnet:457115]
From: jperraud
Hi,
Thanks for reporting this.
Are you noticing a changed behavior running purely from R, or running R expressions via R.NET? I assume the latter but better ask.
I am not following the recent releases, having being tied to other (lesser...) technologies at work, and cannot intuit what may be going on. .libPaths and underlying stuff should really be pure R behavior so far as I know, so the behavior is intriguing. Even
using the R_LIB environment variable should only prepend additional library locations, not override others (see below as I use it to have a version independent library). That said I do not know for sure how it interplays with user's libraries as created by
R for non-admin users.
I'll may be able to look at this within a few days if you do not get other help meanwhile.
> .libPaths()[1] "f:/Rlib""C:/Program Files/R/R-3.0.1/library"