similar to: mean(trim=, c(NA,...), na.rm=FALSE) does not return NA

Calling parse(text=quote(name)) or text=as.name("name") makes parse() prompt for input from the command line and then it returns a parse of the initial characters of 'name' (depending on how many characters were typed at the prompt). E.g., > parse(text=quote(myName)) ?1/3 expression(myN) attr(,"srcfile") <text> >

In R versions 2.10.1 and "2.11.0 Under development (unstable) (2010-03-07 r51225)" on Windows I get the following if I type the commands at the start of the session. Note how the attribute attached to the name "Response" by the initial call to structure() seems to get tied to that name for the remainder of the session: > z <- structure(quote(Response),

Should both parts of a complex number be printed to the same precision? The imaginary part of 0 looks a bit odd when log10(real/imag) >=~ getOption("digits"), but I'm not sure it is awful. Some people might expect the same number of significant digits in the two parts. > 1e7+4i [1] 10000000+0i > 1e7+5i [1] 10000000+0i > 1e10 + 1000i [1] 1e+10+0e+00i >

TIBCO Software Inc. today launched TIBCO Spotfire 3.1, the latest version of its in-memory analytics platform, making predictive analytics based on R & S+ accessible within Spotfire's visual user experience. With this release, R & S+ users will be able to share and deploy their scripts through the Spotfire platform, making advanced analytics accessible to Business Analysts. While R

ANALYTICS CONSULTANT Hiring Manager: Michael O'Connell Location: East Coast US TIBCO is a rapidly growing software company with more than 3000 employees worldwide and approx. $900MM annual revenue in 2011. TIBCO provides a comprehensive software platform that allows customers to perform in-depth analysis on their data, while injecting predictive and complex statistics in the analysis. TIBCO

We are looking for two Analytics Consultants (PhD in Statistics with significant R programming skills preferred) to join our rapidly growing TIBCO Analytic Solutions team. The successful candidates will work closely with our TIBCO / Spotfire implementation and development teams to provide analytics expertise for customer pilots and implementations, methodology/training and product/code

DATA SCIENTIST Location: EU TIBCO is a rapidly growing software company with more than 3000 employees worldwide and more than$1B annual revenue in 2012. TIBCO provides a comprehensive software platform that allows customers to perform in-depth analysis on their data, while injecting predictive and complex statistics in the analysis. TIBCO Spotfire is an interactive, visual environment with

DATA SCIENTIST Hiring Manager: Michael O???Connell Location: US TIBCO is a rapidly growing software company with more than 3000 employees worldwide and more than$1B annual revenue in 2012. TIBCO provides a comprehensive software platform that allows customers to perform in-depth analysis on their data, while injecting predictive and complex statistics in the analysis. TIBCO Spotfire is an

DATA SCIENTIST Hiring Manager: Michael O'Connell Location: US TIBCO is a rapidly growing software company with more than 3000 employees worldwide and more than $1B annual revenue in 2012. TIBCO provides a comprehensive software platform that allows customers to perform in-depth analysis on their data, while injecting predictive and complex statistics in the analysis. TIBCO Spotfire is an

This is a great example how you cannot figure it out after spending two hours troubleshooting, but a few minutes after you post to R-devel, it's just jumps to you (is there a word for this other than "impatient"?); Let me answer my own question. The discrepancy between my sum2() code and the internal code for base::sum() is that the latter uses LDOUBLE = long double (on some system

TIBCO is a rapidly growing software company with more than 3000 employees worldwide and approx. $900MM annual revenue in 2011. TIBCO provides a comprehensive software platform that allows customers to perform in-depth analysis on their data, while injecting predictive and complex statistics in the analysis. TIBCO Spotfire is an interactive, visual environment with inbuilt S+ analytics and

With today's R 2.10.0(devel) I get: > anyDuplicated(c(1,NA,3,NA,5), incomp=NA) # expect 0 Warning: stack imbalance in 'anyDuplicated', 20 then 21 Warning: stack imbalance in '.Internal', 19 then 20 Warning: stack imbalance in '{', 17 then 18 [1] 0 > anyDuplicated(c(1,NA,3,NA,3), incomp=NA) # expect 5 Warning: stack imbalance in 'anyDuplicated', 20 then 21

We are looking for an Analytics Consultant to work closely with our TIBCO Spotfire account management and implementation teams as well as our development team to provide analytics expertise within a pre and post sales capacity, proof-of-concept, customer implementation, methodology development and code development to sharpen our current tool kit to name a few. This position will require some

The problem here is Table doesn't seem to have a way to weigh the data. > ToyData Data1 Data2 Data3 Weight 101 Sam Red Banana 1.1 102 Sam Green Banana 2.1 103 Sam Blue Orange 2.1 104 Fred Red Orange 2.1 105 Fred Green Guava 2.1 106 Fred Blue Guava 2.1 107 <NA> Red Pear 50.1 108 <NA> Green Pear 50.1 109 <NA> Blue

Dear Colleagues, I've been searching for a post or article or something which explains why having na.rm=FALSE or na.action=na.fail as the default is a better choice than TRUE or na.omit. I understand the basic argument: it does not make sense to average a nonexistance into an aggregate, and removing them implicitly leads to accidental pairwise deletion in some cases, and sum(x) /

(I see this in both R-patched r43124 and R-devel r43233.) In the Argument section of ?mean: trim the fraction (0 to 0.5) of observations to be trimmed from each end of x before the mean is computed. Values outside that range are taken as the nearest endpoint. Then in the Value section: If trim is non-zero, a symmetrically trimmed mean is computed with a fraction of trim observations

Hi All, Can anyone tell me why the length function does not use na.rm? I know how to work around it, I'm just curious to know why such a useful option was left out. I'm also interested in the logic of setting na.rm=TRUE as the default on mean, sd, etc. This is the opposite of the many other stat packages I have used, so I assume it provides some programming benefit that is not obvious to

In the past few years we have been working on making it possible to use packages in both R and Spotfire S+ (previously officially called S-PLUS). One problem was that certain lines in the DESCRIPTION file of a package needed to be specific to R or Spotfire S+. E.g., if your package used the xyplot() function then the package would depend upon lattice in R and trellis in Spotfire S+, or a package

The weighted.mean() function replaces NA values with 0.0 when the user specifies na.rm=TRUE: x <- c(101, 102, NA) mean(x, na.rm=TRUE) # 101.5, correct weighted.mean(x, na.rm=TRUE) # 67.66667, wrong weighted.mean(x, w=c(1,1,1), na.rm=TRUE) # 67.66667, wrong weighted.mean(x, w=c(1,1,1)/3, na.rm=TRUE) # 67.66667, wrong The weights are

On Linux when I compile R 2.10.0(devel) (src/main/arithmetic.c in particular) with gcc 3.4.5 using the flags -g -O2 I get noncommutative behavior when adding NA and NaN: > NA_real_ + NaN [1] NaN > NaN + NA_real_ [1] NA If I compile src/main/arithmetic.c without optimization (just -g) then both of those return NA. On Windows, using a precompiled R 2.8.1 from CRAN I get NA for