Re: [darktable-dev] Deconvolution and Python framework

[Aurélien PIERRE]

Hi !

I understand the performance concerns and I'm working on some trade off.
But…

1 - Non-blind Richardson-Lucy deconvolution by gradient descent with
Total Variation regularization (probably not the algorithm used in Gimp
since it's relatively recent) gives very good results in 25 iterations,
thus 16 s on my 2 Mpx test picture with a Python script (on an i7 Ivy
bridge laptop).

2 - Myopic deconvolution (the sort of "blind" deconvolution where you
give a good-enough initial guess of the blur profile) converges faster
than the blind one,

3 - The most computation-demanding operation is convolution product (2
FFT-convolve by non blind iteration, 4 by blind iteration). The good
news is we don't need to compute them on the whole picture (it's
actually bad when you have a large bokeh area) and you can/should mask
the area of interest and do the computations only on it. It saves a lot
of time and gives better results on some cases.

4 - It should be possible to deconvolve the RAW pic first, cache it,
then apply the further edits on the cached picture (similar to the HDR
workflow).

5 - Piccur uses a myopic deconvolution (from what I have understood),
and seems to offer rather decent time/quality ratio. Also, ImageJ has a
similar open-source plugin
(http://imagej.net/Parallel_Iterative_Deconvolution) which code could be
of interest.

Thanks for your interest !

*Aurélien PIERRE*
aurelienpierre.com 



Le 2017-10-11 à 14:59, Heiko Bauke a écrit :
> Hi,
>
> Am 11.10.2017 um 19:11 schrieb Martin Marmsoler:
>> Gimp use python as scripting language. It might be easier to port for
>> Gimp?
>
> by the way: there is a Richardson Lucy sharpening filter in G'MIC. 
> (As far as I understand this is a non-blind deconvolution algorithm.)
>
>
> Heiko
>


___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Deconvolution and Python framework

[Heiko Bauke]

Hi,

Am 11.10.2017 um 19:11 schrieb Martin Marmsoler:

Gimp use python as scripting language. It might be easier to port for Gimp?


by the way: there is a Richardson Lucy sharpening filter in G'MIC.  (As 
far as I understand this is a non-blind deconvolution algorithm.)



Heiko

--
-- Number Crunch Blog @ https://www.numbercrunch.de
--  Cluster Computing @ http://www.clustercomputing.de
--   Professional @ https://www.mpi-hd.mpg.de/personalhomes/bauke
--  Social Networking @ https://www.researchgate.net/profile/Heiko_Bauke
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Fixing the scroll-bar issue

[Rolf Meyerhoff]

Hi

DT has actually two scrollbars for the lighttable. One is located at the
outer most right edge and one at the outer most left edge of the main
window.

However, they are not accessible with a mouse because they're overlaid
by the 'side panel open/close click areas' (or whatever they're called).
The side panels have their own scrollbars.

It always annoyed me that I could see the scrollbars but I couldn't use
them. It would be great of someone could fix that.

Stock Kubuntu 16.4 with current git DT.

Rolf


Am 11.10.2017 um 19:12 schrieb Roman Lebedev:
> On Wed, Oct 11, 2017 at 8:04 PM, Jørn Villesen Christensen
>  wrote:
>> Hi there,
> Hi.
>
>> I have been using Darktable from time to time and think I will be using it
>> more in the future. I have a few ideas of what modules I would like to see
>> in Darktable and I thought I might throw in a few hours myself.
>>
>> Short about me: I have been working 7 years now as a software developer and
>> architect in a Windows oriented environment. Mostly I have been working with
>> Delphi, C#, and C++. In my private life I have been running Linux for ~15
>> years and done some C++ programming - but without GUI.
>> In order to get started and to do something useful, I thought I would look
>> at a bug that I also find annoying. It is described in these two bug
>> reports:
>>   https://redmine.darktable.org/issues/10947
>>   https://redmine.darktable.org/issues/10711
> You should have pointed to https://redmine.darktable.org/issues/9439
>
>> My idea was basically to move the scrollbar from the outer position (where
>> it is currently) to just next to the film roll. See attached photo.
> Which scrollbar? There is a scrollbar for the sidepanels.
> There is no scrollbar for the lighttable view itself.
>
>> Questions:
>>  a) Are there already other people working on solving these bugs?
>>  b) Does my proposed solution seem like a good idea?
>>  c) Would you have any pointers to me on how to get started (which files I
>> should look into or other tips on how *you* would go about solving this).
>>
>> BR
>> Jørn Christensen
> Roman.
>
>> ___
>> darktable developer mailing list
>> to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
>

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Fixing the scroll-bar issue

