search for: 0.1162

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

>> GCC (4.5.2, Windows build from CodeSourcery) - With -O0: 110ms, with -O2: 215ms >> Clang/LLVM (Release mode, LLVM git hash 7f5714f4..., clang git hash >> 9d9cf5...) - With -O0: 110ms, with -O2: 640ms Hi Matt, I only see 2x slowdown on my machine (consistently, O2 and O3), but that's still bad. If you compile to IR then pass "opt -time-passes" you can get a

Dear all, this may be a stupid question but... The underlying model in procedure arima0 is X[t] = a[1]X[t-1] + ... + a[p]X[t-p] + e[t] + b[1]e[t-1] + ... +b[q]e[t-q] Is it possible to get an estimate of e for every point t, t-1 etc. or at least an estimate of the variance of e? Thanks a lot in advance for any hints Kai Arzheimer

Thanks, Matt. This is great information. Sounds like Chandler is looking into the details of what's going on. -Jim On Jul 19, 2012, at 3:55 PM, Matt Fischer <mattfischer84 at gmail.com> wrote: > I've been doing some profiling of LLVM on our codebase, to see how it > stacks up to the existing GCC build that we do. The primary thing I'm > focusing on at the moment is

Hi R community! I've fitted three mixed-effects regression models to a thousand bootstrap samples (case-resampling regression) using the lme4 package in a custom-built for-loop. The only output I saved were the inferential statistics for my fixed and random effects. I did not save any output related to the performance to the machine learning algorithm used to fit the models (REML=FALSE).

I've been doing some profiling of LLVM on our codebase, to see how it stacks up to the existing GCC build that we do. The primary thing I'm focusing on at the moment is build speed, and in this regard LLVM seems to be pretty all over the map. On some files it seems to go quite a bit faster than GCC, and on others it's slower, leading to an aggregate build time for our repository