search

foxsi / foxsi-smex

Tools for scientists to investigate the capabilities of FOXSI
MIT License
2 stars 8 forks source link

Deconvolution routines and example (in progress) #47

Open LinErinG opened 8 years ago

LinErinG commented 8 years ago

I'd like to make the method I use for image deconvolution available to everyone. This will probably take some iteration to get it usable by someone who didn't write the code, so I would appreciate if you can start trying it out. Please try the example in the IDL "docs" folder. If it works, please also try it for some other FOXSI simulated image that you might produce. Let me know what works and what breaks, and what is opaque and confusing. Thank you! @ehsteve @ayshih @aringlis @DanRyanIrish @PascalSH

ayshih commented 8 years ago

Here's my playing around with it (original/through-PSF/10-iteration-deconvolution): example

ayshih commented 8 years ago

Regarding the docs example, to my eye, ~10 iterations is way too many for the coronal source. ~5 iterations seems more appropriate.

LinErinG commented 8 years ago

@ayshih Thanks for trying this out! I'm pleased to see this recovered the original morphology quite well. This was probably a high-statistics case. In the future I think we can probably come up with some ad-hoc rule of max#iterations/#photons, though the tricky cases will be when we have somethings faint and bright together. For that, eventually, we'll need better stopping rules, but it's probably not necessary for the proposal.

I assume you generated a custom instrument response matrix; did this take a long time? I have designs on speeding this up for a future version.

ayshih commented 8 years ago

I assume you generated a custom instrument response matrix; did this take a long time?

The 256x64 matrix took about half an hour to generate (and the save file is a beefy ~1 GB).

LinErinG commented 8 years ago

Wow! Impressive. I've never tried it over such a large FOV (3 arcmin x 3 arcmin) before, on the thinking that it would never be necessary. There are certainly ways the transform calculation can be optimized, if people think FOVs larger than ~1 arcmin are something they'd like to do.