LSSTApplications  19.0.0-14-gb0260a2+72efe9b372,20.0.0+7927753e06,20.0.0+8829bf0056,20.0.0+995114c5d2,20.0.0+b6f4b2abd1,20.0.0+bddc4f4cbe,20.0.0-1-g253301a+8829bf0056,20.0.0-1-g2b7511a+0d71a2d77f,20.0.0-1-g5b95a8c+7461dd0434,20.0.0-12-g321c96ea+23efe4bbff,20.0.0-16-gfab17e72e+fdf35455f6,20.0.0-2-g0070d88+ba3ffc8f0b,20.0.0-2-g4dae9ad+ee58a624b3,20.0.0-2-g61b8584+5d3db074ba,20.0.0-2-gb780d76+d529cf1a41,20.0.0-2-ged6426c+226a441f5f,20.0.0-2-gf072044+8829bf0056,20.0.0-2-gf1f7952+ee58a624b3,20.0.0-20-geae50cf+e37fec0aee,20.0.0-25-g3dcad98+544a109665,20.0.0-25-g5eafb0f+ee58a624b3,20.0.0-27-g64178ef+f1f297b00a,20.0.0-3-g4cc78c6+e0676b0dc8,20.0.0-3-g8f21e14+4fd2c12c9a,20.0.0-3-gbd60e8c+187b78b4b8,20.0.0-3-gbecbe05+48431fa087,20.0.0-38-ge4adf513+a12e1f8e37,20.0.0-4-g97dc21a+544a109665,20.0.0-4-gb4befbc+087873070b,20.0.0-4-gf910f65+5d3db074ba,20.0.0-5-gdfe0fee+199202a608,20.0.0-5-gfbfe500+d529cf1a41,20.0.0-6-g64f541c+d529cf1a41,20.0.0-6-g9a5b7a1+a1cd37312e,20.0.0-68-ga3f3dda+5fca18c6a4,20.0.0-9-g4aef684+e18322736b,w.2020.45
LSSTDataManagementBasePackage
How to manipulate images from python

How to manipulate images from python

You can use the C++ APIs to manipulate images and bits of images from python, e.g.

import lsst.afw.geom as afwGeom
im = afwImage.ImageF(10, 20)
bbox = afwGeom.BoxI(afwGeom.PointI(1, 2), afwGeom.ExtentI(4, 6))
sim = im.Factory(im, bbox)
sim.set(100)
del sim

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:

im[1:5, 2:8] = 100

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:

im[-1, :] = -5
im[..., 18] = -5 # the same as im[:, 18]
im[4, 10] = 10
im[-3:, -2:] = 100
im[-2, -2] = -10
sim = im[1:4, 6:10]
sim[:] = -1
im[0:4, 0:4] = im[2:6, 8:12]

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

im2 = im[0:3, 0:5].clone()

works.

numpy

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:

import numpy as np
nim = im.getArray()
nim[1:5, 2:8] = 100

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.

nim = im.getArray()
nim[:] = 100 + np.sin(nim) - 2*nim

which is very convenient, although there's a good chance that you'll be creating temporaries the size of im.

lsst::afw::image
Backwards-compatibility support for depersisting the old Calib (FluxMag0/FluxMag0Err) objects.
Definition: imageAlgorithm.dox:1
lsst::afw
Definition: imageAlgorithm.dox:1
lsst
A base class for image defects.
Definition: imageAlgorithm.dox:1
ImageF
bbox
AmpInfoBoxKey bbox
Definition: Amplifier.cc:117
lsst::afw::geom
Definition: frameSetUtils.h:40