140 likes | 219 Views
A user’s experience of the FLASH DAQ system. praise & dispraise suggestions for improvement. outline. What we had What we did What problems we had What we can do better. what we had - a user’s view. user experiment. VME Crate front end. camera data TOF data.
E N D
A user’s experience of the FLASH DAQ system praise & dispraise suggestions for improvement Michael Wellhöfer
outline What we had What we did What problems we had What we can do better Michael Wellhöfer
what we had - a user’s view user experiment VME Crate front end camera data TOF data fast ADC 9MHz 24 bit bunch id trigger output • possibility to store • fast ADC data 2-20GHz • images analog GMD signal DAQ machine data local harddisk DAQ Michael Wellhöfer
use C++ / ROOT (not everybody familiar with) analysis is lengthy correlation for free all data in one file what we did use DAQ as measurement tool? Cons Pros included measurement devices in DAQ environment Michael Wellhöfer
what we did ROOT experimental setup acquisition devices machine data analysis of data collected with DAQ Michael Wellhöfer
what we did ROOT acquisition devices experimental setup machine data analysis of data collected with DAQ Michael Wellhöfer
pressure [mbar] pulse energy [µJ] DAQ helped to clean out artefacts what we did machine fluctuations? Michael Wellhöfer
Acqiris data vs. GMD data correlation of GMD, image event and Acqiris event works what we did binned image vs. GMD data Michael Wellhöfer
what problems we had 2005 use windows pcs with 24bit input/output register e.g. Le Croy oscilloscope, firewire cameras, acqiris digitizer problem: pc not triggered, bunch id sometimes shifted by one entry arbitrarily impossible to correlate data afterwards 2006 use linux pcs with ip timer card e.g. firewire cameras, ICCD cameras, acqiris digitizer accurate correlation Michael Wellhöfer
what problems we had before beamtime... • lengthy preparation of beam time • programming of DAQ servers • hardware adaption of devices e.g. Acqiris, Firewire cameras Michael Wellhöfer
what problems we had during beamtime... • slow update rate of the displays (ADC data, images) • limited viewing possibility • only 8000 data points possible • no user defined trace selection • limited data rate • example: acqiris only 800.000 datapoints per acquisition • limited online analysis (middle layer server has to be programmed) Michael Wellhöfer
what problems we had after beamtime... • how to get data back • staging process limited to certain computers • not accessible from outside DESY • correlation of GMD data with user run!!! Michael Wellhöfer
what we can do better • easier access to root files • archive made accessible from outside DESY • computing power provided by DESY • user harddisk to store data • software interface tools to preevaluate data easy conversion to ASCII • more user friendly RUN control interface • easier selection of channels in one device • easier selection of devices (naming) • documentation • online analysis (user defined) • slow ADC to feed user data (e.g. position of drive stage) in DAQ Michael Wellhöfer
conclusion • in principle DAQ works fine from a user’s point of view • data is correlated • everything in one file • improvements to be made! • preanalysis tools • data handling • online viewing and analysis Michael Wellhöfer