-
Loïc Le Guyader authoredLoïc Le Guyader authored
How to's
top
- :doc:`load data in memory <Loading_data_in_memory>`.
misc
- :doc:`bunch pattern decoding <bunch_pattern_decoding>`.
detectors
DSSC
Most of the functions within toolbox_scs.detectors can be accessed directly. This is useful during development, or when working in a non-standardized way, which is often neccessary during data evaluation. For frequent routines there is the possibility to use dssc objects that guarantee consistent data structure, and reduce the amount of recurring code within the notebook.
- bin data using toolbox_scs.tbdet -> to be documented.
- :doc:`bin data using the DSSCBinner <dssc/DSSCBinner>`.
- post processing, data analysis -> to be documented
Point detectors
Detectors that produce one point per pulse, or 0D detectors, are all handled in a similar way. Such detectors are, for instance, the X-ray Gas Monitor (XGM), the Transmitted Intensity Monitor (TIM), the electron Bunch Arrival Monitor (BAM) or the photo diodes monitoring the PP laser.
- :doc:`extract data from point detectors <point_detectors/point_detectors>`.
Photo-Electron Spectrometer (PES)
- :doc:`Basic analysis of PES spectra <PES_spectra_extraction>`.
routines
BOZ: Beam-Splitting Off-axis Zone plate analysis
The BOZ analysis consists of 2 notebooks and a script. The first notebook
:doc:`BOZ analysis part I parameters determination <BOZ analysis part I parameters determination>`
is used to determine all the necessary correction, that is the flat field
correction from the zone plate optics and the non-linearity correction from the
DSSC gain. The inputs are a dark run and a run with X-rays on three broken or
empty membranes. For the latter, an alternative is to use pre-edge data on an
actual sample. The result is a JSON file that contains the flat field and
non-linearity correction as well as the parameters used for their determination
such that this can be reproduced and investigated in case of issues. The
determination of the flat field correction is rather quick, few minutes and is
the most important correction for the change in XAS computed from the 1st and
1st order. For quick correction of the online preview one can bypass the
non-linearity calculation by taking the JSON file as soon as it appears.
The determination of the non-linearity correction is a lot longer and can take
some 2 to 8 hours depending on the number of pulses in the
train. For this reason it is possible to use a script
scripts/boz_parameters_job.sh
in the toolbox to launch the first notebook
via slurm:
sbatch ./boz_parameters_job.sh 615 614 3
where 615 is the dark run number, 614 is the run on 3 broken membranes and 3 is the DSSC gain in photon per bin. The proposal run number is defined inside the script file.
The second notebook :doc:`BOZ analysis part II run processing <BOZ analysis part II run processing>` then use the JSON file to load all needed corrections and process an run with a corresponding dark run to bin data and compute a spectrum or a time resolved XAS scan