Version 6.1 by sendels on 2019/08/22 16:04
Show last authors
1 \\
2
3 [[~[~[image:url:http://hasfweb.desy.de/pub/Setup/DataAccessGeneralConcept/timescale_dataAccess.png~|~|alt="timescale_dataAccess.png"~]~]>>attach:FLASHUSER.Data Acquisition and controls.DAQ and controls overview.WebHome@timescale_dataAccess.png]]
4
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 server and via an API ( [[ONLINE>>doc:FLASH.Online access to DOOCS properties]]) 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 [[trainID>>doc:FLASHUSER.Data Acquisition and controls.Controls (DOOCS, jDDD,\.\.\.).How to read Train IDs at FLASH.WebHome]], which identify each of FLASH's pulse trains. The during a beamtime recorded data 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 sort all events from the individual DOOCS server by trainID. 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 includes the important data from [[the accelerator and its diagnostic>>doc:FLASHUSER.FLASH1 PhotDiag stream]] as well as the data created by the [[users>>doc:FLASHUSER.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 shorter HDF slices via a {{code language="none"}}nearOnline{{/code}} converter within a few minutes. For working with this partially incomplete HDF slices we provide an API called [[BeamtimeDaqAccess>>doc:FLASHUSER.Near-Online data analysis]]. 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.
7
8 \\
9
10 (% class="wrapped" %)
11 |(((
12 online
13 )))|(((
14 live at 10 Hz
15 )))
16 |(((
17 online via DAQmonitor
18 )))|(((
19 live up to 3s into the past
20 )))
21 |(((
22 nearOnline
23 )))|(((
24 a few minutes
25 )))
26 |(((
27 offline
28 )))|(((
29 after the beamtime
30 )))
31
32 [[~[~[image:url:http://hasfweb.desy.de/pub/Setup/DataAccessGeneralConcept/it-infrastructure.png~|~|alt="it-infrastructure.png"~]~]>>attach:it-infrastructure.png]]
33
34 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/IS/Maxwell||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"]].
35
36 \\
37
38 ----