similar to: What does "4m[terminated]" mean?

Hi all, I want to install clang on CentOS 7. After executing "yum install clang", it outputs: [root at hp ~]# yum install clang Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile * base: centos.mia.host-engine.com * elrepo: elrepo.mirrors.arminco.com * extras: centos.arvixe.com * updates: centos.eecs.wsu.edu No package clang available. Error: Nothing to do

Le 08/06/2015 09:30, Nan Xiao a ?crit : > Hi all, > > I want to install clang on CentOS 7. After executing "yum install > clang", it outputs: > > [root at hp ~]# yum install clang > Loaded plugins: fastestmirror > Loading mirror speeds from cached hostfile > * base: centos.mia.host-engine.com > * elrepo: elrepo.mirrors.arminco.com > * extras:

Hello list, I have the following function which, as you can see, uses mean: meanratings <- round(apply(stack03[,c(102:121)],2,function(x) (tapply(x ,actcode, mean, na.rm=T))), digits=1) The above function yields the following output: q27a q27b q27c q27d q27e q27f q27g q27h q27i q27j q27k q27l q27m q27o q27p 1 7.8 8.1 7.7 7.9 7.9 NaN NaN 8.4 7.8 7.0 7.6 NaN NaN 7.1 6.0 2

From ?NA Numerical computations using ?NA? will normally result in ?NA?: a possible exception is where ?NaN? is also involved, in which case either might result. and ?NaN Computations involving ?NaN? will return ?NaN? or perhaps ?NA?: which of those two is not guaranteed and may depend on the R platform (since compilers may re-order computations).

On Fri, Mar 31, 2017 at 10:14 PM, Prof Brian Ripley <ripley at stats.ox.ac.uk> wrote: > From ?NA > > Numerical computations using ?NA? will normally result in ?NA?: a > possible exception is where ?NaN? is also involved, in which case > either might result. > > and ?NaN > > Computations involving ?NaN? will return ?NaN? or perhaps ?NA?: >

On Tue, Jul 3, 2018 at 10:12 AM, Jan Gorecki <j.gorecki at wit.edu.pl> wrote: > Thank you for interesting examples. > I would find useful to document this behavior also in `?mean`, while `+` > operator is also affected, the `sum` function is not. `sum` is "affected" on my system, if you mean: > sum(c(NA,NaN)) [1] NA > sum(c(NaN,NA)) [1] NaN oh, maybe you mean:

Thank you for interesting examples. I would find useful to document this behavior also in `?mean`, while `+` operator is also affected, the `sum` function is not. For mean, NA / NaN could be handled in loop in summary.c. I assume that performance penalty of fix is the reason why this inconsistency still exists. Jan On Mon, Jul 2, 2018 at 8:28 PM, Barry Rowlingson < b.rowlingson at

Yes, the performance overhead of fixing this at R level would be too large and it would complicate the code significantly. The result of binary operations involving NA and NaN is hardware dependent (the propagation of NaN payload) - on some hardware, it actually works the way we would like - NA is returned - but on some hardware you get NaN or sometimes NA and sometimes NaN. Also there are C

In R 3.3.3, I observe the following on Ubuntu 16.04 (when building from source as well as for the sudo apt r-base build): > x <- c(NA, NaN) > mean(x) [1] NA > mean(rev(x)) [1] NaN > rowMeans(matrix(x, nrow = 1, ncol = 2)) [1] NA > rowMeans(matrix(rev(x), nrow = 1, ncol = 2)) [1] NaN > .rowMeans(x, m = 1, n = 2) [1] NA > .rowMeans(rev(x), m = 1, n = 2) [1] NaN >

And for a starker example of this (documented) inconsistency, arithmetic addition is not commutative: > NA + NaN [1] NA > NaN + NA [1] NaN On Mon, Jul 2, 2018 at 5:32 PM, Duncan Murdoch <murdoch.duncan at gmail.com> wrote: > On 02/07/2018 11:25 AM, Jan Gorecki wrote: >> Hi, >> base::mean is not consistent in terms of handling NA/NaN. >> Mean should not

Hi, base::mean is not consistent in terms of handling NA/NaN. Mean should not depend on order of its arguments while currently it is. mean(c(NA, NaN)) #[1] NA mean(c(NaN, NA)) #[1] NaN I created issue so in case of no replies here status of it can be looked up at: https://bugs.r-project.org/bugzilla/show_bug.cgi?id=17441 Best, Jan [[alternative HTML version deleted]]

A bug has found its way into Openssh-1.2pre15. It has forced us to downgrade to pre14. Our test hosts are connected with regular Ethernet and by an internal VPN. With that in mind, any given host has two IP addresses. Starting with pre15 we get the fatal error message below every time we connect to the EXTERNAL ip address (eth0). For some reason, we continue to be able to connect to the INTERNAL

R-developers, In version R 2.11.0, weighted.mean was changed such that: > weighted.mean(NA, na.rm=TRUE) [1] 0 rather than NaN as in previous versions of R. I see a note in the NEWS file indicates that weighted.mean was changed "so an infinite value with zero weight does not force an NaN result." In case the side effect of returning 0 rather than NaN in this case was unintentional,

On 05/03/2015 14:55, Tade?? Palusga wrote: > Hi, > I'm using this mailing list for the first time and I hope this is the > right one. I don't think that the following is a bug but it can be a > performance issue. > > By my opinion, there is no need to filter by [w != 0] in last sum of > weighted.mean.default method defined in >

Dear R-help folks, I am seeing unexpected behaviour from the function mean with option na.rm =TRUE (which is removing a whole column of a data frame or matrix. example: testcase <- data.frame( x = 1:3, y = rep(NA,3)) mean(testcase[,1], na.rm=TRUE) [1] 2 mean(testcase[,2], na.rm = TRUE) [1] NaN OK, so far that seems sensible. Now I'd like to compute both means at once:

Hello, following functions doesnt work correct with my data: median(), geo.mean(). My datafiles contain more than 10.000 lines and six columns from a flow-cytometer-measurment. I need the arithmetic and geometric mean and median. For the calculation of the geometric mean i wrote following function: fix(geo.mean) function(x) { n<-length(x)

Hi, R people: I generated a package using package.skeleton(). But I can not load it using library(). > package.skeleton("RDIPcor", list = c("ROCAUC.i", "cor.i"), path = "/home/xiao") Creating directories ... Creating DESCRIPTION ... Creating READMEs ... Saving functions and data ... Making help files ... Done. Further steps are described in

I encountered an unexpected difference in the way that mean and var work: > mean(numeric(0)) [1] NaN > var(numeric(0)) Error in var(numeric(0)) : `x' is empty Looking into this, I discovered in mean.default that sum(x)/n evaluates as > sum(numeric(0))/length(numeric(0)) [1] NaN The function var calls an .Internal and seems to evaluate this: >

Hi R users, I am trying to use the optim function to maximize a likelihood funciton, and I got the following warning messages. Could anyone explain to me what messege 31 means exactly? Is it a cause for concern? Since the value of convergence turns out to be zero, it means that the converging is successful, right? So can I assume that the parameter estimates generated thereafter are reliable MLE

Full_Name: Rich Calaway Version: 2.9.2 OS: Windows Vista Submission from: (NULL) (65.47.30.18) Consider the following function: myfun <- function(){ print(log(-1)) browser() print("Good-bye!") } In the default case, with options(warn=0), if I call this function and type nothing but standard browser commands (c, n, where, Q) at the browser prompt, the warning produced by log(-1)