Correct SA3 slow data by SASE1 contribution

• correct SA3 slow data by the SASE1 contribution based on the information from Theo (https://in.xfel.eu/elog/SCS+Beamline/3640)
• adds the slowTrain lowpass averaged data from the XGM ADC
• renames the mnemonics to something more systematic in terms of the use of SA3 to identify the bunches and not the XGM device

Unfortunately, the numbers don't check out right now with what is shown in the FEL Status Display: https://in.xfel.eu/elog/SCS+Beamline/3643

Email sent to Theo and Laurent about it. Once the problems are solved we can look into merging.

It seems the problem was in the ADC saturating. (https://in.xfel.eu/elog/SCS+Beamline/3669)

added 1 commit

• d01505d3 - Adds slowTrain channels

Compare with previous version

unmarked as a Work In Progress

changed title from WIP: Correct SA3 slow data by SASA1 contribution to Correct SA3 slow data by SASE1 contribution

changed the description

This probably needs more test and restructuring...

changed the description

added 1 commit

• 57925d4a - Adds function to sort XGM data, updates calibrateXGMs(), matchXgmTimPulseId(),…

Compare with previous version

assigned to @lleguy

There is now a function cleanXGMdata() (maybe not the best name...) that sorts the XGM data by sase, giving dim 'sa1_pId' or 'sa3_pId', compatible with new and old DAQ of XGM. The TIM data also gets the dim 'sa3_pId', with the hope that in the future we can also monitor the SASE 1 pulses with TIM and have a fully consistent XGM/TIM dataset.

The calibrateXGMs() was updated and simplified when new sase-resolved XGM data is available. To be checked with Theo.

Attached a notebook with some tests.

2019-06-24_XTD10_XGM_studies_sase_resolved.ipynb

merged

mentioned in commit fd8ae729