Building a Microscopy Application in Mathematica
September 9, 2011 — Jon McLoone , Director, Technical Communication & Strategy
As a change from my usual recreational content, today I thought I would describe a real Mathematica application that I wrote. The project came from my most important Mathematica user—not because she spends a lot of money with Wolfram Research, but because I am married to her!
Her company, Particle Therapeutics, works on needle-free injection devices that fire powdered drug particles into the skin on a supersonic gas shock wave. She was trying to analyze the penetration characteristics on a test medium by photographing thin slices of a target under a microscope and measuring the locations of the particles.
The problem was that her expensive image processing software was doing a poor job of identifying overlapping particles and gave her no manual override for its mistakes.
Faced with the alternative of holding rulers up to her screen and recording each value by hand, I promised that I could do better in Mathematica, with the added advantage that now her image processing tool would be integrated into her analysis code to go from image file to report document in a single workflow.
Here is a detail from a typical image:
The task breaks into three parts:
- Image processing
- An optimal GUI for adjusting parameters
- Report generation
Step 1 seems like it should be the hardest, but it can be achieved in very little code. First I need to clean up the image by deleting dirt and texture. DeleteSmallComponents removes small white dots within the particles; inverting and doing it again with a parameter lets me delete large black components up to the parameter size.
Once cleaned, I need to erode the components back to a single pixel. But I need multiple particles that slightly overlap to break apart and erode back to separate points. This “ultimate erosion” can be done by finding the local maxima of the DistanceTransform of the image.
I can then use ComponentMeasurements to get information on the identified points—in this case the coordinates of the center.
As a final cleanup, I use DeleteDuplicates to remove spurious points that come from badly shaped particles. I give a user parameter for how close points should be before they are considered the same. Here is all of that packaged into a function:
It turns out that, already, this does better than her image processing software, which was only capable of standard Erosion that treats all touching particles as one.
The hardest part is the GUI, because I want to give lots of control. Here is a video of the final application in action:
Let’s walk through each of those elements.
First I want this to be in a palette of its own, not in a notebook. But I want multiple instances to be able to be open at once. So my code starts by localizing variables into the window instance (not globally to the Mathematica session).
The main guts of the user interface (UI) are then just a Manipulate that first calls the identifyBlobs command, and then displays the results.
identifyBlobs will be called automatically when any of the parameters change, and the image will update automatically without any extra work.
The clever bit is the use of locators, which means that the “+” signs for the identified positions are not just for display, but can be changed by dragging them. With the LocatorAutoCreate option, I can Alt-click to add or remove points and automatically update the particle location data variable. That’s a lot of UI for one line of code.
The sliders for the left and right side of the surface line are just Manipulate controls, except that I choose vertical sliders rather than horizontal and place them in specific order. (It is possible to auto-detect the surface with ImageLines, but in some images the surface is so faint that this manual control is more practical.)
Then we have a button to load the data. It’s mostly error trapping code, but note the Method → “Queued” that prevents the Button from timing out if I spend time dithering about which file to open.
I hide the advanced controls using OpenerView, and I specify the layout of the controls inside that.
Finally, to make the scrollable area, all I have to do is set the ContentSize to manual, with an initial size:
Now on to reporting: I can’t share the details of the analysis she was doing, but here is a rough outline for how reporting works. Mathematica provides a complete document description language, so all I have to do is describe the layout and style of the document in terms of the individual visualizations and analysis that I have done.
This creates a new document that starts with three cells: first a static title, then some text summarizing results, and then a chart.
And that’s it.
In a sensible width window, UI, image processing, analysis, and report generation, including a few extra charts, amount to about 30 lines of code and can be deployed to Mathematica or Mathematica Player Pro.
To view the entire application put together, download this post as a Mathematica notebook.