Changes for page Data Access at FLASH

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -2,7 +2,7 @@
2	2
3	3
4	4	At the Free-electron Laser Hamburg ([[FLASH>>url:https://flash.desy.de/||shape="rect"]]) we use the Distributed Object Oriented Control System ([[DOOCS>>url:http://tesla.desy.de/doocs/doocs.html||shape="rect"]]). Devices are implemented via DOOCS servers and via [[an API >>url:https://ttfinfo.desy.de/DOOCSWiki/Wiki.jsp?page=DOOCS%20Wiki||shape="rect"]]it is possible to request data directly from the DOOCS server by knowing the DOOCS address.
5		-As correlations of different physical properties are often required all data at FLASH are indexed by the [[train ID>>doc:FLASHUSER.Data Acquisition and controls.Controls (DOOCS, jDDD,\.\.\.).How to read Train IDs at FLASH.WebHome]], which identifies each pulse train. The data recorded during a beamtime are stored via a Data Acquisition System ([[DAQ>>doc:FLASHUSER.Data Acquisition and controls.Data Access at FLASH (DAQ, gpfs,\.\.\.).Offline data analysis (DAQ).WebHome]]) which sorts all events from the individual DOOCS server by train ID. Requested [[HDF files>>doc:FLASHUSER.Data Acquisition and controls.DAQ and controls overview.Offline data analysis (DAQ).The FLASH HDF5 structure.WebHome]] are created to analyze s(% id="cke_bm_2799S" style="display:none" %) (%%)ynchronous data during an experiment via an {{code language="none"}}HDF{{/code}} converter within a few minutes. Reading synchronous data via an {{code language="none"}}online{{/code}} API is possible via a configurable DAQ middle layer server, the DAQmonitor, which feeds the correlated data back in the control system while it provides a ring buffer with 32 events in size.
	5	+As correlations of different physical properties are often required all data at FLASH are indexed by the [[train ID>>doc:FLASHUSER.Data Acquisition and controls.Controls (DOOCS, jDDD,\.\.\.).How to read Train IDs at FLASH.WebHome]], which identifies each pulse train. The data recorded during a beamtime are stored via a Data Acquisition System ([[DAQ>>doc:FLASHUSER.Data Acquisition and controls.DAQ and controls overview.Offline data analysis (DAQ).WebHome]]) which sorts all events from the individual DOOCS server by train ID. Requested [[HDF files>>doc:FLASHUSER.Data Acquisition and controls.DAQ and controls overview.Offline data analysis (DAQ).The FLASH HDF5 structure.WebHome]] are created to analyze s(% id="cke_bm_2799S" style="display:none" %) (%%)ynchronous data during an experiment via an {{code language="none"}}HDF{{/code}} converter within a few minutes. Reading synchronous data via an {{code language="none"}}online{{/code}} API is possible via a configurable DAQ middle layer server, the DAQmonitor, which feeds the correlated data back in the control system while it provides a ring buffer with 32 events in size.
6	6
7	7
8	8	(% class="wrapped" %)