IP Scaling functionality far from optimal
Created by: anjos
The documentation and workflow of
bob.ip.scale_as as pretty bad as they currently stand.
If I read the doc of
scale_as, I get the impression it will scale the input image, but actually it just generates a container for one.
The doc of
scaledoes not precise the types of inputs it can handle, nor the type it outputs.
There is no easy handle to scale an image and return a freshly allocated container. I currently have to pass through
scale_asto get a container and then be able to call