Re: Deconvolution advice

Posted by Gens, John Scott on
URL: http://confocal-microscopy-list.275.s1.nabble.com/Deconvolution-advice-tp7579090p7579094.html

*****
To join, leave or search the confocal microscopy listserv, go to:
http://lists.umn.edu/cgi-bin/wa?A0=confocalmicroscopy
*****

Andrew-

You might want to get in touch with Jim McNally.  Last I heard he was
at NIH-NCI.

Some of his older papers on deconvoltion algorithms are below, but he
can probably point
you towards more recent information.

http://www.ncbi.nlm.nih.gov/pubmed/10579932

http://www.ncbi.nlm.nih.gov/pubmed/11541650   ( in particular, fig.2  
compared  a 3D image processed by three different algorithms)


Quoting Andrew York <[hidden email]>:

> *****
> To join, leave or search the confocal microscopy listserv, go to:
> http://lists.umn.edu/cgi-bin/wa?A0=confocalmicroscopy
> *****
>
> Hello, I'm looking for advice and information about deconvolution,
> especially from those with first-hand experience.
>
> Traditionally, one of the processing steps in structured illumination
> microscopy is deconvolution. For our SIM, we decided to use an open-source
> solution:
> https://sites.google.com/site/piotrwendykier/software/deconvolution/paralleliterativedeconvolution
>
> This seemed like a nice tradeoff between reinventing the wheel with our own
> deconvolution code, and subjecting ourselves to a 'black box' closed-source
> solution. However, we've recently tried out the Huygens deconvolution
> software, and the results seem quite promising, possibly an improvement
> over other methods we've tried. I like good images, but I don't like black
> boxes, and I like to understand my data processing.
>
> 1. Is the exact algorithm used in Huygens transparently documented
> anywhere? I spent a few hours searching today, but if it's out there, I
> missed it.
>
> 2. Is there a clear winner for deconvolution algorithms? What should I be
> using?
>
> 3. Are there other deconvolution software packages I should consider?
> Ideally I'm looking for software based on clearly-documented algorithms.
>
> Thanks for the help.
>
> -Andrew York
> NIH/NIBIB
>