lumicks/pylake: v0.8.2

New features Added GaussianMixtureModel to fit a Gaussian Mixture Model to channel data. For more information, see the tutorials section on Population Dynamics Added Scan.size_um and Kymo.size_um to return the scanned size along each dimension. Use these properties to access the scan sizes along each axis for scans and kymographs. Added force calibration functionality to Pylake. Please refer to force calibration for more information. Added support for new metadata format in order to handle widefield TIFF files recorded in Bluelake 1.7. Bug fixes Fixed bug in kymotracker which could result in a line being extended one pixel too far in either direction. Reason for the bug was that a blurring step in the peak-finding routine was being applied on both axes, while it should have only been applied to one axis. Note that while this bug affects peak detection (finding one too many), it should not affect peak localization as that is performed in a separate step. Fixed bug in kymotracker slicing which could result in one line too many or too few being included. The bug was caused by using the timestamp corresponding to one sample beyond the last pixel of the line as "start of the next line" without accounting for the dead time that may be there. Deprecations Scan.scan_width_um and Kymo.scan_width_um have been deprecated. Use Scan.size_um and Kymo.size_um to get the scan sizes. When performing a scan, Bluelake determines an appropriate scan width based on the desired pixel size and the scan width entered in the UI. The property scan_width_um returned the scan size entered by the user, rather than the actual scan size achieved. To obtain the achieved scan size, use Scan.size_um and Kymo.size_um