2.4.0

This is the first release to support both v3 and v4 opsim outputs.

The v4 opsim runs change the database schema in a couple of ways:

the ‘Summary’ table becomes ‘SummaryAllProps’
the names and contents of the tables recording slew details have changed (but this won’t be relevant to most users, because most people probably care about total slew time, rather than the details of the initial vs final slew states)
the column names have changed in many places (much of this is capitalization – fieldID becoming fieldId, for example … but note propID becomes proposalId)
the quantities in the database are now in degrees!! (this is an important change to note)

But the consequences of the above are that MAF has had to adapt to processing both v3 and v4 runs. To this end, the traditional “standard” analysis scripts (schedulerValidation.py and sciencePerformance.py) now come in two flavors (schedulerValidation.py and schedulerValidation3.py).
More interestingly (and the direction we’re planning to go forward), we’ve introduced the concept of “batches”. Batches** are sets of metricBundles which we (or you) can grab and then run on an opsim simulated survey.
An example is that we have a “metadataBasics” batch, which will run a series of measurements on a given column of the opsim output: measuring the min, mean, median, max, rms, and 25/75th percentiles of the Airmass (in all and per filter), generating a histogram of the airmass (in all and per filter), and generating skymaps of the min/mean/median/max airmass (in all and per filter). There are also currently batches to look at various aspects of the number of visits and coadded depth. There are some more available, and more in development – we’d love to have more input on what you think would be a useful and coherent “batch”.
** batch is our name for these for now – better suggestions welcome.

The useful thing about batches is that they will standardize the metricBundle output (name-wise) across v3 and v4, so that we can compare runs from v3 vs. v4 more easily. It’s also useful to be able to run a small set of metrics easily (and again, on either a v3 or v4 run).

sims_2.2.5

• Added ParallaxDCR degeneracy metric, to much better evaluate parallax errors.
• Added white dwarf colors and luminosity function to utilities and star maps.
• Moving from 'sqlconstraint' to 'constraint.
• Updated plotHandler for better/cleaner resolution of plot dictionaries.
• Fixed slowdown in kdtree building with newer versions of scipy.
• Fixed bugs in metricBundle where plotFuncs were not passed to reduce bundles.
• Fixed bugs in userSlicePoints metric.

v2.1.3

Tagged version of MAF with updates to science and scheduler analysis scripts, as used in the Tier 1 run analysis (January 2016).

Updates include :

• Starting to add documentation via sphinx.
• Fix display parameters and captions for the science and scheduler analysis scripts.
• Fix units for dtime metric in science analysis script.

Since last release notes available:

• Stellar density map has been added.

v2.0.1

post LSST 2015 release

v2.0

New features:

• add support for multi-sql constraint to metric bundle group
• added schedulerValidation and sciencePerformance scripts
• Changed default colormaps from jet to cubehelix
• improved display of complex metrics in showMAF.py, supporting reduce order
• more support for reading/restoring saved metrics from metricBundleGroup

Jump to v2.0 to match sims.

v1.1.1

This release

• fixes a few additional bugs in the slicers 'not equal' and 'equal' methods
• fixes a bug when applying the camera footprint

In addition to:

• incorporates the 'new' database API (using database=db filename, instead of sqlalchemy connection string)
• fixed several bugs in the slicers 'not equal' function (and potential bugs in the 'equal' functions of some slicers)
• fixed a bug in 'showMaf.py' when the -d option was used
• added the capability to compare summary statistics and plots from multiple resultsDatabases
• added galactic and equatorial coordinates stackers
• added a metric and stackers related to calculating the maximum distance an NEO would be detectable
• removed a limitation when setting the 'maxl' value for healpix angular power spectrum plots
• updated MAF for API changes in other simulations packages
• removed several outdated examples from the 'example' directory

v1.1

This release

• incorporates the 'new' database API (using database=db filename, instead of sqlalchemy connection string)
• fixed several bugs in the slicers 'not equal' function (and potential bugs in the 'equal' functions of some slicers)
• fixed a bug in 'showMaf.py' when the -d option was used
• added the capability to compare summary statistics and plots from multiple resultsDatabases
• added galactic and equatorial coordinates stackers
• added a metric and stackers related to calculating the maximum distance an NEO would be detectable
• removed a limitation when setting the 'maxl' value for healpix angular power spectrum plots
• updated MAF for API changes in other simulations packages
• removed several outdated examples from the 'example' directory

Release 1.0.2

This tag features minor updates from 1.0.1.

• the '.eq' and '.neq.' functions for slicers and stackers were updated.
• Unnecessary or non-working example pythonscripts were removed (they were based on the pre-1.0 version of MAF).

Release 1.0.1

Fixed a few small bugs that cropped up in more extensive testing of 1.0.0, relating to plotting metrics containing object values.

Release 1.0.0

This release represents a major change from the previous version of MAF, as it introduces metricBundles and metricBundleGroups, and separates plotting into plotting classes.