[Roman Lebedev]

On Wed, Oct 11, 2017 at 8:04 PM, Jørn Villesen Christensen
 wrote:
> Hi there,
Hi.

> I have been using Darktable from time to time and think I will be using it
> more in the future. I have a few ideas of what modules I would like to see
> in Darktable and I thought I might throw in a few hours myself.
>
> Short about me: I have been working 7 years now as a software developer and
> architect in a Windows oriented environment. Mostly I have been working with
> Delphi, C#, and C++. In my private life I have been running Linux for ~15
> years and done some C++ programming - but without GUI.

> In order to get started and to do something useful, I thought I would look
> at a bug that I also find annoying. It is described in these two bug
> reports:
>   https://redmine.darktable.org/issues/10947
>   https://redmine.darktable.org/issues/10711
You should have pointed to https://redmine.darktable.org/issues/9439

> My idea was basically to move the scrollbar from the outer position (where
> it is currently) to just next to the film roll. See attached photo.
Which scrollbar? There is a scrollbar for the sidepanels.
There is no scrollbar for the lighttable view itself.

> Questions:
>  a) Are there already other people working on solving these bugs?
>  b) Does my proposed solution seem like a good idea?
>  c) Would you have any pointers to me on how to get started (which files I
> should look into or other tips on how *you* would go about solving this).
>
> BR
> Jørn Christensen
Roman.

> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Deconvolution and Python framework

[Martin Marmsoler]

Gimp use python as scripting language. It might be easier to port for Gimp?

Am 11.10.2017 17:55 schrieb "Jean-Luc Coulon (f5ibh)" <
jean.luc.cou...@gmail.com>:

> > but those "challenges" would only affect a small sub-set of dt users
> *every* "challenge affect only a small subset of dt users…
> Only base curve, demosaicing, light-contrast-saturation affect everybody ;)
>
> 2017-10-11 17:34 GMT+02:00 Patrick Shanahan :
>
>> * Jørn Villesen Christensen  [10-11-17 11:25]:
>> > On 2017-10-11 15:35, Pete Hall wrote:
>> > >Just an opinion from a devoted user... It might be a very useful tool
>> for
>> > >me. I shoot a lot of sporting events. It's common for me to find a
>> great
>> > >shot ruined because at the critical moment, the camera focused on the
>> > >wrong player, or on the goal keeper's net. Even if it can't be made
>> > >efficient for the normal workflow, it could still be a very useful
>> tool,
>> > >at least for me.
>> >
>> > Same for me - I think that would be an awesome feature, although I am
>> kind
>> > of sceptical that it will be the magical bullet for you, Pete ;-)
>> >
>> > But nonetheless, I hope that it will be possible to fit this
>> functionality
>> > into the workflow of Darktable - although I do see the challenges with
>> the
>> > time requirements.
>>
>> but those "challenges" would only affect a small sub-set of dt users, the
>> same as those working low-light and/or high-noise images.  and you can
>> prioritize usage, work those modules last to minimize delays.
>>
>> --
>> (paka)Patrick Shanahan   Plainfield, Indiana, USA  @ptilopteri
>> http://en.opensuse.orgopenSUSE Community Member
>> facebook/ptilopteri
>> Registered Linux User #207535@
>> http://linuxcounter.net
>> Photos: http://wahoo.no-ip.org/piwigo   paka @ IRCnet
>> freenode
>> 
>> ___
>> darktable developer mailing list
>> to unsubscribe send a mail to darktable-dev+unsubscribe@list
>> s.darktable.org
>>
>>
>
> ___
> darktable developer mailing list to unsubscribe send a mail to
> darktable-dev+unsubscr...@lists.darktable.org
>

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

[darktable-dev] Fixing the scroll-bar issue

[Jørn Villesen Christensen]

Hi there,

I have been using Darktable from time to time and think I will be using 
it more in the future. I have a few ideas of what modules I would like 
to see in Darktable and I thought I might throw in a few hours myself.


