Skip to content

data interpretation from a TDC recorded by a MCP-DLD #74

@daviddoji

Description

@daviddoji

as already discussed with @kluyvert and @schmidtp, it would be nice to find a way for better displaying the data recorded by an MCP-DLD that are processed by a TDC. As of now, with EXtra-data one has to read individual arrays separately.
The path and the data types can be seen in the following screenshot

image

where 500 is the trainId chunked by the DAQ and 1000 is the fixed size array needed by DAQ.
From those 1000 columns, only N of them would have meaningful data, where N is given by the number of events calculated (not necessarily the same as the number of pulses) by the TDC and can vary from train to train. The rest of the columns are just zeros and could be deleted.

In the following path, one can find a couple of files with "ideally perfect" data (arrays ADC and timeTag will not be present in the data anymore):
/gpfs/exfel/exp/SXP/202331/p900367/raw/r0078

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions