On 27/12/2017 9:11 AM, Sun Yijiang wrote:
Thanks for the details. I’m new to R, and I’m not blaming anything here,
just that I’m still not clear what good it makes to keep this inconsistency
between R and Rscript. To me (and probably to many others from Perl/Python
etc.), this is shockingly weird
The chisq.test on line 57 contains following code:
STATISTIC <- sum(sort((x - E)^2/E, decreasing = TRUE))
However, based on book "Accuracy and stability of numerical algorithms"
available from:
http://ftp.demec.ufpr.br/CFD/bibliografia/Higham_2002_Accuracy%20and%20Stability%20of%
Thanks for the details. I’m new to R, and I’m not blaming anything here,
just that I’m still not clear what good it makes to keep this inconsistency
between R and Rscript. To me (and probably to many others from Perl/Python
etc.), this is shockingly weird. I can live with that, and I also want to
k
Duncan,
Very nice tutorial. However it does NOT take away from the fact that _very_
simple_ scripts (like the one posted by Sun at the beginning of this thread)
simply _fail_ in error under Rscript.
Whereas they don't under R or r.
The R environment ships an interpreter meant for command-line a
On 26/12/2017 9:40 AM, Dirk Eddelbuettel wrote:
On 26 December 2017 at 22:14, Sun Yijiang wrote:
| Thanks for the solution. Now I know the work-arounds, but still don't
| quite get it. Why does R_DEFAULT_PACKAGES has anything to do with
| library(methods)?
Because it governs which packages are
