Repository navigation
Releases: mac4DSTEM/SpectroKit
Releases · mac4DSTEM/SpectroKit
Release list
SpectroKit 0.12.0
Full Changelog: 0.11.0...0.12.0
SpectroKit 0.11.0
SpectroKit 0.10.0
SpectroKit 0.9.0
What's Changed
- Fixtures: exSpy pins for task 16 sections 1, 2, 4 by @Paullo9 in #4
- Fixture README and DocC site (Paul merges) by @Paullo9 in #5
Full Changelog: 0.8.2...0.9.0
SpectroKit 0.8.2
What's Changed
- Design note for task 16: EELS zero-loss alignment, background, deconvolution, edge fit by @Paullo9 in #3
Full Changelog: 0.8.1...0.8.2
SpectroKit 0.8.1
SpectroKit 0.8.0
SpectroKit 0.7.1
0.7.0
Dependency range only; no source change, and no SpectroKit API or number moves.
- FormatoKit is now
"0.4.0"..<"0.6.0"(was"0.3.0"..<"0.5.0"): 0.3.x is dropped, 0.5.x added. FormatoKit 0.5.0 addsHDF5Reader,
HDF5AppendWriter,TIFFAppImageand newHDF5FileErrorcases (source-breaking only for an exhaustive switch overHDF5FileError;
SpectroKit has none). - Test fixture:
velox-tiny.txtof the golden test regenerated. FormatoKit 0.3.1 and later add four optionalVeloxMetadatafields (stageXMeters,
stageYMeters,stageZMeters,instrumentClass) that the golden dumps; additive lines only, 251 to 255 lines, no SpectroKit number moves.
Tested against FormatoKit 0.4.0 and 0.5.0.
Migration
Consumers on FormatoKit 0.3.x stay on SpectroKit 0.6.0. An app pinning FormatoKit 0.4.0 or 0.5.0 exact uses SpectroKit 0.7.0; re-pin SpectroKit to 0.7.0.
0.6.1
Dependency range only; no source change, and no SpectroKit API or number moves.
- FormatoKit is now
"0.3.0"..<"0.5.0"(was.upToNextMinor(from: "0.3.0")). FormatoKit 0.4.0 only repackages libhdf5 as XCFrameworks, so
an app that embeds FormatoKit 0.4.0 can still resolve SpectroKit.
Tests only: LineTableParityTests pins all 947 rows of the X-ray line table against exSpy 7185a4d1's own loader (was about 12 rows); no deviation found.
Migration
None. An app that pins FormatoKit 0.4.0 exact must use SpectroKit 0.6.1 or later; re-pin SpectroKit to 0.6.1.