lumicks/pylake: v1.8.0

New features

• Added feature to adaptively determine the fitting range when fitting power spectra using calibrate_force() and fit_power_spectrum(). Provide the parameter corner_frequency_factor to use this feature. When provided, the fitting range will be iteratively determined based on the corner frequency of the power spectrum. Note that this feature is only relevant for systems with a factory calibrated diode response.
• Allow piezo tracking to work with force and trap position data with different sampling rates by downsampling the higher rate data to the lower one. The sampling rates are required to be an integer multiple of each other to avoid any interpolation.
• Added the optional argument data_range to CalibrationResults.plot() to plot a custom frequency range for the data. This helps put the fitted part of the power spectrum in context.
• Added the optional argument where="left" to Slice.downsampled_by() to downsample by a factor while keeping the original timestamps. The default remains "center".
• Added confocal API endpoints axis_units, axis_names, axis_labels to get the units, names and labels of the axes of a confocal scan in human-readable form.
• Bump tabulate dependency to allow versions up to <0.11.
• Added support for Bluelake force calibration items that use adaptive fitting ranges. To get the initial fitting range used during calibration (the one entered in the UI), we added the property ForceCalibrationItem.initial_fit_range. For the final fit range, use the existing property ForceCalibrationItem.fit_range. The used corner frequency factor can be found in ForceCalibrationItem.corner_frequency_factor. For more information see the tutorial:

Bug fixes

• Fixed a bug that could affect calibrations returned by Slice.calibration with a stop time of 0 (01/01/1970). This bug could affect mocked force and calibration data, but it should not affect real data.