These draft notes cover the major updates made by Data Release Production to the LSST stack since release 11.0 (Summer 2015). Please record significant updates here so that they can ultimately be incorporated into the notes accompanying the Winter 2016 release.
Major Functionality and Interface Changes
Dumping task configuration parameters now includes documentation
That is, running ${TASK} ... --show config
displays not only the names and values of the configuration but also associated documentation.
- DM-3811Getting issue details... STATUS
Cleanup interpolation tasks and implement useFallbackValueAtEdge
The interpImageTask
in pipe_tasks
has been refactored to implement a single run
function for interpolation over a list of defects in an image. This run function will accept an afw image type of either MaskedImage or Exposure. A defects list can be passed in directly OR the name of mask plane can be passed from which a defects list will be created. If a PSF is attached to the image, it will be used as the (required) argument for the
function in interpolateoverDefects
meas_algorithms
used for the interpolation. Otherwise a FWHM (in pixels) can be provided or the defaultFWHM value in meas_algorithms
' GaussianFactory
is used. Note that while the PSF is a required argument for meas_algorithms'
interpolateOverDefects
, function it is currently not being used, so it is not necessary to pass in an accurate PSF.
The useFallbackValueAtEdge option is now implemented. This tapers the interpolation to a fallbackValue towards the image edge. The fallbackValue can be set via config parameters to be either computed as a statistical representation of the image data (MEAN, MEDIAN, or MEANCLIP) or set by providing a specific value. Allowance for a negative fallbackValue is also controlled though a config parameter.
- DM-3677Getting issue details... STATUS
Bug Fixes
The following fixes resolve problems visible to end users.
The NaiveDipoleCentroid
and NaiveDipoleFlux
algorithms no longer require centroids
These algorithms do not use centroids internally, but, since they mistakenly included SelfCentroidExtractor
s, it was impossible to initialize them unless a Centroid
slot had been defined. This has been fixed by removing the SafeCentroidExtractor
s from the algorithm definitions.
- DM-3940Getting issue details... STATUS
Correct bad default minInitialRadius
for CModel
The minInitialRadius configuration parameter had a default that is too small, causing many galaxies to be fit with point source models, leading to bad star/galaxy classifications.
- DM-3821Getting issue details... STATUS
Correct algebraic error in CModel uncertainty calculation
There was a simple but important algebra error in the uncertainty calculation, making the uncertainty a strong function of magnitude.
- DM-3821Getting issue details... STATUS
NaiveDipoleCentroid
and NaiveDipoleFlux
algorithms no longer require a centroid slot
Previously, initializing these algorithms was only possible if a centroid was already defined. That was not only unneccessary, but also made them more complicated to use, particularly in testing.
- DM-3940Getting issue details... STATUS
Build and code improvements
These improvements should not usually be visible to end users. They may, however, be important for developers.
Work-around incompatibilities with NumPy 1.10
NumPy 1.10 introduced API changes which were incompatible with existing usage in the stack. The latter has been updated to match
- DM-4063Getting issue details... STATUS - DM-4071Getting issue details... STATUS