LSSTApplications
17.0+124,17.0+14,17.0+73,18.0.0+37,18.0.0+80,18.0.0-4-g68ffd23+4,18.1.0-1-g0001055+12,18.1.0-1-g03d53ef+5,18.1.0-1-g1349e88+55,18.1.0-1-g2505f39+44,18.1.0-1-g5315e5e+4,18.1.0-1-g5e4b7ea+14,18.1.0-1-g7e8fceb+4,18.1.0-1-g85f8cd4+48,18.1.0-1-g8ff0b9f+4,18.1.0-1-ga2c679d+1,18.1.0-1-gd55f500+35,18.1.0-10-gb58edde+2,18.1.0-11-g0997b02+4,18.1.0-13-gfe4edf0b+12,18.1.0-14-g259bd21+21,18.1.0-19-gdb69f3f+2,18.1.0-2-g5f9922c+24,18.1.0-2-gd3b74e5+11,18.1.0-2-gfbf3545+32,18.1.0-26-g728bddb4+5,18.1.0-27-g6ff7ca9+2,18.1.0-3-g52aa583+25,18.1.0-3-g8ea57af+9,18.1.0-3-gb69f684+42,18.1.0-3-gfcaddf3+6,18.1.0-32-gd8786685a,18.1.0-4-gf3f9b77+6,18.1.0-5-g1dd662b+2,18.1.0-5-g6dbcb01+41,18.1.0-6-gae77429+3,18.1.0-7-g9d75d83+9,18.1.0-7-gae09a6d+30,18.1.0-9-gc381ef5+4,w.2019.45
LSSTDataManagementBasePackage
|
You can use the C++ APIs to manipulate images and bits of images from python, e.g.
sets a 4x10
portion of image im
to 100 (I used im.Factory
to avoid repeating afwImage.ImageF
, rendering the code non-generic). I can't simply say sim
=
100
as that'd make sim
an integer rather than setting the pixel values to 100. I used an Image, but a Mask or a MaskedImage would work too (and I can create a sub-Exposure, although I can't assign to it).
This syntax gets boring fast.
We accordingly added some syntactic sugar at the swig level. I can write the preceeding example as:
i.e. create a subimage and assign to it. afw's image slices are always shallow (but you can clone
them as we shall see).
Note that the order is [x, y]
**. This is consistent with our C++ code (e.g. it's PointI(x, y)
), but different from numpy's matrix-like [row, column]
.
This opens up various possiblities; the following all work:
You might expect to be able to say print
im
[0,20] but you won't get what you expect (it's an image, not a pixel value); say print
float(im[0,20])
instead.
The one remaining thing that you can't do it make a deep copy (the left-hand-side has to pre-exist), but fortunately
works.
You will remember that the previous section used [x, y]
whereas numpy uses [row, column]
which is different; you have been warned.
You can achieve similar effects using numpy
. For example, after creating im
as above, I can use getArray
to return a view of the image (i.e. the numpy object shares memory with the C++ object), so:
will also set a sub-image's value (but a different sub-image from im[1:5, 2:8]
). You can do more complex operations using numpy
syntax, e.g.
which is very convenient, although there's a good chance that you'll be creating temporaries the size of im
.