Short about me: I have been working 7 years now as a software developer 
and architect in a Windows oriented environment. Mostly I have been 
working with Delphi, C#, and C++. In my private life I have been running 
Linux for ~15 years and done some C++ programming - but without GUI.


In order to get started and to do something useful, I thought I would 
look at a bug that I also find annoying. It is described in these two 
bug reports:

  https://redmine.darktable.org/issues/10947
  https://redmine.darktable.org/issues/10711

My idea was basically to move the scrollbar from the outer position 
(where it is currently) to just next to the film roll. See attached photo.


Questions:
 a) Are there already other people working on solving these bugs?
 b) Does my proposed solution seem like a good idea?
 c) Would you have any pointers to me on how to get started (which 
files I should look into or other tips on how *you* would go about 
solving this).


BR
Jørn Christensen


___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Deconvolution and Python framework

[Jean-Luc Coulon (f5ibh)]

> but those "challenges" would only affect a small sub-set of dt users
*every* "challenge affect only a small subset of dt users…
Only base curve, demosaicing, light-contrast-saturation affect everybody ;)

2017-10-11 17:34 GMT+02:00 Patrick Shanahan :

> * Jørn Villesen Christensen  [10-11-17 11:25]:
> > On 2017-10-11 15:35, Pete Hall wrote:
> > >Just an opinion from a devoted user... It might be a very useful tool
> for
> > >me. I shoot a lot of sporting events. It's common for me to find a great
> > >shot ruined because at the critical moment, the camera focused on the
> > >wrong player, or on the goal keeper's net. Even if it can't be made
> > >efficient for the normal workflow, it could still be a very useful tool,
> > >at least for me.
> >
> > Same for me - I think that would be an awesome feature, although I am
> kind
> > of sceptical that it will be the magical bullet for you, Pete ;-)
> >
> > But nonetheless, I hope that it will be possible to fit this
> functionality
> > into the workflow of Darktable - although I do see the challenges with
> the
> > time requirements.
>
> but those "challenges" would only affect a small sub-set of dt users, the
> same as those working low-light and/or high-noise images.  and you can
> prioritize usage, work those modules last to minimize delays.
>
> --
> (paka)Patrick Shanahan   Plainfield, Indiana, USA  @ptilopteri
> http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri
> Registered Linux User #207535@ http://linuxcounter.net
> Photos: http://wahoo.no-ip.org/piwigo   paka @ IRCnet freenode
> 
> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscribe@
> lists.darktable.org
>
>

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Deconvolution and Python framework

[Patrick Shanahan]

* Jørn Villesen Christensen  [10-11-17 11:25]:
> On 2017-10-11 15:35, Pete Hall wrote:
> >Just an opinion from a devoted user... It might be a very useful tool for
> >me. I shoot a lot of sporting events. It's common for me to find a great
> >shot ruined because at the critical moment, the camera focused on the
> >wrong player, or on the goal keeper's net. Even if it can't be made
> >efficient for the normal workflow, it could still be a very useful tool,
> >at least for me.
> 
> Same for me - I think that would be an awesome feature, although I am kind
> of sceptical that it will be the magical bullet for you, Pete ;-)
> 
> But nonetheless, I hope that it will be possible to fit this functionality
> into the workflow of Darktable - although I do see the challenges with the
> time requirements.

but those "challenges" would only affect a small sub-set of dt users, the
same as those working low-light and/or high-noise images.  and you can
prioritize usage, work those modules last to minimize delays.  

-- 
(paka)Patrick Shanahan   Plainfield, Indiana, USA  @ptilopteri
http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri
Registered Linux User #207535@ http://linuxcounter.net
Photos: http://wahoo.no-ip.org/piwigo   paka @ IRCnet freenode
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Deconvolution and Python framework

[Jørn Villesen Christensen]

On 2017-10-11 15:35, Pete Hall wrote:
Just an opinion from a devoted user... It might be a very useful tool 
for me. I shoot a lot of sporting events. It's common for me to find a 
great shot ruined because at the critical moment, the camera focused on 
the wrong player, or on the goal keeper's net. Even if it can't be made 
efficient for the normal workflow, it could still be a very useful tool, 
at least for me.


Same for me - I think that would be an awesome feature, although I am 
kind of sceptical that it will be the magical bullet for you, Pete ;-)


