search for: digit

...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 --- a/rulefiles/linux/ignore.d.server/openvpn +++ b/rulefiles/linux/ignore.d.server/openvpn @@ -75,6 +75,11 @@ ^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ (openvpn|ovpn-[._[:alnum:]-]+)\[[[:digit:]]+\]:( ([-_.@[:alnum:]]+/)?[.[:digit:]]{7,15}:[[:digit:]]{2,5})? VERIFY (SCRIPT )?OK: depth=[[:digit:]]+, /[-:_./=@[:alnum:]]+$ ^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ (openvpn|ovpn-[._[:alnum:]-]+)\[[[:digit:]]+\]:( ([-_.@[:alnum:]...

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 XP. Thanks, Glenn #code h=12345.16711 h round(h,digit...

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, digits=0) [1...

...1 files changed, 4 insertions(+), 4 deletions(-) diff --git a/rulefiles/linux/ignore.d.server/postfix b/rulefiles/linux/ignore.d.server/postfix index be14415..2a6b554 100644 --- a/rulefiles/linux/ignore.d.server/postfix +++ b/rulefiles/linux/ignore.d.server/postfix @@ -29,10 +29,10 @@ ^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ postfix/policy-spf\[[[:digit:]]+\]: : SPF pass: smtp_comment=.*: [.[:alnum:]]+ MX [.[:alnum:]]+ A [[:digit:]a-f.:]+, header_comment=[.[:alnum:]]+: domain of [%[:punct:][:alnum:]]+@[.[:alnum:]]+ designates [[:xdigit:].:]{3,39} as permitted sender$ ^\w{3} [ :[:digit:]]{11} [._...

...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 ; old - using asterisk core function ; new - using this configuration file [digit-base](!) ; base rule for digit strings ; XXX incomplete yet _digit:[0-9] => digits/${SAY} _digit:[-] => letters/dash _digit:[*] => letters/star _digit:[@] => letters/at _digit:[0-9]. => digit:${SAY:0:1}, digit:${SAY:1} [date-...

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 McGe...

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 "9.99". I have not found anything explaining the whitespace in the help files. Therefore, I am writing to rep...

...simple switch on 'Zap/19-1' -- Starting simple switch on 'Zap/20-1' -- Starting simple switch on 'Zap/21-1' -- Starting simple switch on 'Zap/22-1' -- Starting simple switch on 'Zap/23-1' -- Executing Set("Zap/1-1", "TIMEOUT(digit)=5") in new stack -- Digit timeout set to 5 -- Executing WaitExten("Zap/1-1", "") in new stack -- Executing Set("Zap/2-1", "TIMEOUT(digit)=5") in new stack -- Digit timeout set to 5 -- Executing WaitExten("Zap/2-1", "&q...

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 <- subset(mylist,mylist[["Time"]] == minute) # Sort by Intensity frame <- frame[order(frame[["Intensity"]],decreasing = TRUE),] # Establish outpu...

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 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) The above is extreme: You're basically setting an option t...

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 = getOption("digits")) { if (length(digits) == 0L) stop("invalid 'digits'") if (all(ina <- i...

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...

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, digits=2,format="fg",flag="#") [1] "0.60" &gt...

...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 -- Playing 'digits/1' (language 'en') -- Playing 'digits/hundred' (language 'en') -- Playing 'digits/90' (language 'en') -- Playing 'digits/2' (language 'en') -- Playing 'digits/million' (language 'en') -- Playing 'di...

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 before they finish dialing...

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 printing the results of summary.glm() with show.residuals = TRUE if there's little dispersion in the residuals. Steve O...

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 >> 2...

.... Your zapsmall() proposal wouldn't zap it to zero, and I don't > see why summary() would if it was using your proposal. > > Duncan Murdoch > > On 17/12/2023 8:43 a.m., Gregory R. Warnes wrote: > > Isn?t that the correct outcome? The user can change the number of > digits if they want to see small values? > > > > > > -- > > Change your thoughts and you change the world. > > --Dr. Norman Vincent Peale > > > >> On Dec 17, 2023, at 12:11?AM, Steve Martin <stevemartin041 at gmail.com> > wrote: > >> > &gt...

...n the doc would clarify the situation but > > would not resolve proposed corner cases. > > > I think that an additional argument 'mx' (absolute max value of > > reference) would do. Consider: > > > zapsmall2 <- > > function (x, digits = getOption("digits"), mx=max(abs(x), na.rm=TRUE)) > > { > > ??? if (length(digits) == 0L) > > ??????? stop("invalid 'digits'") > > ??? if (all(ina <- is.na(x))) > > ??????? return(x) > > ??? round(x,...

>>>>> 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() here, of which prettyNum() is only a wrapper in this case): Here's an example that shows t...