search for: 1e300

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 1e300. cell = fmax...

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/show_bug.cgi?id=1...

...t; Suharto Anggono Suharto Anggono via R-devel <r-devel at r-project.org> >>>>> on Fri, 11 Aug 2017 17:11:06 +0000 writes: > 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 . thank you. > *...

...the 32 bit architecture) on my Ubuntu 16.04.3 LTS machine. Specifically, a test in graphics-Ex.R seems to fail and the last lines of graphics-ex.Rout.fail are: > ## Extreme outliers; the "FD" rule would take very large number of 'breaks': > XXL <- c(1:9, c(-1,1)*1e300) > hh <- hist(XXL, "FD") # did not work in R <= 3.4.1; now gives warning Warning in hist.default(XXL, "FD") : 'breaks = 4.44796e+299' is too large and set to 1e9 Error in pretty.default(range(x), n = breaks, min.n = 1) : cannot allocate vector...

...tty.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 > 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) Thank you. "But" all these work now (in R-devel, rev >= 73094) as they should, at least for me, right? Are you mentioning th...

...r about pythag()'s availability from R's binary. As we say in above manual >> `pythag(A, B)' computes `sqrt(A^2 + B^2)' without overflow or >> destructive underflow: for example it still works when both A and >> B are between `1e200' and `1e300' (in IEEE double precision). -- "Problem" is : The GNU C library (and other C libraries ??) defines a function double hypot(double x, double y) with identical semantics to our pythag() from above The Info (e.g. in Linux Emacs C-h i "m libc") about "Libc" con...

...ror. Note that in rmultinom, the 'prob' is allowed to be *NOT* scaled to sum(.) = 1. Therefore 'Inf' makes sense as the limit (of a sequence) of (a) very large number(s). I claim that rmultinom(1, 3, c(1/2, 1/3, Inf)) should give the same as rmultinom(1, 3, c(1/2, 1/3, 1e300)) even without a warning, and OTOH, an NA in prob may return NA (and signal a warning) instead of an error. > For rgeom() or rbinom(), we got a warning for infinite probability : Yes, but there, prob must be in [0,1] ... so that's somewhat differnt. >> rbinom(1, 3, Inf)...

...d to be *NOT* > scaled to sum(.) = 1. > > Therefore 'Inf' makes sense as the limit (of a sequence) of (a) > very large number(s). > > I claim that > > rmultinom(1, 3, c(1/2, 1/3, Inf)) > > should give the same as > > rmultinom(1, 3, c(1/2, 1/3, 1e300)) > > even without a warning, That case makes sense, but is it worth the effort? Certainly rmultinom(1, 3, c(1/2, Inf, Inf)) can't give a useful answer because we don't know the relative size of the two infinities. I imagine the first NA comes from computing prob/sum(prob...

signif(.) is a <primitive> function. Unfortunately, I couldn't even find WHERE in the source, signif(.) is defined. Here are the symptoms: xmin <- .Machine $ double.xmin signif(xmin,3) #--> NA umach <- unlist(.Machine)[paste("double.x", c("min","max"), sep='')] for(dig in 1:10) {cat("dig=",dig,": ");

Dear all, Using rmultinom() in a stochastic model, I found this function returns an error message 'NA in probability' for an infinite probability. Maybe, a more precise message will be helpful when debugging. > rmultinom(1, 3:5, c(1/2, 1/3, Inf)) Error in rmultinom(1, 3:5, c(1/2, 1/3, Inf)) : NA in probability vector > rmultinom(1, 3:5, c(1/2, 1/3, NA)) Error in rmultinom(1,