But nonetheless, I hope that it will be possible to fit this 
functionality into the workflow of Darktable - although I do see the 
challenges with the time requirements.


~Jørn
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Deconvolution and Python framework

[Patrick Shanahan]

* Pete Hall  [10-11-17 09:37]:
> Just an opinion from a devoted user... It might be a very useful tool
> for me.  I shoot a lot of sporting events.  It's common for me to find a
> great shot ruined because at the critical moment, the camera focused on
> the wrong player, or on the goal keeper's net.  Even if it can't be made
> efficient for the normal workflow, it could still be a very useful tool,
> at least for me.
> 
> On October 11, 2017 3:03:44 AM CDT, Heiko Bauke  wrote:
> >Dear Aurélien,
> >
> >Am 10.10.2017 um 10:25 schrieb Aurélien PIERRE:
> >> Following my work from this Summer, I'm glad to propose my first
> >blind 
> >> deconvolution algorithm, written in Python, based on papers from 
> >> 2011-2014  : https://github.com/aurelienpierre/Image-Cases-Studies
> >> 
> >> TL;DR :
> >> 
> >> Blind deconvolution is a technique used in astronomy and microscopy
> >to 
> >> deblur pictures based on an estimation of the blur "profile" (SPF for
> >
> >> the geeks). This work on motion blur, focus blur, etc. A commercial 
> >> photo software get spectacular results with this technique : 
> >> http://relaunch.piccureplus.com/ (although it's not really blind).
> >> 
> >> My code is a proof of concept which runs now (barely optimized)
> >between 
> >> 50 and 275 s on a 2 Mpx image.
> >> 
> >> I'm still looking for some help to port it in a Darktable module,
> >since 
> >> I'm not a C developper (or at least some doc).
> >
> >I am still rather skeptic regarding the question if a blind 
> >deconvolution algorithm fits into the darktable workflow.  It may be 
> >computationally too demanding.  Nevertheless, this is a very
> >fascinating 
> >topic and I will have a look at your code.  Thanks for your efforts.
> >
> >
> > Heiko
> >
> >
> >-- 
> >-- Number Crunch Blog @ https://www.numbercrunch.de
> >--  Cluster Computing @ http://www.clustercomputing.de
> >--   Professional @ https://www.mpi-hd.mpg.de/personalhomes/bauke
> >--  Social Networking @
> >https://www.researchgate.net/profile/Heiko_Bauke
> >___
> >darktable developer mailing list
> >to unsubscribe send a mail to
> >darktable-dev+unsubscr...@lists.darktable.org
> 
> 
> --
> Pete Hall
> p...@hallcircus.net
> 608-290-0731
> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
> 

I agree with this.  I also shoot a lot of soccer and loose some good shots
because of errant focus.

-- 
(paka)Patrick Shanahan   Plainfield, Indiana, USA  @ptilopteri
http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri
Registered Linux User #207535@ http://linuxcounter.net
Photos: http://wahoo.no-ip.org/piwigo   paka @ IRCnet freenode
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Error in compiled libexr.so

[Jonathan Richards]

