Skip to content

0.12 released, new development phase

Compare
Choose a tag to compare
@felixchenier felixchenier released this 21 Jun 13:52
· 159 commits to master since this release

All onboard, direction version 1.0!

All core features have been implemented and most of them have a stable API. Therefore, I am happy to announce that we enter a new development phase, which is a steady walk toward version 1.0. What does this means?

  1. The current API (public classes, modules, functions) is now in "improvement" mode. No current feature will be removed anymore until version 1.0. In rare circumstances, you may get deprecation warnings that indicate that a given feature will be removed in version 1.0 or later, but these warnings will last for a minimum of 24 months before the feature is actually removed, to ensure that everybody has time to update their code. Generally this was already the case, but this is now a rule that will be enforced systematically.
  2. Most new features will now be developed as Kinetics Toolkit extensions. This will draw a clear line between the stable core API and open research applications. Some future extensions may then be integrated into the core if they are stable and relevant for general-purpose biomechanical analysis.

New feature

  • TimeSeries.resample now accepts a new frequency in Hz in addition to a new time attribute. We can now resample a TimeSeries to a new sampling frequency very easily: ts.resample(120).

Bugfixes

  • Saving a C3D with missing values now works.
  • No more warning in ktk.Player in Python >= 3.10.
  • Fixed deprecation message in deprecated function TimeSeries.get_event_time.
  • Added missing TimeSeries methods in the TimeSeries' dir, for better autocompletion in IDEs.

API changes

  • Removed fill_value parameter from TimeSeries.resample. Now:
    • The resampled has nan where the original signal had nan.
    • Resampling on a larger time span now always works, but there is no extrapolation: bound values are filled with nan systematically.
  • Player.to_html5 has been removed. This was an internal feature for documentation generation, that should not be part of the public API.