I am running things with a call to gc() before each regression, in case what
happens is a race condition where the gc is called in the middle of the
constrction of a new dataframe...
Thanks for the prompt help!
Laurent
2008/7/14 Laurent Gautier <[EMAIL PROTECTED]>:
> 2008/7/15 laurent oget <[EM
Sorry, here's the exact error message: **:
Couldn't execute the R interpreter `sh: R: command not found/bin/R'.
Thanks.
On Mon, Jul 14, 2008 at 6:25 PM, Saket <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I was wondering if someone could help with this problem. I installed R, and
> and am able to use it
2008/7/15 laurent oget <[EMAIL PROTECTED]>:
> can i get a quick hint on how i would go about calling --verbose through RPY
> ?
I suspect that the only way is to hack
line 93 of rpymodule.c
char *defaultargv[] = {"rpy", "-q", "--vanilla"};
and recompile/install rpy.
> I am pretty clueless about
Hi,
I was wondering if someone could help with this problem. I installed R, and
and am able to use it successfully in a regular Python program after
importing it using "import rpy". However, when I try to do "import rpy" from
a Python cgi script, I get an error which says: Couldn't execute the R
i
can i get a quick hint on how i would go about calling --verbose through RPY
?
I am pretty clueless about the way R does the garbage collection. One thing
I know is there are columns that are shared between different linear
regressions, so it might be that the garbage collector cleans up a column
I have tried ulimit -s values of up to 200 but even then I get C stack
limit usage errors in R -> error initializing RPy. Only ulimit -s unlimited
seems to work for my setup.
To clarify, I have had this problem with R-2.4.1 -> R-2.7, so I am inclined to
think it is not 2.7-specific. The old
Someone else reported on this list a similar sounding problem not so long ago.
The problem might be caused by manipulating a stale pointer to an R object
(that is an object that was discarded during R's garbage collection),
and troubleshooting this will likely mean running things through a C debu
I think I am seeing pretty much exactly the same issue, as I reported in
another post. In my case I am doing the looping in python, creating a
dataframe from a python dictionary with r.as_data_frame, calling r.lm and
extracting the results from r.summary. The only work-around i have sofar is
to spa
I am using rpy/R to perform linear regressions on a large number of
datasets, in one python run, and am encountering segmentation faults after a
large number of iteration, while handling cases which, taken on their own
run without a problem. My intuition is that the previous iterations somehow
corr
Thanks for posting it.
I am not a C stack expert, but I suspect that there is a reason why it is not
unlimited by default. I would particularly consider putting somehow a limit
to it on a webserver, although that limit would naturally be larger than the
default one. It would be nice come up with s
Revision: 578
http://rpy.svn.sourceforge.net/rpy/?rev=578&view=rev
Author: lgautier
Date: 2008-07-14 08:21:49 -0700 (Mon, 14 Jul 2008)
Log Message:
---
rlike:
- new package
- in which there is a module 'container'
- in which there is a class 'NamedList'
doc:
- mi
11 matches
Mail list logo