On 08/10/17 20:38, Jonathan Richards wrote:
> On 08/10/17 19:30, Roman Lebedev wrote:
>> On Sun, Oct 8, 2017 at 9:25 PM, Jonathan Richards
>>  wrote:
>>> Hi
>>> I built darktable from the git head on 1 Oct, and everything seemed to
>>> go smoothly; I have been working with JPG, TIFF and Panasonic RW2 files
>>> successfully.  However, when I start darktable from the command line, I
>>> get a message about an error in libexr.so:
>>>
>>> jonathan@Odin:~$ darktable &
>>> [1] 12137
>>> jonathan@Odin:~$ [imageio_load_module] failed to open format `exr':
>>> /opt/darktable/lib/darktable/plugins/imageio/format/libexr.so: undefined
>>> symbol:
>>> _ZNK7Imf_2_014TypedAttributeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIc12writeValueToERNS_7OStreamEi
>> There is some kind of mismatch in openexr versions.
> Oh, OK.  This is what I currently have, maybe the libraries were
> included in updated packages since 1 Oct.
> jonathan@Odin:~$ dpkg -l | grep -i exr
> ii  libilmbase12:amd64  2.2.0-11ubuntu2 amd64several utility
> libraries from ILM used by OpenEXR
> ii  libopenexr-dev  2.2.0-10ubuntu2 amd64development files
> for the OpenEXR image library
> ii  libopenexr22:amd64  2.2.0-10ubuntu2 amd64runtime files for
> the OpenEXR image library
> 
>> Try purging /opt/darktable and the build dir (!!!), and build from scratch.
>> Does it still happen then?
> I'll give that a try shortly, and report back.  Thanks for the swift reply.
>>
>>> Maybe I'm missing some header files?  Please let me know what
>>> information I need to supply.  Grateful for any help; as I say it's not
>>> actually hindering my use of darktable.
>>>
>>> Thanks,
>>> Jonathan
>> Roman.
> Jonathan
>>
>>> Platform info:
>>> jonathan@Odin:~$ uname -a
>>> Linux Odin 4.10.0-35-generic #39~16.04.1-Ubuntu SMP Wed Sep 13 09:02:42
>>> UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
>>>
>>> KDE Neon User LTS Edition 5.8
>>>
>>> jonathan@Odin:~$ file
>>> /opt/darktable/lib/darktable/plugins/imageio/format/libexr.so
>>> /opt/darktable/lib/darktable/plugins/imageio/format/libexr.so: ELF
>>> 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked,
>>> BuildID[sha1]=c92c020e24600e0d4b7656bb9f612b70db8dfb6a, not stripped
>>> ___
>>> darktable developer mailing list
>>> to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
>>>
>>
> 
Hi, all
I did as Roman suggested, deleting and re-creating the build directory,
and using the "manual" build method in the README, capturing output as I
went along, and with an added 'make clean' before 'make'.
In summary, cmake warns about LLVM version (it's 3.9, DT seems to want
4.0), and partially missing OpenJPG (probably not relevant?).
'make' completes with only a couple of warnings about variable-length
arrays (in colortransfer and thinplate, probably also irrelevant).
Install proceeds without error, but the OpenEXR plugin still doesn't
work when starting darktable:
[imageio_load_module] failed to open format `exr':
/opt/darktable/lib/darktable/plugins/imageio/format/libexr.so: undefined
symbol:
_ZNK7Imf_2_014TypedAttributeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIc12writeValueToERNS_7OStreamEi

More detailed log extracts available if needed.
I see at openexr.com that version 2.2.0 is the current version.  Would
it help to compile it myself instead of using the Ubuntu packages?

Regards
Jonathan
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] possible data loss scenario

[Jonathan Richards]

On 10/10/17 18:11, Alexander Rabtchevich wrote:
> Hello
> 
> And the scenario is still working.
> 1. Select an image in the lighttable mode.
> 2. Click into the edit window Max size in the export dialog.
> 3. Move mouse just slightly outside the edit window. It loses focus
> immediately.
> 4. Type the digit you want. It is recognized as rating for the image
> being selected.
> 
> The item 3 is the problematic one. Why does the edit control loose
> focus? One haven't clicked outside the control. A mouse is not
> guaranteed to keep its exact position just after it has been released -
> and it _is_ released to type digits on a keyboard.
> 
> With respect,
> Alexander Rabtchevich
> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
> 
> 
Roman, Alexander
As it happens, I have just recompiled darktable version
2.3.0+971~gf092843 on my system, and I followed Alexander's scenario,
given above.
At step 3, the edit window *keeps* the focus, and I can continue to type
in it even if I move the mouse cursor all the way back over the
lighttable pane.
My hardware is AMD Phenom II CPU, nVidia GeForce 460 GPU.  Software is
KDE Neon LTS User Edition 5.8, KDE Framework 5, Plasma desktop, nVidia
drivers version 375.82
Neon is using Xorg:
jonathan@Odin:~$ ps -ef | grep X
root  1205  1192  3 13:21 tty7 00:02:44 /usr/lib/xorg/Xorg
-nolisten tcp -auth /var/run/sddm/{b2c334be-1a6a-4ae0-8858-0511d6b0c079}
-background none -noreset -displayfd 18 vt7

Xorg version information:
$ /usr/lib/xorg/Xorg -version 2>&1

