>
> Normally with numerical stuff, diff wouldn't be easy unless you knock down precision
> but, even then you may often want to at least look at the noise. I think this wavelet
> transform is invertible and and should be "exact" ( you can transform integers to
> integers and invert if you do everything right). In this case, it may be easier to
> write an inverse wavelet transform and output the numerical differences between
> original and recovered sequences.
>
> More to the point, at least verify that the suspect code block is really guilty and
> try to disassemble it.
>
> Also, as far as speed, look at something like FFTW ( you can find stuff on google).
> They have lots of documentation and discussion posted in various places.
> Or, the link I posted earlier to Intel site should help. Don't just count instructions
> as memory access patterns can be a much bigger deal- think various shades or
> virtual memory.
>

I will do that. Thanx.

---

Explore the seven wonders of the world Learn more!