Trackpy

Latest version: v0.6.4

Safety actively analyzes 687852 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 2 of 4

0.6.1rc1

trackpy v0.6.1 is functionally equivalent to v0.6.0. It is being released to fix an issue with Zenodo, so that this trackpy release has a citable DOI.

See the [release notes for v0.6.0](http://soft-matter.github.io/trackpy/v0.6.0/whatsnew.html) for more information.

0.6.0.1

This release focuses on fixing bugs and some inconsistencies in the prediction
capabilities. Some existing code that used prediction may now fail to run until
a (minor) update is made.

This release includes contributions by magnunor, freemansw1, crisp-snakey,
rbnvrw, caspervdw, tacaswell, and nkeim.

Enhancements

- Linking can now use any ``DistanceMetric`` class from sklearn to compute
distances (692 by freemansw1)
- Several documentation fixes by magnunor and nkeim

API Changes

- When supplying an initial velocity guess to NearestVelocityPredict or
DriftPredict, you must also supply the pos_columns argument to identify
the names of the columns in your array. (For example,
"pos_columns = ['y', 'x']".) Otherwise, creating the predictor will
raise an exception that explains this change. If you provide pos_columns
when creating the predictor, you do not have to supply it when subsequently
using the link_df() or link_df_iter() methods to link your features.
(nkeim, 710)
- ``reconnect_traj_patch()`` is now available as ``trackpy.reconnect_traj_patch``
and is described in the API documentation. (nkeim, 648)

Bug Fixes

- When linking with prediction, the predictor now correctly uses the same
position columns as the linker, and correctly handles the pos_columns
argument if specified. (nkeim, 710)
- The link_df() method of predictor objects now works correctly. (nkeim, 710)

Dependencies

- trackpy is now being tested in conda environments with Python 3.10.
- trackpy is no longer tested with Python 3.6.
- trackpy now requires the ``looseversion`` package to work with newer scipy
(crisp-snakey, 706)
- Much work on testing and packaging infrastructure by tacaswell and caspervdw

**Note:** This release is tagged `v0.6.0.1` on GitHub to address an issue with Zenodo DOI generation. There are no other differences between the GitHub version and the `v0.6.0` packages.

0.5.0

This is a major release focused on enhancements. Most notably, parallel processing is now turned on by default for “trackpy.batch” and “trackpy.locate_brightfield_ring”, resulting in a large performance increase for many users. Another minor speedup changes the way in which particle numbers are generated, which may cause issues with reproducibility in some existing workflows (see “API Changes” below).

Note that Python 2 reached end-of-life in 2020, and it is no longer officially supported by trackpy. Also, trackpy dropped support for older NumPy, Scipy and Pandas. The current minimum requirements are: `python>=3.6 numpy>=1.14 scipy>=1.1 pandas>=0.22`.

See the "What's new in the package" page in the [documentation](http://soft-matter.github.io/trackpy/v0.5.0/whatsnew.html) for a full list of changes.

0.4.2

This is a minor release with two major new features: parallel processing to speed up feature-finding, and a new method for locating features in bright-field microscopy. There is also an overhaul of the walkthrough and other tutorials, and compatibility with the latest version of Pandas (0.25.1).

See the "What's new in the package" page in the [documentation](http://soft-matter.github.io/trackpy/v0.4.2/whatsnew.html) for a full list of changes.

0.4.1

This is a minor release with some important fixes. Additionally, PIMS is no longer a required dependency, which makes installation easier.

0.4

This is a major release that includes new choices for linking and feature-finding algorithms, as well as many performance increases and clean-ups. It is recommended for all trackpy users, but may require minor changes to existing code, as detailed below.

See http://soft-matter.github.io/trackpy/v0.4/whatsnew.html for a full overview of the changes.

Page 2 of 4

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.