search for: sweeps

Interrogating some (of my own) code in another package. >norm.meth <- getMethod("normalize", "MatrixLike") >message("str(norm.meth)") >str(norm.meth) >message("show(norm.meth at .Data)") >show(norm.meth at .Data) Last show() displays this: function (object, ...) { .local <- function (object, method = c("median",

I'm attempting to reflect the information for use with corresponding fields in GUI (in a different package), to provide default values, argname as key for UI label lookups, etc. So I want something much more like the formals of the implementation: { "object", "method": c("median", "vs", "tukey"),

Hi I had a hard-to-find bug in some of my code the other day, which I eventually traced to my misusing of sweep(). I would expect sweep() to give me a warning if the elements don't recycle nicely, but X <- matrix(1:36,6,6) sweep(X,1,1:5,"+") [,1] [,2] [,3] [,4] [,5] [,6] [1,] 2 9 16 23 30 32 [2,] 4 11 18 25 27 34 [3,] 6 13 20 22

...48 kbps compared to 96kHz Vorbis at 31kbps is about double the size and it sounds even worse (than Vorbis) (there is a lot of noise in the lower frequencies when a low frequency tone is being played). Here is what opusinfo outputs: Processing file "D:\Work\Ulrich\Musik\Vega\Opus\Audacity\Test-Sweeps\02 Sweep (0 -20kHz at 96kHz) log.opus"... New logical stream (#1, serial: 000028fd): type opus Encoded with libopus 1.3, libopusenc 0.2.1 User comments section follows... ENCODER=opusenc from opus-tools 0.2-3-gf5f571b ENCODER_OPTIONS=--bitrate 56 --vbr --comp 5 ALBUM=T...

I am having a hard time understanding just what 'sweep' does. The documentation states: Return an array obtained from an input array by sweeping out a summary statistic. So what does it mean "weeping out a summary statistic"? Thank you. Kevin

Hi, I would like to use sweep to "sweep out" proportions and confidence intervals for an array, however when I supply a function which returns a string (containing something like "9% (3-18%)") I get back a list instead of an array, here is a simplified example: # example showing that sweep does not return an array with same dimensions as STATS as advertised

Hi Jean-Marc and others, I put Speex support in Sweep (a sound editor) yesterday, and had some fun with it :) I'd like to get some feedback before releasing it publically. I'm not really used to speech codecs (I work more with music) but I've been quite impressed at the file size and quality (especially when you hear what I did with some of the sample files ;) I didn't have any

...f noise in the lower frequencies > when a low frequency tone is being played). Are you sure your speakers/headphones can even reproduce such low frequencies accurately? I doubt it. > Here is what opusinfo outputs: > > Processing file "D:\Work\Ulrich\Musik\Vega\Opus\Audacity\Test-Sweeps\02 Sweep (0 > -20kHz at 96kHz) log.opus"... > > New logical stream (#1, serial: 000028fd): type opus > Encoded with libopus 1.3, libopusenc 0.2.1 > User comments section follows... > ENCODER=opusenc from opus-tools 0.2-3-gf5f571b > ENCODER_OPTIONS=--bitrat...

...f noise in the lower frequencies > when a low frequency tone is being played). Are you sure your speakers/headphones can even reproduce such low frequencies accurately? I doubt it. > Here is what opusinfo outputs: > > Processing file "D:\Work\Ulrich\Musik\Vega\Opus\Audacity\Test-Sweeps\02 Sweep (0 > -20kHz at 96kHz) log.opus"... > > New logical stream (#1, serial: 000028fd): type opus > Encoded with libopus 1.3, libopusenc 0.2.1 > User comments section follows... > ENCODER=opusenc from opus-tools 0.2-3-gf5f571b > ENCODER_OPTIONS=--bitrat...

At this point I would just due: formals(body(method)[[2L]]) At some point we need to figure out what to do with this .local() confusion. On Wed, Jan 28, 2015 at 10:07 AM, Roebuck,Paul L <PLRoebuck at mdanderson.org> wrote: > I'm attempting to reflect the information for use with corresponding > fields in GUI (in a different package), to provide default values, > argname

On Jan 28, 2015, at 6:37 PM, Michael Lawrence <lawrence.michael at gene.com> wrote: > At this point I would just due: > > formals(body(method)[[2L]]) > > At some point we need to figure out what to do with this .local() confusion. Agreed, definitely. The current hack is to avoid re-matching arguments on method dispatch, so a fix would need to be fairly deep in the

The call to sweep in this function which was working in 0.62.2 is giving me trouble in 62.3: prcomponents <- function(x, center=TRUE, scale=TRUE, N=nrow(x)-1) {if (center) center <- apply(x,2,mean) else center <- rep(0, ncol(x)) if (scale) scale <- sqrt(apply(x,2,var)) else scale <- rep(1, ncol(x)) s <- svd(sweep(sweep(x,2, center),2, scale,

Would you please clarify your exact use case? Thanks, Michael On Wed, Jan 28, 2015 at 9:02 AM, Roebuck,Paul L <PLRoebuck at mdanderson.org> wrote: > Interrogating some (of my own) code in another package. > > >norm.meth <- getMethod("normalize", "MatrixLike") > >message("str(norm.meth)") > >str(norm.meth) > >

I decided to do a direct comparison of transpose and sweep. library(microbenchmark) NN <- matrix(c(1, 2, 3, 4, 5, 6), nrow = 2, byrow = TRUE) # Example matrix lambda <- c(2, 3, 4) # Example vector colNN <- t(NN) microbenchmark( sweep = sweep(NN, 2, lambda, "/"), transpose = t(t(NN)/lambda), colNN = colNN/lambda ) Unit: nanoseconds expr min lq

...sure your speakers/headphones can even reproduce >> >> such low frequencies accurately? I doubt it. >> >> >> >> > Here is what opusinfo outputs: >> >> > >> >> > Processing file "D:\Work\Ulrich\Musik\Vega\Opus\Audacity\Test‑Sweeps\02 >> > Sweep (0 >> >> > ‑20kHz at 96kHz) log.opus"... >> >> > >> >> > New logical stream (#1, serial: 000028fd): type opus >> >> > Encoded with libopus 1.3, libopusenc 0.2.1 >> >> > User comments section fol...

Hi all, To get wider visibility, build a broader consensus and address concerns on this topic, I'm again raising this as an RFC. This is a proposal to change the rule for variable names from CamelCase to camelBack _really this time_. Background: This has been proposed several times on this mailing list in the past. Most recent one was by Michael Platings in February this year [1], and there

A friend of mine just got bitten by the fact that sweep() will happily sweep out a STATS vector of an arbitrary length -- even one whose length is not a divisor of any of the margins -- without complaining. I know the answer to this could be "well just don't do that", but it's easy to make a mistake in which margin you're sweeping ... What would R-core think of the

[just so i don't end up with "why haven't you spoken up"] On Sun, Sep 8, 2019 at 1:32 AM Philip Reames via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > I do not support this. I feel the benefit is low, and the churn cost is high. > > I'm not strongly opposed or anything, I just don't believe this is worthwhile. Same thoughts. > Philip Roman

Given a long zoo matrix, the goal is to "sweep" out a statistic from the entire length of the sequences. longzoomatrix<-zoo(matrix(rnorm(720),ncol=6),as.yearmon(outer(1900,seq(0,length=120)/12,"+"))) cnames<-c(12345,23456,34567,45678,56789,67890) colnames(longzoomatrix)<-cnames longzoomatrix[1:24,] 12345 23456 34567 45678

rc<-list(c( 123,321,234,543,654,768,986,987,246,284),c("Jan","Feb","Mar","Apr","May","Jun","Jul","Aug","Sep","Oct","Nov","Dec")) # the matrix has rownames that are used as identifiers and columns # of time. 1 years worth of data. Thats the native format