similar to: Irregularity in stem() display (PR#8934)

Displaying 20 results from an estimated 1000 matches similar to: "Irregularity in stem() display (PR#8934)"

2006 Jun 04
4
xy.coords(MATRIX) bug in code or documentation (PR#8937)
Hi, people. xy.coords() does not behave like its documentation says, when given some matrices. ?xy.coords says: If 'y' is 'NULL' and 'x' is a [...] formula [...] list [...] time series [...] matrix with two columns [...] In any other case, the 'x' argument is coerced to a vector and returned as *y* component [...] Now, consider this short
2006 May 15
2
Truncated labels in hist (PR#8864)
Hi, people. Executing the following command: hist(rpois(100,5), labels=TRUE) yields a graphic in which some labels are truncated (on an X11 device). The truncated labels are those over the highest bars. The hist function should ideally manage enough room for the labels, automatically. (Specifying ylim solves my problem, but yet, hist could be frienlier.) --please do not edit the
2007 Aug 27
1
R 2.5.1 - Rscript through tee
Hi, people. I met a little problem for which someone might have a solution. Let's say I have an executable file (named "pp.R") with this contents: #!/usr/bin/Rscript options(echo=TRUE) a <- 1 Sys.sleep(3) a <- 2 If I execute "./pp.R" at the shell prompt, the output shows the timely progress of the script as expected. If I use "./pp.R | tee
2006 May 27
0
Correction to ?alist (PR#8904)
Hi, people. ?alist says: 'alist' is like 'list', except in the handling of tagged arguments with no value. As written, this description is misleading. For example: > list(e=3+5) $e [1] 8 > alist(e=3+5) $e 3 + 5 We are not in the situation of tagged arguments with no value, and then, clearly, 'list' and 'alist' behave
2006 Feb 01
1
Difficulty with qqline in logarithmic context
Hi, R friends. I had some difficulty with the following code: qqnorm(freq, log='y') qqline(freq) as the line drawn was seemingly random. The exact data I used appears below. After wandering a bit within the source code for "abline", I figured out I should rather write: qqnorm(freq, log='y') par(ylog=FALSE) qqline(log10(freq)) par(ylog=TRUE)
2006 Mar 28
1
Error once having applied (PR#8718)
Hi, people. Here is a transcript of a "R --vanilla" session: ======================================================================> R : Copyright 2005, The R Foundation for Statistical Computing Version 2.2.1 (2005-12-20 r36812) ISBN 3-900051-07-0 R est un logiciel libre livr?? sans AUCUNE GARANTIE. Vous pouvez le redistribuer sous certaines conditions. Tapez 'license()'
2006 Sep 28
1
unable to load lapack.so
Hi, I'm having problems using ACML with R. I made two changes in config.site by setting LDFLAGS="-L/opt/acml3.1.0/gnu64/lib" BLAS_LIBS="-lacml" ./config and make go through but when I try to use the lm() function, I get the error message Error in chol2inv(Qr$qr[p1, p1, drop = FALSE]) : lapack routines cannot be loaded In addition: Warning message: unable to load
2005 Apr 09
1
R-generated animation of a polynomiograph
Hi, people. Two days ago, I sent to this list a little toy for exploring polynomiographs (yet, the mathematical formulas were not polynomials anymore, so the name is not really appropriate). After studying R calls, expressions and functions a bit more, I gave myself the homework of producing an animation out of my recent toy. The resulting animation, and also the sources, are available at:
2006 Feb 23
1
Tiny documentation error for ?options (PR#8633)
Hi, people. The output produced by "?options" contains: 'expressions': sets a limit on the number of nested expressions that will be evaluated. Valid values are 25...500000 with default 1000. [...] and a bit further down: The 'factory-fresh' default settings of some of these options are [...] 'expressions'
2006 Feb 22
1
Spurious output white line in R script (PR#8631)
I noticed that R scripts produce a spurious white line after output. For example, the following shell script, #!/bin/sh R --slave --vanilla <<EOF cat("Hello\n") EOF when made executable under the name ``hello`` along the search path, behaves like this: $ hello | od -bc 0000000 110 145 154 154 157 012 012 H e l l o \n \n 0000007 The second newline is
2005 Apr 01
1
R mailing list archive difficulty
Hi, people! This is my first babble on this list, please be kind! :-) Last Tuesday, I wrote to the (likely) Webmaster of the R site to report a little problem, but also to ask for advice about how to get a bulk copy of the mailing list archives, from 2002 to now. While I quite understand that from Tuesday to now, there has been little time, and it is only normal that I did not receive a reply
2007 Aug 29
1
Excel (off-topic, sort of)
Except for the ability to perform circular recalculation, I believe that the closest programming analogy to a spreadsheet is a functional programming language. Check out Haskell (or LISP or Erlang) to do what you describe. -----Original Message----- From: r-help-bounces at stat.math.ethz.ch [mailto:r-help-bounces at stat.math.ethz.ch] On Behalf Of Fran?ois Pinard Sent: Wednesday, August 29, 2007
2006 May 14
1
Suggestion for system.time()
Hi, people. A tiny suggestion for the system.time function. Could the returned vector have names? These could be like: c("User", "System", "Elapsed", "Sub.User", "Sub.System") That would then produce self-documenting output. -- Fran?ois Pinard http://pinard.progiciels-bpi.ca
2005 Apr 11
2
R_LIBS difficulty ?
Hi, R people. I'm shy reporting this, as a bug in this area sounds very unlikely. Did I make my tests wrongly? I'm still flaky at all this. Let me dare nevertheless, who knows, just in case... Please don't kill me! :-) Not so long ago, I wrote to this list: > (For now, [the library code] works only for me when I do _not_ use `-l > MY/OWN/LIBDIR' at `R CMD INSTALL'
2007 Jul 03
1
R 2.5.1 - ?factor examples, details
Hi, R people. In ?factor, in the "Examples:" section, we see: ## suppose you want "NA" as a level, and to allowing missing values. (x <- factor(c(1, 2, "NA"), exclude = "")) is.na(x)[2] <- TRUE x # [1] 1 <NA> NA, <NA> used because NA is a level. is.na(x) # [1] FALSE TRUE FALSE I'm a bit confused by this example, as I
2006 May 09
1
"Unfelicity" :-) with edit()
Hi, people. This is about R 2.3.0 under Linux. It seems that edit() may change a function environment. Here is a transcript, more comments follow: ======================================================================> > fix(f) > f function () { } > fix(f) Erreur dans edit(name, file, title, editor) : une erreur s'est produite ? la ligne 3 utilisez une commande du
2005 Nov 20
1
mapply() gives seg fault (PR#8332)
--KsGdsel6WgEHnImy Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Disposition: inline Content-Transfer-Encoding: 8bit Hi, people. Wandering in R archives, and seeing the message attached below, I noticed that: mapply(rep,times=1:4, MoreArgs=42) still segfaults on R 2.2.0, and thought I should be a good citizen and report it, even if I do not have an actual problem
2006 May 10
1
Mere chat on vectorisation matters
Hi, people. Allow me to chat a tiny bit on two vectorisation-related matters, in the context of R. I'm curious about if the following ideas have ever been considered, and rejected already. First is about using the so-called Duff's device for partially unrolling loops. I did not overly check in R sources, and am not familiar with them anyway, but the only usage I saw is within
2006 May 18
0
?hist and $density explanation
Hi, people. Within ?hist (using R 2.3.0), one reads: density: values f^(x[i]), as estimated density values. If 'all(diff(breaks) == 1)', they are the relative frequencies 'counts/n' and in general satisfy sum[i; f^(x[i]) (b[i+1]-b[i])] = 1, where b[i] = 'breaks[i]'. I trip on this explanation each time I read it. Some R guardians will be
2006 Jun 24
0
Documentation detail [was: Merging factor levels.]
Hi to R developers. In the "Details:" section of "?levels", it would be nice including the following sentence, taken from a reply from Brian Ripley: If you set two levels to be the same label, they get merged. Granted, the "Examples:" section does have a terse comment and examples from which users may imply this behaviour. Yet, the documentation would be