This code is used to analyze data measured at FLASH using the HEXTOF (high energy X-ray time of flight) instrument. The HEXTOF uses a delay line detector (DLD) to measure the position and arrival time of single electron events.
The analysis of the data is based on "clean tables" of single events as dask dataframes.
There are two dataframes generated in the data readout process.
The main dataframe dd
contains all detected electrons and can be binned according to the needs of the experiment.
The second dataframe ddMicrobunches
contains the FEL pulses and is commonly used for normalization.
The class DldProcessor
contains the dask dataframes as well as the methods to perform binning in a parallelized fashion.
The DldFlashDataframeCreatorExpress
class subclasses DldProcessor
and is used for creating the dataframes from the hdf5 files generated by the DAQ system.
In this section we will walk you through all you need to get up and running with the hextof-processor.
For using this package with the old FLASH data structure, please refer to README_DEPR.md.
If you don't have python on your local machine yet we suggest to start with anaconda
or miniconda
.
Details about how to install can be found here.
Download the package by cloning to a local folder.
$ git clone https://github.com/momentoscope/hextof-processor.git
Create a clean new environment (We strongly suggest you to always do so!)
If you are using conda:
$ conda env create -f environment.yml
now, to activate your new environment (windows):
$ conda activate hextof-express
if you are using linux:
$ source activate hextof-express
To add the newly created environment to the Jupyter Notebooks kernel list, and install your new kernel:
(hextof-express)$ python -m ipykernel install --user --name=hextof-express
Finally, you need to initialize your local settings. This can be done by running
InitializeSettings.py
, in the same repository folder
(hextof-env)$ python InitializeSettings.py
This will create a file called SETTINGS.ini in the local repository folder. This is used to store the local settings as well as calibration values (will change in future..) and other options.
In order to make sure your folders are in the right place, open this file and modify the paths in the [path]
section.
- data_raw_dir - location where the raw h5 files from FLASH are stored
- data_h5_dir - storage of binned hdf5 files
- data_parquet_dir where the apache parquet data files from the generated single event tables are stored (we suggest using an SSD for this folder, since would greatly improve the binning performance.)
- data_results_dir folder where to save results (figures and binned arrays)
if you are installing on Maxwell, we suggest setting the following paths:
[paths]
data_raw_dir = /asap3/flash/gpfs/pg2/YYYY/data/xxxxxxxx/raw/
data_h5_dir = /asap3/flash/gpfs/pg2/YYYY/data/xxxxxxxx/processed/
data_parquet_dir = /asap3/flash/gpfs/pg2/YYYY/data/xxxxxxxx/processed/parquet/
data_results_dir = /asap3/flash/gpfs/pg2/YYYY/data/xxxxxxxx/processed/*USER_NAME*/binned/
Where YYYY
is the current year and xxxxxxxx
is the beamtime number.
If you like, in the settings, you can add the sector_correction list, which will shift any misalignment of the sectors. At the very least, this should include the "bit stealing hack" correction, where the last bits of the dldTime are set so they encode dldSectorId. This can be achieved by using the calibration.gen_sector_correction function which will generate the list for you, given the energy shifts you want.
Please refer to XPSdoniachs/README.md for compilation instructions.
In order to test your local installation, we have provided a series of tutorial Jupyter Notebooks. You can find all the relevant material in the tutorial folder in the main repository. We suggest setting testing Express data readout.ipynb.
The documentation of the package can be found here.
Examples are available as Jupyter Notebooks. Some example data is provided together with the examples. More compatible data is being collected and will soon be added to online open-access repositories.
If you use this software, please consider citing these two papers: