-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add demo: inpainting #138
base: source
Are you sure you want to change the base?
add demo: inpainting #138
Conversation
|
||
using ImageInpainting, TestImages, ImageCore | ||
|
||
img = Float64.(Gray.(testimage("lighthouse"))); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it because the inpaint
only accepts numerical array as inputs? In that case, we should fix and make it also works for AbstractArray{<:AbstractGray}
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay I would like to work on that
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like the algorithm isn't optimized well, the memory allocation is conspicuous to me.
julia> @time out = inpaint(img, mask, Criminisi(30,30));
14.502141 seconds (2.16 M allocations: 13.540 GiB, 18.97% gc time)
I'm not sure what's currently on your TODO list, but I guess this is also worth checking.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Update on this:
@time out = inpaint(img, mask, Criminisi(30,30));
17.644576 seconds (4.94 M allocations: 13.659 GiB, 3.46% gc time)
😄 It's pretty slow,let's check
Added a demo of Image inpainting
@johnnychen94