search for: rep_len

...rsatility comes at a cost: it takes a bit of effort to learn (and remember) its syntax. This is a problem, since rep is one of the first functions many beginners will come across. Of the three main uses of rep, two have simpler alternatives. rep(x, times = ) has rep.int rep(x, length.out = ) has rep_len I think that a rep_each function would be a worthy addition for the third use case rep(x, each = ) (It might also be worth having rep_times as a synonym for rep.int.) While this could go in a package, since one of its main benefits is to help beginners, I feel it ought to go in base R. Before...

...takes a bit of effort to learn (and remember) its syntax. > This is a problem, since rep is one of the first functions many > beginners will come across. Of the three main uses of rep, two have > simpler alternatives. > > rep(x, times = ) has rep.int > rep(x, length.out = ) has rep_len > > I think that a rep_each function would be a worthy addition for the > third use case > > rep(x, each = ) > > (It might also be worth having rep_times as a synonym for rep.int.) I think this is exactly the wrong approach. Indeed, the aim should be to get rid of function...

...ical(test) n <- length(test) n.yes <- length(yes); n.no <- length(no) if (n.yes != n) { if (n.no == n) { # swap yes <-> no test <- !test ans <- yes; yes <- no; no <- ans n.no <- n.yes } else yes <- yes[rep_len(seq_len(n.yes), n)] } ans <- yes if (n.no == 1L) ans[!test] <- no else ans[!test & !is.na(test)] <- no[ if (n.no == n) !test & !is.na(test) else rep_len(seq_len(n.no), n)[!test & !is.na(test)]] stopifnot(length(NA.) ==...

...???? I think that for, say, lambda>1e6, rpois should return rnorm(., lambda, sqrt(lambda)). ????? For my particular Monte Carlo, I have replaced my call to rpois with a call to the following: ?rpois. <- function(n, lambda){ ????? n2 <- max(length(n), length(lambda)) ????? n <- rep_len(n, n2) ????? lambda <- rep_len(lambda, n2) # ????? big <- (lambda>1e6) ????? out <- rep(NA, n2) ????? out[big] <- rnorm(sum(big), lambda[big], sqrt(lambda[big])) ????? out[!big] <- rpois(sum(!big), lambda[!big]) ????? out ? } ????? Comments? ????? Thanks, ????? Spencer...

..., method = "radix"). I was mildly aware that data.table ordering has made it into base R but I first thought the grouping feature of forder had been removed. However in fact it is there but disabled. base::order lines 31-35 reads: if (method == "radix") { decreasing <- rep_len(as.logical(decreasing), length(z)) return(.Internal(radixsort(na.last, decreasing, FALSE, TRUE, ...))) } which is essentially: return(.Internal(radixsort(na.last, decreasing, retGrp, sortStr, ...))) with the retGrp arguments which returns the group starts and the maximum grou...

Hi, In R < 3.0.0, we used to get: > substring(c(A="abcdefghij", B="123456789"), 2, 6:2) A B A B A "bcdef" "2345" "bcd" "23" "b" But in R >= 3.0.0, we get: > substring(c(A="abcdefghij", B="123456789"), 2, 6:2) [1] "bcdef"

I can only reproduce on Windows, but reliably (both 4.0.0 and 4.0.2): $> R --vanilla x <- c(0L, -2e9:2e9) # > Segmentation fault Tried to reproduce on Linux but the above worked as expected. Not an issue merely with the length of the vector; for example, x <- rep_len(1:10, 1e10) works, though the altrep vector must be long to reproduce: x <- c(0L, -1e9:1e9) #ok Segmentation faults occur with the following too: x <- (-2e9:2e9) + 1L

...ps://github.com/tdhock/namedCapture-article/blob/master/figure-trackDb-pkgs.R I suspect that a fix can be accomplished by optimizing the implementation of substring, for the special case when the text/subject is a single element (character scalar). Right now I notice that the substring R code uses rep_len so that the text/subject which is passed to the C code is a character vector with the same length as the number of substrings to extract. Maybe the C code is calling strlen for each of these (identical) text/subject elements? Anyway, it would be useful to have some feedback to make sure this is in...

I propose a patch to ifelse that leverages anyNA(test) to achieve an improvement in performance. For a test vector of length 10, the change nearly halves the time taken and for a test of length 1 million, there is a tenfold increase in speed. Even for small vectors, the distributions of timings between the old and the proposed ifelse do not intersect. The patch does not intend to change the

...lpha = alpha)) if(rev) rev(cols) else cols } else character() } A bug fix would be to recycle alpha to the right length and only pass in portions of it, e.g. terrain.colors <- function (n, alpha, rev = FALSE) { if ((n <- as.integer(n[1L])) > 0) { alpha <- rep_len(alpha, length.out = n) k <- n%/%2 h <- c(4/12, 2/12, 0/12) s <- c(1, 1, 0) v <- c(0.65, 0.9, 0.95) cols <- c(hsv(h = seq.int(h[1L], h[2L], length.out = k), s = seq.int(s[1L], s[2L], length.out = k), v = seq.int(v[1L], v[2L], length.o...

Hi, I would have expected that I get always 3 colors as result which is not true: hcl.colors(3, alpha=c(0, 0.5, 1)) # 3 colors rainbow(3, alpha=c(0, 0.5, 1)) # 3 colors heat.colors(3, alpha=c(0, 0.5, 1)) # 3 colors terrain.colors(3, alpha=c(0, 0.5, 1)) # 6 colors cm.colors(3, alpha=c(0, 0.5, 1)) # 6 colors topo.colors(3, alpha=c(0, 0.5, 1)) # 9 colors R-Version and

....0.0 and 4.0.2): >> $> R --vanilla >> x <- c(0L, -2e9:2e9) >> # > Segmentation fault >> Tried to reproduce on Linux but the above worked as expected. Not an >> issue merely with the length of the vector; for example, x <- >> rep_len(1:10, 1e10) works, though the altrep vector must be long to >> reproduce: >> x <- c(0L, -1e9:1e9) #ok >> Segmentation faults occur with the following too: >> x <- (-2e9:2e9) + 1L > Your operation would "need" (not in theory, but in...

...blob/master/figure-trackDb-pkgs.R >> >> I suspect that a fix can be accomplished by optimizing the implementation >> of substring, for the special case when the text/subject is a single >> element (character scalar). Right now I notice that the substring R code >> uses rep_len so that the text/subject which is passed to the C code is a >> character vector with the same length as the number of substrings to >> extract. Maybe the C code is calling strlen for each of these (identical) >> text/subject elements? >> >> Anyway, it would be useful t...

...; >> x <- c(0L, -2e9:2e9) >> >> >> # > Segmentation fault >> >> >> Tried to reproduce on Linux but the above worked as expected. Not an >> >> issue merely with the length of the vector; for example, x <- >> >> rep_len(1:10, 1e10) works, though the altrep vector must be long to >> >> reproduce: >> >> >> x <- c(0L, -1e9:1e9) #ok >> >> >> Segmentation faults occur with the following too: >> >> >> x <- (-2e9:2e9) + 1L >> >&...

...x <- c(0L, -2e9:2e9) >> >> >> # > Segmentation fault >> >> >> Tried to reproduce on Linux but the above worked as expected. Not an >> >> issue merely with the length of the vector; for example, x <- >> >> rep_len(1:10, 1e10) works, though the altrep vector must be long to >> >> reproduce: >> >> >> x <- c(0L, -1e9:1e9) #ok >> >> >> Segmentation faults occur with the following too: >> >> >> x <- (-2e9:2e9)...

...X...1 1 Ben Franklin 2 Millard Fillmore 3 <NA> <NA> 4 <NA> <NA> Now to compare timings over multiple reps: lengths <- sort(outer(c(1, 2, 5), 10^(1:4))) reps <- 20 time_strcapture <- function(text, length, regex, proto, reps) { text <- rep_len(text, length) str <- system.time(for (i in seq_len(reps)) strcapture(regex, text, proto, perl = TRUE)) str2 <- system.time(for (i in seq_len(reps)) strcapture2(regex, text, proto, perl = TRUE)) c(strcapture = str[["user.self"]], strcapture2 = str2[["user.self"]...

...amedCapture-article/blob/master/figure-trackDb-pkgs.R > > I suspect that a fix can be accomplished by optimizing the implementation > of substring, for the special case when the text/subject is a single > element (character scalar). Right now I notice that the substring R code > uses rep_len so that the text/subject which is passed to the C code is a > character vector with the same length as the number of substrings to > extract. Maybe the C code is calling strlen for each of these (identical) > text/subject elements? > > Anyway, it would be useful to have some feedback...

...ws, but reliably (both 4.0.0 and 4.0.2): > $> R --vanilla > x <- c(0L, -2e9:2e9) > # > Segmentation fault > Tried to reproduce on Linux but the above worked as expected. Not an > issue merely with the length of the vector; for example, x <- > rep_len(1:10, 1e10) works, though the altrep vector must be long to > reproduce: > x <- c(0L, -1e9:1e9) #ok > Segmentation faults occur with the following too: > x <- (-2e9:2e9) + 1L Your operation would "need" (not in theory, but in practice) to go from alt...

...cols > } else character() > } > > > A bug fix would be to recycle alpha to the right length and only pass in > portions of it, e.g. > > terrain.colors <- function (n, alpha, rev = FALSE) > { > if ((n <- as.integer(n[1L])) > 0) { > alpha <- rep_len(alpha, length.out = n) > k <- n%/%2 > h <- c(4/12, 2/12, 0/12) > s <- c(1, 1, 0) > v <- c(0.65, 0.9, 0.95) > cols <- c(hsv(h = seq.int(h[1L], h[2L], length.out = k), > s = seq.int(s[1L], s[2L], length.out = k), > v =...

...ical(test) ? ? n <- length(test) ? ? n.yes <- length(yes); n.no <- length(no) ? ? if (n.yes != n) { ? ? ? ? if (n.no == n) {? # swap yes <-> no ? ? ? ? ? ? test <- !test ? ? ? ? ? ? ans <- yes; yes <- no; no <- ans ? ? ? ? ? ? n.no <- n.yes ? ? ? ? } else yes <- yes[rep_len(seq_len(n.yes), n)] ? ? } ? ? ans <- yes ? ? if (n.no == 1L) ? ? ? ? ans[!test] <- no ? ? else ? ? ? ? ans[!test & !is.na(test)] <- no[ ? ? ? ? ? ? if (n.no == n) !test & !is.na(test) ? ? ? ? ? ? else rep_len(seq_len(n.no), n)[!test & !is.na(test)]] ? ? stopifnot(length(NA.) ==...