Hi,
This report deals with p-values coming from chisq.test using
the simulate.p=TRUE option. The issue is numerical accuracy
and was brought up in previous bug reports 3486 and 3896.
The bug was considered fixed but apparently was only mostly
fixed. Just the typical problem of two values that ar
Yes, only the middle matrix was problematic. Others were included to show
what the value should (approx) be. Sorry that I didn't mention I was
using 32 bit.
There are of course very easy fixes to this, just wasn't sure what was
the "best" approach in this situation (i.e. wasn't sure if the usu
Full_Name: Doug Grove
Version: 2.10.0 10-26-2009
OS: x86_64-unknown-linux-gnu
Submission from: (NULL) (140.107.164.65)
Hi,
Looks like the revisions to help.search didn't get completely finished.
When the user specifies the argument 'package' the code doesn't define the
variable 'paths' prior
Full_Name: Doug Grove
Version: 2.7.0-dev (Feb 28)
OS: Linux
Submission from: (NULL) (140.107.164.65)
In the par() help page, for component 'xaxs' it says:
"Style '"r"' (regular) first extends
the data range by 4 percent and then ..."
Not quite correct, should say that the data range is ex
Full_Name: Doug Grove
Version: 2.2.1
OS: SuSE 9.3 Linux
Submission from: (NULL) (140.107.156.61)
Could someone please alter the wording of the documentation of the 'xlim'
argument
in plot.default? It currently includes "(min,max)" which led me to think that
I couldn't use a specification like xl
Full_Name: Doug Grove
Version: 2.3.1 patched (2006-07-03 r38485)
OS: Windows
Submission from: (NULL) (24.19.37.159)
A msg. to R-help prompted me to read the help page for split.screen/screen,
etc.
I understand what the function is for, but could not find information that
described how the argume
