Kinetics Toolkit 0.11 released

[felixchenier]

New features

• ktk.write_c3d can now write analogs in addition to points.
• ktk.geometry.rotate, ktk.geometry.translate, ktk.geometry.scale: Instead of having to create a series of transformation matrices and then apply this series to a series of coordinates, we can now use these three shortcut functions that directly transform series of coordinates.

Enhancements

• Addition of a scales parameter to ktk.geometry.create_transforms. We already had angles and translations, we now also have a scales parameter to create all kinds of rigid transforms matrices.
• Now every ktk.geometry operation with rigid transforms checks that the transform matrices are rigid (determinant = 1) before doing the calculation. This is mainly to ensure that (1) there is no user error with the shape and contents of the provided matrix series, and (2) we propagate error from long lists of calculations on badly conditioned matrices.
• Parameter convert_point_unit is now optional and defaults to None in ktk.read_c3d. The docstring and behaviour of ktk.read_c3d were clarified for cases when c3d points are not expressed in meters, to clear confusion when the file contains application-specific "points" such as calculated angles, powers and forces.
• These functions are not experimental anymore:
  • ktk.kinematics.create_cluster,
  • ktk.kinematics.extend_cluster,
  • ktk.kinematics.track_cluster,
  • ktk.geometry.register_points,
  • ktk.TimeSeries.resample,
  • ktk.TimeSeries.fill_missing_samples.

Bugfixes

• Now we get a clear error message in ktk.cycles.time_normalize when an unknown event name is given as parameter.

Requirement changes

• Now requires Python 3.10 or later.

---

This discussion was created from the release 0.11.0.