Every acquisition leaves the instrument as a stream of events — each one carrying a position and an arrival time. Nothing is binned, gated or fitted before you see it, which means the analysis is yours to define: choose the spatial binning after the fact, gate the decay differently for two regions of the same image, or fit a model our software has never heard of.
58,092,587 photons · τ 0.83 – 1.43 ns · 412 MB
Every example on this page runs against that file, so you can follow along before an instrument is on your bench.
f = photonscore.File('lily-of-the-valley.photons');
photons = f.photons();
tau = photonscore.flim.lifetime(photons, 'Components', 2);
imagesc(tau.tau(:,:,1)); colormap turbo; caxis([0.5 4.0]);Photon lists as NumPy structured arrays.
pip install photonscoreA toolbox that hands you struct arrays and the usual plotting.
photonscore.mltbxSpans over memory-mapped photon records — no copy on read.
dotnet add package PhotonscoreThe MATLAB reference is generated from the source docstrings. Until that step is wired into the build, the prose documentation at Documentation is the authoritative description.
Every binding, for every platform, on the downloads page.