ImageFeatures.jl WIP: replace Images with specific packages

Currently the bottleneck is gaussian_pyramid which is still in Images.jl

Jul 23 '23 11:07 timholy

Can we bring pyramid functions here or somewhere more appropriate if needed?That almost empties out algorithms.jl in Images.jl if threshold ones are gone too today and much closer to a meta package than ever.

Jul 23 '23 11:07 ashwanirathee

Pyramids should be a separate package; ImageTracking among likely many others needs them. Though perhaps they could move to ImageBase; it's a pretty fundamental concept in image processing.

Jul 24 '23 08:07 timholy

Should we make it a separate package then or keep it in ImageBase.jl? I am assuming it doesn't conflict with monorepo work because Images.jl is at top level and ImageBase.jl seems to be separate enough too.

Jul 30 '23 06:07 ashwanirathee

I don't have a strong opinion, but I think since restrict is in ImageBase and we might use restrict in making fast pyramids, I think moving it to ImageBase seems fine.

Jul 31 '23 18:07 timholy