Timeline for Wiggly and imprecise animated gif output
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 29, 2015 at 21:25 | vote | accept | მამუკა ჯიბლაძე | ||
| Nov 29, 2015 at 21:15 | comment | added | მამუკა ჯიბლაძე | (1) seems to work - reached 500 frames without problems and now trying more. As for (2), it depends on how often new circles grow perceptibly, if I am not mistaken this happens more frequently than once in 10 frames and then the animation would become jumpy. Will try though, maybe it will work. | |
| Nov 29, 2015 at 20:57 | comment | added | Michael E2 | (1) Converting each frame to a bitmap can save some memory at the expense of vector graphics. E.g. ColorConvert[Rasterize[frames[[1]], "Image", ImageSize -> 500], "Grayscale"] takes about 125KB. (2) Another idea is to compute every 10th frame or so and zoom in via changing the PlotRange (via something like Show[frame[[Ceiling[i/10]]], PlotRange -> {..}]) on a given frame 10 times before moving to the next frame. | |
| Nov 29, 2015 at 20:48 | comment | added | Michael E2 | @მამუკაჯიბლაძე Yes c and e are from the first program. I used the height; one could use width. One can guess what to multiply by (60*2 Pi in my code), or one could calculate. What looks good will depend on resolution of final images. This might look good and use less memory: Ceiling[Max[3, 15 2 Pi Sqrt[r/scale]]]. | |
| Nov 29, 2015 at 19:02 | comment | added | მამუკა ჯიბლაძე | Heigth definitely produces nice output, and is reasonably quick, but eats memory, at least in my case (4gb ram). After 500th frame it was swapping so wildly I could not even restart the system, had to switch the machine off by hand. Somehow I cannot figure out, is your scale designed in such way that one pixel radius requires one point only? | |
| Nov 29, 2015 at 18:16 | comment | added | მამუკა ჯიბლაძე | Oh I think i've got it, you mean c and e from my first code? The height itself? | |
| Nov 29, 2015 at 17:44 | comment | added | მამუკა ჯიბლაძე | Thanks! Looks quite promising and I tried but could not figure out what are c and e. I tried r/height (radius by size of the viewed rectangle) instead of your Abs[c-e], the cycle is almost as quick, but exporting seems to take too much time (it is still not finished). So I don't know what is the optimal scale, could you please explain? | |
| Nov 29, 2015 at 16:46 | history | edited | Michael E2 | CC BY-SA 3.0 | Added explanation |
| Nov 29, 2015 at 16:01 | history | edited | Michael E2 | CC BY-SA 3.0 | Fixed typo |
| Nov 29, 2015 at 15:34 | history | answered | Michael E2 | CC BY-SA 3.0 |