On Tue, 9 Mar 2004 [EMAIL PROTECTED] wrote:
> The documentation of read.table could be a bit clearer if
> the explanation of the argument nrows makes clear that eventual
> header line(s) are not included.
Why would they be? The `rows' are of the data frame, just as in
`row.names'.
Do you want
A package of 1.8.1 should not have a package stats. If this is 1.9.0, you
should be using VR_7.2-0 or later.
Someone is confused about version numbers.
On Wed, 10 Mar 2004, Robert King wrote:
> (I'm guessing the same problem) is also present in 7.1.14-2 of the debian
> package r-cran-vr with
On Wed, Mar 10, 2004 at 12:55:40PM +1100, Robert King wrote:
> (I'm guessing the same problem) is also present in 7.1.14-2 of the debian
> package r-cran-vr with r-base-core 1.8.1.cvs.20040229-2
> it can be fixed with
>
> /usr/lib/R/library/MASS:
>
> tolstoy:/usr/lib/R/library/MASS# diff -u NAMES
On Tue, Mar 09, 2004 at 08:02:10PM -0600, Dirk Eddelbuettel wrote:
> On Wed, Mar 10, 2004 at 12:55:40PM +1100, Robert King wrote:
> > (I'm guessing the same problem) is also present in 7.1.14-2 of the debian
> > package r-cran-vr with r-base-core 1.8.1.cvs.20040229-2
> > it can be fixed with
> >
>
(I'm guessing the same problem) is also present in 7.1.14-2 of the debian
package r-cran-vr with r-base-core 1.8.1.cvs.20040229-2
it can be fixed with
/usr/lib/R/library/MASS:
tolstoy:/usr/lib/R/library/MASS# diff -u NAMESPACE~ NAMESPACE
--- NAMESPACE~ Wed Mar 10 12:42:26 2004
+++ NAMESPACE We
The documentation of read.table could be a bit clearer if
the explanation of the argument nrows makes clear that eventual
header line(s) are not included.
Kjetil Halvorsen
__
[EMAIL PROTECTED] mailing list
https://www.stat.math.ethz.ch/mailman/listinf
On Wednesday 03 March 2004 04:08, Wolfram Fischer wrote:
> PROBLEM
> # Allocating strip labels by the function strip.fun():
>
> strip.test()
> # Result: No strips: ok. No strings: NOT OK.
> # The distance ``y.text=unit(6,"points")'' is ignored;
> # the strings ar
`Ripley' has already corrected the R sources: from NEWS
o chisq.test(simulate.p.value = TRUE) was returning slightly
incorrect p values, notably p = 0 when the data gave the most
extreme value.
Note that all the p values were incorrect as one needs to be added to both
numer
the help file (?arima) says $residuals is the standardized residuals and
they are not.
it actually delivers raw residuals.
best wishes
--
Stoyan Iliev
PhD Candidate in Finance
Queen's University
__
[EMAIL PROTECTED] mailing list
https://www.stat.math.et
This is a message for whoever maintains "chisq.test": For an
outcome more extreme than 2000 simulations, a Monte Carlo p-value of "<
2.2e-16" was printed. Ripley said the proper p-value for such cases
should be 1/(B+1) = 1/2001. This can be easily fixed by adding
"if(PVAL==0)PVAL <- 1/(
Hi,
[ Re: Re: Your website ]
I have received your email, but it may take a while to respond. I'm really
sorry to have to hook up this auto-responder, as it is so impersonal.
However, I get a lot of email every day and find it very difficult to keep
up with it. Please be patient while I try to g
11 matches
Mail list logo