similar to: History of seq and seq.int

This is a message for someone familiar with the implementation. Superficially the R code for seq.default and the C code for seq.int appear to be semantically very similar. My question is whether, in fact, it is intended that behave identically for all inputs. I have found two cases so far where they differ, first that seq.int will coerce a character string to a real (via Rf_asReal) whereas

On 1/4/17 1:26 AM, Martin Maechler wrote: >>>>>> Mick Jordan <mick.jordan at oracle.com> >>>>>> on Tue, 3 Jan 2017 07:57:15 -0800 writes: > > This is a message for someone familiar with the implementation. > > Superficially the R code for seq.default and the C code for seq.int > > appear to be semantically very

I have a script that goes wrong because I assumed that seq.int would return integers. Below please see it does not unless user is super cautious about inserting "L" with inputs. I think seq.int should do coercion for me before returning the sequence. > xx <- seq.int(1,10) > class(xx) [1] "integer" > is.integer(xx) [1] TRUE > xx <- seq.int(1,10, 2) >

>>>>> Mick Jordan <mick.jordan at oracle.com> >>>>> on Tue, 3 Jan 2017 07:57:15 -0800 writes: > This is a message for someone familiar with the implementation. > Superficially the R code for seq.default and the C code for seq.int > appear to be semantically very similar. My question is whether, in fact, > it is intended that

Full_Name: Jens Oehlschl?gel Version: 2.10.1 OS: Windows XP Submission from: (NULL) (156.109.18.2) # fine as expected from help page: # "from+by, ..., up to the sequence value less than or equal to to" # thus 1+10=11 is not in > seq.int(1L, 10L, by=10L) [1] 1 # of course 1+1e7 should also not be in # but is: wrong > seq.int(1L, 1e7L, by=1e7L) [1] 1e+00 1e+07 # since we use

>>>>> Mick Jordan <mick.jordan at oracle.com> >>>>> on Wed, 4 Jan 2017 08:15:03 -0800 writes: > On 1/4/17 1:26 AM, Martin Maechler wrote: >>>>>>> Mick Jordan <mick.jordan at oracle.com> >>>>>>> on Tue, 3 Jan 2017 07:57:15 -0800 writes: >> > This is a message for someone familiar

... and also all objects that actually live in the .GenericArgsEnv environment. > all( sapply( ls( .GenericArgsEnv ), function(.) is.null(environment(.)) ) ) [1] TRUE This has the consequence preventing argsAnywhere to get the args of seq.int. > argsAnywhere( seq.int ) Error in exists(".packageName", envir = envir, inherits = FALSE) : use of NULL environment is defunct

The problem seems that ":" always coerces to integer, but should not.. 9.9:12 ## R: [1] 9 10 11 ## S-plus 3.4: [1] 9.9 10.9 11.9 ## and many more examples.... -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-devel mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html Send "info", "help", or

Pardon the barrage of time series related questions, but another issue I'm trying to solve is how to determine a sequence of dates a la seq.dates() except going BACKWARDS in time, e.g. if seq.dates() allowed for the "to" variables to be set alone, rather than the from=. Ultimately, I'd like to have a set of dates preceding a given date in predefined intervals (the same ones

Hello, in scilab /Matlab there are functions that can create linear sequences (like R's seq()) as well as logarithmic sequences. Is there a logarithmic aequivalent of seq()? Or maybe this would be an idea for newer R-releases, maybe a type-option with "linear" and "logarithmic" as parameters....?! Ciao, Oliver

Hi all, Is there any problem of precision when using seq?. For example: x<- seq(0,4,0.1) x[4]=0.3 BUT: x[4]-0.3=5.551115e-17 It means when I use this condition within an if clause, it does not find values with 0.3 for x[4] as it is not precisely 0.3. Is there any bug in seq() ? -- View this message in context: http://r.789695.n4.nabble.com/Inconsistency-using-seq-tp4633739.html Sent from

Using the IRanges package from Bioconductor and somewhat recent R-2.9.1. ov = IRanges(1:3, 4:6) length(ov) # 3 seq(along = ov) # 1 2 3 as wanted seq_along(ov) # 1! I had expected that the last line would yield 1:3. My guess is that somehow seq_along don't utilize that ov is an S4 class with a length method. The last line of the *Details* section of ?seq has a typeo. Currently it is

Dear all, ggplot gives me an error when trying to plot time series data using a date variable as the x axis. g<-structure(list(Date = c("2011-12-23", "2011-12-30", "2012-01-06", "2011-12-23", "2011-12-30", "2012-01-06", "2011-12-23", "2011-12-30", "2012-01-06"), variable = structure(c(1L, 1L, 1L, 2L, 2L,

In R, seq(0, 1, 0.1) gives the same result as (0:10)*0.1. It is not the same as c(0, 0.1, 0.2, 0.3, 0.4, 0.5, 0.6, 0.7, 0.8, 0.9, 1) , as 0.1 is not represented exactly. I am fine with it. In R, seq(0, 1, length=11) gives the same result as seq(0, 1, 0.1). However, for seq(0, 1, length=11), it is more accurate to return c(0, 0.1, 0.2, 0.3, 0.4, 0.5, 0.6, 0.7, 0.8, 0.9, 1) . It can be obtained by

Gabriel Becker writes: AFAIK R does not automatically copy function arguments. R actually tries very hard to avoid copying while maintaining "pass by value" functionality. ... R only copies data when you modify an object, not when you simply pass it to a function. This is a bit misleading. R tries to avoid copying by maintaining a count of how many references there are to an

Hello Peter, Thank you, and the R core team, for the new release. I see that in R 2.11.0 there is now support for rendering of raster (bitmap) images through rasterImage(). I am wondering - can this be used to create a texture/fill-pattern for hist()/barplot() ? (A request made several times throughout the years on the mailing list. For example:

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

HI: Could someone help me with the seq function? I have a range of values starting from 1 to 52 but I want seq to start at 27 by=2, but when it reaches 51 start with with number 1 to 25. is this possible. I can do the basics of seq() but I can't figure how to do this one. This is how I want my sequence to look like: 27 29 31 33 35 37 ............51 1 3 5 7 9 11 13 ...........25 Felipe D.

Dear List, I've been running a numerical simulation and I found this odd error in my code where the which command could not identify which rows of a column of data.frame were corresponding to the value 0.3. There are 7 unique values in this column (0.01,0.05,0.1,0.2,0.3,0.4,0.5), and this does not work only for 0.3. So I looked at the column and manually tried to use the which() command, and

Full_Name: Jeremiah Cohen Version: 2.9.0 OS: Windows XP Submission from: (NULL) (129.59.230.235) I believe there is a bug in the seq() function for certain values of the "from" argument. Here are examples: > seq(-.2, .1, .1) [1] -0.2 -0.1 0.0 0.1 > seq(-.3, .1, .1) [1] -3.000000e-01 -2.000000e-01 -1.000000e-01 5.551115e-17 1.000000e-01 > seq(-.4, .1, .1) [1] -0.4 -0.3