search for: reevaluated

Hi All, I just used "dump" on Splus to transfer a pile of survival objects from Splus 3.4 on Solaris 7 to R 0.63.3 on Intel. The only trick is that survival objects contain an element holding the original call that generated the object. When Splus writes these out, it doesn't mark them in any way, so when R tries to read them in, it ends up trying to reevaluate the call. Not

Hi All, I just used "dump" on Splus to transfer a pile of survival objects from Splus 3.4 on Solaris 7 to R 0.63.3 on Intel. The only trick is that survival objects contain an element holding the original call that generated the object. When Splus writes these out, it doesn't mark them in any way, so when R tries to read them in, it ends up trying to reevaluate the call. Not

On Jan 11, 2013, at 8:35 AM, Brooks Davis <brooks at freebsd.org> wrote: > On Fri, Jan 11, 2013 at 08:02:22AM -0500, Justin Holewinski wrote: >> That said, I think MSVC 2010 is a reasonable target. Just MHO, but I think it is far too early to drop support for MSVC 2010. > It's a bit more complex for FreeBSD (and probably the others) due to > assumptions in our build

Dear R-helpers, How come that in the following code the rnorm() function is evaluated only once for each branch of the 'ifelse' ? x <- rnorm(10) y1 <- ifelse(x > 0, rnorm(1) , rnorm(1)) What is the right way to make it called/evaluated for each row, apart from a 'for' loop ? Thanks, Jacques.

Hello all, I would like to ask several questions regarding cacheSweave: 1) Is there a way to set "cache=true" globally? (I tried it using \SweaveOpts but it didn't seem to work) 2) Is there a way to "flush" specific cache once it is created? (other then erasing the entire cache directory)? Changing the code in the code chunk seems to do it, but I am not sure to what

----- Original Message ----- > From: "Andrew Trick" <atrick at apple.com> > To: "Sanjoy Das" <sanjoy at playingwithpointers.com> > Cc: "Daniel Berlin" <dberlin at dberlin.org>, "llvm-dev" > <llvm-dev at lists.llvm.org>, "Joseph Tremoulet" > <jotrem at microsoft.com>, "Oscar Blumberg" >

Hi all I want to get the design matrix for a model, evaluated at a single value. For example, if I pass in a data frame with a=2, b=2, y=3, and my model is y ~ a+b+a:b, then I would like to get the values 3, 2, 2, 4 out. I can do this with: tmp <- model.matrix(fit, data=mydata) or tmp <- predict(fit, newdata=mydata, type="terms") However, if the fit had a smoothing spline

On 03/23, Hongbin Zheng wrote: > Hi Johannes, > > On Mon, Mar 21, 2016 at 6:35 PM, Johannes Doerfert < > doerfert at cs.uni-saarland.de> wrote: > > > Hey Utpal, > > > > First of, I think you made nice process here and have some very good > > ideas of what we could do in the future. > > > > [NOTE: I CC'ed some people that have shown

Hey Utpal, First of, I think you made nice process here and have some very good ideas of what we could do in the future. [NOTE: I CC'ed some people that have shown interest in this topic but I might have forgotten some, therefor I also added the llvm-dev list.] For the upcoming GSoC proposal we should slow down a little bit and reevaluate our goals. After talking to a couple of LLVM and

Hi all, I'm in a very preliminary phase of a language project which requires some specific optimizations to be reasonably efficient. LLVM already looks very good; I'd just like to know whether I can push these optimizations through LLVM to the JIT phase (which, as far as I understand the docs, is a pretty powerful part of LLVM). The optimizations that I need to get to work are: *

Hello LLVM, This is a proposal for a new pass that improves performance and code size in some nested loop situations. The pass is target independent. >From the description in the file header: This optimization finds loop exit values reevaluated after the loop execution and replaces them by the corresponding exit values if they are available. Such sequences can arise after the SimplifyIndVals+LoopStrengthReduce passes. This pass should be run after LoopStrengthReduce. A former colleague created this pass back in LLVM 2.9 and we've bee...

Nadav, Arnold, et al., I have a number of loops that I would like us to be able to autovectorize (common, for example, in n-body inter-particle force kernels), and the problem is that they look like this: for (int i = 0; i < N; ++i) { if (r[i] > 0) v += m[i]*...; } where, as written, m[i] is not accessed unless the condition is true. The general problem (as is noted by the loop

http://www.winehq.org/announce/1.2 I also submitted it to Slashdot, please click up: http://slashdot.org/submission/1284766/Wine-12-released - d. ---------- Forwarded message ---------- From: Alexandre Julliard <julliard at winehq.org> Date: 16 July 2010 19:22 Subject: Post-release plans To: wine-devel at winehq.org Folks, First I want to thank everybody for your great work of the

On Fri, Jul 15, 2016 at 5:25 PM, Andrew Trick <atrick at apple.com> wrote: > > On Jul 15, 2016, at 4:48 PM, Hal Finkel <hfinkel at anl.gov> wrote: > > Why? A decision was made to give pointers types, and we've decided to > change that. It is not clear to me that the decision to allow implicit > early exits was, in retrospect, optimal. I think it is completely

Hello Rowland, Thanks for your reactions. We will internally discuss it how to implement an AD solution. Kind regards, Paul ----- Original Message ----- From: "Rowland penny" <rpenny at samba.org> To: "sambalist" <samba at lists.samba.org> Sent: Monday, 25 January, 2016 10:46:21 Subject: Re: [Samba] Best way to sync Samba AD 4 LDAP with OpenLDAP On 25/01/16

...6_64-apple-darwin9.8.0) The problem DOES NOT occur under R 2.10.0 on Win32. If the code below is bracketed with pdf("test.pdf") and dev.off(), the correct labels appear in the file. This behavior doesn't seem to appear if there is only one plot. My guess is that the titles are being reevaluated when the plot is redrawn, and since the value of i is 2 when the redraw occurs, both labels get set to "i=2". I guess "Save as" forces a redraw because a dialog box pops up? If could be that this behavior is what is intended, and that somewhere between R 2.10.0 and R 2.13.2 a...

Hello all, due to unexplained differences between statistical results from collaborators and our lab that arose in the same large proteomics dataset we reevaluated the t.test() function. Here, we found a weird behaviour that is also reproducible in the following small test dataset: Suppose, we have two vectors with numbers and some missing values that refer to the same individuals and that should therefore be evaluated with a paired t-test: > testda...

Suppose I have a single ZFS pool on a single disk; I want to upgrade the system to use two different, larger disks and I want to mirror. Can I do something like: - I start with disk #0 - add mirror on disk #1 (resilver) - replace first disk (#0) with disk #2 (resilver) Casper

...ifference. LLVM, OTOH, does a large amount of IPO and IPA, such as dead argument elimination, IPSCCP, and other things. Something that is good to inline for GCC is not necessarily good for LLVM. 3. Once these annotations are added to a source base, they are almost never removed or reevaluated. This exacerbates #2. In my mind, the right solution to this problem is to use profile-directed inlining. If you actually care this much about the performance of your code, you should be willing to use profile information. Profile information will help inlining, but it can also be used for f...

I found this tracing a bug when experimenting with a new sort() function using match.arg(). It was triggered because mosaicplot.default(.) has an argument called `sort' and calls itself the sort() function in which I was using match.arg()... Here is (input for) a small clean example : #### bad match.arg() // sys.function() bug : #### MM, 22.3.2002 callme <- function(a = 1, mm =