Wiki source code of Data Access at FLASH
Last modified by sndueste on 2025/02/05 11:22
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | [[image:attach:FLASHUSER.Data Acquisition and controls.DAQ and controls overview.WebHome@timescale_dataAccess.png||height="400"]] | ||
| 2 | |||
| 3 | |||
| 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.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 | |||
| 7 | |||
| 8 | (% class="wrapped" %) | ||
| 9 | |((( | ||
| 10 | online | ||
| 11 | )))|((( | ||
| 12 | live at 10 Hz | ||
| 13 | ))) | ||
| 14 | |((( | ||
| 15 | online via DAQmonitor | ||
| 16 | )))|((( | ||
| 17 | live up to 3s into the past | ||
| 18 | ))) | ||
| 19 | |((( | ||
| 20 | offline | ||
| 21 | )))|((( | ||
| 22 | a few minutes ... till after the beamtime | ||
| 23 | ))) | ||
| 24 | |||
| 25 | [[image:attach:it-infrastructure.png||height="250"]] | ||
| 26 | |||
| 27 | During a beamtime at FLASH we have two IT infrastructures each with different purpose. In the FLASH halls you have local machines which are used with functional accounts and they have access to the [[beamline files-system>>url:https://confluence.desy.de/display/ASAP3/Directory+Structure||shape="rect"]] for your current experiment. For more demanding task we could also provide workstations which can be dedicated to a single user experiment. For offline analysis the [[Maxwell cluster>>url:https://confluence.desy.de/display/MXW/Maxwell+Cluster||shape="rect"]] for high performance computing is available. On the Maxwell cluster you have to work with personal accounts as this regulates data access to the [[core file-system>>url:https://confluence.desy.de/display/ASAP3/Directory+Structure||shape="rect"]]. | ||
| 28 | |||
| 29 | |||
| 30 | ---- |