similar to: Convenience function to get unevaluated ... function arguments

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,

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

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

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

On Thu, Sep 20, 2012 at 9:01 AM, David Winsemius <dwinsemius at comcast.net> wrote: (In response to an OP's aplogy for an "awkwardly worded question"): > Awkwardly worded questions will get much better answers if they are accompanied by some test data. Fortune nomination! Cheers, Bert > -- > David Winsemius, MD > Alameda, CA, USA > >

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

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

Hello, I'm analysing reaction time data from a linguistic experiment (a variant of a lexical decision task). To ascertain that the data was normally distributed, I used *shapiro.test *for each participant (see commands below), but only one out of 21 returns a p value above p.0 05. > f = function(dfr) return(shapiro.test(dfr$Target.RTinv)$p.value) > p = as.vector(by(newdat,

... 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

On 1 December 2010 07:04, Bill Wendling <wendling at apple.com> wrote: > The unwind edge from an invoke instruction jumps to a landing pad. That landing pad contains code which performs optional cleanups, and then determines which catch handler to call (if any). If no catch handlers are applicable, the exception resumes propagation either to the next enclosing region or out of the

A pseudo poll on AR error handling... With AR, you have the choice between the following: (1) if thing.save go_for_it else handle_the_error end (2) begin thing.save! rescue RecordInvalid => error handle_the_error end (3) override rescue_action_in_public (ala the recipes book) or do something homegrown, and then just thing.save! --- The questions are: -Which idiom do you use and

Hi there, Suppose the cmd is "a<-3", I can parse the cmd sexp with R_ParseVector and eval it. My question is - is it possible to parse a cmd like "a <- ?", afterwards evaluation will give corresponding result depend on different argument? In other words, '?' is just a placeholder. Thanks. Xin [[alternative HTML version deleted]]

Thanks to Deepayan Sarkar (lattice) and Paul Murrell (grid) I have nearly finished porting the Hmisc library's xYplot function to R. xYplot extends xyplot to allow for error bars, bands, and a few other features. In S-Plus I extended the Trellis function xyplot mainly by writing panel.xYplot. In R, xyplot contains a lot of code, so I implemented xYplot by calling xyplot from it. Things are

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

I was just trying to build lldb-6.0 from source (and had previously successfully build llvm-6.0, clang-6.0, and lld-6.0 from source), but received a compile error while using both just cmake and cmake+ninja Does this look familiar to anyone? In file included from llvm/lldb-6.0.0.src/source/API/SystemInitializerFull.cpp:89: In file included from

On Tue, Jan 15, 2019 at 2:50 AM Vivien Millet <vivien.millet at gmail.com> wrote: > Hello Zachary ! > Thanks for your time ! > So you are one of the happy guys who suffered from the lack of PDB format > information :) > Yes, that would be me :) > To be honest I'm really a beginner in the PDB stuff, I just read some llvm > documentation to understand what went

+ Jonas who hit the same bug recently. On Wed, May 16, 2018 at 8:01 AM, Eric Gorr via llvm-dev <llvm-dev at lists.llvm.org> wrote: > I was just trying to build lldb-6.0 from source (and had previously > successfully build llvm-6.0, clang-6.0, and lld-6.0 from source), but > received a compile error while using both just cmake and cmake+ninja > > Does this look familiar to

Ok just tried on Win 7 and the same problem occurs. I am building with : cmake -G "Ninja" -DCMAKE_BUILD_TYPE=Release -DLLVM_USE_CRT_RELEASE=MT -DLLVM_ENABLE_TIMESTAMPS=ON -DLLVM_ENABLE_ASSERTIONS=ON -DLLVM_INSTALL_TOOLCHAIN_ONLY=ON -DLLVM_TARGETS_TO_BUILD="ARM;X86" -DPYTHON_EXECUTABLE=$python_exe -DLLVM_BUILD_TESTS=ON -DLLVM_LIT_TOOLS_DIR=C:/cygwin64/bin fwiw compiler-rt is

Well, that’s certainly possible, but improving llvm-pdbutil is another possibility. Doing it directly in your jit compiler will probably save you time though, since you won’t have to worry about writing tests and going through code review On Wed, Jan 16, 2019 at 1:01 PM Vivien Millet <vivien.millet at gmail.com> wrote: > Thanks for the tips ! > When you talk about doing all of this I