similar to: Fortune nomination

Folks: I thought John Nash's comment below was profound and a possible Fortunes candidate: (Aside: I believe it applies to a great deal of what is discussed on this list, not just stochastic optimization.) Cheers, Bert ... (in the context of stochastic optimization) >... As with many tools in this domain, for effective use they > require more knowledge than many of their users

Folks: I thought the following excerpt from Bruce McCullough's post would be a good candidate for the R fortunes package -- except that it's about Excel, not R! So I nominate it... but leave it to others to say whether it's really "qualified" to be nominated. ---- "The idea that the Excel solver "has a good reputation for being fast and accurate" does not

Please, I am receiving lot of e-mails that I do not want. Please could you delete my e-mail. Thank, Judit -----Original Message----- From: r-help-bounces at r-project.org [mailto:r-help-bounces at r-project.org] On Behalf Of Thomas Adams Sent: Monday, December 12, 2011 3:22 PM To: Bert Gunter Cc: r-help at r-project.org Subject: Re: [R] Boxplot of multiple vectors with different lengths Bert,

Folks: Suppose I wish to input a text file with variable length lines and possible whitespace as is and then parse the resulting character vector in R. Each line of text is terminated with "\n" (newline character). Is there any reason to prefer one or the other of: scan (filename, what ="a",sep ="\n") ##or readLines(filename) If it makes a difference, I'm on

I will repost on R-devel. -- Bert On Tue, Jul 17, 2012 at 10:32 AM, Prof Brian Ripley <ripley@stats.ox.ac.uk>wrote: > On 17/07/2012 18:20, Bert Gunter wrote: > >> Folks: >> >> sessionInfo() >> R version 2.15.0 (2012-03-30) >> Platform: i386-pc-mingw32/i386 (32-bit) >> >> locale: >> [1] LC_COLLATE=English_United States.1252 >> [2]

Hi Folks: I'm writing a little package that may not ever hit CRAN or even be distributed beyond a relatively narrow audience at my company. Nevertheless, I have tried to adhere to practices that would work if it were. With that in mind, I have read the Writing R Extensions Manual (and my humble kudos to its writers, as it has successfully guided even an ignoramus like myself ) and Luke

Folks: sessionInfo() R version 2.15.0 (2012-03-30) Platform: i386-pc-mingw32/i386 (32-bit) locale: [1] LC_COLLATE=English_United States.1252 [2] LC_CTYPE=English_United States.1252 [3] LC_MONETARY=English_United States.1252 [4] LC_NUMERIC=C [5] LC_TIME=English_United States.1252 attached base packages: [1] datasets splines grid tcltk stats graphics grDevices [8] utils

Below. -- Bert On Tue, Apr 3, 2012 at 1:47 PM, Danielle Duncan <dlduncan2 at alaska.edu> wrote: > Thanks for the response, I should have clarified that the NOEL is the > smallest dose above which there is a statistically significant effect. > This is not a scientifically meaningful nor defensible definition as it is stochastic, depends on the test used, design, level chosen, etc.

Folks: Herein is a suggestion for a little R convenience function mainly to obtain unevaluated ... function arguments. It arose from a query on R-help on how to get these arguments. The standard (I think) idiom to do this is via match.call(expand.dots=FALSE)$... However, Bill Dunlap pointed out that this repeats the argument matching of the function call and suggested a couple of alternatives

Hi Bert, I won't post any more messages on this thread as problem has shifted from Optimization in R to Graph Algorithms. Rest fine Khris. On Aug 2, 2012, at 9:13 PM, Bert Gunter [via R] wrote: > This discussion needs to be taken off (this) list, as it appears to > have nothing to do with R. > > -- Bert > > On Thu, Aug 2, 2012 at 2:27 AM, khris <[hidden email]>

This is a followup to a recent post on using atop() to obtain multiline expressions. My reading of the plotmath docs makes it clear that issuing (in base graphics) the specification par(cex = 2) doubles symbols and regular text in subsequent plotmath expressions. However, it is unclear to me what specifying cex _within_ the annotation function using plotmath should do, and the following seems

AdvisoRs: Is the following a bug, feature, hinky error message, or dumb Bert? > mtest <- matrix(1:12,nr=4) > dftest <- data.frame(mtest) > ix <- cbind(1:2,2:3) > mtest[ix] <- NA > mtest [,1] [,2] [,3] [1,] 1 NA 9 [2,] 2 6 NA [3,] 3 7 11 [4,] 4 8 12 ## But ... > dftest[ix] <- NA Error in `[<-.data.frame`(`*tmp*`, ix, value

WARNING: COMPLETELY OFF TOPIC -- Nothing to do with R. I thought readers of this list might enjoy the following. The link to the full article is at the bottom. I hope this is not "too" inappropriate. ------- Overconfidence in crime statistics doesn?t pay. In a new study, a team of criminologists makes the case that reported crime rates should acknowledge uncertainty in the data. The

Note the edited subject line! I don't know why I typed it as it was before. This says that as.numeric(as.character(f)) will work regardless of the implementation, and I agree. It's the recommendation to use as.numeric(levels(f))[f] that has me wondering about section 2.3.1 of the language definition. I expect that this idiom is in widespread use, and perhaps the language definition

... Well, this works in this simple case, but is too clumsy for a general formulation of this problem: given a "dictionary" consisting of two character vectors of unique "names" (or two columns in a data frame), x and y, how does one convert a factor z with levels in x into the corresponding equivalent with levels in y? There are likely a zillion ways to do this with various

Hi Folks: Here's the situation: > m <- cbind(x=letters[1:3], y = letters[4:6]) > m x y [1,] "a" "d" [2,] "b" "e" [3,] "c" "f" ## m is a 2 column character matrix > d <- data.frame(a=1:3,b=4:6) > d$c <- m > d a b c.x c.y 1 1 4 a d 2 2 5 b e 3 3 6 c f ## But please note (as was remarked

Folks: Over the years, many people -- including some who I would consider real expeRts -- have criticized factors and advocated the use (sometimes exclusively) of character vectors instead. I would just like to point out that, for me, factors provide one feature that I find to be very convenient: ordering of levels. ** As an example, suppose one has a character vector of labels

John (to a serial querulant): ...but with such a sweeping lack of information from you, don't congratulate yourself if you get a helpful answer. It wasn't your fault. David Winsemius Alameda, CA, USA 'Any technology distinguishable from magic is insufficiently advanced.' -Gehm's Corollary to Clarke's Third Law

> On May 25, 2016, at 4:27 PM, Hal Finkel via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > ----- Original Message ----- >> From: "Andrew Trick via llvm-dev" <llvm-dev at lists.llvm.org> >> To: "llvm-dev" <llvm-dev at lists.llvm.org> >> Sent: Wednesday, May 25, 2016 6:17:54 PM >> Subject: [llvm-dev] SCEV/IndVars Code Owner

On 05/26/2016 02:23 AM, Mikhail Zolotukhin via llvm-dev wrote: > >> On May 25, 2016, at 4:27 PM, Hal Finkel via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> >> ----- Original Message ----- >>> From: "Andrew Trick via llvm-dev" <llvm-dev at lists.llvm.org> >>> To: "llvm-dev" <llvm-dev at lists.llvm.org> >>>