I have the following piece of R code:
# next line loads a variable called "dat"
load('/tmp/dat.R')
# make a copy
d <- dat
# extract the dat$web fields for the future
d <- subset(d, web == 'future')
In rpy, I figured out that the equivalent starts out with:
r.load('/tmp/dat.r')
Peter said the following at 09/05/2007 03:25 PM :
> from rpy import r
> r("d <- load('/tmp/dat.R')")
> r("d <- subset(d, web == 'future')")
> print r("d")
>
Oh, I didn't realise that one could simply write r("r-command-goes-here").
In that case I think I'm fine, because I have working R code, so
D. R. Evans said the following at 09/05/2007 03:59 PM :
> Peter said the following at 09/05/2007 03:25 PM :
>
>> from rpy import r
>> r("d <- load('/tmp/dat.R')")
>> r("d <- subset(d, web == 'future')")
>> print r(&qu
D. R. Evans said the following at 09/05/2007 04:25 PM :
> but when I convert these to:
> r("attach(d)")
> r"(lo <- loess(percent ~ ncms * ds, d, control=loess.control(trace.hat =
> 'approximate'))")
>
> I get:
> r("lo <-
I have the following piece of R code:
# next line loads a variable called "dat"
load('/tmp/dat.R')
# make a copy
d <- dat
# extract the dat$web fields for the future
d <- subset(d, web == 'future')
In rpy, I figured out that the equivalent starts out with:
r.load('/tmp/dat.r')
I have a script that works fine under Linux.
I just installed R and Rpy on Windows (and the other modules, etc.
that are needed in Windows). I have altered the path to include the
directory c:\program files\R\R-2.5.1\bin.
When I run the script under Windows, all that ever happens is the following