X.Org X Server 1.19.3
Release Date: 2017-03-15
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.4.0-87-generic x86_64 Ubuntu
Current Operating System: Linux Odin 4.10.0-35-generic
#39~16.04.1-Ubuntu SMP Wed Sep 13 09:02:42 UTC 2017 x86_64
Kernel command line: BOOT_IMAGE=/vmlinuz-4.10.0-35-generic
root=UUID=ddb4c2a2-33b1-4edf-99bc-322be3d2badc ro quiet splash vt.handoff=7
Build Date: 25 July 2017  01:30:08PM
xorg-server 2:1.19.3-1ubuntu1~16.04.2 (For technical support please see
http://www.ubuntu.com/support)
Current version of pixman: 0.33.6

Happy to help drive out this bug, if I can.  I hate data loss!!

Regards

Jonathan

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Deconvolution and Python framework

[Pete Hall]

Just an opinion from a devoted user... It might be a very useful tool for me. I 
shoot a lot of sporting events. It's common for me to find a great shot ruined 
because at the critical moment, the camera focused on the wrong player, or on 
the goal keeper's net. Even if it can't be made efficient for the normal 
workflow, it could still be a very useful tool, at least for me.

On October 11, 2017 3:03:44 AM CDT, Heiko Bauke  wrote:
>Dear Aurélien,
>
>Am 10.10.2017 um 10:25 schrieb Aurélien PIERRE:
>> Following my work from this Summer, I'm glad to propose my first
>blind 
>> deconvolution algorithm, written in Python, based on papers from 
>> 2011-2014  : https://github.com/aurelienpierre/Image-Cases-Studies
>> 
>> TL;DR :
>> 
>> Blind deconvolution is a technique used in astronomy and microscopy
>to 
>> deblur pictures based on an estimation of the blur "profile" (SPF for
>
>> the geeks). This work on motion blur, focus blur, etc. A commercial 
>> photo software get spectacular results with this technique : 
>> http://relaunch.piccureplus.com/ (although it's not really blind).
>> 
>> My code is a proof of concept which runs now (barely optimized)
>between 
>> 50 and 275 s on a 2 Mpx image.
>> 
>> I'm still looking for some help to port it in a Darktable module,
>since 
>> I'm not a C developper (or at least some doc).
>
>I am still rather skeptic regarding the question if a blind 
>deconvolution algorithm fits into the darktable workflow.  It may be 
>computationally too demanding.  Nevertheless, this is a very
>fascinating 
>topic and I will have a look at your code.  Thanks for your efforts.
>
>
>   Heiko
>
>
>-- 
>-- Number Crunch Blog @ https://www.numbercrunch.de
>--  Cluster Computing @ http://www.clustercomputing.de
>--   Professional @ https://www.mpi-hd.mpg.de/personalhomes/bauke
>--  Social Networking @
>https://www.researchgate.net/profile/Heiko_Bauke
>___
>darktable developer mailing list
>to unsubscribe send a mail to
>darktable-dev+unsubscr...@lists.darktable.org


--
Pete Hall
p...@hallcircus.net
608-290-0731
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Deconvolution and Python framework

[Heiko Bauke]

Dear Aurélien,

Am 10.10.2017 um 10:25 schrieb Aurélien PIERRE:
Following my work from this Summer, I'm glad to propose my first blind 
deconvolution algorithm, written in Python, based on papers from 
2011-2014  : https://github.com/aurelienpierre/Image-Cases-Studies


TL;DR :

Blind deconvolution is a technique used in astronomy and microscopy to 
deblur pictures based on an estimation of the blur "profile" (SPF for 
the geeks). This work on motion blur, focus blur, etc. A commercial 
photo software get spectacular results with this technique : 
http://relaunch.piccureplus.com/ (although it's not really blind).


My code is a proof of concept which runs now (barely optimized) between 
50 and 275 s on a 2 Mpx image.


I'm still looking for some help to port it in a Darktable module, since 
I'm not a C developper (or at least some doc).


I am still rather skeptic regarding the question if a blind 
deconvolution algorithm fits into the darktable workflow.  It may be 
computationally too demanding.  Nevertheless, this is a very fascinating 
topic and I will have a look at your code.  Thanks for your efforts.



Heiko


--
-- Number Crunch Blog @ https://www.numbercrunch.de
--  Cluster Computing @ http://www.clustercomputing.de
--   Professional @ https://www.mpi-hd.mpg.de/personalhomes/bauke
--  Social Networking @ https://www.researchgate.net/profile/Heiko_Bauke
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org