search for: digitation

From: Simon Deziel <simon.deziel at gmail.com> Fixes LP: #806537 Signed-off-by: Simon Deziel <simon.deziel at gmail.com> --- rulefiles/linux/ignore.d.server/openvpn | 7 ++++++- 1 files changed, 6 insertions(+), 1 deletions(-) diff --git a/rulefiles/linux/ignore.d.server/openvpn b/rulefiles/linux/ignore.d.server/openvpn index 2b4bfd6..d80f42f 100644 ---

I am trying to use round()to force R to display a specific number of decimals, but it seems to display <=2 decimals no matter what I specify in the digits argument. As an alternative I tried signif(), but it also produces unexpected results. See example code and results below. Format() works, but then the result no longer is numeric. Am I missing something simple? I am using R 2.9.0 on Windows

R developers, Seems I get a bad result ("%#4.0-1e" in particular) when trying to use prettyNum digits=0 with scientific notation. I tried on both my Linux box and on an online R evaluator and saw the same problem, so it's not limited to my box at least. I see the problem in both R 3.5.3 and R 3.3.2. options(scipen=-100) prettyNum(1, digits=0) [1] "%#4.0-1e" prettyNum(2,

At least the policyd-weight in lenny seems to generate quite different patterns. For example the 'rate' is output multiple times in some situations, the 'check from' is omited sometimes and somehow those log messages have a trailing blank. With those patterns logcheck stays silent again. Signed-off-by: Mathias Krause <minipli at googlemail.com> ---

Hi I am using following say.conf file. Its a default file, which comes with Asterisk installation. When I call SAY DATETIME AGI function, it simply returns without playing date & time. Where as if I use mode=old setting, it works. Is this a bug or mode=new is not implemented for SAY DATETIME AGI function? [general] mode=new ; method for playing numbers and dates ;

FWIW, it doesn't seem to be happening on Mac OS: > format(2^30, digits=0) [1] "1.e+09" > prettyNum(12345.6, digits=0) [1] "1.e+04" A glibc misfeature? -pd > On 22 Mar 2019, at 10:10 , Martin Maechler <maechler at stat.math.ethz.ch> wrote: > > Thank you, Robert for raising this here ! > >>>>>> Robert McGehee

Dear R Core Team, First of all, thank you for your amazing work on developing and maintaining this wonderful language. I just stumbled upon the following behavior in R version 3.6.0: format(9.91, digits = 2, nsmall = 2) format(9.99, digits = 2, nsmall = 2) yield "9.91" and " 9.99" with an extraneous whitespace. My expected output for the second command is

Every so often, and it seems that it happens only when a call is in progress, all 24 Zap channels get reset. All channels are opened and then timeout. This causes the in-progress calls to terminate. There are no corresponding Red/Yellow alarms on wither the PBX or Asterisk although we do receive a fair amount of Blue Alarms. The Asterisk server is connected to a legacy PBX through a Digium

Does anybody have any insight into how to make this faster? I suspect, that the rounding going on may be an issue, as is the stepping through data frame rows using integers ... If you have the patience to teach a noob, he will highly appreciate it ;0) Joh digit <- 4 for (minute in seq(from=25,to=lrange[2])){ # Extract all data associtaed with the current time (minute) frame <-

Thank you, Robert for raising this here ! >>>>> Robert McGehee >>>>> on Thu, 21 Mar 2019 20:56:19 +0000 writes: > R developers, > Seems I get a bad result ("%#4.0-1e" in particular) when trying to use prettyNum digits=0 with scientific notation. I tried on both my Linux box and on an online R evaluator and saw the same problem, so

I was quite suprised to discover that applying `zapsmall` to a scalar value has no apparent effect. For example: > y <- 2.220446e-16 > zapsmall(y,) [1] 2.2204e-16 I was expecting zapsmall(x)` to act like > round(y, digits=getOption('digits')) [1] 0 Looking at the current source code, indicates that `zapsmall` is expecting a vector: zapsmall <- function (x, digits =

How to copy/transfer/download Blu-ray/DVD Digital Copy to Computer? What is a Digital Copy? A Digital Copy is an extra copy of the movie you bought on Blu-ray?/DVD disc that enables you to download or stream your movie to a computer, mobile device, or Internet-connected TV, Blu-ray? player or set top box. If your Blu-ray? Disc or DVD has the "Digital Copy" logo on the back it will

Hi all I am not a C programmer, but I am trying to understand formatC to get consistent printing of reals to a given number of significant digits. Can someone please explain this to me? These first three give what I expect on reading ?formatC: > formatC(0.0059999, digits=2,format="fg",flag="#") [1] "0.0060" > formatC(0.59999,

Hello I am starting to learn AGI. I have setup an extension to play the agi-test.agi perl script and the output I get is this on console: On Polycom 300: -- Executing Answer("SIP/200-72d2", "") in new stack -- Executing AGI("SIP/200-72d2", "agi-test.agi") in new stack -- Launched AGI Script /var/lib/asterisk/agi-bin/agi-test.agi --

Hello, I have an installation in Austria; ISDN service provided by Austria Telekom. The main number of the service is 6 digits. Incoming calls may contain 2 additional digits, which I then use to route the call to the correct extension. Telekom sends me all the digits. My problem is that when someone tries to dial an 8 digit number to an extension from an outside analog phone, AT sends the call

Zapping a vector of small numbers to zero would cause problems when printing the results of summary(). For example, if zapsmall(c(2.220446e-16, ..., 2.220446e-16)) == c(0, ..., 0) then print(summary(2.220446e-16), digits = 7) would print Min. 1st Qu. Median Mean 3rd Qu. Max. 0 0 0 0 0 0 The same problem can also appear when

Hi, Consider the following situation : <SIP/asterisk-0000001d>AGI Rx << WAIT FOR DIGIT 3000 <SIP/asterisk-0000001d>AGI Tx >> 200 result=48 <SIP/asterisk-0000001d>AGI Rx << WAIT FOR DIGIT 3000 <SIP/asterisk-0000001d>AGI Tx >> 200 result=48 <SIP/asterisk-0000001d>AGI Rx << WAIT FOR DIGIT 3000 <SIP/asterisk-0000001d>AGI Tx >>

I think what's been missed is that zapsmall works relative to the absolute largest value in the vector. Hence if there's only one item in the vector, it is the largest, so its not zapped. The function's raison d'etre isn't to replace absolutely small values, but small values relative to the largest. Hence a vector of similar tiny values doesn't get zapped. Maybe the line

Le 18/12/2023 ? 11:24, Martin Maechler a ?crit?: >>>>>> Serguei Sokol via R-devel >>>>>> on Mon, 18 Dec 2023 10:29:02 +0100 writes: > > Le 17/12/2023 ? 18:26, Barry Rowlingson a ?crit?: > >> I think what's been missed is that zapsmall works relative to the absolute > >> largest value in the vector. Hence if

>>>>> peter dalgaard >>>>> on Fri, 22 Mar 2019 17:30:19 +0100 writes: > FWIW, it doesn't seem to be happening on Mac OS: >> format(2^30, digits=0) > [1] "1.e+09" >> prettyNum(12345.6, digits=0) > [1] "1.e+04" > A glibc misfeature? It seems (and note we are talking about format.default()