search for: pretty

...le to hear our call center agents. Then the call drops or the caller hangs up unable to hear. I could see following lines inside full log ---------------------------------------------------------------------------------- [Jan 20 15:21:35] DEBUG[14982] audiohook.c: Write factory 0x7f32f4005940 was pretty quick last time, waiting for them. [Jan 20 15:21:35] DEBUG[14988] audiohook.c: Write factory 0x7f32dc00a0d0 was pretty quick last time, waiting for them. [Jan 20 15:21:35] DEBUG[15013] audiohook.c: Write factory 0x7f32f0016660 was pretty quick last time, waiting for them. [Jan 20 15:21:35] DEBUG[14...

...as decimal separator in plots and Mr. Paul Murrell wrote: ------- You could try something with axis() and chartr(), like ... par(mfrow=c(2,1)) plot(1:10/11, rep(1, 10), main="Standard X-Axis") plot(1:10/11, rep(1, 10), main="Customised X-Axis", axes=F) axis(1, at=pretty(1:10/11), labels=chartr(".", ",", as.character(pretty(1:10/11)))) axis(2) box() ------- This was very useful to me, but in the example: x <- rnorm(50, mean=2, sd=0.1) y <- rnorm(50, mean=2, sd=0.2) plot(x,y) axis(1,at=pretty(x),labels=chartr("."...

Hi, I have a following vector: > smallch [1] 0.0652840 0.1181300 0.0319370 0.0155700 0.0464110 0.0107850 [7] 0.0158970 0.0375900 0.0603090 0.0310300 0.0105920 0.0540580 [13] -0.0177740 0.0039393 Pretty (R 1.5.1) has problems with zero: > pretty(smallch) [1] -2.000000e-02 -3.469447e-18 2.000000e-02 4.000000e-02 6.000000e-02 [6] 8.000000e-02 1.000000e-01 1.200000e-01 You notice -3.46e-18 instead of 0. Is this feature changed in 1.6.0, or are there any simple ways to get around of it? O...

Hi, I have a following vector: > smallch [1] 0.0652840 0.1181300 0.0319370 0.0155700 0.0464110 0.0107850 [7] 0.0158970 0.0375900 0.0603090 0.0310300 0.0105920 0.0540580 [13] -0.0177740 0.0039393 Pretty (R 1.5.1) has problems with zero: > pretty(smallch) [1] -2.000000e-02 -3.469447e-18 2.000000e-02 4.000000e-02 6.000000e-02 [6] 8.000000e-02 1.000000e-01 1.200000e-01 You notice -3.46e-18 instead of 0. Is this feature changed in 1.6.0, or are there any simple ways to get around of it? O...

When I issue the command: if ( c(2.8,3)[1] < pretty (c(2.8,3))[1]) print ("problem") the result is "problem" prints. I have traced it to bits and the 2.8 of the returned vector from pretty is slightly larger. This seems to be due to the conversion to base 10 with the ns and unit variables in src/appl/pretty.c. Anyway if I do so...

I have written a set of functions for POSIXt objects that I would like to offer for consideration for use in base R. They augment and extend existing functions. Briefly, ## pretty.ct function(x,specs=pretty.ct.specs) ## round.ct function(x, tstr='1 min' ) ## axis.ct function(side,x,specs=NULL,...) ## parse.timeint function(dv) ## parse.tstr function(tstr) ## pretty.ct.specs default value for the 'specs' argume...

Examples similar to pretty(c(-1,1)*1e300, n = 1e9, min.n = 1) with smaller 'n': pretty(c(-1,1)*1e304, n = 1e5, min.n = 1) pretty(c(-1,1)*1e306, n = 1e3, min.n = 1) A report on 'pretty' when working with integers, similar to what led to change of 'seq' fuzz, is https://bugs.r-project.org/bugzilla3/sho...

I've added a few LLVM GDB pretty printers a while back (& just added llvm::Optional earlier today) & thought people might be interested in how to use them, etc. I use them by adding the following to my .gdbinit: source /path/to/llvm/src/utils/gdb-scripts/prettyprinters.py Also, I can suggest adding: set print prett...

...y work now. I mentioned them partly because the commit description said overflow for large n and partly to be considered for regression tests. -------------------------------------------- On Sat, 19/8/17, Martin Maechler <maechler at stat.math.ethz.ch> wrote: Subject: Re: [Rd] Issues of R_pretty in src/appl/pretty.c Cc: r-devel at r-project.org Date: Saturday, 19 August, 2017, 7:47 PM >>>>> Suharto Anggono Suharto Anggono via R-devel <r-devel at r-project.org> >>>>> on Fri, 18 Aug 2017 15:44:06 +0000 writes: > Examples similar to >...

Dear all, I got stuck with a weird behavior of pretty: pretty(c(-1,1),n=1) yields -2, 0, 2 instead of the desired result -1 1. Likewise, pretty(c(-2,2),n=1) yields -5, 0, 5 instead of the desired result -2 2. With n=0, the result is the same, while with n=2 everything is as documented. This behavior nastily messed up some of my cube plots. I...

Hello everybody, This is a bug involving functions in core R package: graphics::hist.default, grDevices::nclass.FD, and base::pretty.default. It is not yet on Bugzilla. I cannot submit it myself, as I do not have an account. Could somebody else add it for me, perhaps? That would be much appreciated. Kind regards, Sietse Sietse Brouwer Summary ------- Floating point errors can cause a data vector to have an ultra-small inter...

Added some basic DenseMap support in r290011 On Fri, Dec 16, 2016 at 2:05 PM David Blaikie <dblaikie at gmail.com> wrote: > I've added a few LLVM GDB pretty printers a while back (& just added > llvm::Optional earlier today) & thought people might be interested in how > to use them, etc. > > I use them by adding the following to my .gdbinit: > > source /path/to/llvm/src/utils/gdb-scripts/prettyprinters.py > > Also, I c...

In current versions of R, pretty(333) gives an infinite loop (due to a silent integer overflow in src/appl/pretty.c). I've looked at this problem and also at what S-plus does, (no code there to inspect, just experiments), and then I have fixed pretty.c. I think that it now behaves much more reasonably (both than befo...

...oublesome code! I first produce a barplot, saving the positions of the bar's centers. par(mar = c(6.1, 5.1, 4.1, 4.1), mgp = c(3, 3.0, 0)) ticks.loc <- barplot(sum.of.weights, col = 5, xlab = "", ylab = "", axes = FALSE, axisnames = FALSE) pretty.bar <-pretty(c(0, sum.of.weights), 6) pretty.lab <- paste(pretty.bar, "%", sep = "") axis(side = 2, at = pretty.bar, labels = pretty.lab, col = 1, line = 0, cex.axis = 0.80, las = 2, mgp = c(3, 2, 0)) my.axis(side = 1, at = ticks.loc, labels = plot.labels,...

patch against recent SVN ... as far as I can tell this trivial typo has been there for 20 years: https://github.com/wch/r-source/blame/ba7920a99fb2fb62b89e404e65f8b132ed4c150a/src/library/base/man/pretty.Rd =================================================================== --- pretty.Rd (revision 74426) +++ pretty.Rd (working copy) @@ -21,8 +21,8 @@ \item{min.n}{nonnegative integer giving the \emph{minimal} number of intervals. If \code{min.n == 0}, \code{pretty(.)} may return a sin...

Hello list, what does this mean in the debug-log : [Jan 19 15:11:04] DEBUG[1475] audiohook.c: Write factory 0x153cf678 was pretty quick last time, waiting for them. [Jan 19 15:11:04] DEBUG[1701] audiohook.c: Read factory 0x14fe5ef0 was pretty quick last time, waiting for them. [Jan 19 15:11:04] DEBUG[1475] audiohook.c: Read factory 0x153cec40 and write factory 0x153cf678 both fail to provide 160 samples [Jan 19 15:11:04] DE...

...mailing list. Piotr 2016-12-17 1:04 GMT+01:00 David Blaikie via llvm-dev < llvm-dev at lists.llvm.org>: > Added some basic DenseMap support in r290011 > > On Fri, Dec 16, 2016 at 2:05 PM David Blaikie <dblaikie at gmail.com> wrote: > >> I've added a few LLVM GDB pretty printers a while back (& just added >> llvm::Optional earlier today) & thought people might be interested in how >> to use them, etc. >> >> I use them by adding the following to my .gdbinit: >> >> source /path/to/llvm/src/utils/gdb-scripts/prettyprinter...

...Piotr > > 2016-12-17 1:04 GMT+01:00 David Blaikie via llvm-dev < > llvm-dev at lists.llvm.org>: > > Added some basic DenseMap support in r290011 > > On Fri, Dec 16, 2016 at 2:05 PM David Blaikie <dblaikie at gmail.com> wrote: > > I've added a few LLVM GDB pretty printers a while back (& just added > llvm::Optional earlier today) & thought people might be interested in how > to use them, etc. > > I use them by adding the following to my .gdbinit: > > source /path/to/llvm/src/utils/gdb-scripts/prettyprinters.py > > Also, I c...

...Flushing audiohook 0x7f5aa4095500 so it remains in sync ....... audiohook.c messages ....... ....... [Nov 25 17:49:04] DEBUG[27462] audiohook.c: Flushing audiohook 0x7f5aa4095500 so it remains in sync [Nov 25 17:49:04] DEBUG[27464] audiohook.c: Read factory 0x7f5aa4095570 was pretty quick last time, waiting for them. [Nov 25 17:49:04] DEBUG[27464] audiohook.c: Read factory 0x7f5aa4095570 was pretty quick last time, waiting for them. [Nov 25 17:49:04] DEBUG[27462] audiohook.c: Flushing audiohook 0x7f5aa4095500 so it remains in sync [Nov 25 17:49:04] DEBUG[27464] audiohook...

See https://stat.ethz.ch/pipermail/r-devel/2017-August/074746.html for the origin of the example here. That pretty(c(-1,1)*1e300, n = 1e9, min.n = 1) gave 20 intervals, far from 1e9, but pretty(c(-1,1)*1e300, n = 1e6, min.n = 1) gave 1000000 intervals (on a machine), made me trace through the code to function 'R_pretty' in https://svn.r-project.org/R/trunk/src/appl/pretty.c . *lo is -1e300, *up is 1e30...