Pykoop

Latest version: v1.2.3

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

Scan your dependencies

Page 1 of 3

1.2.3

This release once again fixes a problem in the Read the Docs config file.

**Full changelog**: https://github.com/decargroup/pykoop/compare/v1.2.2...v1.2.3

1.2.2

This release fixes a typo in the Read the Docs config file.

**Full changelog**: https://github.com/decargroup/pykoop/compare/v1.2.1...v1.2.2

1.2.1

This release adds a missing Read the Docs config file that was preventing the documentation from being built.

**Full changelog**: https://github.com/decargroup/pykoop/compare/v1.2.0...v1.2.1

1.2.0

This release allows users to manually set a Koopman matrix computed outside of `pykoop` for easier interoperability with other libraries or custom regression code. The release also adds global configuration management, specifically to skip input validation. This can significantly (2x!) speed up `predict_trajectory()` and other methods that call `lift()`, `retract()`, etc. frequently. Finally, this release fixes some awkward scoring behaviour, making `score_trajectory()` work better in hyperparameter optimization setups.

**Full changelog**: https://github.com/decargroup/pykoop/compare/v1.1.3...v1.2.0

New features

* Added `DataRegressor` to allow `KoopmanPipeline` objects to be created directly from NumPy arrays (129)
* Added sklearn-style configuration management (`set_config(skip_validation)`, `get_config()` and `config_context(skip_validation)` ) to allow skipping input validation in performance-critical areas (151)
* Added `KoopmanPipeline.frequency_response()` to compute the frequency response of a Koopman system without plotting the Bode plot (143)
* Added the `plot_error` parameter to `plot_predicted_trajectory()` to allow plotting the prediction error instead of the trajectory (148)
* Made `DelayLiftingFn` compatible with `SplitPipeline` (145)

Bug fixes

* Fixed bug where `score_trajectory()` could return a worse score than the `error_score`, or even return `NaN` (132)

1.1.3

This release fixes a bug where diverging predictions were not scored correctly. It also adds the `error_score` parameter to `KoopmanPipeline.make_scorer()` and `score_trajectory()` to allow more fine-grained control over the behaviour.

**Full changelog**: https://github.com/decargroup/pykoop/compare/v1.1.2...v1.1.3

Bug fixes

* Fix incorrect scoring with `NaN` entries (https://github.com/decargroup/pykoop/pull/123)

1.1.2

This release exists because I forgot to bump the version number in the source code when releasing v1.1.1. Sorry!

**Full changelog**: https://github.com/decargroup/pykoop/compare/v1.1.1...v1.1.2

Page 1 of 3

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.