Page History

...

• The first step is the generation of the "small data" file, the colloquial name for run-based hdf5 files which contain different data arrays where the first dimension is the number of events. This production can be run automatically on each new run so that the data is available only a few minutes after the run has ended. It can also be run on request in case you want to tweak the data extraction. Pre-processing of the area detector can be configured at this stage, performing operation such as extracting a region of interest, azimuthal integration, photon counting, etc.
  The following pages describe this in more detail:

  Generation of small hdf5 files

  Configuration of SmallData

  Adding Data from area detectors

• The second stage depends much more on the type of experiment. Different options are available:
  • Adapt one of the templated analysis notebooks to suit the current experiment needs. These custom templates have been made for the more common experiments performed at different endstation at LCLS and are available at <path> /reg/g/psdm/sw/tools/smalldata_tools/example_notebooks. This approach is generally recommended for lightweight data analysis, for which the area detector images are reduced to a single (or few) number (integration of a ROI, azimuthal binning, for example). Please refrain from modifying these released notebooks.
    A description of the example notebooks can be found here: <link> Example notebooks
  • Binning of the full detector images can be performed by setting up the cube analysis, which will return a dataset of binned data and images, resulting in a relatively light-weight file. This approach is recommended in cases where the analysis of the full image is needed (Q-resolved diffused scattering analysis, for example).
    Details on the cube workflow are given here: <link> Cube production

The contents of the smallData files are described here

...