You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

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-3811 - Getting 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 SelfCentroidExtractors, it was impossible to initialize them unless a Centroid slot had been defined. This has been fixed by removing the SafeCentroidExtractors from the algorithm definitions.

DM-3940 - Getting 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-3821 - Getting 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-3821 - Getting 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-3940 - Getting 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-4063 - Getting issue details... STATUS DM-4071 - Getting issue details... STATUS

  • No labels