Changes for page Data Access at FLASH

Last modified by sndueste on 2025/02/05 11:22
From version 10.1
edited by sndueste
on 2023/02/13 12:52
Change comment: There is no comment for this version
To version 11.1
edited by sndueste
on 2024/03/13 15:10
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,11 +1,9 @@
1 1  [[image:attach:FLASHUSER.Data Acquisition and controls.DAQ and controls overview.WebHome@timescale_dataAccess.png||height="400"]]
2 2  
3 -\\
4 4  
5 5  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.
6 -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. When requested [[HDF files>>doc:FLASHUSER.Data Acquisition and controls.Data Access at FLASH (DAQ, gpfs,\.\.\.).Offline data analysis (DAQ).The FLASH HDF5 structure.WebHome]] are created after the beamtime which include the important data from [[the accelerator and its diagnostic>>doc:FLASH.FLASH1 PhotDiag stream]] as well as the data created by the [[users>>doc:FLASH.Configuring the user DAQs]]. This time scale we define as {{code language="none"}}offline{{/code}} as the HDF files are converted after the beamtime is over. For synchronous data during an experiment it is possible to create HDF slices via a {{code language="none"}}nearOnline{{/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 [[doc:FLASHUSER.Data Acquisition and controls.Data Access at FLASH (DAQ, gpfs,\.\.\.).Online data analysis.DAQmonitor.WebHome]], 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.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.Data Access at FLASH (DAQ, gpfs,\.\.\.).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 ivia 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.
7 7  
8 -\\
9 9  
10 10  (% class="wrapped" %)
11 11  |(((
... ... @@ -19,22 +19,15 @@
19 19  live up to 3s into the past
20 20  )))
21 21  |(((
22 -nearOnline
23 -)))|(((
24 -a few minutes
25 -)))
26 -|(((
27 27  offline
28 28  )))|(((
29 -after the beamtime
22 +a few minutes ... till after the beamtime
30 30  )))
31 31  
32 -\\
33 33  
34 34  [[image:attach:it-infrastructure.png||height="250"]]
35 35  
36 -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 and nearOnline 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 +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"]].
37 37  
38 -\\
39 39  
40 40  ----