Skip to content

Releases: choderalab/pymbar

4.1.0 Bugfix Release

07 Aug 22:48
6836440
Compare
Choose a tag to compare

This release fixes some typos in documentation and adds some clarity.
Some bugs that affected users have been fixed:

  • Index error in subsample_correlated_data #552
  • Verbose=True with MBAR results in an error for alternative input types of u_kn #538
  • Make MBAR bootstrapping deterministic independent of verbose flag #551

Details below 👇

What's Changed

New Contributors

Full Changelog: 4.0.3...4.1.0

4.0.3 Support for Python 3.12 and Jax 0.3.25+

21 Mar 16:54
1b50851
Compare
Choose a tag to compare

Updates the builds to work against Python 3.8 through and including Python 3.12. Also fixes some upstream JAX and CI dependency issues.

What's Changed

Full Changelog: 4.0.2...4.0.3

4.0.2 Optional JAX build

11 Aug 20:01
7b4f89f
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: 4.0.1...4.0.2

3.1.1

30 Nov 17:19
ad7d9c4
Compare
Choose a tag to compare

What's Changed

The former is specified using solver_tolerance and the latter is specified using bootstrap_solver_tolerance.

Full Changelog: 3.1...3.1.1

pymbar 3.1 LTS Release

29 Jul 15:18
a314f00
Compare
Choose a tag to compare

What's New

We now support computation of bootstrapped uncertainties for MBAR free energies -- just specify n_bootstraps=n_desired_bootstraps when initializing MBAR(), where n_desired_bootstraps is the number of bootstrap iterations you'd like to run, and uncertainty_method='bootstrap' when calling getFreeEnergyDifferences().

What's Changed

New Contributors

Full Changelog: 3.0.7...3.1

4.0.1

20 Jul 21:58
445170f
Compare
Choose a tag to compare

Breaking Changes Ahead!

This pymbar release has several API changes and some exciting new features (such as JAX acceleration and support)

See this guide on how to migrate from pymbar 3.x to pymbar 4.x.

pymbar 3.x support

We will still support the pymbar 3.x version line as a long term support release. We encourage new pymbar users to use the 4.x version, but due to the considerable infrastructure build around pymbar 3.x, we will continue to provide maintenance support. Don't expect new features to be backported, but we will fix bugs.

What's Changed

Full Changelog: 3.0.7...4.0.1

4.0.0

20 Jul 21:21
58fe32b
Compare
Choose a tag to compare

Breaking Changes Ahead!

This pymbar release has several API changes and some exciting new features (such as JAX acceleration and support)

See this guide on how to migrate from pymbar 3.x to pymbar 4.x.

pymbar 3.x support

We will still support the pymbar 3.x version line as a long term support release. We encourage new pymbar users to use the 4.x version, but due to the considerable infrastructure build around pymbar 3.x, we will continue to provide maintenance support. Don't expect new features to be backported, but we will fix bugs.

What's Changed

Full Changelog: 3.0.7...4.0.0

Bugfix Release

13 May 23:07
7ff37e9
Compare
Choose a tag to compare

What's Changed

Full Changelog: 3.0.6...3.0.7

Bugfix Release

24 Jan 21:42
15f932a
Compare
Choose a tag to compare

What's Changed

  • Fixes sanity check for empty bins in computePMF by @tuckerburgin in #324
  • Change anaconda channel from omnia to conda-forge by @chrisjonesBSU in #404
  • Update README installation instructions from -c omnia to -c conda-forge. by @bdice in #418
  • Forward maximum_iterations from MBAR constructor by @maxentile in #425
  • Removed travis CI config file by @mikemhenry in #426

New Contributors

Full Changelog: 3.0.5...3.0.6

Critical bugfix release

02 Dec 01:24
1d14e80
Compare
Choose a tag to compare

In adding support for python 3.8 and scipy 1.0, pymbar 3.0.4 accidentally changed the API for key components to a new experimental API in which dict objects were returned for convenience.

This release restores the previous API behavior in pymbar 3.0.0-3.0.3, but allows the new API to be accessed via the optional keyword argument return_dict=True (via PR #319). Without this keyword, the old API is used.

We will consider making the dict API the default in pymbar 4, but we will plan to add warnings of the API change well in advance of this change.

Apologies to all our users who were affected by this issue!