Skip to main content

dynamic - Slow image manipulation


This is some extremely simple code that shows an image and manipulates a circle (that will be used to select a region of the image to analyze). All those Dynamics eliminate some terrible lag, I understand the one for the circle, but why are the other necessary?


theImage = pickAnImage;  (*mine is 368 by 252*)
Manipulate[
circularSelector = Graphics[{Yellow, Dynamic[Circle[center, radius]]}];
xRange = Dynamic[{center[[1]] - radius, center[[1]] + radius}];
yRange = Dynamic[{center[[2]] - radius, center[[2]] + radius}];


Column[{Show[theImage, circularSelector],
xRange,
yRange}],

{{center, {184, 126}}, {0, 0}, {368, 252}, 1, Locator, Appearance -> None},
{{radius, 50}, 2, 100, 1, Appearance -> "Labeled"}]

Consider now adding one line of code to show the section of the image in the selection, something like


ImageTake[theImage,xRange,yRange],


Well, that doesn't work. It works if the Dynamics are removed from the definition of xRange and yRange, but then all the lag is back!:


theImage = pickAnImage;  (*mine is 368 by 252*)
Manipulate[
circularSelector = Graphics[{Yellow, Dynamic[Circle[center, radius]]}];
xRange = {center[[1]] - radius, center[[1]] + radius};
yRange = {center[[2]] - radius, center[[2]] + radius};

Column[{Show[theImage, circularSelector],
xRange,
yRange,

ImageTake[theImage, yRange, xRange]}],

{{center, {184, 126}}, {0, 0}, {368, 252}, 1, Locator, Appearance -> None},
{{radius, 50}, 2, 100, 1, Appearance -> "Labeled"}]

How do I fix this? More importantly, what's the reason behind it? When using Manipulate, I seem to run into lag and this Dynamic stuff seems to be behind it. I've checked the usual resources, but something as simple as this (A Manipulate with several images, or how to optimize code for snappiness) is rarely described.


EDIT: As requested by Nasser (thanks btw) I'm adding the code that doesn't work (selection is not shown):


theImage = pickAnImage;  (*mine is 368 by 252*)
Manipulate[
circularSelector =

Graphics[{Yellow, Dynamic[Circle[center, radius]]}];
xRange = Dynamic[{center[[1]] - radius, center[[1]] + radius}];
yRange = Dynamic[{center[[2]] - radius, center[[2]] + radius}];

Column[{Show[theImage, circularSelector],
xRange,
yRange,
ImageTake[theImage, yRange, xRange]}],

{{center, {184, 126}}, {0, 0}, {368, 252}, 1, Locator, Appearance -> None},

{{radius, 50}, 2, 100, 1, Appearance -> "Labeled"}]

As mentioned before, if the Dynamic are removed from xRange and yRange this works (second code above), but moving the circle is laggy compared to the first code (and it will get worst once more complex code is added).



Answer



The code is bit complicated, at least the prospect of explaining exactly what's going on seems complicated.


Roughly some principles that can help someone understand what's going on.




  1. In Manipulate[body, etc], anytime a variable that body depends on changes, body will be executed. Nested Dynamic and Refresh within body will make things more complicated (Ref: [1] etc.) You set a lot of variables in the body of your Manipulate. They cause the body to be reevaluated.





  2. Use Dynamic to isolate parts of the viewable output that can be updated independently. Dynamic[x] is not the same as x, but it will display as the value of x if and when it is displayed by the Front End. Thus ImageTake[theImage, Dynamic[{row1, row2}],..] won't work because it happens in the Kernel; and Dynamic[{row1, row2}] is not the same as {row1, row2}.




  3. Display theImage can take an appreciable amount of time if the image is large, especially if done multiple times whenever the Locator is moved. (If the image is small, one might not notice the slow down.)




  4. Generally global variables in Manipulate are bugs waiting to happen. That's not a particular issue here from what I see, but I offer it as general advice.







The easiest way to fix 1 is TrackedSymbols :> {center, radius}. It improves the performance, but theImage will be re-displayed, which will still cause a lag. Below I used Dynamic in places to isolated dynamic segments of the output and With to replace your global variables. With is nice in that it inserts code without creating a variable that will be tracked. To isolate theImage, I had to make the Column structure more complicated. I also made the domain for the Locator depend on the radius, which you may or may not have wanted. ;)


