|
LSSTApplications
1.1.2+25,10.0+13,10.0+132,10.0+133,10.0+224,10.0+41,10.0+8,10.0-1-g0f53050+14,10.0-1-g4b7b172+19,10.0-1-g61a5bae+98,10.0-1-g7408a83+3,10.0-1-gc1e0f5a+19,10.0-1-gdb4482e+14,10.0-11-g3947115+2,10.0-12-g8719d8b+2,10.0-15-ga3f480f+1,10.0-2-g4f67435,10.0-2-gcb4bc6c+26,10.0-28-gf7f57a9+1,10.0-3-g1bbe32c+14,10.0-3-g5b46d21,10.0-4-g027f45f+5,10.0-4-g86f66b5+2,10.0-4-gc4fccf3+24,10.0-40-g4349866+2,10.0-5-g766159b,10.0-5-gca2295e+25,10.0-6-g462a451+1
LSSTDataManagementBasePackage
|
All of these algorithms require the inclusion of lsst/afw/image/ImageAlgorithm.h, and are in namespace lsst::afw::image.
afw supports for_each_pixel as a way to process each pixel in an Image, in a similar way to the STL's for_each. The name doesn't follow the LSST C++ guidelines, but in this case I felt that conformity to the spirit of the STL was more important. There are variants of for_each_pixel corresponding to setting a pixel to a function, setting it to a function of an Image, and setting it to a function of its value and a second Image's pixel value. The selection of which of these operations is desired is done by requiring the functor to inherit from a class such as pixelOp0 or pixelOp1XY, each of which is a tr1::function with a virtual operator() added.
for_each_pixel(Image<LhsT> &lhs, pixelOp0<LhsT> const& func) Set each pixel in lhs to the value of func.
for_each_pixel(Image<LhsT> &lhs, pixelOp1<LhsT> const& func) Set each pixel in lhs to the value of func(lhs).
for_each_pixel(Image<LhsT> &lhs, pixelOp1XY<LhsT> const& func) Set each pixel in lhs to the value of func(x, y, lhs).
for_each_pixel(Image<LhsT> &lhs, Image<RhsT> const& rhs, pixelOp1<RhsT> const& func) Set each pixel in lhs to the value of func(lhs).
for_each_pixel(Image<LhsT> &lhs, Image<RhsT> const& rhs, pixelOp2<Lhs, RhsT> const& func) Set each pixel in lhs to the value of func(lhs, rhs).
for_each_pixel(Image<LhsT> &lhs, Image<RhsT> const& rhs, pixelOp2XY<Lhs, RhsT> const& func) Set each pixel in lhs to the value of func(x, y, lhs, rhs).
This code is in forEachPixel.cc.
Include needed header file, and define a namespace alias
operator() is declared const, as we pass these functors by (const) reference. If this surprises you, take a look at Meyers, Effective STL, Item 38.
std::fill, but if I called it fill then following a using namespace std; the compiler would complain about ambiguity; it's simpler just to use a different name.
Here are examples of pixelOp1 and pixelOp2.
erase to each pixel in img1, setVal to each pixel in img2, set img1 = img2 + 1, and finally img1 /= img1
(xc, yc) and with central intensity 1000.
1.8.5