Skip to content

Latest commit

 

History

History
246 lines (166 loc) · 9.78 KB

CHANGELOG.rst

File metadata and controls

246 lines (166 loc) · 9.78 KB

0.5.4

This is a bug-fix release, and doesn't introduce any new features.

Breaking changes

This release is not believed to introduce any backwards-incompatible changes.

Merges

  • ligo!107: Allows additional files to be specified for condor transfers of bilby jobs.
  • ligo!110: Fixes a bug with bilby frame retrieval when no frame files are specified.
  • ligo!109: Allows total mass priors to be specified in bilby jobs.
  • ligo!113: Fixes a bug with asset retrieval in analyses with multiple requirements.

0.5.3

This is a bug-fix release, and doesn't introduce any new features.

Breaking changes

This release is not believed to introduce any backwards-incompatible changes.

Merges

  • ligo!105: Fixes an issue with accounting tags for the asimov start command.
  • ligo!104: Restores ability to calculate the precessing SNR in a PESummary post-processing pipeline.

0.5.2

This is a bug-fix release, and doesn't introduce any new features.

Breaking changes

This release is not believed to introduce any backwards-incompatible changes.

Merges & changes

  • ligo!94: Enables pipeline jobs to run without calibration information
  • ligo!102: Fixes to the distribution infrastructure for asimov for pypi and conda forge
  • Accounting information - Support was restored for clusters which do not require accounting information by making accounting data optional
  • Preferred event data - Preferred event data is now stored correctly as ligo>preferred event in the ledger when new event data is downloaded from GraceDB.
  • Frame files (bayeswave) - Fixes are implemented in the Bayeswave interface to pass cache files rather than frame files to the pipeline, and ensure that these are associated to the correct interferometer. The Bayeswave interface was updated to explicitly skip the datafind step if cache files are provided.
  • Frame files (bilby) - A fix was added to ensure that the data-dict dictionary has the correct key:value format in the config file.
  • PSD compatibility testing - A bug was fixed whereby PSDs would fail to pass compatibility criteria because of flawed tests; these tests have been respecified to avoid the bug.

0.5.1

This is a bug-fix release, and doesn't introduce any new features.

Breaking changes

This release is not believed to introduce any backwards-incompatible changes.

Merges

  • ligo!98: Fixes to handling of preferred event data from LIGO GraceDB
  • ligo!93: Fixes to allow code to run in environments where accounting tags are not required
  • ligo!94: Fixes errors when calibration files are not available
  • ligo!92: Fixes an issue with adding PSD files to some analyses
  • ligo!90: Fixes an issue with bayeswave when data files are provided

0.5.0

This is a minor feature release designed to implement new functionality required for running LIGO's O4a parameter estimation workflows.

Breaking changes

This release is not believed to introduce any backwards-incompatible changes.

Merges

  • ligo!51: Updates to the RIFT ini file
  • ligo!71: Introduces monitor and application hooks
  • ligo!72: Changes to the handling of state vectors
  • ligo!73: Changes to allow bilby to use new likelihood models
  • ligo!74: Changes to the handling of priors in bilby, removal of prior files
  • ligo!76: Improvements to ledger file handling
  • ligo!77: Fixes a bug with profiling data collection
  • ligo!78: Allow ROQ use in bilby
  • ligo!79: Fix a bug where accounting information is omitted from asimov-generated condor jobs
  • ligo!86: Updates various bilby defaults

Major New Features

Hooks

Introduced in ligo!71, asimov now allows plugins to interact with the monitor loop, and gain access to the ledger once the monitoring process has completed. It also allows external packages to provide new data via the asimov apply interface.

ROQ bases in bilby

This version introduces support for ROQ bases in bilby.

Review status

The newly reviewed features in asimov 0.5.0 are:

The newly reviewed capabilities in asimov 0.5.0 are:

Additional reviewed updates:

  • Revised BayesWave defaults associated with v1.1.0
  • Revised bilby_pipe defaults associated with v1.0.8 and also compatible with v1.1.0.
  • Compatibility with pesummary v1.0.0

Getting asimov v0.5.0

pypi

You can install this preview directly from pypi using pip: pip install --upgrade asimov==v0.5.0

git

You can clone this repository and install from source by running

git clone git@git.ligo.org:asimov/asimov.git
git checkout v0.5.0
pip install .

What's next?

You can find the most up to date O4 development roadmap on the project wiki<https://git.ligo.org/asimov/asimov/-/wikis/o4-roadmap>.

0.4.1

This is a bug-fix release.

Breaking changes

This release is not believed to introduce any backwards-incompatible changes.

Bugs Fixed

0.4.0

Breaking changes

This release of asimov is not backwards compatible with releases from the v0.3 series, and has multiple breaking changes.

Major New Features

Projects

This version of asimov represents a major update compared to the previously released versions of asimov. In the past asimov has relied on gitlab issue trackers in order to organise a project. In this version we introduce infrastructure within asimov to enable management of much smaller projects as well as those asimov was initially intended for. Projects can now be created in a user's home directory and used to organise and automate multiple runs.

Pipeline interface improvements

We've made a serious effort in this version to improve the interface between asimov and various gravitational wave analysis pipelines, including Bayeswave, bilby, and lalinference. We've made it much easier to use other pipelines with asimov too, which can now be implemented as plugins without requiring upstream changes to the asimov codebase.

Reporting improvements

We've introduced a number of new features to the report pages which are created by asimov in order to give a more useful overview of all of the analyses which are being run.

Command-line interface

Asimov now has a cleaner, and more consistent command line interface, which has been renamed asimov. When we started work on the project we weren't sure how asimov would be used, but we've come to the conclusion that having everything named consistently is for the best.

Blueprint files

Setting up events and analyses in asimov requires a large amount of information. To assist with this, asimov is now able to read-in this information in yaml-format files which we call "blueprints". A curated collection of these for the events included in the GWTC catalogues, and the analyses used for those catalogues are available from https://git.ligo.org/asimov/data.

Review status

This release has been reviewed for use in parameter estimation analyses of the LVK. + Review statements can be found in the REVIEW.rst file in this repository. + Full information regarding the review is available `in this wiki page<https://git.ligo.org/pe/O4/asimov-review/-/wikis/Asimov-version-O4>`_.

Getting asimov v0.4.0

pypi

You can install this preview directly from pypi using pip: pip install --upgrade asimov==v0.4.0

git

You can clone this repository and install from source by running

git clone git@git.ligo.org:asimov/asimov.git
git checkout v0.4.0
pip install .

What's next?

You can find the most up to date O4 development roadmap on the project wiki<https://git.ligo.org/asimov/asimov/-/wikis/o4-roadmap>.