Timeline for Tooltip over Fourier transform of an image
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 10 at 0:12 | history | bounty ended | David G. Stork | ||
| Feb 9 at 16:41 | vote | accept | David G. Stork | ||
| Feb 6 at 17:55 | comment | added | Domen | @azerbajdzan, oh, thanks. I was under the impression that these won't get recalculated every time. Yes, the tooltip just shows the corresponding Fourier component at that particular wavelengths. One could multiply it with the magnitude of the FT, then it would depend on the actual image. | |
| Feb 6 at 17:52 | history | edited | Domen | CC BY-SA 4.0 |
deleted 19 characters in body
|
| Feb 6 at 17:46 | comment | added | azerbajdzan | By the way I do not get what the tooltip image should represent since it is totally independent of underlying image? Or maybe the question is more appropriate for OP. | |
| Feb 6 at 17:11 | comment | added | azerbajdzan |
Putting definitions of dims and imgFT inside first argument of DynamicModule such as: {pos, waves, dims = ImageDimensions[img], imgFT = ImagePeriodogram[img]} increases the speed.
|
|
| Feb 6 at 16:57 | comment | added | David G. Stork | Oh nice... excellent ($+1$). Let me wait just a bit to see if anyone gives a marked improvement, but if not I'll accept, as this nearly suffices, save for speed. (I wouldn't have thought that speed is too much of a problem because one merely needs to read a value and quickly plot a sine wave.) | |
| Feb 6 at 16:10 | history | answered | Domen | CC BY-SA 4.0 |