Manipulate[
With[{circularSelector = Graphics[{Yellow, Dynamic[Circle[center, radius]]}]},
Column[{Show[theImage, circularSelector],
Dynamic @ Column @
With[{
xRange = {center[[1]] - radius, center[[1]] + radius},
yRange = ImageDimensions[theImage][[2]] - center[[2]] + {-radius, +radius}},
{xRange,

yRange,
ImageTake[theImage, yRange, xRange]}]}]],
{{center, {184, 126}}, {radius, radius}, ImageDimensions@theImage - radius, 1,
Locator, Appearance -> None},
{{radius, 50}, 2, 100, 1, Appearance -> "Labeled"},
{{theImage, ExampleData[{"TestImage", "Mandrill"}]}, None}]

Mathematica graphics


(For the None specificiation, see this question.)


Comments

Popular posts from this blog

plotting - Plot 4D data with color as 4th dimension

I have a list of 4D data (x position, y position, amplitude, wavelength). I want to plot x, y, and amplitude on a 3D plot and have the color of the points correspond to the wavelength. I have seen many examples using functions to define color but my wavelength cannot be expressed by an analytic function. Is there a simple way to do this? Answer Here a another possible way to visualize 4D data: data = Flatten[Table[{x, y, x^2 + y^2, Sin[x - y]}, {x, -Pi, Pi,Pi/10}, {y,-Pi,Pi, Pi/10}], 1]; You can use the function Point along with VertexColors . Now the points are places using the first three elements and the color is determined by the fourth. In this case I used Hue, but you can use whatever you prefer. Graphics3D[ Point[data[[All, 1 ;; 3]], VertexColors -> Hue /@ data[[All, 4]]], Axes -> True, BoxRatios -> {1, 1, 1/GoldenRatio}]

plotting - Filling between two spheres in SphericalPlot3D

Manipulate[ SphericalPlot3D[{1, 2 - n}, {θ, 0, Pi}, {ϕ, 0, 1.5 Pi}, Mesh -> None, PlotPoints -> 15, PlotRange -> {-2.2, 2.2}], {n, 0, 1}] I cant' seem to be able to make a filling between two spheres. I've already tried the obvious Filling -> {1 -> {2}} but Mathematica doesn't seem to like that option. Is there any easy way around this or ... Answer There is no built-in filling in SphericalPlot3D . One option is to use ParametricPlot3D to draw the surfaces between the two shells: Manipulate[ Show[SphericalPlot3D[{1, 2 - n}, {θ, 0, Pi}, {ϕ, 0, 1.5 Pi}, PlotPoints -> 15, PlotRange -> {-2.2, 2.2}], ParametricPlot3D[{ r {Sin[t] Cos[1.5 Pi], Sin[t] Sin[1.5 Pi], Cos[t]}, r {Sin[t] Cos[0 Pi], Sin[t] Sin[0 Pi], Cos[t]}}, {r, 1, 2 - n}, {t, 0, Pi}, PlotStyle -> Yellow, Mesh -> {2, 15}]], {n, 0, 1}]

plotting - Mathematica: 3D plot based on combined 2D graphs

I have several sigmoidal fits to 3 different datasets, with mean fit predictions plus the 95% confidence limits (not symmetrical around the mean) and the actual data. I would now like to show these different 2D plots projected in 3D as in but then using proper perspective. In the link here they give some solutions to combine the plots using isometric perspective, but I would like to use proper 3 point perspective. Any thoughts? Also any way to show the mean points per time point for each series plus or minus the standard error on the mean would be cool too, either using points+vertical bars, or using spheres plus tubes. Below are some test data and the fit function I am using. Note that I am working on a logit(proportion) scale and that the final vertical scale is Log10(percentage). (* some test data *) data = Table[Null, {i, 4}]; data[[1]] = {{1, -5.8}, {2, -5.4}, {3, -0.8}, {4, -0.2}, {5, 4.6}, {1, -6.4}, {2, -5.6}, {3, -0.7}, {4, 0.04}, {5, 1.0}, {1, -6.8}, {2, -4.7}, {3, -1....