search for: summarydefault

On 28 May 2017 at 17:37, Arne Henningsen wrote: | Dear all | | I am happy that summary.default() no longer rounds since R 3.4.0. | | However, in R 3.4.0, in a few cases, print.summaryDefault() rounds the | mean value (and the median value) differently on my GNU/Linux machine | and on my colleague's MS-Windows machine. Here is a small (simplified) | reproducible example: | | R> a <- 1234568.01 + c(0:1) | R> summary(a) | | Output on MS-Windows (expected rounding of the mea...

Dear all I am happy that summary.default() no longer rounds since R 3.4.0. However, in R 3.4.0, in a few cases, print.summaryDefault() rounds the mean value (and the median value) differently on my GNU/Linux machine and on my colleague's MS-Windows machine. Here is a small (simplified) reproducible example: R> a <- 1234568.01 + c(0:1) R> summary(a) Output on MS-Windows (expected rounding of the mean value): Min...

...t; On Sun, May 28, 2017 at 5:51 PM, Dirk Eddelbuettel <edd at debian.org> wrote: > > On 28 May 2017 at 17:37, Arne Henningsen wrote: > | Dear all > | > | I am happy that summary.default() no longer rounds since R 3.4.0. > | > | However, in R 3.4.0, in a few cases, print.summaryDefault() rounds the > | mean value (and the median value) differently on my GNU/Linux machine > | and on my colleague's MS-Windows machine. Here is a small (simplified) > | reproducible example: > | > | R> a <- 1234568.01 + c(0:1) > | R> summary(a) > | > | Output on MS...

...o run pvals.fnc in the newest version of R (2.13.0). The function lmer worked fine, but when I tried to use pvals.fnc on the lmer object, I got the following error: "Error in pvals.fnc(elogr.subj.dys.sum.3x3.p, nsim = 10000) : trying to get slot "coefs" from an object (class "summaryDefault") that is not an S4 object." How can I fix this problem? Thanks in advance for your help. -- Amy DiBattista Ph.D. Candidate Department of Psychology Northeastern University (617) 373-3077 dibattista.a@husky.neu.edu [[alternative HTML version deleted]]

...e, where the NA's are not printed, 'nr' is 6, rather than 7. 6 is correct, since that is the actual length of the result vector from summary.Date(), even though the printed output of the result, would appear to contain 7 elements, including the NA count, because of the behavior of print.summaryDefault(). This results in an apparent truncation of the result, with a loss of the "NAs" attribute from summary.Date(), when the result is returned by summary.data.frame(). If the source vector is numeric, as per my example above, then 'nr' is set to 7 when NA's are present and the...

...sses the routine parts of R CMD check. The following test shows that, with lme4 loaded, coef(summary([object of class "mer"])) works in the global environment, but not in a function defined inside the namespace of the package. The output ends with: > coeftab.default(gm1) [1] "summaryDefault" "table" Error in object$coefficients : $ operator is invalid for atomic vectors Calls: coeftab.default -> coef -> coef -> coef.default which indicates that inside the function, summary() is calling summary.default instead of seeing the summary method for "mer"...

...object), qq[ 4L:5L]), digits = digits) names( qq) <- c( "Min.", "1st Qu.", "Median", "Mean", "3rd Qu.", "Max.") v <- if( any( nas)) c( qq, NAs = sum( nas)) else qq class( v) <- c("summaryDefault", "table") v } I get the following (look at the number of NA's): > my.summary( c( 1:2, NA)) Min. 1st Qu. Median Mean 3rd Qu. Max. NAs 1.00 1.25 1.50 1.50 1.75 2.00 1.00 Could somebody please point me to what I'm overlooking?...

...mmary(model)) inside a function to do that. Model is the output of a call to glmer() from the lme4.0 package. coef(summary(model)) throws an error: $ operator is invalid for atomic vectors I have tracked it down to a problem with summary(model) because str(summary(model)) gives this Classes 'summaryDefault', 'table' Named chr [1:3] "1" "mer" "S4" ..- attr(*, "names")= chr [1:3] "Length" "Class" "Mode" But it should return Formal class 'summary.mer' [package "lme4.0"] with 42 slots ..@ methTitle:...

I think what's been missed is that zapsmall works relative to the absolute largest value in the vector. Hence if there's only one item in the vector, it is the largest, so its not zapped. The function's raison d'etre isn't to replace absolutely small values, but small values relative to the largest. Hence a vector of similar tiny values doesn't get zapped. Maybe the line

...ystems with sub-architectures. ? installed.packages() has a new argument subarch to filter on sub-architecture. ? The summary() method for packageStatus() now has a separate print() method. ? The default summary() method returns an object inheriting from class "summaryDefault" which has a separate print() method that calls zapsmall() for numeric/complex values. ? The startup message now includes the platform and if used, sub-architecture: this is useful where different (sub-)architectures run on the same OS. ? The getGraphicsEvent() mech...

...ystems with sub-architectures. ? installed.packages() has a new argument subarch to filter on sub-architecture. ? The summary() method for packageStatus() now has a separate print() method. ? The default summary() method returns an object inheriting from class "summaryDefault" which has a separate print() method that calls zapsmall() for numeric/complex values. ? The startup message now includes the platform and if used, sub-architecture: this is useful where different (sub-)architectures run on the same OS. ? The getGraphicsEvent() mech...