search for: inaccuraci

Displaying 20 results from an estimated 244 matches for "inaccuraci".

Did you mean: inaccuracy
2011 Jun 16
1
lines(..., lwd=3) inaccuracy
Using a line width > 1 results in not only a thicker line but also some fuzz in the other direction, as shown in this example program. You will see that the thick vertical black lines extend below the gray scale horizontal lines. Does anyone know whether this is intended or is it a bug? The application is for displaying a correlation matrix (here just some random U(0,1)s). Thanks -Frank
2015 Jun 18
2
[LLVMdev] Contributing a buildbot for the BPF backend
Thank you. Alexei just committed the change to SVN. Regards, Marco Leogrande Sent by a carbon-based life form; hence, it may contain repetitions, inaccuracies, logical fallacies and repetitions. On Wed, Jun 17, 2015 at 2:52 PM, Galina Kistanova <gkistanova at gmail.com> wrote: > LGTM. > Please commit. > > Thanks > > Galina > > On Tue, Jun 16, 2015 at 8:32 PM, Marco Leogrande <marcol at plumgrid.com> > wrote: &gt...
2007 Jun 28
2
inaccuracy in qbinom with partial argument matching
Hi, I found the following strange effect with qbinom & partial argument matching p0 <- pbinom(0, size = 3, prob = 0.25) qbinom(p0, size = 3, prob = 0.25) ## 0 o.k. qbinom(p0-0.05, size = 3, prob = 0.25) ## 0 o.k. ## positional matching: qbinom(p0, 3, 0.25) ## 0 o.k. ## partial argument matching: qbinom(p0 , s = 3, p = 0.25) ## 1 ??? qbinom(p0-0.05,
2015 Jun 17
2
[LLVMdev] Contributing a buildbot for the BPF backend
...a bit more sense. I have added the new builder under _get_experimental_scheduled_builders(), as the comment above that function suggested me it would be a good idea. :) Does it look a reasonable start? Regards, Marco Leogrande Sent by a carbon-based life form; hence, it may contain repetitions, inaccuracies, logical fallacies and repetitions. On Wed, Jun 10, 2015 at 7:06 PM, Marco Leogrande <marcol at plumgrid.com> wrote: > Hi Galina, > > thanks for the info! > > I think we will go for the "LLVM+clang with cmake" approach, since the > BPF target has been marked no...
2004 Aug 06
1
Sample rate inaccuracy
Hi all, I'm having some problems with inaccurate sampling rates between sending and receiving party. (Using a simple raw UDP protocol sending packets from speex to speex) Both PC's have their soundcard set to 8 khz, but the samplerate seems to differ slightly between machines. The problem I have is that the sending machine sometimes samples with a slightly lower rate than the player
2008 Aug 05
0
qgamma inaccuracy
Hello, I have been working with various probability distributions in R, and it seems the gamma distribution is inaccurate for some inputs. For example, qgamma(1e-100, 5e-101, lower.tail=FALSE) gives: 1.0. However, it seems this is incorrect; I think the correct answer should be 0.082372029620717283. When I check these numbers using pgamma, I get: pgamma(1,5e-101, lower.tail=FALSE) =
2008 Oct 03
1
Bug or inaccuracy in cumsum( )
I came across this: shouldn't the last value be a more exact zero? It did not do that with 1 - sum( rep(0.1, 10) ) > 1 - cumsum( rep(0.1, 10) ) [1] 9.000000e-01 8.000000e-01 7.000000e-01 6.000000e-01 5.000000e-01 4.000000e-01 3.000000e-01 2.000000e-01 [9] 1.000000e-01 1.110223e-16 > version _ platform
2010 Sep 24
0
Inaccuracy of kummerU (fAsianOptions) (Tricomi function)
Hello, I need to use the confluent function of second kind, also known as Tricomi function. It is implemented as kummerU() function in fAsianOptions package, but I've found very inaccurate values, comparing with those provided by Mathematica. I think Mathematica values are OK because kummerU values leads to negative probabilities. For example, if you try the kummerU() function example, you
2010 Sep 28
1
small inaccuracy in startup warning message
Hi, Cosmetic. Starting R with e.g. --max-ppsize=-10 produces the following warning: WARNING: '-max-ppsize' value is negative: ignored The name of the option displayed in the warning is incorrect. Could that be fixed? See src/main/CommandLineArgs.c (there are 3 places in that file where the name of this option needs to be adjusted). This is with current R-alpha. Thanks! H. --
2011 Nov 17
1
inaccuracy in man page for duplicated() + anyDuplicated() not working with MARGIN=0
Hi, In man page for duplicated: Value: ?duplicated()?: For a vector input, a logical vector of the same length as ?x?. For a data frame, a logical vector with one element for each row. For a matrix or array, a logical array with the same dimensions and dimnames. When 'x' is a matrix or array, the returned value is NOT a logical array: > m <-
2011 Dec 21
0
CHANGELOGs inaccuracies
Hello. I am reading changelogs from rails master git branch from time to time, because I like to know what''s new. But every time, there are some errors. Mainly in version releases dates. For example in actionpack changelog (https://github.com/rails/rails/blob/ 6481bc5f49ef26e8fde68ac964dc984d12f33189/actionpack/CHANGELOG.md) is last released version Rails 3.1.0. We all know, that latest
2016 Jul 27
4
[PATCH v2 repost 6/7] mm: add the related functions to get free page info
On 07/26/2016 06:23 PM, Liang Li wrote: > + for_each_migratetype_order(order, t) { > + list_for_each(curr, &zone->free_area[order].free_list[t]) { > + pfn = page_to_pfn(list_entry(curr, struct page, lru)); > + if (pfn >= start_pfn && pfn <= end_pfn) { > + page_num = 1UL << order; > + if (pfn + page_num > end_pfn) > + page_num =
2016 Jul 27
4
[PATCH v2 repost 6/7] mm: add the related functions to get free page info
On 07/26/2016 06:23 PM, Liang Li wrote: > + for_each_migratetype_order(order, t) { > + list_for_each(curr, &zone->free_area[order].free_list[t]) { > + pfn = page_to_pfn(list_entry(curr, struct page, lru)); > + if (pfn >= start_pfn && pfn <= end_pfn) { > + page_num = 1UL << order; > + if (pfn + page_num > end_pfn) > + page_num =
2007 Feb 02
1
Inaccuracy in ?convolve
Hi, Man page for 'convolve' says: conj: logical; if 'TRUE', take the complex _conjugate_ before back-transforming (default, and used for usual convolution). The complex conjugate of 'x', of 'y', of both? In fact it seems that it takes the complex conjugate of 'y' only which is OK but might be worth mentioning because (1) conj=TRUE is the
2016 Jan 12
1
Small inaccuracy in the Writing R Extensions manual
G'day Duncan, On Tue, 12 Jan 2016 07:32:05 -0500 Duncan Murdoch <murdoch.duncan at gmail.com> wrote: > On 11/01/2016 11:59 PM, Berwin A Turlach wrote: > > G'day all, > > > > In Chapter 1.4 (Writing package vignettes) the Writing R Extensions > > manual states: > > > > By default @code{R CMD build} will run @code{Sweave} on all > >
2005 Jan 12
2
Inaccuracy in seq() function (PR#7503)
Full_Name: Vlad Stolin Version: R 2.0.0 OS: Windows 2000 Submission from: (NULL) (204.128.232.211) When generating the sequence using seq() function with non-integer numbers result is somewhat unpredictable. Example: > v1<-seq(1.60,1.90,.05) > v2<-c(1.60,1.65,1.70,1.75,1.80,1.85,1.90) > v1-v2 [1] 0.000000e+00 2.220446e-16 2.220446e-16 0.000000e+00 0.000000e+00 0.000000e+00
2015 May 28
0
[LLVMdev] Callgraph inaccuracy
I'm working on this issue, thank you for reporting it. The short answer is that the callgraph reported by TD is the same as discovered/computed during BU (and BU can't determine the indirect call can only target C2). I've added this example, and a few other related tests, to the DSA's test suite[1] to document this behavior while I'm working out what the best solution is.
2008 Aug 07
1
qgamma inaccuracy (PR#12324)
Full_Name: Version: 2.7.1 (2008-06-23) OS: windows vista Submission from: (NULL) (216.82.144.137) Hello, I have been working with various probability distributions in R, and it seems the gamma distribution is inaccurate for some inputs. For example, qgamma(1e-100, 5e-101, lower.tail=FALSE) gives: 1.0. However, it seems this is incorrect; I think the correct answer should be
2015 Jun 10
2
[LLVMdev] Contributing a buildbot for the BPF backend
...XPERIMENTAL_TARGETS_TO_BUILD=BPF ../path/to/src/ > make -jX > ./bin/llvm-lit test/CodeGen/BPF/ > > > Any suggestion would be appreciated. > > Thanks! > > Regards, > > Marco Leogrande > > Sent by a carbon-based life form; hence, it may contain repetitions, > inaccuracies, logical fallacies and repetitions. > > > On Thu, May 7, 2015 at 8:56 PM, Marco Leogrande <marcol at plumgrid.com> > wrote: > > Hi everyone, > > I am working with Alexei Starovoitov to contribute an LLVM buildbot > > for the experimental BPF backend. > >...
2016 Jan 12
3
Small inaccuracy in the Writing R Extensions manual
G'day all, In Chapter 1.4 (Writing package vignettes) the Writing R Extensions manual states: By default @code{R CMD build} will run @code{Sweave} on all Sweave vignette source files in @file{vignettes}. If @file{Makefile} is found in the vignette source directory, then @code{R CMD build} will try to run @command{make} after the @code{Sweave} runs, otherwise @code{texi2pdf} is run on