Getting Started

Documentation

Glish

Learn More

Programming

Contact Us

Version 1.9 Build 803

News	FAQ
Search	Home

Open questions

1. TempLattice::init()

   When in the disk based mode, each construction of TempLattice results into a creation of a Table on the disk. TempLattice::init() gets called twice in each call to LatticeConvolver::convolve(), which in turn is called in the inner loop of Clark-CLEAN. When TempLattice uses PagedArray, this results into creation of a new Table every time. Is this a performance hit?

2. What's the design/functional/whatever advantage in the LatticeFFT layer? Should LatticeFFT be just derived from FFTServer and LatticeConvolver be part of LatticeFFT (or at least derived from it)? Use of the two other convolves in AIPS++ (the Convolver class and the StokesImageUtil::convolver should certainly be discouraged.