similar to: fisher.test negative value error

? stato filtrato un testo allegato il cui set di caratteri non era indicato... Nome: non disponibile URL: <https://stat.ethz.ch/pipermail/r-help/attachments/20130501/294047df/attachment.pl>

Dear list, When calling R from C, what appears like a spurious error can be triggered during the execution of chisq.test(x, y). This is happening when the following conditions are met: - x and y are "anonymous" C-level R vectors (they do not have a symbol), but they are protected from garbage collection - x and y are "not too small" (it was experienced as soon as they are

Hi This is my function. It serves an HTML page after the calculations. I'm connecting to a MSSQL DB using pyodbc. def CAPM(self,client): r=self.r cds="1590" bm="20559" d1 = [] v1 = [] v2 = [] print"Parsing GET Params" params=client.g[1].split("&") for items in

Dear list, there seems to be a problem with the standard location of R?s 64-bit libs at least under openSUSE. I had two user questions regarding the compilation of rpy2 for 64-bit systems. Personally I don`t know rpy2 but maybe someone on this list can decide if the mistake lies on R`s side or on rpy2?s side or in between. R-devel is installed in these cases, I asked. Latest R-base or

? stato filtrato un testo allegato il cui set di caratteri non era indicato... Nome: non disponibile URL: <https://stat.ethz.ch/pipermail/r-help/attachments/20100121/95fb8869/attachment.pl>

On 20 October 2010 at 09:57, Aman Thakral wrote: | Thanks for your reply. I just created a link to | /usr/local/lib/R/lib/libRlapack.so in /usr/local/lib. It works now. | I'm just curious, is this the "right" way to do it? Is there a better way? I am coming to this a little late but ... it is a band aid to a self-inflicted wound. You only have libRlapack because you built R

Beside the possible argumentation that with an API elegance and convenience might sometimes be superior to necessity, the suggested pattern ("every program, including R itself, keeping its own flag") does no work too well when the nested embedding of R is involved. A concrete example is: ``` $ R -q > library('rPython'); python.exec('import rpy2.robjects') R is already

rPython appears to provide an interface from R to Python by embedding Python and I'd think that it can safely assume that R has been initialized, but might not be the point here. The issue is that a Python package embedding itself R (here rpy2) appears to have no way to know that earlier in the life of the process R was initialized. 2015-05-03 19:48 GMT-04:00 Duncan Murdoch

Hi again. I'm putting together a little project with R, python, and a website. So I have an HTML file, a py file, an R file. Here is the HTML file: <form action="/cgi-bin/radio4.py" method="post" target="_blank"> <input type="radio" name="subject" value="Integrate" /> Integrate <input type="radio"

Hi While installing RPy2, I had curious problems which, if I traced them back correctly, have their root in the way that libR.so find the R installation directory. I wonder if this might be a subtle bug that only causes problems when one has several versions of R on one system but then can be very annoying and cause very strange behaviour. It seems to me that libR.so asks the Unix shell to

I am having a strange problem. I have been using python + rpy2 on my Mac for quite sometime now. I recently upgraded to OS X 10.8 from 10.6 and that's when the problem began. Now, when I try to load some R packages (like zoo) using robjects.r, python crashes with seg fault 11. Here's an example below: >> import rpy2.robjects as ro >> ro.r(''' library(zoo)

I am having a strange problem. I have been using python + rpy2 on my Mac for quite sometime now. I recently upgraded to OS X 10.8 from 10.6 and that's when the problem began. Now, when I try to load some R packages (like zoo) using robjects.r, python crashes with seg fault 11. Here's an example below: >> import rpy2.robjects as ro >> ro.r(''' library(zoo)

I am trying to create a pie chart using rpy2 of the following data Pathway Occurrences A 10% B 50% C 20% E 10% filename = './testing.png' grdevices = importr('grDevices') rdevices.png(file=filename, width=1200, height=800) dataf = Robjects.DataFrame({'pathways':Robjects.StrVector(Pathways),

In Python, it is literally this easy: import rpy2.robjects as robjects robjects.r(""" source("C:/ YOUR R FILE GOES HERE ") """) Type the name of your R source code into this script and save it as a Python script (add the suffix .py), and then you can run by double-clicking. If you want to see the results of your program, you'll have

Hi, There appear to be no way to check whether R has already been initialized. Could a function like "Rf_isinitialized" be added to the API ? Best, Laurent [[alternative HTML version deleted]]

Hi, In Rcpp, we now have a "Function" class to encapsulate functions (they cover all three kinds, but this may change). To call the function, what we do is generate a call with the function as the first node and then evaluate the call. SEXP stats = PROTECT( R_FindNamespace( mkString( "stats") ) ); SEXP rnorm = PROTECT( findVarInFrame( stats, install( "rnorm") ) )

Laurent, On May 3, 2015, at 8:07 PM, Laurent Gautier <lgautier at gmail.com> wrote: > rPython appears to provide an interface from R to Python by embedding > Python and I'd think that it can safely assume that R has been initialized, > but might not be the point here. > > The issue is that a Python package embedding itself R (here rpy2) appears > to have no way to

[Disclaimer: what is below reflects my understanding from reading the R source, others will correct where deemed necessary] On 1/2/10 12:00 PM, r-devel-request at r-project.org wrote: > > Hello, > > We are currently making lots of changes to Rcpp (see the open Rcpp > mailing list if interested [1] in the details). > > We are now using [2] R_PreserveObject and R_ReleaseObject

On 03/05/2015 7:02 PM, Laurent Gautier wrote: > Beside the possible argumentation that with an API elegance and > convenience might sometimes be superior to necessity, the suggested > pattern ("every program, including R itself, keeping its own flag") does > no work too well when the nested embedding of R is involved. > > A concrete example is: > ``` > $ R -q

Dear all, When running function 'testQAReport()', which uses function 'buildVignettes()' to create a pdf-file I get the following error: > source("testQAReport.R") > testQAReport() Error in .get_package_metadata(pkgdir) : Files 'DESCRIPTION' and 'DESCRIPTION.in' are missing. Since I did not get this error in earlier versions of R, could you