search for: occorring

Displaying 4 results from an estimated 4 matches for "occorring".

Did you mean: according
2011 Jul 08
1
Getting wrong NA values using "for" cmd
...0.74 0.79 NA 0.90 NA 1.00 and dissecting this: > s[4] [1] 0.15 > dados[,3][dados[,2]==0.15][1] [1] 0.11 > dados[,3][dados[,2]==s[4]][1] [1] NA > s[4]==0.15 [1] FALSE > s[5]==0.20 [1] TRUE > dados[,3][dados[,2]==s[5]][1] [1] 0.16 Anyone could help me to discover why this is occorring? dados[,2] and dados[,3] came from rounded values. Could this fact interfere the results? Thanks in advance. -- View this message in context: http://r.789695.n4.nabble.com/Getting-wrong-NA-values-using-for-cmd-tp3654335p3654335.html Sent from the R help mailing list archive at Nabble.com.
2000 Feb 14
2
Error report on empty matrices (PR#435)
Dear R developers: When using R.0.99a (Version 0.99.0 Patched (February 9, 2000), source compiled with gcc under SuSE 6.2) on a PIII 500Mhz Machine under SuSE 6.2 Linux I found the following bug: x <- matrix(0,10,0) rbind(x,2) causes an R-crash with the message "Gleitkomma-Ausnahme" (floating point exception) which is probably due to the non-applicability of the recyling
2010 Jan 25
1
Bug#566012: xen-hypervisor-3.2-1-i386: Another crash. Is this a hypervisor-problem, or is this the kernel?
Package: xen-hypervisor-3.2-1-i386 Version: 3.2.1-2 Followup-For: Bug #566012 Just had another crash. I got the output from a serial console. The kernel doesn't say anything though. (XEN) traps.c:1996:d6 Domain attempted WRMSR 00000400 from 00000000:0000ffff to ffffffff:ffffffff. (XEN) traps.c:1996:d6 Domain attempted WRMSR 00000404 from 00000000:00018000 to ffffffff:ffffffff. (XEN)
2006 Feb 20
0
crashed would be solved by sudo ?
Hi all, Most of time I like to try out wine with game console emulators which use fare amount of d3d or opengls, to see how much wine supports on this. Suddenly today that the wine does not work with any emulator I have tried with, came up with error message that is followed. But I accidentally found a workround that with ``sudo'', the problem won't occor. Any idea ?