search for: caluculating

Question: How can I get access to the bias value of a boot statistic? Details: Boot function: boot(data, statistic, R, sim="ordinary", stype="i", strata=rep(1,n), L=NULL, m=0, weights=NULL, ran.gen=function(d, p) d, mle=NULL, ...) When I create an object, containing the bootstrap statistic (object <- boot (....))I can call it and will get an output

Hi, suppose I have a matrix (or dataframe) as a result from subsetting. mat <- matrix(1:20,ncol=2) mat[c(3,6,9),] <- NA cc <- complete.cases(mat) sub <- mat[cc,,drop=FALSE] sub <- sub * 2 #some caluculations with sub. now I would like to expand sub somehow so row 3,6, and 9 would be filled with NAs but the rest should be in place again. Is there a simple function for this?

Hello all I have a feeling this is very simple......but I am not sure how to do it My boss has two variables, one is an average of 4 numbers, the other is an average of 3 of those numbers i.e var1 = (X1 + X2 + X3 + X4)/4 var2 = (X1 + X2 + X3)/3 all of the X variables are supposed to be measuring similar constructs not surprisingly, these are highly correlated (r = .98), the question is how

I have browsed the archive, and played around with a whole bunch of ways of approaching the problem, and I cannot get the answer that I want. I have a list with 2000 elements. Each element is a data frame with 2 columns. As an example, see element 1999 below. [[1999]] H N 6 0.54 26 10 0.31 13 11 0.12 34 13 0.00 38 4 0.59 37 16 0.44 9 19 0.08 13 14 0.64 39 8

Hi * I encounter severe problems with changing ACL settings in Samba 3.0.2a after migrating users from NT PDC to LDAP-SAM. I did not find anything about this in the mailing list yet. However, I have no idea (if) what I am doing wrong here. Although I can hardly believe that I am the first one to trigger that bug, it looks like a problem with the sid_to_gid routine. So please take a look at that:

Hi, Thank you for you input! We tried that already. That, however, doesn't do the same thing. It is then simply a DFS server and not the "magical" msdfs proxy - yes the user can now click on a link to get to the desired spot, but the proxy function _automagically_ sends the user, when they access the msdfs share, to the netapp's readonly share without the extra click. And it

...e . ( that is not the case in ac3 , mp3 ) . The problems are ----> 1. How physcoacoustic model is generated . I was reading noise masking . I have understood that FFT of 2048 samples is used for finding tone masking . And MDCT of same samples is used for noise masking . Now while caluculating noise masking , logmdct input is used . And function bark_noise_hybridmp is called . In that function some mathematical computation is done and noise is calculate . ( noise[i] = R - offset ) Can anyone explain me what is the funda behind it . <p>2. NOw about overlap and add...

Hey, thanks for the input! I am looking into that. It is however a bit complicated due to the authentication lines and share connect lines being only related due to proximity in the log. It would probably work for most of the instances, but it would not be 100% viable, meaning we would be getting compaints and questions from our user "I ain't got that share?! WTF!!" I was going to

Well, this doesn't fix the preexec issue, but you might scan through the samba logs finding connections to the RO share, identify that IP address there, track back to Hostname and/or user who authenticated to that share and the use that as the basis for the email address. On Tue, May 19, 2015 at 12:38 PM, Greg Enlow <grenlow at hk.mailbox.de> wrote: > Hi, > > Thank you for you

Hi, I've got a problem with packed OGG files taking a long time to open before they start playing. I have about 30+ OGG files that I have joined together, now the engine I am working on has its own file management and when I use the OV open_callbaks it spends a long time constantly seeking and reading in different sets of 8500 bytes inside the open_callbacks function, some time for as

On Mon, May 18, 2015 at 03:31:55PM +0200, Greg Enlow wrote: > Hi, > > The Server to which the msdfs is pointing is a netapp. Though we theoretically can access the shell on it then begin to mess around there, we would really like to avoid that. Warranty and such make it a bit of a legal issue. That is the reason we went with a separate instance in the first place and now wonder why the