Displaying 20 results from an estimated 3000 matches similar to: "fisher.test FEXACT memory bug "should not occur" (PR#1662)"
2002 Jun 13
0
possum sleeping: thanks and fisher.test() FEXACT error
Dear helplist
Many many thanks to everyone who helped me. The trick was to use
tabulate() or, better,
tab <- rep(0,50)
names(tab) <- 1:50
tab[names(table(sleeps))] <- table(c)
My original dataset was a list of 50 trees and a length 12 vector
recording which tree a certain possum slept in on 12 nights. As
Professor Ripley points out, a Monte-Carlo simulation is easy to set
up, and it
2008 Apr 28
1
problem with fisher.test
I posted this last night but I think I figured out the problem.
I checked on the underlying equation for the Fisher Exact Test for tables
greater than 2X2. It looks like I have an insane amount of factorials to be
multiplied.
Is that problem? Is it an overflow issue?
Jeff
Last night’s post:
I just a ran a fisher.test on a 9x5 table and received the following message
2004 Jul 23
2
fisher.test FEXACT error 7
Hello,
I have an error message that doesn't seem to make sense in that having
read the R documentation I was under the impression that R was able to
grab as much memory as it needed, and has been able to do so for some
time, so the advice given below about increasing the size of the
workspace is redundant.
If I'm right, does anyone have a solution to the problem of the size of
2009 Mar 20
1
fisher.test - FEXACT error 7
Dear all,
I’m having an awkward problem in R. When I write the command
Fisher.test(school.data,workspace=2e+07), where school.data is the matrix
corresponding to the data set,
I get the error message:
FEXACT error 7.
LDSTP is too small for this problem.
Try increasing the size of the workspace.
Increasing the workspace:
Fisher.test(school.data,workspace=1e+10),
I
2002 Jun 13
1
bad fisher.test() bug (PR#1662)
(CC'ed to R-bugs ``for the record'')
>>>>> "BDR" == Prof Brian D Ripley <ripley@stats.ox.ac.uk> writes:
BDR> On Thu, 13 Jun 2002, Martin Maechler wrote:
>> >>>>> "MM" == Martin Maechler
>> <maechler@stat.math.ethz.ch> writes:
>>
>> >>>>> "BDR" ==
2012 Mar 16
1
Segfault while calling fexact in C
Hi folks,
I'm trying to call an R function (fisher.test) in my program for like a
billion times! Though my program is in Python and I feel that using rpy2 to
interface R to python doesn't give me satisfactory performance. So I looked
into R code and found out that fisher.test is actually a wrapper around
another function called fexact which is implemented in C. Using Cython I
managed to
2002 Nov 19
1
fexact.c
Dear All,
I am using fexact.c on a C++ program I wrote. To minimize dependencies on
other files (e.g., to not need to include R.h and ctest.h ---now I only
include the R files Boolean.h, Constants.h, and Memory.h), I have re-written
all declarations of Sints as ints and, what is potentially more serious, I
have re-written the line (lines 329 and 330, in fexact.c on R-1.6.1)
/* IMAX is the
2004 Jun 17
1
Bug in FEXACT: gave negative key (PR#6986)
Hello,
I'm using R to apply Fishers exact test to a whole pile of
contingency tables, and I've run into the bug shown below.
regards,
Francis
--
> dat1 = matrix(c(0,1,0,1,0,0,1,0,0,0,1,0,1,0,0,1,0,0,0,1,0,1,0,0,1,0,0,0,0,
1,1,0,0,1,0,0,1,0,0,1,0,0,3,0,0,2,0,0,1,0,0,0,1,0,0,2,0,0,
2,0,0,1,0,1,0,0,3,0,0,2,0,0,0,1,0,5,0,0,0,1,0,1,0,0), nrow=3)
>
2008 Jul 08
1
fisher.test
Hi!
I am Marta Colombo, student in Mathematical Engineering at "Politecnico di Milano". For my master degree thesis I have to analyze some categorical data. My dataset is composed by 327 individuals and 16 variables. I am using Fisher exact test to test independence on IxJ contingency tables, but I have a problem with one variable.
R gives me this error message:
FEXACT error 7.
2000 Dec 22
5
(HP-UX) scan: last line gets duplicated (PR#790)
The last line gets duplicated when a file is read like this:
a <- scan(file=filename, what="", sep="\n",
strip.white=c(TRUE), quiet=TRUE)
(This error does not occur on Linux, the only other platform I
tested.)
Version:
platform = hppa2.0-hp-hpux10.20
arch = hppa2.0
os = hpux10.20
system = hppa2.0, hpux10.20
Actually, all binaries are
2004 Mar 10
1
Re: R-help Digest, Vol 13, Issue 9
C?dric Finet wrote:
>
> I thank you for your answer but I do not understand yet why the Fisher?s exact
> test does not work. And why is a "negative key".
>
> C?dric Finet
>
Running the original TOMS643 fortran code (R uses an f2c translation of
this) says:
FEXACT ERROR: 30
Stack length exceeded in f3xact. This problem should not occur.
The integer hash key is
2002 Jun 12
4
table problems
dear helplist,
my student has fifty trees, numbered one to fifty, and a vector
recording which tree a certain possum slept in on 12 nights.
R> c
[1] 3 14 17 22 26 26 17 40 43 25 46 46
R>
Thus it slept in tree #3 on Monday, then tree #14 on Tues, and so on.
I wish to test the null hypothesis that the animal chooses trees
randomly; try
R> table(c)
c
3 14 17 22 25 26 40 43 46
1 1
2006 Nov 13
1
hybrid in fisher.test broken?
The hybrid feature in fisher.test looks to me like an excellent way to
analyze my two-way tables. The only problem is that it does not seem
to be implemented. Am I right about this?
An example is pasted below. I note that I get the warning message only
when I shouldn't: for a 2x2 table hybrid seems to be ignored without
warning. In no case does fisher.test seem to be checking Cochran
2007 Nov 09
1
fisher.test, chisq.test
Hi,
I want to analyse a contigency table (3 x 12) with a fisher.test
beacause there are cells that are less than 5.
?mmen Anken Baf Belchen H?chi Hof Porti R?m Schmutz Sch?n Sissa Tann
class14 7 26 150 2 46 68 126 66 3 31 7 61
class24 7 6 55 5 49 71 93 90 1 18 16 79
class34 1 1 4 3 19 8 29 61
2008 Apr 28
0
problem in fisher.test
I just a ran a fisher.test on a 9x5 table and received the following message
Error in fisher.test(apaslg.t) : FEXACT error 30.
Stack length exceeded in f3xact.
This problem should not occur.
I agree. The problem should not occur.
I did some searching but only found other reports of the problem.
Does anyone know of a fix?
Jeff
Internal Virus Database is out-of-date.
2006 Jan 12
2
Basis of fisher.test
I want to ascertain the basis of the table ranking,
i.e. the meaning of "extreme", in Fisher's Exact Test
as implemented in 'fisher.test', when applied to RxC
tables which are larger than 2x2.
One can summarise a strategy for the test as
1) For each table compatible with the margins
of the observed table, compute the probability
of this table conditional on the
2002 Jul 01
1
functions of dataframes
Hello experts
I have a thing which I can't vectorize. Can any gurus out there help?
This is my truncated dataset; it is a dataframe of five possums and
which tree they slept in on three days.
R> dataset
p14 p88 p82 p90 p98
1 6 7 5 1 3
2 8 9 10 1 11
3 8 7 12 13 14
I can manipulate it with simple functions fine:
R> f
function(n){n+1000}
R> f(dataset)
2000 Mar 29
5
Porting R
I am trying to get R 1.0 running on the Mac.
The main target is MacX. Anyone else working on that?
For the recent Macintosh system, I am trying to compile R using MachTen.
The R core compiles and runs without any changes, using the Unix make files.
The libraries give some problems, presumably due to handling of shared
libraries. It seems I am missing something to link. Before I spend my time
2006 Mar 25
1
Suggest patch for princomp.formula and prcomp.formula
Dear all,
perhaps I am using princomp.formula and prcomp.formula in a way that
is not documented to work, but then the documentation just says:
formula: a formula with no response variable.
Thus, to avoid a lot of typing, it would be nice if one could use '.'
and '-' in the formula, e.g.
> library(DAAG)
> res <- prcomp(~ . - case - site - Pop - sex, possum)
2003 Mar 17
2
scoping rules; summary
Hi everyone
thanks for the replies.
The issue was NOT a font problem; I deliberately chose ll1 and l11 as
examples of easily confused variable names (evidently these were too
easily confused ;-). The code snippet was written as intended, and
increment() contained a deliberate, highlighted, bug. I was asking
for guidance on avoiding/finding this sort of coding error.
That was why I wrote