#include <LatticeApply.h>

Static Public Member Functions
static void	lineApply (MaskedLattice< U > &latticeOut, const MaskedLattice< T > &latticeIn, LineCollapser< T, U > &collapser, uInt collapseAxis, LatticeProgress *tellProgress=0)
	This function iterates line by line through an input lattice and applies a user supplied function object to each line along the specified axis. More...

static void	lineApply (MaskedLattice< U > &latticeOut, const MaskedLattice< T > &latticeIn, const LatticeRegion &region, LineCollapser< T, U > &collapser, uInt collapseAxis, LatticeProgress *tellProgress=0)

static void	lineMultiApply (PtrBlock< MaskedLattice< U > * > &latticeOut, const MaskedLattice< T > &latticeIn, LineCollapser< T, U > &collapser, uInt collapseAxis, LatticeProgress *tellProgress=0)
	This function iterates line by line through an input lattice and applies a user supplied function object to each line along the specified axis. More...

static void	lineMultiApply (PtrBlock< MaskedLattice< U > * > &latticeOut, const MaskedLattice< T > &latticeIn, const LatticeRegion &region, LineCollapser< T, U > &collapser, uInt collapseAxis, LatticeProgress *tellProgress=0)

static void	tiledApply (MaskedLattice< U > &latticeOut, const MaskedLattice< T > &latticeIn, TiledCollapser< T, U > &collapser, const IPosition &collapseAxes, Int newOutAxis=-1, LatticeProgress *tellProgress=0)
	This function iterates tile by tile through an input lattice and applies a user supplied function object to each chunk along the specified axes. More...

static void	tiledApply (MaskedLattice< U > &latticeOut, const MaskedLattice< T > &latticeIn, const LatticeRegion &region, TiledCollapser< T, U > &collapser, const IPosition &collapseAxes, Int newOutAxis=-1, LatticeProgress *tellProgress=0)

static void	tiledMultiApply (PtrBlock< MaskedLattice< U > * > &latticeOut, const MaskedLattice< T > &latticeIn, TiledCollapser< T, U > &collapser, const IPosition &collapseAxes, LatticeProgress *tellProgress=0)
	This function iterates tile by tile through an input lattice and applies a user supplied function object to each chunk along the specified axes. More...

static void	tiledMultiApply (PtrBlock< MaskedLattice< U > * > &latticeOut, const MaskedLattice< T > &latticeIn, const LatticeRegion &region, TiledCollapser< T, U > &collapser, const IPosition &collapseAxes, LatticeProgress *tellProgress=0)

Static Private Member Functions
static IPosition	prepare (const IPosition &shapeIn, const IPosition &shapeOut, const IPosition &collapseAxes, Int newOutAxis)
	Do some checks on the given arguments. More...

static IPosition	_chunkShape (uInt axis, const MaskedLattice< T > &latticeIn)

Detailed Description

template<class T, class U = T>
class casacore::LatticeApply< T, U >

Optimally iterate through a Lattice and apply provided function object

Intended use:

Public interface

Review Status

Date Reviewed:: yyyy/mm/dd

Prerequisite

Synopsis

This function iterates through a Lattice and applies a user given function object to chunks along the specified axes. Usually the function collapses the chunk to 1 or a few values (e.g. get min/max). The result of the function is written into the output Lattice(s) at the location of the collapsed chunk. The output lattice(s) must be supplied with the correct shape. E.g. when a lattice with shape [nx,ny,nz] is collapsed by calculating the mean of each y-line, the output lattice has to have shape [nx,nz]. It is also possible to have output shape [nx,1,nz], [1,nx,nz], [nx,nz,1] or even e.g. [nx,1,1,1,nz].

By specifying a region it is possible to apply the function object to a subset of the lattice. Of course, the shape of the output lattice(s) have to match the shape of the region.

The iteration is done in an optimal way. To keep memory usage down, it caches as few tiles as possible. There are 2 ways to iterate.

For some applications an entire line is needed. An example is the calculation of the moment. The functions lineApply and lineMultiApply can be used for that purpose. Internally they use the TiledLineStepper navigator, so only a few tiles are kept in the cache.
One can also think of applications where an entire plane (or cube) is needed. This is not supported, but can be implemented when needed.
Other applications do not care how the data are traversed, making it possible to iterate tile by tile (which is optimal). An example is the calculation of the minimum, maximum, mean of a line, plane, etc.. For this purpose the function tiledApply can be used. This function is faster and uses less memory than lineApply, so whenever possible this one should be used. Another advantage of this function is that it is possible to operate per line, plane, etc. or even for the entire lattice.

The user has to supply a function object derived from the abstract base class LineCollapser or TiledCollapser, resp.. The process function in these classes has to process the chunk of data passed in. The nstepsDone function in these classes can be used to monitor the progress.

The class is Doubly templated. Ths first template type is for the data type you are processing. The second type is for what type you want the results of the processing assigned to. For example, if you are computing sums of squares for statistical purposes, you might use higher precision (Float->Double) for this. No check is made that the template types are self-consistent.

Example

Collapse each line in the y-direction using my collapser function object.

MyLineCollapser collapser;
PagedArray<Float> latticeIn("lattice.file");
IPosition shape = latticeIn.shape();
shape(1) = 1;
ArrayLattice<Double> latticeOut(shape);
LatticeApply<Float,Double>::lineApply (latticeOut, latticeIn, collapser, 1);

Motivation

This class makes it possible that a user can apply functions to a lattice in an optimal way, without having to know all the details of iterating through a lattice.

Definition at line 137 of file LatticeApply.h.