Spin-ARPES datasets tend to look a bit different than spin-integrated ARPES datasets. For one, they tend not to have as many dimensions as standard ARPES datasets, as many spin detectors only measure a single (k, E, S) point at a time, or might measure several components of S at once for single (k, E). Other detectors, like we one we have in the Lanzara lab, measure a single (k, S) point at once, but produce full EDCs.
Furthermore, SARPES datasets have the discrete spin label S. PyARPES
xarray as our data primitive makes it excellently suited
for handling SARPES data, because the different spin channels can exist
xr.DataArrays on the same
Spin-ARPES conventions in PyARPES
Most functionality in PyARPES works just as well for SARPES as for other modalities. You can load data just as you would with any other type:
Instead of having a
spectrum data variable as we several:
t_down. As we can see
time coordinates, while
energy coordinates. This spin spectrum comes from a time of flight
t_down are the raw timing spectra, while
down are the interpolated spectra after conversion to
You can think of
down in the same way that
is treated for spin integrated datasets. All analysis code that operates
xr.DataArrays should work for these as well.
Note for plugin writers: PyARPES reserves
down for the spin channels of ToF detectors and the spin
channels of energy-aware detectors respectively. You should ensure
plugins produce the appropriately variables. Spin-integrated time of
flight detectors should produce
Plotting multidimensional spin data using false color for the different spin components, an intensity-saturation/polarization-hue scheme, or by quiver plot is also straightforward.
Converting Time-of-Flight Data to Kinetic Energy
PyARPES contains support for converting time of flight photoemission data to energy and momentum space. Our support for this currently supports the Lanzara Lab’s Spin-ARPES spectrometer, but support is largely generic to multidimensional (ARToF) and PEEM-ToF detectors, given an associated data loading plugin.
Utilities can be found in
Note about units: Be aware that the energy coordinates produced by conversion from ToF data are the electron kinetic energies. Because PyARPES is more concerned about axes having meaningful and consistent units, it does not distinguish between the binding and kinetic energy: both are labelled by ‘eV’. This has advantages, because analysis code will still work transparently on either type of data. You will apply a correction or offset to adjust units appropriately so that the chemical potential lies at zero binding energy.