similar to: Re placing null values (#NULL!)

Dear all, I'm building binomial mixed-model using lme4 package. I'm able to obtain outputs properly except when I include two particular variables: date (from 23 to 34; 1 being to first sampling day) and Latitude (UTM/100 000, from 55.42 to 56.53). No "NA" is any of those variables. In those cases, I get the warning message: "nlminb failed to converge" I tried to

It was found when running fio sequential write test with a XFS ramdisk on a KVM guest running on a 2-socket x86-64 system, the %CPU times as reported by perf were as follows: 69.75% 0.59% fio [k] down_write 69.15% 0.01% fio [k] call_rwsem_down_write_failed 67.12% 1.12% fio [k] rwsem_down_write_failed 63.48% 52.77% fio [k] osq_lock 9.46% 7.88% fio [k]

It was found when running fio sequential write test with a XFS ramdisk on a KVM guest running on a 2-socket x86-64 system, the %CPU times as reported by perf were as follows: 69.75% 0.59% fio [k] down_write 69.15% 0.01% fio [k] call_rwsem_down_write_failed 67.12% 1.12% fio [k] rwsem_down_write_failed 63.48% 52.77% fio [k] osq_lock 9.46% 7.88% fio [k]

Hi, I'm trying to use the R Survival analysis on a windows 7 system. The input data format is described at the end of this mail. 1/ I tried to perform a survival analysis including stratified variables using the following formula. cox.xtab_miR=coxph(Surv(time, status) ~ miR + strata(sex,nbligne, age), data=matrix) and obtain the following error message Warning message: In fitter(X, Y,

It was found when running fio sequential write test with a XFS ramdisk on a VM running on a 2-socket x86-64 system, the %CPU times as reported by perf were as follows: 69.75% 0.59% fio [k] down_write 69.15% 0.01% fio [k] call_rwsem_down_write_failed 67.12% 1.12% fio [k] rwsem_down_write_failed 63.48% 52.77% fio [k] osq_lock 9.46% 7.88% fio [k]

It was found when running fio sequential write test with a XFS ramdisk on a VM running on a 2-socket x86-64 system, the %CPU times as reported by perf were as follows: 69.75% 0.59% fio [k] down_write 69.15% 0.01% fio [k] call_rwsem_down_write_failed 67.12% 1.12% fio [k] rwsem_down_write_failed 63.48% 52.77% fio [k] osq_lock 9.46% 7.88% fio [k]

This is resolved: apt-get remove libspeex-dev cd ~/src/speex-1.2rc1/ ./configure --prefix=/usr make; make install cd ../ffmpeg ./configure --enable-libspeex make; make install worked; then I was able to decode a Speex .flv file: ~/flvs$ ffmpeg -i SpeexQ6R16Efalse.flv foo.wav FFmpeg version SVN-r17174, Copyright (c) 2000-2009 Fabrice Bellard, et al. configuration: --enable-libspeex

Dear all i use R only a few days and don't understand the difference between fivenum(x) und summary(x). > x [1] 20.77 22.56 22.71 22.99 26.39 27.08 27.32 27.33 27.57 27.81 28.69 29.36 [13] 30.25 31.89 32.88 33.23 33.28 33.40 33.52 33.83 33.95 34.82 > fivenum(x) [1] 20.770 27.080 29.025 33.280 34.820 > summary(x) Min. 1st Qu. Median Mean 3rd Qu. Max. 20.77 27.14

Dear R users, I've written the following functions to implement Silverman's modality test ("Using kernel density estimates to investigate multimodality", J.R. Stat. Soc. B, 43, (1981), 97-99.), and I tested them on the Chondrite data set (Good & Gaskins, J. Amer. Stat. Ass., 75, (1980), 42-56). Values for the critical window width seem OK, which is not the case for the

When all else fails, read the help page... ?fivenum says to look at ?boxplot.stats, and the "Details" section of ?boxplot.stats has, well, details. Tukey had reasons to call those hinges rather than quartiles. Andy > -----Original Message----- > From: Knut M. Wittkowski [mailto:kmw at rockefeller.edu] > Sent: Thursday, May 29, 2003 5:58 PM > To: Matthias Kirschner >

Hello folks, TL;DR: This is my proposed hashing interface based on a proposed standard hashing interface. It also is implemented with a much faster and higher quality algorithm than the current one. This is an *early draft* of the code, looking for initial feedback. There has been recent interest in improving the quality and consistency of LLVM's approach to hashing. In particular, getting

Dear all, after trying to compile R on our IBM Power3/AIX 5.1 machine I've been able to run it correctly. First of all I would thank all who responded my mails. I explain here how I've done it: First of all, it seems that configure and some shared libraries of AIX does not work at the same time. I tried to configure & make with the following environment vars CC=xlc F77=xlf CCC=xlC

Dear all, after trying to compile R on our IBM Power3/AIX 5.1 machine I've been able to run it correctly. First of all I would thank all who responded my mails. I explain here how I've done it: First of all, it seems that configure and some shared libraries of AIX does not work at the same time. I tried to configure & make with the following environment vars CC=xlc F77=xlf CCC=xlC

v3->v4: - Fix x86-32 build error. v2->v3: - Provide an optimized __raw_callee_save___kvm_vcpu_is_preempted() in assembly as suggested by PeterZ. - Add a new patch to change vcpu_is_preempted() argument type to long to ease the writing of the assembly code. v1->v2: - Rerun the fio test on a different system on both bare-metal and a KVM guest. Both sockets were

v3->v4: - Fix x86-32 build error. v2->v3: - Provide an optimized __raw_callee_save___kvm_vcpu_is_preempted() in assembly as suggested by PeterZ. - Add a new patch to change vcpu_is_preempted() argument type to long to ease the writing of the assembly code. v1->v2: - Rerun the fio test on a different system on both bare-metal and a KVM guest. Both sockets were

v2->v3: - Provide an optimized __raw_callee_save___kvm_vcpu_is_preempted() in assembly as suggested by PeterZ. - Add a new patch to change vcpu_is_preempted() argument type to long to ease the writing of the assembly code. v1->v2: - Rerun the fio test on a different system on both bare-metal and a KVM guest. Both sockets were utilized in this test. - The commit log was

v2->v3: - Provide an optimized __raw_callee_save___kvm_vcpu_is_preempted() in assembly as suggested by PeterZ. - Add a new patch to change vcpu_is_preempted() argument type to long to ease the writing of the assembly code. v1->v2: - Rerun the fio test on a different system on both bare-metal and a KVM guest. Both sockets were utilized in this test. - The commit log was

On Fri, Sep 14, 2007 at 11:42:18PM -0700, Tanya Lattner wrote: > The 2.1 pre-release (version 1) is available for testing: > http://llvm.org/prereleases/2.1/version1/ > > [...] > > 2) Download llvm-2.1, llvm-test-2.1, and the llvm-gcc4.0 source. > Compile everything. Run "make check" and the full llvm-test suite > (make TEST=nightly report). > > Send