search for: maxf

R 1.4.1, Linux and Windows for(i in 1:1000) { X <- rnorm(i) XX <- fft(fft(X), inverse=T)/i if(max(Mod(XX-X)) > 1e-10) print(i) } [1] 392 [1] 588 [1] 968 [1] 980 and I then get a segfault during gc(). The answers are way off, with imaginary parts 1e10 or more. These numbers are all multiples of 7^2 or 11^2. (Based on a report to R-help Date: Thu, 28 Mar 2002 09:37:34

...be appreciated. thanks a lot. Mira ---------------------------------------------------------------------------------------------- #sub function for finding index rfind <- function(x)seq(along=x)[x*(1-x)>MAF*(1-MAF)] #sub function for permutation test perm.F = function(y,x,nperms,sites) { maxF = c(); for (i in 1:nperms) { F=numeric(S) #create an empty vector to store the F-values newY=sample(y,length(y)) #permute the cancer types newX = cbind(x, newY); # anova for all sites for ( i in sites ) { a <- anova(lm(newY~factor(newX[,i]))); F[i] &...

I have very large csv files (up to 1GB each of ASCII text). I'd like to be able to read them directly in to R. The problem I am having is with the variable length of the data in each record. Here's a (simplified) example: $ cat foo.csv Name,Start Month,Data Foo,10,-0.5615,2.3065,0.1589,-0.3649,1.5955

This message is in MIME format --_=XFMail.1.3.p0.Linux:990422185944:4782=_ Content-Type: text/plain; charset=us-ascii R-0.64.0 on RedHat Linux 5.1 Some problems with multivariate fast fourier transform. I have attached the dump of a 30 x 3 matrix that seems to reliably reproduce these problems 1) mvfft doesn't like vectors. It complains about not having enough memory: R>

...To is the total amount of sectors, Fo is the amount of free sectors for data Fs is the size of one FAT in sectors Cs is the cluster size Ss is the sector size Rs is the reserved sectors before the FAT's Re is the entries in the root-directory Fe is the FAT element size Nf is the number of FATs MaxFE is the maximum number of FAT entries As with the post above, we'll start with that last variable, since it is the one that is crucial to getting our computation right: MaxFatEn = Fs * Ss / Fe Now, if we follow Ady's post to compute the total number of sectors addressable, we want...

...s the amount of free sectors for data > Fs is the size of one FAT in sectors > Cs is the cluster size > Ss is the sector size > Rs is the reserved sectors before the FAT's > Re is the entries in the root-directory > Fe is the FAT element size > Nf is the number of FATs > MaxFE is the maximum number of FAT entries > > As with the post above, we'll start with that last variable, since it is > the one that is crucial to getting our computation right: > > MaxFatEn = Fs * Ss / Fe > > Now, if we follow Ady's post to compute the total numbe...

Hi Ady, On 2016.02.25 02:08, Ady via Syslinux wrote: > There is an "extra" sector, in comparison to... what exactly? Sorry if I wasn't clear. I think I implied that the Large FAT32 fat size had an extra sector compared to minfatsize, when of course I meant the opposite (the Large FAT32 has one less sector than the minfatsize computed by the unpatched code, hence the check

This patch series adds support for preservation of the VM generation ID buffer address in xenstore across save/restore and migrate, and also code to increment the value in all cases except for migration. The first patch modifies creation of the hvmloader key in xenstore and adds creation of a new read/write hvmloader/generation-id-addr key. The second patch changes hvmloader to use the new key (as

This patch series adds support for preservation of the VM generation ID buffer address in xenstore across save/restore and migrate, and also code to increment the value in all cases except for migration. The vast majority of the code is in second patch. The first patch merely changes the xenstore key name used by hvmloader to store the buffer address.

The following is a revised patch series to add support for a VM generation ID virtual device for HVM guests. The basic requirements of this device are as follows: - It must be exposed somewhere in ACPI namespace with a _CID of "VM_Gen_Counter". - It must also include a _DDN of "VM_Gen_Counter". - It must contain a _HID object but no particular value is required. - It must