4 ms·
Could you describe more in detail how your algorithm differs from a wavelet transform, if at all? The website doesn't say. You mention that your wavelet transf
by fluffything 7y ago
Could you describe more in detail how your algorithm differs from a wavelet transform, if at all? The website doesn't say.
You mention that your wavelet transform is "real-time", but the normal wavelet transform already is real time.. or what am I missing ?
- avaku 7y agoI guess you're missing the detail of how it's actually implemented in practice. The short description would be just "wavelet transform" I guess. The details is in how to implement it efficiently so that it can run on the phone in real-time, and draw the visualisation at the same time, without drowning the CPU (plus the additional feature of high-precision detection, which is not solved by wavelet transform itself). I will describe it in more details when I'll be open sourcing the algorithm (after I've implemented something on top of it that I could potentially start selling).
- fluffything 7y agoI see, thanks. FWIW, if your phone has an APU or GPU, it is quite easy to implement with CUDA. Is pretty much a massively parallel problem.
- avaku 7y agoThat would be hard to target different phones... I am just using SSE/AVX (via Apple's Accelerate framework) for now for some parallelisation, helps to speed up the detection x10.