search for: nspec

.../8)*taper*2) u4 <- (1 - (93/128)*taper*2) if (pad > 0) { x <- rbind(x, matrix(0, nrow = N * pad, ncol = ncol(x))) N <- nrow(x) } NewN <- if(fast) nextn(N) else N x <- rbind(x, matrix(0, nrow = (NewN - N), ncol = ncol(x))) N <- nrow(x) Nspec <- floor(N/2) freq <- seq.int(from = xfreq/N, by = xfreq/N, length.out = Nspec) xfft <- mvfft(x) pgram <- array(NA, dim = c(N, ncol(x), ncol(x))) for (i in 1L:ncol(x)) { for (j in i:ncol(x)) { # N0 = #{non-0-padded} pgram[, i, j] <- xfft[, i] * Con...

...using DTrace to track down a problem recently, we came across an unexpected restriction: the compiler will not permit different speculations to be committed in the same instance of a probe identifier. For instance, consider the following useless D script: #!/usr/sbin/dtrace -s #pragma D option nspec=2 BEGIN { spec1 = speculation(); spec2 = speculation(); } END { commit(spec1); commit(spec2); } # ./spec.d dtrace: failed to compile script ./spec.d: line 12: commit( ) may not follow commit( ) However, if the script is changed to: #!/usr/sbin/dtra...

...;blue") > spec.ar(ldeaths, add = TRUE) the resulting plots do not compare over the same frequency range. This results because spec.ar defines frequency as > freq <- seq.int(0, 0.5, length.out = n.freq) whereas spec.pgram uses > xfreq <- frequency(x) > N <- nrow(x) > Nspec <- floor(N/2) > freq <- seq.int(from = xfreq/N, by = xfreq/N, length.out = Nspec) And so the reason the spectral estimates of lh are similar is that frequency(lh) = 1, whereas frequency(ldeaths) = 12. The documentation seems more extensive for spec.pgram (and the pertinent section in MAS...

...#Number of depth intervals P.int = c(rep(0.07, 8),.12, .18,rep(0.21,3),rep(0.35,2), rep(0.42,2),rep(0.07, 8), rep(0.01, 5)) Z.int = P.int/7 N.int = c(rep(0.1, 13), rep(4.55, 5), rep(10,12)) state = c(P.int, Z.int, N.int) Time = seq(0,100, by = 1) NPZ.out <- ode.1D(state, Time, NPZ, params1, nspec = 3, names = c("P","Z","N")) After running for about 7 hours, the result returns: DLSODA- At current T (=R1), MXSTEP (=I1) steps taken on this call before reaching TOUT In above message, I = [1] 5000 In above message, R = [1] 0.0498949 Warning? 1: In lsoda(y[ii...

I'm trying to apply a function defined in the VW R docs, that attemps to convert a data.table object to Vowpal Wabbit format. In the process i'm getting the error in printf mentioned in the subject. The original function is here: https://github.com/JohnLangford/vowpal_wabbit/blob/master/R/dt2vw.R Below there is a small example that reproduces the error. The function works great with

dear R-friends, i`ve got a large dataset of vegetation-samples with about 500 variables(=species) in the following format: 1 spec1 1 spec23 1 spec54 1 spec63 2 spec1 2 spec2 2 spec253 2 spec300 2 spec423 3 spec20 3 spec88 3 spec121 3 spec200 3 spec450 . . this means: sample 1 (grassland) with the species (=spec) 1, 23, 54, 63 is it possible to get a following data-structure for further

This is v3 of my disk series. What were previously patches 01-06 have been applied. These are the tested and updated remainder, addressing the previous comments. 1 Preparatory work. 2-4 The new parser and its documentation. 5-6 Replace old parsers with calls to the new one. 7-8 Two features, one of them essential. 9 Basic test suite for disk string parsing, as adhoc script.

...let (book, use and release a Remote R > Instance via HTTP Tunneling) > - Use R to generate Graphics on the fly for thin web clients > - Use R from within a Workbench that includes an advanced script > editor, a Spreadsheet View fully connected to R data and functions, an > R Object Inspector, > composable and dockable Views, interactive R devices, clonable R > Graphics.. > - Use the Workbench from within a browser or via Java Web Start to > access a pool of Remote R Instances > - Use the Workbench to control on demand any Remote R Instance > - Provide a packaging f...