THIS PAGE IS A WORK IN PROGRESS. PLEASE REFRAIN FROM EDITING, COMMENTING ON, OR BELIEVING ANY OF THIS UNTIL IT IS RELEASED.
In the next major release of the LSST stack, the system for measuring the properties of sources will be replaced by a new one, housed mostly in the new meas_base package. In addition to providing new Task classes and a new plugin interface for measurement algorithms, this overhaul also includes changes to the schemas of the catalogs produced by the measurement framework. The new framework will not be entirely complete as of the next releasereleto a schema, you follow the naming conventions for the schema version of the framework you are using.ase, but it will have sufficient functionality to replace the old framework as the default. The old system will remain available via config on the S14 final release, but will be removed entirely before the W15 release.
...
Some care has been taken to make all of the tasks called by processImage sensitive to which measurement framework and schema version are in use, so that the pipeline will work with either measurement task. However, the developer should be careful when accessing or adding fields to the schemas to know which measurement task and which naming conventions are in effect. For new code, we encourage the use of the meas_base measurement framework and schema version=1 tables.
Here are some examples where you must use schema=0 names if you revert to the old framework:
- Code which adds a field by name to the schema.
- Plugin and slot names should follow the version: e.g., "centroid.sdss" for the old framework and "base_SdssCentroid" for the new.
- Config items for tasks which name specific fields, such as "badFlags" in the StarSelector configurations.
NOTE: If you are reading this document prior to the changeover to the end of Summer 14, just the opposite instructions will hold for using the New Framework. That is, you must retarget the above 3 tasks using the SingleFrameMeasurementTask, which resides in lsst.meas.base.
...