similar to: Help Documentation (PR#6716)

Ivo, Let me address your points in reverse order: 1. There is a `wishlist' category for bug reports, which I guess you've overlooked. 2. There is also a `Contributed Documentation' section on the R web site, which you can submit your contribution. As well, there are a few introductory level documents there already that you might be interested. 3. I must repectfully disagree about

Dear all,=20 without taking sides here, I see two major advantage of keeping the redundancy in any documentation minimal. First, it makes the maintanance of the documentation as simple as possible. This in turn, minimizes the risk for getting inconsistent documentation in new updates. Otherwise, someone has to have a really good overview and know where to update when, say, one default argument is

I think many people share your view and are aghast at the reception that some well-intentioned posts receive. There have been past discussions on this and many people feel the way you and I do. Just to head off another round, let me acknowledge that there appears to be multiple viewpoints and although hard to believe by myself, there actually is a contingent that views what I see as

I think many people share your view and are aghast at the reception that some well-intentioned posts receive. There have been past discussions on this and many people feel the way you and I do. Just to head off another round, let me acknowledge that there appears to be multiple viewpoints and although hard to believe by myself, there actually is a contingent that views what I see as

For the question at the end, try barplot with the horiz=TRUE argument. Date: Tue, 24 Feb 2004 09:30:21 -0500 From: ivo welch <ivo.welch at yale.edu> To: <r-help at stat.math.ethz.ch> Cc: <r-help-owner at stat.math.ethz.ch>,ivo welch <ivo.welch at yale.edu> Subject: [R] Suggestions ?!?! hi chaps: * I have some suggestion, the first of which is about

ladies and gents: I have posted a couple of simple questions recently. As often happens to novices, the information was there somewhere, even in front of my eyes, and I just did not see it. I looked in docs that seemed to me to be the right place for this particular information, but did not find it. There is no question: mea culpa, and everything is documented somewhere in R. (Worst

On 28 Mar 2004 at 16:52, ivo welch wrote: > > ladies and gents: > > I have posted a couple of simple questions recently. As often happens . . . > I was told by Brian to stop sending such suggestions, in order not to > clutter the R bug report list. OK, I can save my time; I just wanted He told you stop sending them to R-bugs! When you get a little more experience, send them

Full_Name: ivo welch Version: 1.8.1 OS: linux Submission from: (NULL) (130.132.33.212) please define aliases for the 5 essential data set operations delete row insert row delete column insert column rename column these are too difficult for novices as-is now, and the cost for doing this for you would be very low. if need be, define hints only, such as dataset.del.row() <-

dear R experts---I have been experimenting with the foreach package (with doMC) for a while. my first impression is that it is a very easy way to acquire parallel processing capabilities. (thanks, revolution R.) the only two gotchas were about installation (it required an exit and restart), and the precedence order of the foreach (higher than '+', I think), but once I understood this,

dear R wizards: an operation I execute often is the deletion of all observations (in a matrix or data set) that have at least one NA. (I now need this operation for kde2d, because its internal quantile call complains; could this be considered a buglet?) usually, my data sets are small enough for speed not to matter, and there I do not care whether my method is pretty inefficient (ok, I

Dear R developers: R is supposed to be slow for iterative calculations. actually, it isn't. matrix operations are fast. it is data frame operations that are slow. R <- 1000 C <- 1000 example <- function(m) { cat("rows: "); cat(system.time( for (r in 1:R) m[r,20] <- sqrt(abs(m[r,20])) + rnorm(1) ), "\n") cat("columns: "); cat(system.time(for (c

dear wizards: FYI: gentoo is a linux meta distribution, which compiles all packages. Once running, gentoo is stable on most applications. (it has some problems with system tools, such as grub.) the compiler is gcc 3.3.3. I do not expect anyone to track down for me why R fails on the gentoo amd64+gcc3.3.3 system, but I thought that it would be good to put it on the record to save

dear wizards: FYI: gentoo is a linux meta distribution, which compiles all packages. Once running, gentoo is stable on most applications. (it has some problems with system tools, such as grub.) the compiler is gcc 3.3.3. I do not expect anyone to track down for me why R fails on the gentoo amd64+gcc3.3.3 system, but I thought that it would be good to put it on the record to save

Full_Name: ivo welch Version: any OS: linux Submission from: (NULL) (130.132.33.212) hi: in "?stop", in "See Also", please add "quit()" as a mention. Similarly, I would create a help for ?exit, which simply states that "you are probably looking for quit() or stop()". regards, /ivo

Avi, Yes, R (really S) was not designed for novice users but rather for experts. For better or worse it has evolved into a programming language used by tyros, and experts. Debugging tools should be easy to use, generally known, and helpful for tyro and expert. It would certainly help if R reported the line number, or the code, that generated the error. John John David Sorkin M.D., Ph.D.

I ran into an interesting oddity of R, if (0) { print(1); } else { print(2); } is a syntax error, while if (0) { print(1); } else { print(2); } or if (0) { print(1); } else { print(2); } is not. I presume it has to do with the duality of the newline functioning as an end of command (;) character, though it still seems a bit odd, and it took me a while to figure out

SAS * better manuals. * tech support for most universities contracted into the price, thus for researchers. * batch orientation. if you have to handle data sets that are as large as your memory, SAS generally does it better. It seems to be an "n-pass design." Years ago, when memory was expensive, I could not use S/R even for simple problems. Just a few simple operations, and I

for the googleable r-help archives, I thought I would post what I wrote into my .Rprofile to automatically set some system information. the most relevant aspect is the determination of mc.cores. this is useful when users want to use the parallel package options(uname= system("uname", intern=TRUE)) options(os= if (getOption("uname")=="Darwin") "osx"

Arguably, R was not designed or evolved for truly novice users, nor really was Python or just about all computer languages. As they evolved and became in many ways more powerful, they tended to get ever less user friendly in the way you are asking for and gotten so bloated that many features are not familiar even to expert users. Compiled languages can have ways to keep track of what LINE of code

I sent this privately to ivo welch yesterday, and he thinks it might be useful to someone else as well. Since I'm on a Mac the screen device is quartz(): > quartz() > plot( c(0,1), c(0,1) ); > text( 0.5, 0.5, "\u2113" ) # and then File/Save As/ -- David. Begin forwarded message: > From: David Winsemius <dwinsemius at comcast.net> > Date: August 17,