search for: acuraci

Dear All, Hans Borchers and I have been trying to compute "exact" derivatives in R using the idea of complex-step derivatives that Hans has proposed. This is a really, really cool idea. It gives "exact" derivatives with only a minimal effort (same as that involved in computing first-order forward-difference derivative). Unfortunately, we cannot implement this in R as the

Hi Jean-Marc and list, Is the spx_fft function in fftwrap.c a standard fft function? void spx_fft(void *table, spx_word16_t *in, spx_word16_t *out) When I say standard, I mean the input "in" is 128 point short data for example and the output "out" is 128 short complex value which is stored in 256 short array with real and image part. Looks like the function did some

(keeping this on the list) William Zhang wrote: > I read the mdf.c an my understanding is that N is actually window size for > the FFT. The actual length L = N/2 which is the frame length. The > second part of the buffer is padded with the new frame data. So this is > like the overlap-save method for improving the acuracy in calculating > the fft of > long sequence of data?

Hi I believe the dt() function in stats has small areas of inaccuracy. SmallRangeMostDetaileddf150.png shows this occurring in the 10-11th decimal place. MyD4 is computed using Myt_NC(), at the bottom of BugL.R - my function is very slow due to using mpfr, but i believe accurate to the accuracy of genhypergeo() which it uses - 14-15 dp. LargeRangeDiffdf150.png, which is difference

Thanks for the explaination. Please see my questions and comment in lines. On 4/16/07, Jean-Marc Valin <jean-marc.valin@usherbrooke.ca> wrote: > (keeping this on the list) > > William Zhang wrote: > > I read the mdf.c an my understanding is that N is actually window size for > > the FFT. The actual length L = N/2 which is the frame length. The > > second part