Wiki source code of The FLASH HDF5 structure

Version 82.1 by sndueste on 2024/05/17 10:13

version	line-number	content
44.1	1	{{layout}}
	2	{{layout-section ac:type="single"}}
	3	{{layout-cell}}
1.1	4	== Contents ==
	5
	6
	7
13.1	8	{{toc/}}
1.1	9
	10
	11	== General information about HDF5 ==
	12
79.1	13	HDF5 is a data format maintained by the HDF group. For detailed general information see [[here~[~[image:url:http://hasfweb.desy.de/pub/TWiki/TWikiDocGraphics/external-link.gif~\|~\|height="12" width="13"~]~]>>url:https://portal.hdfgroup.org/display/support\|\|shape="rect"]]
1.1	14
79.1	15	To download the HDF5 Viewer click [[here~[~[image:url:http://hasfweb.desy.de/pub/TWiki/TWikiDocGraphics/external-link.gif~\|~\|height="12" width="13"~]~]>>url:https://portal.hdfgroup.org/display/support/Download+HDFView\|\|shape="rect"]]
1.1	16
79.1	17	For use on the DESY Maxwell or PAL (max-fsc or pal) hdfview is available in the xray module :
	18	{{code language="none"}}> module load xray{{/code}}
1.1	19	{{code language="none"}}> hdfview{{/code}}
	20
49.1	21	or you can use
	22
79.1	23	{{code language="none"}}
	24	> silx view
	25	{{/code}}
49.1	26
	27
4.1	28	[[Contents>>doc:\|\|anchor="Contents"]]
1.1	29
45.1	30	== The FLASH HDF5 format ==
1.1	31
45.1	32	FLASH provides a conversion of its data acquisition (DAQ) to the commonly used [[HDF5>>url:https://www.hdfgroup.org/solutions/hdf5/\|\|shape="rect"]] format. Correlated data are mapped by a primary index called train ID. Every data set has an individual index of train IDs to identify the data even when data are missing or deviate in update rate. If the data set of choice contains gaps, users have to decide how to treat missing values. DAQ channels are spread across various files with one file name pattern for each DAQ. This means users have to assemble data from different files if necessary.
40.1	33
	34	The hierarchy is realized using a human readable named HDF tree with each DAQ channel containing the data sets "//value//" and "//index//". Additionally, the HDF group //zraw// contains a tree of the original DAQ channel names.
	35
	36	Reference implementation, which follows the concept of Python libraries like Pandas, Xarray, or Dask, is given below.
	37
	38	{{expand title="Discontinued HDF formats"}}
47.1	39	=== Comparison to FLASH's deprecated HDF formats ===
40.1	40
	41	Before 2021, FLASH provided two different HDF formats formally known as //near-online// and //offline// HDF files.
	42
	43	All data sets were aligned by the same global index by filling in missing data. Fast DAQ channels (pulse synchronous data - update 10 Hz) are filled in by NaN or 0, slow channels (not pulse synchronous data - update e.g. 1 Hz ) are interpolated by the DAQs libraries, by keeping the value constant up to the next change.
	44
	45	While the near-online HDF files were converted live during the beamtime, the offline HDF files were manually compiled weeks/months later. Near-online HDF files were used by a provided API [[BeamtimeDaqAccess>>url:https://confluence.desy.de/display/FLASHUSER/Near-Online+data+analysis#Near-Onlinedataanalysis-BriefUserGuidetoBeamtimeDAQAccess\|\|shape="rect"]], which also searches for DAQ channels in files. With assembled files "by run", all DAQ channels were existing in the same HDF file. While shorter runs usually fitted into one file, longer runs still had to be aggregated over several files. The creation of the assembled type of files still involves the use of fairly unstable DAQ Mex-functions As the environment required for using the Mex-functions is already deprecated, its continued existence is uncertain.
	46
	47	The HDF hierarchy is almost identical in all formats. While in the the recent format each DAQ channel contains the data sets "value" and "index", the deprecated format had one data set for each DAQ channel. The deprecated formats supplies no time axis parameters for spectra data types.
45.1	48
	49
46.1	50	HDF5 example files (old format)
45.1	51
	52	Here we have a few HDF5 samples (User data combined with Photon diagnostics data) from a few beamtimes showing the different kind options.
	53
	54	[[image:attach:image2019-10-21_17-2-50.png\|\|thumbnail="true" width="300"]] [[download HDF5 (Images @ FL2)>>url:https://desycloud.desy.de/index.php/s/nyEgeCWJFC4gao2\|\|shape="rect"]]
	55
	56
	57	[[~[~[image:attach:image2019-10-22_10-52-27.png~\|~\|thumbnail="true" width="300"~]~]download HDF5 (GHz ADC and OPIS @ FL2)>>url:https://desycloud.desy.de/index.php/s/AeA2kPNNnZgX95A\|\|shape="rect"]]
	58
	59
79.1	60
40.1	61	{{/expand}}
	62
45.1	63	=== HDF examples: ===
44.1	64	{{/layout-cell}}
	65	{{/layout-section}}
40.1	66
44.1	67	{{layout-section ac:type="three_equal"}}
	68	{{layout-cell}}
79.1	69	* ADC data as example for fast data (10 Hz):
40.1	70
44.1	71	[[image:attach:image2020-11-16_15-26-28.png\|\|height="250"]]
	72	{{/layout-cell}}
	73
	74	{{layout-cell}}
71.1	75	* The //average// FEL pulse energy as example for the slow data. Here the data is not saved with 10 Hz - thus not for every FEL pulse train. The data is typically saved with 1 Hz if the values are changing (like the FEL energy) and every about 20 sec if there is no change for longer time ( e.g. motor set values). Thus to use the data together with the "fast" one, one has to interpolate the data as explained in the examples in the repos below show (e.g. {{code language="none"}}df['GMD_T_average'] = df['GMD_T_average'].interpolate(method='linear'){{/code}})
44.1	76
70.1	77	( as example only every 10th train ID is listed in the HDF group "index")
40.1	78
44.1	79	[[image:attach:image2020-11-16_15-31-45.png\|\|height="250"]]
	80	{{/layout-cell}}
	81
	82	{{layout-cell}}
41.1	83	* (((
44.1	84	//zraw// group contains the original DAQ (DOOCS) names
41.1	85	)))
40.1	86
41.1	87	of the properties saved in the DESY internal raw format. (For experts)
40.1	88
	89
44.1	90	[[image:attach:image2020-11-16_16-26-3.png\|\|height="400"]]
	91	{{/layout-cell}}
	92	{{/layout-section}}
41.1	93
44.1	94	{{layout-section ac:type="single"}}
	95	{{layout-cell}}
53.1	96	{{info}}
79.1	97	=== There are different options that help you to work with the FLASH HDF5 data in Python ===
40.1	98
78.1	99	* The currently developed option for large data sets: [[the FAB package>>url:https://hasfcpkg.desy.de/fab/fab.html\|\|shape="rect"]] ... see below
	100	* and for smaller projects: (% class="Object" %)[[https:~~/~~/gitlab.desy.de/christopher.passow/flash-daq-hdf>>url:https://gitlab.desy.de/christopher.passow/flash-daq-hdf\|\|shape="rect"]]
40.1	101
78.1	102	(% class="Object" %)See also the collection of Demo data and sample scripts : [[doc:FLASHUSER.Data Acquisition and controls.Data Access at FLASH (DAQ, gpfs,\.\.\.).Offline data analysis (DAQ).Collection of HDF5 sample data from different beamlines.WebHome]] and [[doc:FLASHUSER.Data Acquisition and controls.Data Access at FLASH (DAQ, gpfs,\.\.\.).Offline data analysis (DAQ).DEMO - Working with FLASH data.WebHome]]
40.1	103	{{/info}}
44.1	104	{{/layout-cell}}
	105	{{/layout-section}}
40.1	106
44.1	107	{{layout-section ac:type="single"}}
	108	{{layout-cell}}
63.1	109
	110
45.1	111	== Complete list of recordable parameters ==
40.1	112
79.1	113	The complete list for the relation between DOOCS names and HDF5 names for the recordable parameters can be found in [[DESY's Repository~[~[image:url:http://hasfweb.desy.de/pub/TWiki/TWikiDocGraphics/external-link.gif~\|~\|height="12" width="13"~]~]>>url:https://stash.desy.de/projects/CS/repos/pah/browse/src/camp/data/channel2HdfName.dat\|\|shape="rect"]].
	114
1.1	115
79.1	116	== Most popular FLASH parameters and their names in HDF5, DOOCS and (raw) DAQ ==
1.1	117
30.1	118	{{id name="DOOCSparameters"/}}
	119
5.1	120	Note, the HDF group and data set names apply to our HDF tree version since vers. 0.3.0.
1.1	121
	122
	123	=== FLASH1 ===
	124
	125	==== Beamline info (FLASH1) ====
	126
79.1	127	{{code language="none"}}/FL1/Beamlines/Attenuator/pressure{{/code}}
	128	//always saved (PBD)//
	129	DOOCS prop : {{code language="none"}}FLASH.FEL/GAS_DOSING/FL1.ATTENUATOR/PRESSURE{{/code}}
	130	DAQ channel: {{code language="none"}}FLASH.FEL/GAS_DOSING/FL1.ATTENUATOR/PRESSURE{{/code}}
	131	desc: set pressure in the gas attenuator
1.1	132	units: mbar
79.1	133
1.1	134
79.1	135	{{code language="none"}}/FL1/Beamlines/BL/Fast shutter/open{{/code}}
	136	//always saved (PBD)//
	137	DOOCS prop : {{code language="none"}}FLASH.FEL/ADC.SIS.FL1FS/BL.SHUTTER/CH00.TD{{/code}}
	138	DAQ channel: {{code language="none"}}FLASH.FEL/ADC.SIS.FL1FS/BL.SHUTTER{{/code}}
	139	desc: BL Beamline Fast shutter state: 1 is open, 0 is closed ( for technical reasons there are 100 vales of this state saved ...)
1.1	140	units: none
	141
79.1	142	{{code language="none"}}/FL1/Beamlines/PG/Fast shutter/open{{/code}}
	143	//always saved (PBD)//
	144	DOOCS prop : {{code language="none"}}FLASH.FEL/ADC.SIS.FL1FS/PG.SHUTTER/CH00.TD{{/code}}
	145	DAQ channel: {{code language="none"}}FLASH.FEL/ADC.SIS.FL1FS/PG.SHUTTER{{/code}}
	146	desc: PG Beamline Fast shutter state: 1 is open, 0 is closed ( for technical reasons there are 100 vales of this state saved ...)
1.1	147	units: none
	148
79.1	149	{{code language="none"}}/FL1/Beamlines/BL/Filters/BL filter wheel/position filter 1{{/code}}
	150	//always saved (PBD)//
	151	DOOCS prop : {{code language="none"}}TTF2.FEL/BLFILTERS1/FILTER1/FW.MOTOR.POS{{/code}}
	152	DAQ channel: {{code language="none"}}TTF2.FEL/BLFILTERS1/FILTER1/FW.MOTOR.POS{{/code}}
24.1	153	desc: Position of the BL filter wheel 1 - to correlate with the filter material please look [[here>>doc:FLASHUSER.jddd-linked help pages.Filter-Units.Filter wheels in FLASH1 and FLASH2.WebHome]]
1.1	154	units: degree
79.1	155
1.1	156
79.1	157	{{code language="none"}}/FL1/Beamlines/BL/Filters/BL filter wheel/position filter 2{{/code}}
	158	//always saved (PBD)//
	159	DOOCS prop : {{code language="none"}}TTF2.FEL/BLFILTERS2/FILTER2/FW.MOTOR.POS{{/code}}
	160	DAQ channel: {{code language="none"}}TTF2.FEL/BLFILTERS2/FILTER2/FW.MOTOR.POS{{/code}}
24.1	161	desc: Position of the BL filter wheel 2 - to correlate with the filter material please look [[here>>doc:FLASHUSER.jddd-linked help pages.Filter-Units.Filter wheels in FLASH1 and FLASH2.WebHome]]
1.1	162	units: degree
79.1	163
1.1	164
79.1	165	{{code language="none"}}/FL1/Beamlines/PG/Filters/position filter 1{{/code}}
	166	//always saved (PBD)//
	167	DOOCS prop : = TTF2.FEL/BDAF1/BDA.F1/FW.MOTOR.POS=
	168	DAQ channel: {{code language="none"}}TTF2.FEL/BDAF1/BDA.F1/FW.MOTOR.POS{{/code}}
	169	desc: Position of the PG filter wheel 1
1.1	170	units: degree
79.1	171
1.1	172
79.1	173	{{code language="none"}}/FL1/Beamlines/PG/Filters/position filter 2{{/code}}
	174	//always saved (PBD)//
	175	DOOCS prop : {{code language="none"}}TTF2.FEL/BDAF2/BDA.F2/FW.MOTOR.POS{{/code}}
	176	DAQ channel: {{code language="none"}}TTF2.FEL/BDAF2/BDA.F2/FW.MOTOR.POS{{/code}}
	177	desc: Position of the PG filter wheel 2
1.1	178	units: degree
79.1	179
1.1	180
79.1	181	{{code language="none"}}/FL1/Beamlines/PG/Filters/position filter 3{{/code}}
	182	//always saved (PBD)//
	183	DOOCS prop : {{code language="none"}}TTF2.FEL/PGFILTERS/PGFILTERS/FW.MOTOR.POS{{/code}}
	184	DAQ channel: {{code language="none"}}TTF2.FEL/PGFILTERS/PGFILTERS/FW.MOTOR.POS{{/code}}
	185	desc: Position of the PG filter wheel 3
1.1	186	units: degree
8.1	187
1.1	188
8.1	189
34.1	190	NOTE: Aperture positions in the beamline as well as the positions of the beam steering mirrors are also saved. For more Info contact your local contact
8.1	191
4.1	192	[[Contents>>doc:\|\|anchor="Contents"]]
1.1	193
8.1	194
39.1	195	==== Photon Diagnostics SASE ([[GMD>>url:http://photon-science.desy.de/facilities/flash/photon_diagnostics/gmd_intensity_and_position/index_eng.html\|\|shape="rect"]]) ====
1.1	196
55.1	197	{{expand title="Discontinued GMD format (used until 2021)"}}
79.1	198	(% style="color:#000000" %)Discontinued GMD data recording / evaluation (VME + PhotonFlux ML server)
39.1	199
79.1	200	{{code language="none"}}/FL1/Photon Diagnostic/GMD/Average energy/energy tunnel{{/code}}
40.1	201	//always saved (PBD)//
34.1	202
79.1	203	(% style="color:#000000" %)DOOCS prop : {{code language="none"}}TTF2.DAQ/PHFLUX/OUT04/VAL{{/code}} (%%)
	204	(% style="color:#000000" %)DAQ channel: {{code language="none"}}PBD.PHFLUX/TUNNEL.ENPULSEIC{{/code}}(%%)
	205	desc : calibrated average SASE Energy/pulse measured in the TUNNEL upstream the gas attenuator (ion current)
1.1	206	units : microJ
	207
79.1	208	{{code language="none"}}/FL1/Photon Diagnostic/GMD/Pulse resolved energy/energy tunnel{{/code}}
34.1	209	//always saved (PBD)//
	210
79.1	211	DOOCS prop : {{code language="none"}}TTF2.DAQ/PHFLUX/OUT34/VAL{{/code}}
	212	DAQ channel: {{code language="none"}}PBD.PHFLUX/TUNNEL.ENERGYPULSE.USER{{/code}}
1.1	213	desc :Energy per pulse Tunnel (from e-) - the values are set to "0" if there was no SASE beam in the FEL
23.1	214	units : a.u. (more or less µJ but need to be calibrated with the "Average energy" for good precision) [[see here for help>>doc:FLASHUSER.jddd-linked help pages.Calibrating the pulse resolved (electron) data from GMD.WebHome]]
1.1	215
79.1	216	{{code language="none"}}/FL1/Photon Diagnostic/GMD/Pulse resolved energy/energy tunnel (raw){{/code}}
	217	//always saved (PBD)//
	218	DOOCS prop : {{code language="none"}}TTF2.DAQ/PHFLUX/OUT14/VAL{{/code}}
	219	DAQ channel: {{code language="none"}}PBD.PHFLUX/TUNNEL.ENERGYPULSE.FF{{/code}}
	220	desc :Energy per pulse Tunnel (from e-) - uncorrected values. There are also values saved if there was no beam ... just background noise
23.1	221	units : a.u. (more or less µJ but need to be calibrated with the "Average energy" for good precision) [[see here for help>>doc:FLASHUSER.jddd-linked help pages.Calibrating the pulse resolved (electron) data from GMD.WebHome]]
1.1	222
79.1	223	{{code language="none"}}/FL1/Photon Diagnostic/GMD/Average energy/energy BDA{{/code}}
34.1	224	//always saved (PBD)//
	225
79.1	226	DOOCS prop : {{code language="none"}}TTF2.DAQ/PHFLUX/OUT05/VAL{{/code}}
	227	DAQ channel: {{code language="none"}}PBD.PHFLUX/BDA.ENPULSEIC{{/code}}
1.1	228	desc : calibrated average SASE Energy/pulse measured in the BDA (in the experimental hall) after the attenuator (ion current)
	229	units : microJ
	230
79.1	231	{{code language="none"}}/FL1/Photon Diagnostic/GMD/Pulse resolved energy/energy BDA{{/code}}
34.1	232	//always saved (PBD)//
	233
79.1	234	DOOCS prop : {{code language="none"}}TTF2.DAQ/PHFLUX/OUT35/VAL{{/code}}
	235	DAQ channel: {{code language="none"}}PBD.PHFLUX/BDA.ENERGYPULSE.USER{{/code}}
1.1	236	desc :Energy per pulse BDA (from e-) - the values are set to "0" if there was no SASE beam in the FEL
23.1	237	units : a.u. (more or less µJ but need to be calibrated with the "Average energy" for good precision) [[see here for help>>doc:FLASHUSER.jddd-linked help pages.Calibrating the pulse resolved (electron) data from GMD.WebHome]]
1.1	238
79.1	239	{{code language="none"}}/FL1/Photon Diagnostic/GMD/Pulse resolved energy/energy BDA (raw){{/code}}
	240	//always saved (PBD)//
	241	DOOCS prop : {{code language="none"}}TTF2.DAQ/PHFLUX/OUT15/VAL{{/code}}
	242	DAQ channel: {{code language="none"}}PBD.PHFLUX/BDA.ENERGYPULSE.FF{{/code}}
	243	desc :Energy per pulse BDA (from e-) - uncorrected values. There are also values saved if there was no beam ... just background noise
23.1	244	units : a.u. (more or less µJ but need to be calibrated with the "Average energy" for good precision) [[see here for help>>doc:FLASHUSER.jddd-linked help pages.Calibrating the pulse resolved (electron) data from GMD.WebHome]]
54.1	245	{{/expand}}
1.1	246
34.1	247
79.1	248	(% style="color:#000000; letter-spacing:0px" %)NEW (since 2021) GMD data recording / evaluation (same format as FLASH2 and XFEL)
54.1	249
79.1	250	{{code language="none"}}/FL1/Photon Diagnostic/GMD/Average energy/energy tunnel{{/code}}
	251	//always saved (PBD)//
	252	(% style="color:#000000" %)DOOCS prop : {{code language="none"}}FLASH.FEL/XGM.PHOTONFLUX/FL1.TUNNEL/PHOTONFLUX.UJ{{/code}} (%%)
	253	(% style="color:#000000" %)DAQ channel: {{code language="none"}}FLASH.FEL/XGM.PHOTONFLUX/FL1.TUNNEL/PHOTONFLUX.UJ{{/code}}
39.1	254
79.1	255	desc : calibrated average SASE Energy/pulse measured in the TUNNEL upstream the gas attenuator
39.1	256	units : microJ
	257
	258
79.1	259	{{code language="none"}}/FL1/Photon Diagnostic/GMD/Pulse resolved energy/energy tunnel{{/code}}
39.1	260	//always saved (PBD)//
	261
79.1	262	(% style="color:#000000" %)DOOCS prop :
39.1	263	{{code language="none"}}FLASH.FEL/XGM.INTENSITY/FL1.TUNNEL/INTENSITY.TD{{/code}}DAQ channel: {{code language="none"}}FLASH.FEL/XGM.INTENSITY/FL1.TUNNEL/INTENSITY.TD{{/code}}
	264
	265	desc : Energy per pulse measured in the Tunnel. In addition measurement errors and beam position are included for EACH pulse in the pulse train !! (see below)
	266	units : a.u. (more or less µJ but need to be calibrated with the "Average energy" for good precision) [[see here for help>>doc:FLASHUSER.jddd-linked help pages.Calibrating the pulse resolved (electron) data from GMD.WebHome]]
	267
	268	{{info title="GMD pulse resolved data structure"}}
79.1	269	For every pulse in the pulse train the information is saved:
39.1	270
	271
	272	1. Intensity per pulse (a.u. (more or less µJ ))
	273	1. Intensity per pulse (auxillary GMD) - not used
	274	1. Position horizontal (mm, for a single pulse the position information may be very noisy - talk to your local contact)
	275	1. Position vertical (mm, for a single pulse the position information may be very noisy - talk to your local contact)
79.1	276	1. Intensity per pulse sigma (a.u. (more or less µJ ), (% style="color:#000000" %)This parameter gives an indication of the error of the measurement of the pulse energy. This takes signal to noise, detector resolution, uncertainties in crossection etc into account. (it is NOT the measurement of the statistical fluctuation of the SASE pulses)(%%))
39.1	277	1. Position horizontal sigma (mm, indicates the error (RMS, sigma) of the measurement according to known uncertainties and signal to noise)
	278	1. Position vertical sigma (mm, indicates the error (RMS, sigma) of the measurement according to known uncertainties and signal to noise)
	279	1. Combined warning and error flags
	280
	281	The pulse energy and the error are plotted for the first bunch of the pulse trains saved in this
	282	file
	283
	284
	285	[[image:attach:image2021-2-9_10-51-6.png\|\|height="250"]]
	286
79.1	287
39.1	288	{{/info}}
	289
79.1	290	All values for the GMD are also available for the BDA GMD which is located in the experimental hall down stream the gas attenuator. If the attenuator is on the ratio between BDA and Tunnel signal shows the attenuation. BUT NOTE that the filter units are downstream the GMD. So if filters are used this influence is NOT measured by the GMD BDA !
39.1	291
	292
	293	Besides pulse energy the GMD also provides information about the beam position
	294
79.1	295	{{code language="none"}}/FL1/Photon Diagnostic/GMD/Beam position/position BDA horizontal{{/code}}
	296	//always saved (PBD)//
	297	DOOCS prop : {{code language="none"}}FLASH.FEL/XGM.POSMON/FL1.BDA/IX.POS{{/code}}
	298	DAQ channel: {{code language="none"}}FLASH.FEL/XGM.POSMON/FL1.BDA/IX.POS{{/code}}
	299	desc :Beam position of the photon Beam determined by the GMD (BDA, x=horizontal)
1.1	300	units : mm
	301
79.1	302	{{code language="none"}}/FL1/Photon Diagnostic/GMD/Beam position/position BDA vertical{{/code}}
	303	//always saved (PBD)//
	304	DOOCS prop : {{code language="none"}}FLASH.FEL/XGM.POSMON/FL1.BDA/IY.POS{{/code}}
	305	DAQ channel: {{code language="none"}}FLASH.FEL/XGM.POSMON/FL1.BDA/IY.POS{{/code}}
	306	desc :Beam position of the photon Beam determined by the GMD (BDA, y=vertical)
1.1	307	units : mm
	308
79.1	309	{{code language="none"}}/FL1/Photon Diagnostic/GMD/Beam position/position tunnel horizontal{{/code}}
	310	//always saved (PBD)//
	311	DOOCS prop : {{code language="none"}}FLASH.FEL/XGM.POSMON/FL1.TUNNEL/IX.POS{{/code}}
	312	DAQ channel: {{code language="none"}}FLASH.FEL/XGM.POSMON/FL1.TUNNEL/IX.POS{{/code}}
	313	desc :Beam position of the photon Beam determined by the GMD (TUNNEL, x=horizontal)
1.1	314	units : mm
	315
79.1	316	{{code language="none"}}/FL1/Photon Diagnostic/GMD/Beam position/position tunnel vertical{{/code}}
	317	//always saved (PBD)//
	318	DOOCS prop : {{code language="none"}}FLASH.FEL/XGM.POSMON/FL1.TUNNEL/IY.POS{{/code}}
	319	DAQ channel: {{code language="none"}}FLASH.FEL/XGM.POSMON/FL1.TUNNEL/IY.POS{{/code}}
	320	desc :Beam position of the photon Beam determined by the GMD (TUNNEL, y=vertical)
1.1	321	units : mm
	322
39.1	323
	324	==== Spectrometer (FLASH1) ====
	325
79.1	326	{{code language="none"}}/FL1/Photon Diagnostic/Wavelength/Tunnelspectrometer/wavelength{{/code}}
	327	_always saved (when Spectrum is measured !!) (PBD) _
	328	DOOCS prop : {{code language="none"}}TTF2.EXP/PHOTONWL.ML/WAVE_LENGTH/VAL.TD{{/code}}
	329	DAQ channel: {{code language="none"}}PBD.PHOTONWL.ML/WAVE_LENGTH{{/code}}
	330	desc : XUV Spectrum measured with the "tunnel spectrometer"
1.1	331	units :
	332
79.1	333	{{code language="none"}}/FL1/Photon Diagnostic/Wavelength/Tunnelspectrometer/wavelength start value{{/code}}
	334	_always saved (when Spectrum is measured !!) (PBD) _
	335	DOOCS prop : {{code language="none"}}TTF2.EXP/PBD.PHOTONWL.ML/BSTART/VAL{{/code}}
	336	DAQ channel: {{code language="none"}}TTF2.EXP/PBD.PHOTONWL.ML/BSTART/VAL{{/code}}
	337	desc : start value (in nm) for the wavelength axis of the XUV Spectrum measured with the "tunnel spectrometer"
1.1	338	units : nm
	339
79.1	340	{{code language="none"}}/FL1/Photon Diagnostic/Wavelength/Tunnelspectrometer/wavelength increment{{/code}}
	341	_always saved (when Spectrum is measured !!) (PBD) _
	342	DOOCS prop : ==
	343	DAQ channel: ==
	344	desc : increment value (in nm) for each pixel for the wavelength axis of the XUV Spectrum measured with the "tunnel spectrometer"
1.1	345	units : nm
	346
79.1	347	{{code language="none"}}/FL1/Photon Diagnostic/Wavelength/PG2 spectrometer/photon energy{{/code}}
	348	//saved on DEMAND (PBD spectrometer stream)//
	349	DOOCS prop : ==
	350	DAQ channel: {{code language="none"}}PBD.PHOTONEN.ML/PHOTON_ENERGY{{/code}}
1.1	351	desc : XUV Spectrum in eV measured with the "PG2 spectrometer"
	352	units :
	353
79.1	354	{{code language="none"}}/FL1/Photon Diagnostic/Wavelength/PG2 spectrometer/photon energy start value{{/code}}
	355	//saved on DEMAND (PBD spectrometer stream)//
	356	DOOCS prop : ==
	357	DAQ channel: ==
	358	desc : start value (in eV) for the wavelength axis of the XUV Spectrum measured with the "PG2 spectrometer"
1.1	359	units : eV
	360
79.1	361	{{code language="none"}}/FL1/Photon Diagnostic/Wavelength/PG2 spectrometer/photon energy increment{{/code}}
	362	//saved on DEMAND (PBD spectrometer stream)//
	363	DOOCS prop : ==
	364	DAQ channel: ==
	365	desc : increment value (in eV) for each pixel for the wavelength axis of the XUV Spectrum measured with the "PG spectrometer"
1.1	366	units : eV
	367
79.1	368	{{code language="none"}}/FL1/Photon Diagnostic/Wavelength/PG2 spectrometer/photon wavelength{{/code}}
	369	//saved on DEMAND (PBD spectrometer stream)//
	370	DOOCS prop : ==
	371	DAQ channel: {{code language="none"}}PHOTONEN.ML/PHOTON_WAVE_LEN{{/code}}
1.1	372	desc : XUV Spectrum in nm measured with the "PG2 spectrometer"
	373	units :
	374
79.1	375	{{code language="none"}}/FL1/Photon Diagnostic/Wavelength/PG2 spectrometer/photon wavelength increment{{/code}}
	376	//saved on DEMAND (PBD spectrometer stream)//
	377	DOOCS prop : ==
	378	DAQ channel: ==
	379	desc : start value (in nm) for the wavelength axis of the XUV Spectrum measured with the "PG2 spectrometer"
1.1	380	units : nm
	381
79.1	382	{{code language="none"}}/FL1/Photon Diagnostic/Wavelength/PG2 spectrometer/photon wavelength start value{{/code}}
	383	//saved on DEMAND (PBD spectrometer stream)//
	384	DOOCS prop : ==
	385	DAQ channel: ==
	386	desc : increment value (in nm) for each pixel for the wavelength axis of the XUV Spectrum measured with the "PG spectrometer"
1.1	387	units : nm
	388
4.1	389	[[Contents>>doc:\|\|anchor="Contents"]]
1.1	390
	391	==== Electron Beam properties (FLASH1) ====
	392
	393	===== bunch charge =====
	394
79.1	395	{{code language="none"}}/FL1/Electron Diagnostic/Bunch charge/after undulator{{/code}}
	396	//always saved (PBD)//
	397	DOOCS prop : {{code language="none"}}FLASH.DIAG/TOROID.ML/12EXP/CHARGE.FLASH1{{/code}}
	398	DAQ channel: {{code language="none"}}FLASH.DIAG/TOROID/12EXP{{/code}}
	399	desc: electron bunch charge (FLASH1)
1.1	400	units: nC
	401
5.1	402	=====
57.1	403	arrival time (BAM) =====
1.1	404
57.1	405	{{info title="BAM information: updates 2022"}}
59.1	406	* see: [[Info collection about the BAMs and how to use the BAM data>>url:https://confluence.desy.de/display/FLASHUSER/Info+collection+for+the+BAM\|\|shape="rect"]]
57.1	407	* The data format of the BAM has been completely altered in the 2022 shutdown
	408	* before 2022 BAMs were always saving the arrival time information for each 1µs bucked regardless if there were electrons in the accelerator or not. IN addition the arrival times for FL1 and FL2 were saved in the same parameter ...
61.1	409	* THIS is now different. There are new parameters saving only the arrival times for pulses that go to FL1 and to FL2 (in detail: first time slot of the accelerator and second)
57.1	410	* There has been also a renaming (and relocation) of the BAMs.
	411	** acc: 4DBC3 → FL0.DBC2
	412	** FL1: 1SFELC → FL1.SFELC
79.1	413	** FL2: FL2XTDS → (% style="color:#172b4d" %)FL2.SEED5
57.1	414	* for more Info: [[LINK to detailed infos from MSK>>url:https://confluence.desy.de/display/SDiagPublic/BAM+Data+Structure\|\|shape="rect"]]
	415	* [[Link a collection of papers related to the BAM and the analysis of pump-probe experiments>>doc:FLASHUSER.Additional helpful things.FLASH beamlines and instruments references.WebHome]]
	416	* a recent [[talk about the working principle of the BAM>>attach:BAM-basics and outlook-2018_DESY-template_16-9Format.pdf]]
	417	{{/info}}
	418
	419	{{expand title="Discontinued BAM format (used until end 2021)"}}
79.1	420	(% style="color:#000000" %)Discontinued BAM data recording
57.1	421
79.1	422	{{code language="none"}}/FL1/Electron Diagnostic/BAM/4DBC3/electron bunch arrival time (low charge){{/code}}
	423	//always saved (PBD)//
	424	DOOCS prop : {{code language="none"}}FLASH.SDIAG/BAM/4DBC3/LOW_CHARGE_ARRIVAL_TIME{{/code}}
	425	DAQ channel: {{code language="none"}}FLASH.SDIAG/BAM.DAQ/4DBC3.LOW_CHARGE_ARRIVAL_TIME{{/code}}
	426	desc: Electron bunch arrival time measured with the BAM inside the accelerator - however shows a very good correlation to the arrivaltime of the XUV pulses in the experiment (pulse resolved data).
33.1	427	units: ps (bigger numbers indicate later arrivaltime of the electrons)
1.1	428
58.1	429
79.1	430	{{code language="none"}}/FL1/Electron Diagnostic/BAM/1SFELC/electron bunch arrival time (low charge){{/code}}
	431	//always saved (PBD)//
	432	DOOCS prop : {{code language="none"}}FLASH.SDIAG/BAM/1SFELC/LOW_CHARGE_ARRIVAL_TIME{{/code}}
	433	DAQ channel: {{code language="none"}}FLASH.SDIAG/BAM.DAQ/1SFELC.LOW_CHARGE_ARRIVAL_TIME{{/code}}
	434	desc: Electron bunch arrival time measured with the BAM before the undulator (pulse resolved data). This one was newly installed in 2020.
58.1	435	units: ps (bigger numbers indicate later arrival time of the electrons)
57.1	436	{{/expand}}
33.1	437
68.1	438	====== BAM FL0.DBC2{{code language="none"}}{{/code}} ======
	439
79.1	440	(% style="color:#ff6600" %)DBC2/electron bunch arrival time (HDF5 name not yet implemented - see zraw)(%%)
68.1	441	//always saved (PBD)//
74.1	442	{{code language="none"}}/FL1/Electron Diagnostic/BAM/ {{/code}}DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.ABSOLUTE.SA1.COMP
79.1	443	DAQ (% style="color:#000000" %)channel: FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.ABSOLUTE.SA1.COMP (%%)
74.1	444	desc: Electron bunch arrival time measured with the BAM inside the accelerator (after bunch compressor 2). The property contains only the arrival time of the bunches sent to FL1 (e.g. if there are 30 bunches in FL1 the first 30 values are the arrival time the remaining numbers still may have arbitrary numbers looking like a signal which they are not ). These are the same values as the "raw" data below - just "cleaned". The values show a very good correlation to the arrival time of the XUV pulses in the experiment (see help).
68.1	445
74.1	446	units: fs (bigger numbers (typically) indicate later arrival times of the electrons).
68.1	447
	448
79.1	449	(% style="color:#ff6600" %)DBC2/electron bunch arrival time (raw) (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL1/Electron Diagnostic/BAM/{{/code}}(%%)
	450	//always saved (PBD)//
67.1	451	DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.ABSOLUTE
79.1	452	DAQ channel: (% style="color:#000000" %)FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.ABSOLUTE (%%)
68.1	453	desc: Electron bunch arrival time measured with the BAM inside the accelerator (after bunch compressor 2). Here the complete bunch train from the FEL is recorded (FLASH1 and FLASH2 pulses). Thus there are values from FLASH 1 in the first part. they may be separated by several "0" values if the reprate is different from 1 MHz ... - It shows a very good correlation to the arrival time of the XUV pulses in the experiment (see help).
58.1	454	units: fs (bigger numbers (typically) indicate later arrival times of the electrons).
	455
57.1	456
79.1	457	(% style="color:#ff6600" %)DBC2/error (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL1/Electron Diagnostic/BAM/{{/code}}(%%)
	458	//always saved (PBD)//
	459	DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIM(% style="color:#000000" %)E.bamError(%%)
	460	DAQ channel: (% style="color:#000000" %)FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.BAMERROR(%%)
58.1	461	desc: If the value is 0 , the BAM is working well. If it is non-zero there is a problem !!
57.1	462
58.1	463
79.1	464	(% style="color:#ff6600" %)DBC2/status (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL1/Electron Diagnostic/BAM/{{/code}}(%%)
	465	//always saved (PBD)//
	466	DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIM(% style="color:#000000" %)E..bamStatus.//1//(%%)
	467	DAQ channel(% style="color:#000000" %): FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.BAMSTATUS.1(%%)
	468	desc: (% style="letter-spacing:0.0px" %) status bit: 0 - data is valid; 1 - beam present; 2 - calibration ongoing; 3 - feedback enabled; 4 - feedback acting; mostly check for bit 0 == 1 is sufficient
57.1	469
	470
68.1	471	====== BAM FL1.SFELC{{code language="none"}}{{/code}} ======
	472
79.1	473	(% style="font-family:SFMono-Medium,~"SF Mono~",~"Segoe UI Mono~",~"Roboto Mono~",~"Ubuntu Mono~",Menlo,Courier,monospace; letter-spacing:0.0px" %)/FL1/Electron Diagnostic/BAM/SFELC(% style="color:#ff6600" %)/electron bunch arrival time (HDF5 name not yet implemented - see zraw)
68.1	474
	475	//always saved (PBD)//
79.1	476	(% style="color:#172b4d" %)FL1.SFELC(%%)
	477	(% style="color:#000000" %)channel: FLASH.SDIAG/BAM/(% style="color:#172b4d" %)FL1.SFELC(% style="color:#000000" %)/ARRIVAL_TIME.ABSOLUTE.SA1.COMP
	478	{{code language="none"}} DOOCS prop : FLASH.SDIAG/BAM//ARRIVAL_TIME.ABSOLUTE.SA1.COMPDAQ {{/code}}(% style="letter-spacing:0.0px" %)desc: Electron bunch arrival time measured with the BAM before the undulator (pulse resolved data). This one was newly installed in 2020.. The property contains only the arrival time of the bunches sent to FL1 (e.g. if there are 30 bunches in FL1 the first 30 values are the arrival time the remaining numbers still may have arbitrary numbers looking like a signal which they are not). These are the same values as the "raw" data below - just "cleaned". The values show a very good correlation to the arrival time of the XUV pulses in the experiment (see help).
68.1	479	units: fs (bigger numbers (typically) indicate later arrival times of the electrons).
	480
	481
	482
79.1	483	(% style="color:#172b4d" %)SFELC(% style="color:#ff6600" %)/electron bunch arrival time (raw) (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL1/Electron Diagnostic/BAM/{{/code}}(%%)
	484	//always saved (PBD)//
	485	DOOCS prop : FLASH.SDIAG/BAM/(% style="color:#172b4d" %)FL1.SFELC(%%)/ARRIVAL_TIME.ABSOLUTE
	486	DAQ channel: (% style="color:#000000" %)FLASH.SDIAG/BAM/FL1.SFELC/ARRIVAL_TIME.ABSOLUTE (%%)
68.1	487	desc: Electron bunch arrival time measured with the BAM before the undulator (pulse resolved data). This one was newly installed in 2020. Here the complete bunch train from the FEL is recorded (FLASH1 and FLASH2 pulses). Thus there are values from FLASH 1 in the first part. they may be separated by several "0" values if the reprate is different from 1 MHz ... - It shows a very good correlation to the arrival time of the XUV pulses in the experiment (see help).
58.1	488	units: fs (bigger numbers (typically) indicate later arrival times of the electrons).
	489
	490
79.1	491	(% style="color:#172b4d" %)SFELC(% style="color:#ff6600" %)/error (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL1/Electron Diagnostic/BAM/{{/code}}(%%)
	492	//always saved (PBD)//
	493	DOOCS prop : FLASH.SDIAG/BAM/(% style="color:#172b4d" %)FL1.SFELC(%%)/ARRIVAL_TIM(% style="color:#000000" %)E.bamError(%%)
	494	DAQ channel(% style="color:#000000" %): FLASH.SDIAG/BAM/FL1.SFELC/ARRIVAL_TIME.BAMERROR(%%)
58.1	495	desc: If the value is 0 , the BAM is working well. If it is non-zero there is a problem !!
	496
	497
79.1	498	(% style="color:#172b4d" %)SFELC(% style="color:#ff6600" %)/status (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL1/Electron Diagnostic/BAM/{{/code}}(%%)
	499	//always saved (PBD)//
	500	DOOCS prop : FLASH.SDIAG/BAM/(% style="color:#172b4d" %)FL1.SFELC(%%)/ARRIVAL_TIM(% style="color:#000000" %)E..bamStatus.//1//(%%)
	501	DAQ chann(% style="color:#000000" %)el: FLASH.SDIAG/BAM/FL1.SFELC/ARRIVAL_TIME.BAMSTATUS.1(%%)
59.1	502	desc: status bit: 0 - data is valid; 1 - beam present; 2 - calibration ongoing; 3 - feedback enabled; 4 - feedback acting; mostly check for bit 0 == 1 is sufficient
58.1	503
	504
33.1	505
1.1	506	===== electron beam profile =====
	507
79.1	508	{{code language="none"}}/FL1/Electron Diagnostic/Electron bunch profile/TDS profile{{/code}}
	509	//always saved (PBD) - IF LOLA is ON and ACTIVATED in the PBD DAQ (talk to expert)//
	510	DOOCS prop : {{code language="none"}}TTF2.DAQ/BEAM.PROF.ML/BEAM.PROF/OUT.PROF.CCCED{{/code}}
	511	DAQ channel: {{code language="none"}}PBD.BEAM.PROF.ML/DAQ.OUT.PROF.CCCED{{/code}}
	512	desc: temporal profile of electron bunch, y axis in Ampers (FLASH1)
1.1	513	units: pixel
79.1	514
1.1	515
79.1	516	{{code language="none"}}/FL1/Electron Diagnostic/Electron bunch profile/Expert stuff/TDS calibration constant{{/code}}
	517	//always saved (PBD) - IF LOLA is ON and ACTIVATED in the PBD DAQ (talk to expert)//
	518	DOOCS prop : {{code language="none"}}TTF2.DAQ/BEAM.PROF.ML/BEAM.PROF/CALIB.CONST.T{{/code}}
	519	DAQ channel: = PBD.BEAM.PROF.ML/CCT=
	520	desc: TDS calibration constant for the x-axis of the profiles: fs per pixel
1.1	521	units: fs per pixel
79.1	522
1.1	523
79.1	524	{{code language="none"}}/FL1/Electron Diagnostic/Electron bunch profile/TDS profile width rms{{/code}}
	525	//always saved (PBD) - IF LOLA is ON and ACTIVATED in the PBD DAQ (talk to expert)//
	526	DOOCS prop : {{code language="none"}}TTF2.DAQ/BEAM.PROF.ML/BEAM.PROF/SOWS.W.CCTED{{/code}}
	527	DAQ channel: {{code language="none"}}PBD.BEAM.PROF.ML/PROFWIDTHCCTED{{/code}}
	528	desc: rms pulse width of the measures TDS electron bunch profile
1.1	529	units: fs
	530
	531	===== electron bunch energy =====
	532
79.1	533	{{code language="none"}}/FL1/Electron Diagnostic/Electron energy/average electron energy{{/code}}
	534	//always saved (PBD)//
	535	DOOCS prop : {{code language="none"}}TTF2.DAQ/ENERGY.DOGLEG/E_INTRA_MEAN/VAL{{/code}}
	536	DAQ channel: {{code language="none"}}PBD.ENERGY.DOGLEG/E_MEAN{{/code}}
	537	desc: electron bunch energy (average over the bunch train)
2.1	538	units: (% class="twikiNewLink" %)MeV(%%)
79.1	539
1.1	540
79.1	541	{{code language="none"}}/FL1/Electron Diagnostic/Electron energy/pulse resolved energy{{/code}}
	542	//always saved (PBD)//
	543	DOOCS prop : {{code language="none"}}TTF2.DAQ/ENERGY.DOGLEG/E_SPECT/VAL.TD{{/code}}
	544	DAQ channel: {{code language="none"}}PBD.ENERGY.DOGLEG/E_SPECT{{/code}}
	545	desc: electron bunch energy bunch resolved
5.1	546	units: (% class="twikiNewLink" %)MeV
1.1	547
	548
79.1	549	{{code language="none"}}/FL1/Electron Diagnostic/Electron energy/wavelength bunch train average{{/code}}
	550	//always saved (PBD)//
	551	DOOCS prop : {{code language="none"}}TTF2.DAQ/ENERGY.DOGLEG/LAMBDA_MEAN/VAL{{/code}}
	552	DAQ channel: {{code language="none"}}PBD.ENERGY.DOGLEG/LAMBDA_MEAN{{/code}}
	553	desc: Wavelength calculated by the electron bunch energy (average over the bunch train) (FLASH1)
1.1	554	units: nm
79.1	555
1.1	556
4.1	557	[[Contents>>doc:\|\|anchor="Contents"]]
1.1	558
	559
5.1	560	==== Timing information, rep rate etc. (FLASH1) ====
1.1	561
	562	===== bunch repetition rate =====
	563
79.1	564	{{code language="none"}}/FL1/Timing/repetition rate{{/code}}
	565	//always saved (PBD)//
	566	DOOCS prop : {{code language="none"}}FLASH.DIAG/TIMER/FLASHCPUTIME1.0/REP_RATE_KHZ.1{{/code}}
	567	DAQ channel: {{code language="none"}}TTF2.UTIL/LASER.CONTROL/GUN/PULSE_FREQ{{/code}}
1.1	568	desc: repetition rate of the bunches / pulses within the burst (FLASH1)
	569	units: kHz
79.1	570
1.1	571
	572	===== set number of pulses =====
	573
79.1	574	(% style="color:#ff6600" %)(HDF5 name not yet implemented - see zraw)(% style="color:#ff0000" %){{code language="none"}}/FL1/Timing/set number of bunches {{/code}}(%%)
	575	//always saved (PBD)//
74.1	576	DOOCS prop : {{code language="none"}}FLASH.DIAG/TIMINGINFO/TIME1.BUNCH_FIRST_INDEX.1 [4th number]{{/code}}
	577	DAQ channel: {{code language="none"}}FLASH.DIAG/TIMINGINFO/TIME1.BUNCH_FIRST_INDEX.1 [4th number]{{/code}}
	578	desc: Number of bunches set in the control (timing) system. The property contains 4 numbers. the last one is the number of pulses (see also [[doc:FLASH.Timing properties]] (internal link)). If pulses are used for diagnostic of the protection system of the accelerator limits the number of bunches to be accelerated and thus the actual number of pulses may be smaller than the set one
1.1	579	units:
	580
	581	===== actual number of pulses =====
	582
79.1	583	{{code language="none"}}/FL1/Timing/actual number of bunches{{/code}}
	584	//always saved (PBD)//
	585	DOOCS prop : {{code language="none"}}FLASH.DIAG/TOROID.ML/12EXP/NUMBEROFBUNCHES.FLASH1{{/code}}
	586	DAQ channel: {{code language="none"}}TTF2.DIAG/PBD.TOROID.ML/12EXP{{/code}}
	587	desc: Number of bunches measured BEHIND the undulator. If pulses are used for diagnostic of the protection system of the accelerator limits the number of bunches to be accelerated this is the actual number that created XUV radiation.The number is calculated by the DAQ middle layer server, (FLASH1)
1.1	588	units:
79.1	589
1.1	590
	591	===== actual pulse pattern recorded after the undulator =====
	592
79.1	593	{{code language="none"}}/FL1/Timing/Bunch pattern/pattern after undulator{{/code}}
	594	//always saved (PBD)//
	595	DOOCS prop : {{code language="none"}}TTF2.DIAG/PBD.TOROID.ML/12EXP/CHARGE.TD{{/code}}
	596	DAQ channel: {{code language="none"}}TTF2.DIAG/PBD.TOROID.ML/12EXP{{/code}}
	597	desc: The bunch pattern as function of time in a burst recorded by toroid diagnostic BEHIND the undulator. (FLASH1)
1.1	598	units:
79.1	599
1.1	600
	601	===== Train ID =====
	602
79.1	603	{{code language="none"}}/Timing/train ID{{/code}}
	604	//always saved (PBD)//
	605	DOOCS prop : {{code language="none"}}none{{/code}}
	606	DAQ channel: {{code language="none"}}none{{/code}}
	607	desc: Each 10 Hz burst has its unique train ID. For the HDF5 data set the ID is the same for all parameters with the same index (note camera images may be shifted by 1 ID - talk to the experts !)
1.1	608	units:
79.1	609
1.1	610
	611	===== Train time =====
	612
79.1	613	{{code language="none"}}/Timing/train time{{/code}}
	614	desc:Local time as array of day, hour, minute, second, and centisecond. This data set is meant for visualization purposes only. For correlations use the train ID or the Unix time of the time stamp
1.1	615	units: d h min s cs
79.1	616
1.1	617
79.1	618	{{code language="none"}}/Timing/time stamp{{/code}}
	619	desc:first column: Local time in unix time. To get day, hour, minute, second you can use unix: e.g. date ~-~-date='@1553617729' or matlab, python etc
	620	second column: microseconds
1.1	621	third column: Train ID of FLASH
79.1	622
1.1	623
4.1	624	[[Contents>>doc:\|\|anchor="Contents"]]
1.1	625
	626
	627	==== Pump Probe Laser (FLASH1) ====
	628
63.1	629	PIGLET (PG laser)
62.1	630
63.1	631	{{code language="none"}}/FL1/Experiment/Pump probe laser{{/code}}
	632
82.1	633	{{info width="100"}}
80.1	634	list of saved parameters status May 2024 (up to now the parameters can be found in /zraw/ ... )
63.1	635
81.1	636
82.1	637	Download the PDF:
	638
	639	[[~[~[image:Screenshot 2024-05-17 094435.png~\|~\|height="429" width="336"~]~]>>attach:FSLADAQ-DAQParameterlistPiGLET.pdf]]
81.1	640
80.1	641	{{/info}}
69.1	642
62.1	643	{{expand title="Parameters used until 2021"}}
79.1	644	{{code language="none"}}
	645	/FL1/Experiment/Pump probe laser/laser attenuation
	646	{{/code}}
5.1	647
79.1	648	//always saved (PBD)//
	649	DOOCS prop : {{code language="none"}}TTF2.FEL/PPDELAYCAL/PPDELAYCAL/ROT2.CURRENT{{/code}}
	650	DAQ channel: {{code language="none"}}TTF2.FEL/PPDELAYCAL/PPDELAYCAL/ROT2.CURRENT{{/code}}
	651	desc: attenuation of the PPLaser (rotation of a waveplate)
1.1	652	units : 0 no transmission , 1: full transmission
	653
5.1	654
79.1	655	{{code language="none"}}/FL1/Experiment/Pump probe laser/laser delay{{/code}}
	656	//always saved (PBD)//
	657	DOOCS prop : {{code language="none"}}TTF2.FEL/PPDELAYCAL/PPDELAYCAL/DLY1.CURRENT{{/code}}
	658	DAQ channel: {{code language="none"}}TTF2.FEL/PPDELAYCAL/PPDELAYCAL/DLY1.CURRENT{{/code}}
	659	desc: delay of the Pump probe laser - measured by the read back position of the motor. only read out every secound ... better use the encoder
1.1	660	units : ps ( pos delay means IR comes later)
	661
5.1	662
79.1	663	{{code language="none"}}/FL1/Experiment/Pump probe laser/delay line IK220.0/ENC.DELAY{{/code}}
	664	//always saved (PBD)//
	665	DOOCS prop : {{code language="none"}}TTF2.FEL/DELLINE.ENC/IK220.0/ENC.DELAY{{/code}}
	666	DAQ channel: {{code language="none"}}TTF2.FEL/DELLINE.ENC/IK220.0:ENC.DELAY{{/code}}
	667	subsystem: {{code language="none"}}DELLINE.ENC{{/code}} desc : delay of the Pump probe laser - measured by an encoder. The position is read out with 10Hz train synchronized and should be used to determine the actual laser delay (the motor position is only read out about every second
1.1	668	units : ps ( pos delay means IR comes later)
	669
5.1	670
79.1	671	{{code language="none"}}/FL1/Experiment/Pump probe laser/Synchronization/timing jitter RMS GECCO{{/code}}
	672	//always saved (PBD)//
	673	DOOCS prop : {{code language="none"}}FLASH.SYNC/F1PPL.LASER_LOCK/28C.F1PPL1.CONTROLLER/ADV_CTRL_MANAGER.0.PID_INPUT_JITTER.2.RD{{/code}}
	674	DAQ channel: {{code language="none"}}FLASH.SYNC/F1PPL.LASER_LOCK/28C.F1PPL1.CONTROLLER/ADV_CTRL_MANAGER.0.PID_INPUT_JITTER.2.RD{{/code}}
2.1	675	desc: rms jitter of the GECCO (% class="twikiNewLink" %)TiSa(%%) Oscillator units: fs
1.1	676
	677
79.1	678	{{code language="none"}}/FL1/Experiment/Pump probe laser/streak camera delay time{{/code}}
	679	//always saved (PBD)//
	680	DOOCS prop : {{code language="none"}}TTF2.FEL/TDOLFEL/TDOLFEL/STREAK.CAM.TIME{{/code}}
	681	DOOCS prop : {{code language="none"}}TTF2.FEL/TDOLFEL/TDOLFEL/STREAK.CAM.TIME{{/code}}
52.1	682	desc: delay time between the optical laser and the FEL units: ps
62.1	683	{{/expand}}
1.1	684
	685
4.1	686	[[Contents>>doc:\|\|anchor="Contents"]]
1.1	687
	688
	689	==== User Data (FLASH1) ====
	690
52.1	691	The data saved specifically for detectors at an experiment will show up in /Experiment/ there is a large number of options for cameras or monitoring of slow properties (motor positions etc) for user experiments. For details please ask your local contact.
18.1	692
	693	NOTE: If parameters for an experiment are included on short notice the correct naming in the HDF5 may not be in time and the data will show up in /uncategorized/ with the DOOCS names
	694
	695	The most common and permanently installed device used by experiment are our ADCs:
	696
1.1	697	===== GHz ADCs =====
	698
79.1	699	ADC traces of the (SPDevices 412) GHZ ADCs available for the users . More information about the ADCs can be found [[here>>doc:FLASHUSER.Data Acquisition and controls.Controls (DOOCS, jDDD,\.\.\.).MTCA ADCs.WebHome]]
	700	//saved on DEMAND in the user DAQ//
1.1	701	\\The HDF5 names for the ADC traces are depending on the beamline :
79.1	702	\\PG Beamline:
	703	{{code language="none"}}/FL1/Experiment/PG/ADQ412 GHz ADC/CH00/TD{{/code}}
	704	{{code language="none"}}/FL1/Experiment/PG/ADQ412 GHz ADC/CH01/TD{{/code}}
	705	{{code language="none"}}/FL1/Experiment/PG/ADQ412 GHz ADC/CH02/TD{{/code}}
1.1	706	{{code language="none"}}/FL1/Experiment/PG/ADQ412 GHz ADC/CH03/TD{{/code}}
	707
79.1	708	BL Beamlines:
	709	{{code language="none"}}/FL1/Experiment/BL1/ADQ412 GHz ADC/CH00/TD{{/code}}
	710	{{code language="none"}}/FL1/Experiment/BL1/ADQ412 GHz ADC/CH01/TD{{/code}}
	711	{{code language="none"}}/FL1/Experiment/BL1/ADQ412 GHz ADC/CH02/TD{{/code}}
	712	{{code language="none"}}/FL1/Experiment/BL1/ADQ412 GHz ADC/CH03/TD{{/code}}
	713	\\{{code language="none"}}/FL1/Experiment/BL2/ADQ412 GHz ADC/CH00/TD{{/code}}
	714	{{code language="none"}}/FL1/Experiment/BL2/ADQ412 GHz ADC/CH01/TD{{/code}}
	715	\\{{code language="none"}}/FL1/Experiment/BL3/ADQ412 GHz ADC/CH02/TD{{/code}}
1.1	716	{{code language="none"}}/FL1/Experiment/BL3/ADQ412 GHz ADC/CH03/TD{{/code}}
	717
79.1	718	DOOCS prop : {{code language="none"}}FLASH.FEL/ADC.ADQ.PG/EXP1.CH00/CH00.TD or CH00.DAQ.TD{{/code}}
52.1	719	here the {{code language="none"}}CH00.TD{{/code}} is the full ADC trace as it is sampled ( typically several 100.000 samples per pulse train) while the {{code language="none"}}CH00.DAQ.TD{{/code}} trace only has the number of samples which are sent to the DAQ OR if //grouping// is activated the {{code language="none"}}CH00.DAQ.TD{{/code}} contains only the grouped spectra. To read the ADC trace with an online analysis program the {{code language="none"}}CH00.DAQ.TD{{/code}} is used preferably.
1.1	720	DAQ channel: {{code language="none"}}FLASH.FEL/ADC.ADQ.PG/EXP1.CH00{{/code}}
	721
18.1	722	In addition there are also additional parameters saved like:
1.1	723
16.1	724	* {{code language="none"}}sample frequency{{/code}}: it shows the sample frequency in MHz (number of samples per µs). NOTE: the clock of the ADC is NOT synchronized to the FLASH timing system. Thus the number of samples between bunches in the bunch train may be not integer numbers which will be show up for long bunch trains.
52.1	725	* {{code language="none"}}number of samples{{/code}}: total number of samples recorded for each 10 Hz trigger
79.1	726	* {{code language="none"}}error (ADC):{{/code}}0 indicates that there was no error
1.1	727
	728	===== MHz ADCs =====
	729
79.1	730	similar to the GHz ADCs the MHz ADCs are saved with HDF5 names like:
	731	{{code language="none"}}/FL1/Experiment/BL1/SIS8300 100MHz ADC/CH2/TD{{/code}}
	732	DOOCS prop : FLASH.FEL/ADC.SIS.BL1/EXP1.CH02/CH00.TD
1.1	733	DAQ channel: : FLASH.FEL/ADC.SIS.BL1/EXP1.CH02
	734
18.1	735	In addition there are also additional parameters saved like:
1.1	736
18.1	737	* {{code language="none"}}sample frequency{{/code}}: it shows the sample frequency in MHz (number of samples per µs). NOTE: the clock of the ADC is NOT synchronized to the FLASH timing system. Thus the number of samples between bunches in the bunch train may be not integer numbers which will be show up for long bunch trains.
52.1	738	* {{code language="none"}}number of samples{{/code}}: total number of samples recorded for each 10 Hz trigger
18.1	739
4.1	740	[[Contents>>doc:\|\|anchor="Contents"]]
1.1	741
18.1	742
	743
	744
1.1	745	=== FLASH2 ===
	746
7.1	747	There is analog to FLASH1 a permanently running "PhotonDagnostic DAQ FLASH2" (PBD2) and 2 User DAQs
1.1	748
7.1	749	==== Beamline info (FLASH2) ====
6.1	750
79.1	751	{{code language="none"}}/FL2/Beamlines/Attenuator/pressure {{/code}}
	752	(% style="color:#000000" %)//always saved (PBD2)// (%%)
	753	(% style="color:#000000" %)DOOCS prop : {{code language="none"}}FLASH.FEL/ATT.GAS_DOSING/FL2.HALL/PRESSURE{{/code}} (%%)
	754	(% style="color:#000000" %)DAQ channel: {{code language="none"}}FLASH.FEL/ATT.GAS_DOSING/FL2.HALL/PRESSURE{{/code}} (%%)
	755	(% style="color:#000000" %)desc: set pressure in the gas attenuator (%%)
	756	(% style="color:#000000" %)units: mbar(%%)
	757
5.1	758
79.1	759	{{code language="none"}}/FL2/Beamlines/FL20/Shutter/open{{/code}}
	760	//always saved (PBD2)//
	761	DOOCS prop : {{code language="none"}}FLASH.FEL/ADC.SIS.FL2FS/FL20.SHUTTER/CH00.TD{{/code}}
	762	DAQ channel: {{code language="none"}}FLASH.FEL/ADC.SIS.FL2FS/FL20.SHUTTER{{/code}}
	763	desc: BL Beamline Fast shutter state: 1 is open, 0 is closed ( for technical reasons there are 100 vales of this state saved ...)
6.1	764	units: none
5.1	765
	766
79.1	767	{{code language="none"}}/FL2/Beamlines/Filter wheel/position wheel 1{{/code}}
	768	//always saved (PBD2)//
	769	DOOCS prop : {{code language="none"}}FLASH.FEL/FL20H.PH.MOTOR/MOTOR1.MOT3/FPOS{{/code}}
	770	DAQ channel: FLASH.FEL/FL20H.PH.MOTOR/MOTOR1.MOT3/FPOS
24.1	771	desc: Position of the BL filter wheel 1 - to correlate with the filter material please look [[here>>doc:FLASHUSER.jddd-linked help pages.Filter-Units.Filter wheels in FLASH1 and FLASH2.WebHome]]
6.1	772	units: degree
79.1	773
6.1	774
79.1	775	/FL2/Beamlines/Filter wheel/position wheel 2
	776	always saved (PBD2)
	777	DOOCS prop : {{code language="none"}}FLASH.FEL/FL20H.PH.MOTOR/MOTOR2.MOT3/FPOS{{/code}}
	778	DAQ channel: {{code language="none"}}FLASH.FEL/FL20H.PH.MOTOR/MOTOR2.MOT3/FPOS{{/code}}
40.1	779	desc: Position of the BL filter wheel 2 - to correlate with the filter material please look [[here>>doc:FLASHUSER.jddd-linked help pages.Filter-Units.Filter wheels in FLASH1 and FLASH2.WebHome]]
	780	units: degree
6.1	781
8.1	782
	783	NOTE: Aperture positions in the beamline as well as the positions of the beam steering mirrors are also saved. for more Info contact your local contact
	784
6.1	785	[[Contents>>doc:\|\|anchor="Contents"]]
	786
	787
	788
10.1	789	==== Photon Diagnostics SASE ([[XGMD>>url:http://photon-science.desy.de/facilities/flash/photon_diagnostics/gmd_intensity_and_position/index_eng.html\|\|shape="rect"]] - FLASH2) ====
8.1	790
79.1	791	{{code language="none"}}/FL2/Photon Diagnostic/GMD/Average energy/energy tunnel{{/code}}
	792	//always saved (PBD2)//
	793	DOOCS prop : {{code language="none"}}FLASH.FEL/XGM.PHOTONFLUX/FL2.TUNNEL/PHOTONFLUX.UJ{{/code}}
	794	DAQ channel:{{code language="none"}} FLASH.FEL/XGM.PHOTONFLUX/FL2.TUNNEL/PHOTONFLUX.UJ{{/code}}
	795	desc : calibrated average ( ~~ 20 sec averaging time ) SASE Energy/pulse measured in the TUNNEL before the attenuator (ion current)
8.1	796	units : microJ
	797
	798
79.1	799	{{code language="none"}}/FL2/Photon Diagnostic/GMD/Pulse resolved energy/energy tunnel{{/code}}
	800	//always saved (PBD2)//
	801	DOOCS prop : {{code language="none"}}FLASH.FEL/XGM.INTENSITY/FL2.TUNNEL/INTENSITY.TD{{/code}}
	802	DAQ channel: {{code language="none"}}FLASH.FEL/XGM.INTENSITY/FL2.TUNNEL/INTENSITY.TD{{/code}}
38.1	803	desc : Energy per pulse measured in the Tunnel (in front of the gas attenuator and the apertures in the Hall) In addition measurement errors and beam position are included for EACH pulse in the pulse train !! (see below)
23.1	804	units : a.u. (more or less µJ but need to be calibrated with the "Average energy" for good precision) [[see here for help>>doc:FLASHUSER.jddd-linked help pages.Calibrating the pulse resolved (electron) data from GMD.WebHome]]
8.1	805
39.1	806	{{info title="GMD pulse resolved data structure"}}
79.1	807	For every pulse in the pulse train the information is saved:
38.1	808
8.1	809
38.1	810	1. Intensity per pulse (a.u. (more or less µJ ))
	811	1. Intensity per pulse (auxillary GMD) - not used
39.1	812	1. Position horizontal (mm, for a single pulse the position information may be very noisy - talk to your local contact)
	813	1. Position vertical (mm, for a single pulse the position information may be very noisy - talk to your local contact)
79.1	814	1. Intensity per pulse sigma (a.u. (more or less µJ ), (% style="color:#000000" %)This parameter gives an indication of the error of the measurement of the pulse energy. This takes signal to noise, detector resolution, uncertainties in crossection etc into account. (it is NOT the measurement of the statistical fluctuation of the SASE pulses)(%%))
38.1	815	1. Position horizontal sigma (mm, indicates the error (RMS, sigma) of the measurement according to known uncertainties and signal to noise)
	816	1. Position vertical sigma (mm, indicates the error (RMS, sigma) of the measurement according to known uncertainties and signal to noise)
	817	1. Combined warning and error flags
8.1	818
38.1	819	The pulse energy and the error are plotted for the first bunch of the pulse trains saved in this
	820	file
8.1	821
38.1	822
	823	[[image:attach:image2021-2-9_10-51-6.png\|\|height="250"]]
8.1	824
79.1	825
39.1	826	{{/info}}
38.1	827
8.1	828
79.1	829	All values for the GMD are also available for the HALL GMD which is located in the experimental hall down stream the gas attenuator. If the attenuator is on the ratio between Hall and Tunnel signal shows the attenuation. BUT NOTE that the filter unit and the Aperture 4 are downstream the GMD. So if filters and aperture are used this influence is NOT measured by the GMD hall !
8.1	830
	831
9.1	832	Besides pulse energy the GMD also provides information about the beam position
8.1	833
9.1	834
79.1	835	{{code language="none"}}/FL2/Photon Diagnostic/GMD/Average Beam position/position tunnel horizontal{{/code}}
	836	//always saved (PBD2)//
	837	DOOCS prop : {{code language="none"}}FLASH.FEL/XGM.POSMON/FL2.TUNNEL/IX.POS{{/code}}
	838	DAQ channel: {{code language="none"}}FLASH.FEL/XGM.POSMON/FL2.TUNNEL/IX.POS{{/code}}
	839	desc : the Average ( ~~ 20 sec averaging time ) Beam position of the photon Beam determined by the GMD (tunnel, x=horizontal)
8.1	840	units : mm
	841
9.1	842
79.1	843	{{code language="none"}}/FL2/Photon Diagnostic/GMD/Average Beam position/position tunnel vertical{{/code}}
	844	//always saved (PBD2)//
	845	DOOCS prop : {{code language="none"}}FLASH.FEL/XGM.POSMON/FL2.TUNNEL/IY.POS{{/code}}
	846	DAQ channel: {{code language="none"}}FLASH.FEL/XGM.POSMON/FL2.TUNNEL/IY.POS{{/code}}
	847	desc : the Average ( ~~ 20 sec averaging time ) Beam position of the photon Beam determined by the GMD (tunnel, x=horizontal)
8.1	848	units : mm
	849
	850
79.1	851	/FL2/Photon Diagnostic/GMD/Pulse resolved beam position/position tunnel x
40.1	852	always saved (PBD2)
	853	DOOCS prop : FLASH.FEL/XGM.BPM/FL2.HALL/X.TD
79.1	854	DAQ channel: FLASH.FEL/XGM.BPM/FL2.HALL:2
40.1	855	desc: Besides the well calibrated averaged beam position information there is also the option to measure the beam position on a single bunch level. HOWEVER this methide needs a perfectly adjusted signal level (talk to your local contact !!) and also then the signal to noise is rather small and one needs some averaging ... BUT with this option one can determine if there was a spatial slope on a burst (say forst bunches were lower than the last ones or so ...)
	856	units : mm
8.1	857
40.1	858	(x=horizontal, y = vertial)
9.1	859
	860	again the same parameter set is available for the HALL GMD
	861
8.1	862
9.1	863
15.1	864	==== Photon Diagnostics OPIS[[ >>url:http://photon-science.desy.de/facilities/flash/photon_diagnostics/opis_spectrometer/index_eng.html\|\|shape="rect"]](FLASH2) ====
10.1	865
19.1	866	for more info see: [[ OPIS>>url:http://photon-science.desy.de/facilities/flash/photon_diagnostics/opis_spectrometer/index_eng.html\|\|shape="rect"]]
10.1	867
	868	(The OPIS hall is not installed yet ...)
	869
9.1	870
10.1	871	{{code language="none"}}/FL2/Photon Diagnostic/Wavelength/OPIS tunnel/Processed/mean photon energy{{/code}}
79.1	872	// saved opon request (PBD2)//
	873	DOOCS prop : {{code language="none"}}FLASH.UTIL/STORE/FL2.TUNNEL.OPIS/VAL042{{/code}}
	874	DAQ channel:{{code language="none"}} FLASH.UTIL/STORE/FL2.TUNNEL.OPIS/VAL042{{/code}}
10.1	875	desc : mean photon energy ( ~~ 1 sec averaging time ) measured in the TUNNEL for a specific bunch out of the bunch train (via photoelectron spectroscopy)
	876	units : eV
	877
9.1	878
10.1	879	{{code language="none"}}/FL2/Photon Diagnostic/Wavelength/OPIS tunnel/Processed/mean wavelength{{/code}}
79.1	880	// saved opon request (PBD2)//
	881	DOOCS prop : {{code language="none"}}FLASH.UTIL/STORE/FL2.TUNNEL.OPIS/VAL040{{/code}}
10.1	882	DAQ channel:{{code language="none"}} FLASH.UTIL/STORE/FL2.TUNNEL.OPIS/VAL040{{/code}}
52.1	883	desc : mean wavelength ( ~~ 1 sec averaging time ) measured in the TUNNEL for a specific bunch out of the bunch train (via photoelectron spectroscopy)
10.1	884	units : nm
	885
9.1	886
10.1	887	{{code language="none"}}/FL2/Photon Diagnostic/Wavelength/OPIS tunnel/Processed/number of analyzed bunch (in older version this can be found in OPIS tunnel/Expert stuff/General operation parameters/){{/code}}
79.1	888	// saved opon request (PBD2)//
	889	DOOCS prop : {{code language="none"}}FLASH.UTIL/STORE/FL2.TUNNEL.OPIS/VAL060{{/code}}
10.1	890	DAQ channel:{{code language="none"}} FLASH.UTIL/STORE/FL2.TUNNEL.OPIS/VAL060{{/code}}
11.1	891	desc : The bunch number of the bunch used for the wavelength calculation
	892	units :
10.1	893
9.1	894
52.1	895	If Opis is running typically on the the averaged data is saved. For several experiments it may make sense to save the information for each single bunch. This is up to now done by saving the complete ADC trace of the TOF setup. This is a huge amount of data and needs processing. This has to be performed after the beamtime in close contact to [[Markus Braune>>mailto:markus.braune@desy.de\|\|shape="rect"]] ( responsible for [[OPIS>>url:http://photon-science.desy.de/facilities/flash/photon_diagnostics/opis_spectrometer/index_eng.html\|\|shape="rect"]])
11.1	896
9.1	897
52.1	898	In case OPIS was not operating there is still information about the set wavelength for the undulators (see below) which may differ by up to 5 % from the actual wavelength due to different settings in the FEL ...
12.1	899
9.1	900
	901
12.1	902	==== Electron Beam properties (FLASH2) ====
	903
	904	===== bunch charge =====
	905
79.1	906	{{code language="none"}}/FL2/Electron Diagnostic/Bunch charge/after undulator{{/code}}
	907	//always saved (PBD2)//
12.1	908	DOOCS prop : {{code language="none"}}FLASH.DIAG/PBD2.TOROID.ML/9FL2BURN/CHARGE.FLASH2{{/code}}
79.1	909	DAQ channel: {{code language="none"}}FLASH.DIAG/PBD2.TOROID.ML/9FL2BURN/CHARGE.FLASH2{{/code}}
	910	desc: electron bunch charge FLASH2 (average value for each bunchtrain).
12.1	911	units: nC
	912
9.1	913
52.1	914	===== electron bunch energy =====
9.1	915
52.1	916	{{code language="none"}}/FL2/Electron Diagnostic/Electron energy/energy of first bunch/behind undulators{{/code}}
79.1	917	//always saved (PBD2)//
52.1	918	DOOCS prop : {{code language="none"}}FLASH.DIAG/BEAM_ENERGY_MEASUREMENT/FL2XTDS/ENERGY.FLASH2{{/code}}
79.1	919	DAQ channel: (% style="color:#5e6c84" %)TTF2.DAQ/PBD2.BEAM.ENERGY.MEAS.ML.COPY/FL2XTDS.ENERGY.FLASH2{{code language="none"}}{{/code}}(%%)
	920	desc: electron bunch energy measured behind the undulator. Data is saved with 10 Hz - BUT (for computation reasons) only the energy of the FIRST bunch is recorded. The data is also available for (% style="color:#5e6c84" %)extraction and septum in the beginning of FLASH2
52.1	921
79.1	922	(% style="letter-spacing:0.0px" %)units: (% class="twikiNewLink" %)MeV
52.1	923
	924
	925	(% style="color: rgb(94,108,132);font-weight: 600;letter-spacing: 0.0px;" %)
	926	undulator settings
	927
79.1	928	{{code language="none"}}/FL2/Electron Diagnostic/Undulator setting/set wavelength{{/code}}
	929	//always saved (PBD2)//
14.1	930	DOOCS prop : {{code language="none"}}TTF2.FEEDBACK/FL2.WAVELENGTHCONTROL/FLASH2/WAVELENGTH{{/code}}
79.1	931	DAQ channel: {{code language="none"}}TTF2.FEEDBACK/FL2.WAVELENGTHCONTROL/FLASH2/WAVELENGTH{{/code}}
14.1	932	desc: Set value for the anticipated wavelength . This parameter is used to set the undulator gap. It may however deviate from the actual wavelength by several % ...
	933	units: nm
12.1	934
79.1	935	{{code language="none"}}/FL2/Electron Diagnostic/Undulator setting/SASE14 gap{{/code}}
	936	//always saved (PBD2)//
14.1	937	DOOCS prop : {{code language="none"}}FLASH.UTIL/FL2.UND.MOTOR/FL2SASE14/GAP{{/code}}
79.1	938	DAQ channel: {{code language="none"}}FLASH.UTIL/FL2.UND.MOTOR/FL2SASE14/GAP{{/code}}
15.1	939	desc: gap value of the undulators. This can be used to follow up how many undulators were closed and if there was a taper
14.1	940	units: mm
	941
15.1	942	The gap values are saved for all 12 undulators (Nr 3 to 14). Undulator 14 is the one closest to the experimental hall.
14.1	943
12.1	944	=====
59.1	945	arrival time (BAM) =====
12.1	946
59.1	947	{{info title="BAM information: updates 2022"}}
	948	* see: [[Info collection about the BAMs and how to use the BAM data>>url:https://confluence.desy.de/display/FLASHUSER/Info+collection+for+the+BAM\|\|shape="rect"]]
	949	* The data format of the BAM has been completely altered in the 2022 shutdown
60.1	950	* before 2022 BAMs were always saving the arrival time information for each 1µs bucked regardless if there were electrons in the accelerator or not. I addition the arrival times for FL1 and FL2 were saved in the same parameter ...
61.1	951	* THIS is now different. There are new parameters saving only the arrival times for pulses that go to FL1 and to FL2 (in detail: first time slot of the accelerator and second)
59.1	952	* There has been also a renaming (and relocation) of the BAMs.
	953	** acc: 4DBC3 → FL0.DBC2
	954	** FL1: 1SFELC → FL1.SFELC
79.1	955	** FL2: 8FL2XTDS → (% style="color:#172b4d" %)FL2.SEED5
59.1	956	* for more Info: [[LINK to detailed infos from MSK>>url:https://confluence.desy.de/display/SDiagPublic/BAM+Data+Structure\|\|shape="rect"]]
	957	* [[Link a collection of papers related to the BAM and the analysis of pump-probe experiments>>doc:FLASHUSER.Additional helpful things.FLASH beamlines and instruments references.WebHome]]
	958	* a recent [[talk about the working principle of the BAM>>attach:BAM-basics and outlook-2018_DESY-template_16-9Format.pdf]]
	959	{{/info}}
	960
	961	{{expand title="Discontinued BAM format (used until end 2021)"}}
79.1	962	(% style="color:#000000" %)Discontinued BAM data recording
59.1	963
79.1	964	{{code language="none"}}/FL2/Electron Diagnostic/BAM/8FL2XTDS/electron bunch arrival time (low charge){{/code}}
	965	//always saved (PBD2)//
	966	DOOCS prop : {{code language="none"}}FLASH.SDIAG/BAM/8FL2XTDS/LOW_CHARGE_ARRIVAL_TIME{{/code}}
	967	DAQ channel: {{code language="none"}}FLASH.SDIAG/BAM.DAQ/8FL2XTDS.LOW_CHARGE_ARRIVAL_TIME{{/code}}
	968	desc: Electron bunch arrival time measured with the BAM after the FLASH2 undulator (pulse resolved data)
33.1	969	units: ps (bigger numbers indicate later arrivaltime of the electrons)
	970
79.1	971	FL1{{code language="none"}}//Electron Diagnostic/BAM/4DBC3/electron bunch arrival time (low charge){{/code}}
	972	//always saved (PBD2)//
	973	DOOCS prop : {{code language="none"}}FLASH.SDIAG/BAM/4DBC3/LOW_CHARGE_ARRIVAL_TIME{{/code}}
	974	DAQ channel: {{code language="none"}}FLASH.SDIAG/BAM.DAQ/4DBC3.LOW_CHARGE_ARRIVAL_TIME{{/code}}
	975	desc: Electron bunch arrival time measured with the BAM in the accelerator (pulse resolved data)
14.1	976	units: ps (bigger numbers indicate later arrivaltime of the electrons)
12.1	977
80.1	978	{{info title="BAM hints"}}
79.1	979	* The BAM 4DBC3 measures the arrivaltime of FLASH 1 and FLASH2 in the same data set (thus also sorted in at /FL1/ !).
33.1	980	* The BAM 8FL2XTDS measures only for FLASH2 BUT has the same data structure as the other BAMS ... thus there are also (random) values in in the FLASH1 time slot
	981	** Structure: The first values are for FLASH1 bunches. After a gap of about 70 micros ( 70 colums) with as entry for the switching between FLASH 1 and 2 the values for the electrons used in FLASH2 start. The start time of FLASH2 is also recorded in the DAQ. FLASH1 start time is for historic reasons 700. thus if e.g. the start time of FLASH2 ( property name see below) is 1200 it means that FLASH starts at column 500 (1200-700) ... .In case of doubt ask your local contact
	982	* [[Link a collection of papers related to the BAM and the analysis of pump-probe experiments >>doc:FLASHUSER.Additional helpful things.FLASH beamlines and instruments references.WebHome]]
79.1	983	* [[LINK to detailed infos from MSK (may only work inside DESY network~[~[image:url:http://hasfweb.desy.de/pub/TWiki/TWikiDocGraphics/external-link.gif~\|~\|height="12" width="13"~]~]>>url:http://www.desy.de/~~mbock/pages/BAM_daq_channel_descriptions.html\|\|shape="rect"]]
33.1	984	* a recent [[talk about the working principle of the BAM>>attach:BAM-basics and outlook-2018_DESY-template_16-9Format.pdf]]
	985	{{/info}}
59.1	986	{{/expand}}
10.1	987
68.1	988
	989	====== BAM FL0.DBC2{{code language="none"}}{{/code}} ======
	990
79.1	991	(% style="color:#ff6600" %)DBC2/electron bunch arrival time (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL2/Electron Diagnostic/BAM/{{/code}}
73.1	992
79.1	993	{{code language="none"}}
	994	/zraw/FLASH.SDIAG/BAM.DAQ/FL0.DBC2.ARRIVAL_TIME.ABSOLUTE.SA2.COMP/dGroup/
	995	{{/code}}
73.1	996
68.1	997	//always saved (PBD)//
	998	FL0.DBC2
79.1	999	(% style="color:#000000" %)channel: FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.ABSOLUTE.SA2.COMP
	1000	{{code language="none"}} DOOCS prop : FLASH.SDIAG/BAM//ARRIVAL_TIME.ABSOLUTE.SA2.COMPDAQ {{/code}}(% style="letter-spacing:0.0px" %)desc: Electron bunch arrival time measured with the BAM inside the accelerator (after bunch compressor 2). The property contains only the arrival time of the bunches sent to FL2 (e.g. if there are 30 bunches in FL2 the first 30 values are the arrival time the remaining numbers still may have arbitrary numbers looking like a signal which they are not0). These are the same values as the "raw" data below - just "cleaned". The values show a very good correlation to the arrival time of the XUV pulses in the experiment (see help).
68.1	1001	units: fs (bigger numbers (typically) indicate later arrival times of the electrons).
	1002
	1003
79.1	1004	(% style="color:#ff6600" %)DBC2/electron bunch arrival time (raw) (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL2/Electron Diagnostic/BAM/{{/code}}
73.1	1005
	1006	{{code language="none"}}/zraw/FLASH.SDIAG/BAM.DAQ/FL0.DBC2.ARRIVAL_TIME.ABSOLUTE.SA2/dGroup/{{/code}}
79.1	1007	//always saved (PBD)//
68.1	1008	{{code language="none"}}DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.ABSOLUTE{{/code}}
79.1	1009	(% style="color:#000000" %)FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.ABSOLUTE {{code language="none"}}DAQ channel: {{/code}}(%%)
68.1	1010	desc: Electron bunch arrival time measured with the BAM inside the accelerator (after bunch compressor 2). Here the complete bunch train from the FEL is recorded (FLASH1 and FLASH2 pulses). Thus there are values from FLASH 2 in the second part. they may be separated by several "0" values if the reprate is different from 1 MHz ... - It shows a very good correlation to the arrival time of the XUV pulses in the experiment (see help).
59.1	1011	units: fs (bigger numbers (typically) indicate later arrival times of the electrons).
14.1	1012
59.1	1013
79.1	1014	(% style="color:#ff6600" %)DBC2/error (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL2/Electron Diagnostic/BAM/{{/code}}(%%)
	1015	//always saved (PBD)//
	1016	(% style="color:#000000" %)E.bamError{{code language="none"}}DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIM{{/code}}(%%)
	1017	(% style="color:#000000" %)FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.BAMERROR{{code language="none"}}DAQ channel: {{/code}}(%%)
59.1	1018	desc: If the value is 0 , the BAM is working well. If it is non-zero there is a problem !!
	1019
	1020
79.1	1021	(% style="color:#ff6600" %)DBC2/status (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL2/Electron Diagnostic/BAM/{{/code}}(%%)
	1022	//always saved (PBD)//
	1023	(% style="color:#000000" %)E..bamStatus.//2//{{code language="none"}}DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIM{{/code}}(%%)
	1024	(% style="color:#000000" %): FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.BAMSTATUS.2{{code language="none"}}DAQ channel{{/code}}(%%)
59.1	1025	desc: status bit: 0 - data is valid; 1 - beam present; 2 - calibration ongoing; 3 - feedback enabled; 4 - feedback acting; mostly check for bit 0 == 1 is sufficient
	1026
	1027
68.1	1028	====== BAM FL2.SEED5{{code language="none"}}{{/code}} ======
	1029
79.1	1030	/FL2/Electron Diagnostic/BAM/SEED5(% style="color:#ff6600" %)/electron bunch arrival time (HDF5 name not yet implemented - see zraw)
68.1	1031
79.1	1032	(% style="color:#000000" %){{code language="none"}}/zraw/FLASH.SDIAG/BAM.DAQ/FL0.SEED5.ARRIVAL_TIME.ABSOLUTE.SA2.COMP/dGroup/{{/code}}
73.1	1033
68.1	1034	//always saved (PBD)//
79.1	1035	(% style="color:#172b4d" %)FL2.SEED5(%%)
	1036	(% style="color:#000000" %)channel: FLASH.SDIAG/BAM/(% style="color:#172b4d" %)FL2.SEED5(% style="color:#000000" %)/ARRIVAL_TIME.ABSOLUTE.SA1.COMP
74.1	1037	{{code language="none"}} DOOCS prop : FLASH.SDIAG/BAM//ARRIVAL_TIME.ABSOLUTE.SA1.COMPDAQ {{/code}}(%%)desc: Electron bunch arrival time measured with the BAM before the undulator (pulse resolved data). This one was newly installed in 2020.. The property contains only the arrival time of the bunches sent to FL2 (e.g. if there are 30 bunches in FL2 the first 30 values are the arrival time the remaining numbers still may have arbitrary numbers looking like a signal which they are not). These are the same values as the "raw" data below - just "cleaned". The values show a very good correlation to the arrival time of the XUV pulses in the experiment (see help).
68.1	1038	units: fs (bigger numbers (typically) indicate later arrival times of the electrons).
	1039
	1040
	1041
79.1	1042	(% style="color:#172b4d" %)SEED5(% style="color:#ff6600" %)/electron bunch arrival time (raw) (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL2/Electron Diagnostic/BAM/{{/code}}
73.1	1043
79.1	1044	(% style="color:#000000" %){{code language="none"}}/zraw/FLASH.SDIAG/BAM.DAQ/FL0.SEED5.ARRIVAL_TIME.ABSOLUTE.SA2/dGroup/{{/code}}(%%)
	1045	//always saved (PBD)//
	1046	(% style="color:#172b4d" %)FL2.SEED5{{code language="none"}}DOOCS prop : FLASH.SDIAG/BAM//ARRIVAL_TIME.ABSOLUTE{{/code}}(%%)
	1047	~ (% style="color:#000000" %)FLASH.SDIAG/BAM/(% style="color:#172b4d" %)FL2.SEED5(% style="color:#000000" %)/ARRIVAL_TIME.ABSOLUTE {{code language="none"}}DAQ channel:{{/code}}(%%)
68.1	1048	desc: Electron bunch arrival time measured with the BAM before the undulator (pulse resolved data). This one was newly installed in 2020. Here the complete bunch train from the FEL is recorded (FLASH1 and FLASH2 pulses). Thus there are values from FLASH 2 in the second part. they may be separated by several "0" values if the reprate is different from 1 MHz ... - It shows a very good correlation to the arrival time of the XUV pulses in the experiment (see help).
59.1	1049	units: fs (bigger numbers (typically) indicate later arrival times of the electrons).
	1050
	1051
79.1	1052	(% style="color:#172b4d" %)SEED5(% style="color:#ff6600" %)/error (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL2/Electron Diagnostic/BAM/{{/code}}(%%)
	1053	//always saved (PBD)//
	1054	(% style="color:#172b4d" %)FL2.SEED5(% style="color:#000000" %)E.bamError{{code language="none"}}DOOCS prop : FLASH.SDIAG/BAM//ARRIVAL_TIM{{/code}}(%%)
	1055	(% style="color:#000000" %): FLASH.SDIAG/BAM/(% style="color:#172b4d" %)FL2.SEED5(% style="color:#000000" %)/ARRIVAL_TIME.BAMERROR{{code language="none"}}DAQ channel{{/code}}(%%)
59.1	1056	desc: If the value is 0 , the BAM is working well. If it is non-zero there is a problem !!
	1057
	1058
79.1	1059	(% style="color:#172b4d" %)SEED5(% style="color:#ff6600" %)/status (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL2/Electron Diagnostic/BAM/{{/code}}(%%)
	1060	//always saved (PBD)//
	1061	(% style="color:#172b4d" %)FL2.SEED5(% style="color:#000000" %)E.bamStatus.//2//{{code language="none"}}DOOCS prop : FLASH.SDIAG/BAM//ARRIVAL_TIM{{/code}}(%%)
	1062	(% style="color:#000000" %)el: FLASH.SDIAG/BAM/(% style="color:#172b4d" %)FL2.SEED5(% style="color:#000000" %)/ARRIVAL_TIME.BAMSTATUS.2{{code language="none"}}DAQ chann{{/code}}(%%)
59.1	1063	desc: status bit: 0 - data is valid; 1 - beam present; 2 - calibration ongoing; 3 - feedback enabled; 4 - feedback acting; mostly check for bit 0 == 1 is sufficient
	1064
	1065
15.1	1066	[[Contents>>doc:\|\|anchor="Contents"]]
12.1	1067
	1068
16.1	1069	==== Timing information, rep rate etc. (FLASH2) ====
12.1	1070
15.1	1071	===== start time of FLASH2 =====
12.1	1072
79.1	1073	{{code language="none"}}/FL2/Timing/start time flash2{{/code}}
	1074	//always saved (PBD2)//
	1075	DOOCS prop : {{code language="none"}}FLASH.DIAG/TIMER/FLASHCPUTIME1.0/BUNCH_POSITION.2{{/code}}
	1076	DAQ channel: {{code language="none"}}FLASH.DIAG/TIMER/FLASHCPUTIME1.0/BUNCH_POSITION.2{{/code}}
17.1	1077	desc: The max 600 µs acceleration time of FLASH is devided between FLASH1 and FLASH2. This 600 µs window starts with FLASH1 (up to now) at a time"label" of 700 µs (for historic reasons). Thus the first bunch of FLASH 1 comes at "700" and the last possibel bunch comes at 1300 (700+600). After FLASH1 train is over ther is a about 70µs switching time with no bunches. Then comes the first FLASH2 bunch. Thus if e.g. the start time of FLASH2 is 1200 it means that FLASH2 starts at column 500 (1200-700) in the HDF5 files. (However for yet unknown reasons this may change by 2-3 colums ...)
15.1	1078	units: µs
12.1	1079
	1080	===== bunch repetition rate =====
	1081
79.1	1082	{{code language="none"}}/FL2/Timing/repetition rate{{/code}}
	1083	//always saved (PBD2)//
	1084	DOOCS prop : {{code language="none"}}FLASH.DIAG/TIMER/FLASHCPUTIME1.0/REP_RATE_KHZ.2{{/code}}
	1085	DAQ channel: {{code language="none"}}FLASH.DIAG/TIMER/FLASHCPUTIME1.0/REP_RATE_KHZ.2{{/code}}
15.1	1086	desc: repetition rate of the bunches / pulses within the burst (FLASH2)
12.1	1087	units: kHz
	1088
74.1	1089
	1090	===== set number of pulses =====
	1091
79.1	1092	(% style="color:#ff6600" %)(HDF5 name not yet implemented - see zraw)(% style="color:#ff0000" %){{code language="none"}}/FL2/Timing/set number of bunches {{/code}}(%%)
	1093	//always saved (PBD2)//
74.1	1094	DOOCS prop : {{code language="none"}}FLASH.DIAG/TIMINGINFO/TIME1.BUNCH_FIRST_INDEX.2 [4th number]{{/code}}
	1095	DAQ channel: {{code language="none"}}FLASH.DIAG/TIMINGINFO/TIME1.BUNCH_FIRST_INDEX.2 [4th number]{{/code}}
	1096	desc: Number of bunches set in the control (timing) system. The property contains 4 numbers. the last one is the number of pulses (see also [[doc:FLASH.Timing properties]] (internal link)). If pulses are used for diagnostic of the protection system of the accelerator limits the number of bunches to be accelerated and thus the actual number of pulses may be smaller than the set one
	1097	units:
	1098
12.1	1099	===== actual number of pulses =====
	1100
79.1	1101	{{code language="none"}}/FL1/Timing/actual number of bunches{{/code}}
	1102	//always saved (PBD2)//
	1103	DOOCS prop : {{code language="none"}}FLASH.DIAG/PBD2.TOROID.ML/3GUN/NUMBEROFBUNCHES.FLASH2{{/code}}
	1104	DAQ channel: {{code language="none"}}FLASH.DIAG/PBD2.TOROID.ML/3GUN/NUMBEROFBUNCHES.FLASH2{{/code}}
	1105	desc: Number of bunches measured BEHIND the undulator. If pulses are used for diagnostic of the protection system of the accelerator limits the number of bunches to be accelerated this is the actual number that created XUV radiation.The number is calculated by the DAQ middle layer server, (FLASH2)
12.1	1106	units:
79.1	1107
12.1	1108
	1109	===== actual pulse pattern recorded after the undulator =====
	1110
79.1	1111	{{code language="none"}}/FL1/Timing/Bunch pattern/pattern after undulator{{/code}}
	1112	//always saved (PBD2)//
	1113	DOOCS prop : {{code language="none"}}FLASH.DIAG/PBD2.TOROID.ML/9FL2BURN.PULSEPATTERN{{/code}}
	1114	DAQ channel: {{code language="none"}}FLASH.DIAG/PBD2.TOROID.ML/9FL2BURN.PULSEPATTERN{{/code}}
	1115	desc: The bunch pattern as function of time in a burst recorded by toroide diagnostic BEHIND the undulator. (FLASH2)
12.1	1116	units:
79.1	1117
12.1	1118
	1119	===== Train ID =====
	1120
79.1	1121	{{code language="none"}}/Timing/train ID{{/code}}
	1122	//always saved (PBD2)//
	1123	DOOCS prop : {{code language="none"}}none{{/code}}
	1124	DAQ channel: {{code language="none"}}none{{/code}}
	1125	desc: Each 10 Hz burst has its unique train ID. For the HDF5 dataset the ID is the same for all parameters with the same index (note camera images may be shifted by 1 ID - talk to the experts !)
12.1	1126	units:
79.1	1127
12.1	1128
	1129	===== Train time =====
	1130
79.1	1131	//always saved (PBD2)//
	1132	{{code language="none"}}/Timing/train time{{/code}}
	1133	desc:Local time as array of day, hour, minute, second, and centisecond. This dataset is meant for visualisation purposes only. For correlations use the train ID or the Unix time of the time stamp
12.1	1134	units: d h min s cs
79.1	1135
12.1	1136
79.1	1137	{{code language="none"}}
	1138	/Timing/time stamp
	1139	{{/code}}
16.1	1140
79.1	1141	//always saved (PBD2)//
	1142	desc: first column: Local time in unix time. To get day, hour, minute, second you can use unix: e.g. date ~-~-date='@1553617729' or matlab, python etc
	1143	second column: microseconds
12.1	1144	third column: Train ID of FLASH
79.1	1145
12.1	1146
	1147	[[Contents>>doc:\|\|anchor="Contents"]]
	1148
	1149
19.1	1150	==== User Data (FLASH2) ====
18.1	1151
19.1	1152	The data saved specifically for detectors at an experiment will show up in /Experiment/ there is a large number of options for cameras or monitoring pslow properties (motor positons etc) for user experiments. For details please ask your local contact.
	1153
	1154	NOTE: If parameters for an experiment are included on short notice the correct naming in the HDF5 may not be in time and the data will show up in /uncategorized/ with the DOOCS names
	1155
	1156	The most common and permanently installed device used by experiment are our ADCs:
	1157
18.1	1158	===== GHz ADCs =====
	1159
79.1	1160	ADC traces of the (SPDevices 412) GHZ ADCs available for the users . More information about the ADCs can be found [[here>>doc:FLASHUSER.Data Acquisition and controls.Controls (DOOCS, jDDD,\.\.\.).MTCA ADCs.WebHome]]
	1161	//saved on DEMAND in the user DAQ//
19.1	1162	\\Up to now there are 4 channels available at FL24
	1163	\\\\{{code language="none"}}/FL2/Experiment/MTCA-EXP1/ADQ412 GHz ADC/CH00/TD{{/code}}
	1164	{{code language="none"}}/FL2/Experiment/MTCA-EXP1/ADQ412 GHz ADC/CH01/TD{{/code}}
	1165	\\{{code language="none"}}/FL2/Experiment/MTCA-EXP1/ADQ412 GHz ADC/CH02/TD{{/code}}{{code language="none"}}/FL2/Experiment/MTCA-EXP1/ADQ412 GHz ADC/CH03/TD{{/code}}
18.1	1166
	1167
79.1	1168	DOOCS prop : {{code language="none"}}FLASH.FEL/ADC.ADQ.FL2EXP1/FL2EXP1.CH00/CH00.TD or CH00.DAQ.TD{{/code}}
18.1	1169	here the {{code language="none"}}CH00.TD{{/code}} is the full ADC trace as it is sampled ( typically several 100.000 samples per pulse train) while the {{code language="none"}}CH00.DAQ.TD{{/code}} trace only has the number of samples which are sent to the DAQ OR if //grouping// is activated the {{code language="none"}}CH00.DAQ.TD{{/code}} conatins only the grouped spectra. To read the ADC trace with an online analysis program the {{code language="none"}}CH00.DAQ.TD{{/code}} is used preferablly.
19.1	1170	DAQ channel: {{code language="none"}}FLASH.FEL/ADC.ADQ.FL2EXP1/FL2EXP1.CH00{{/code}}
18.1	1171
	1172	In addition there are also additional parameters saved like:
	1173
	1174	* {{code language="none"}}sample frequency{{/code}}: it shows the sample frequency in MHz (number of samples per µs). NOTE: the clock of the ADC is NOT synchronized to the FLASH timing system. Thus the number of samples between bunches in the bunch train may be not integer numbers which will be show up for long bunch trains.
	1175	* {{code language="none"}}number of samples{{/code}}: total number of samoles recorded for each 10 Hz trigger
79.1	1176	* {{code language="none"}}error (ADC):{{/code}}0 indicates that there was no error
18.1	1177	* {{code language="none"}}/CH0-CH3/offset{{/code}}: To use the full dynamic range of the ADC one can shift the base line . This offset is saved here.
	1178
	1179	===== MHz ADCs =====
	1180
79.1	1181	similar to the GHz ADCs the MHz ADCs are saved with HDF5 names like:
	1182	{{code language="none"}}/FL2/Experiment/MTCA-EXP1/SIS8300 100MHz ADC/CH2/TD{{/code}}
	1183	DOOCS prop : FLASH.FEL/ADC.SIS.FL2EXP1/FL2EXP1.CH02/CH00.TD
19.1	1184	DAQ channel: : FLASH.FEL/ADC.SIS.FL2EXP1/FL2EXP1.CH02
18.1	1185
	1186	In addition there are also additional parameters saved like:
	1187
	1188	* {{code language="none"}}sample frequency{{/code}}: it shows the sample frequency in MHz (number of samples per µs). NOTE: the clock of the ADC is NOT synchronized to the FLASH timing system. Thus the number of samples between bunches in the bunch train may be not integer numbers which will be show up for long bunch trains.
	1189	* {{code language="none"}}number of samples{{/code}}: total number of samoles recorded for each 10 Hz trigger
	1190
	1191	[[Contents>>doc:\|\|anchor="Contents"]]
	1192
12.1	1193
	1194
77.1	1195	==== FL 24 Pump Probe Laser (FLASH2) ====
21.1	1196
80.1	1197	{{info}}
	1198	list of saved parameters status May 2024 (up to now the parameters can be found in /zraw/ ... )
	1199
	1200	[[attach:FSLADAQ-FL23.pdf\|\|target="_blank"]]
	1201
	1202	[[attach:FSLADAQ-DAQParameterlistFL24.pdf\|\|target="_blank"]]
	1203
	1204	[[attach:FSLADAQ-DAQParameterlistPPlaser.pdf\|\|target="_blank"]]
	1205	{{/info}}
	1206
	1207
79.1	1208	These are the parameters that can be saved in the FL2 User DAQ for the FL2 PP laser// FOR BEAMLINE FL24//
21.1	1209
64.1	1210	User delay
	1211
	1212	Delay (set value):
	1213
79.1	1214	{{code language="none"}}
	1215	FLASH.SYNC/LASER.LOCK.EXP/F2.PPL.OSC/FMC0.MD22.0.POSITION_SET.WR
	1216	{{/code}}
64.1	1217
77.1	1218	Delay (readback):
64.1	1219
79.1	1220	{{code language="none"}}
	1221	FLASH.SYNC/LASER.LOCK.EXP/F2.PPL.OSC/FMC0.MD22.0.POSITION.RD
	1222	{{/code}}
64.1	1223
79.1	1224	(% style="letter-spacing:0.0px" %)Delay (encoder readback):
77.1	1225
79.1	1226	{{code language="none"}}
	1227	FLASH.SYNC/LASER.LOCK.EXP/F2.PPL.OSC/FMC0.MD22.0.ENCODER_POSITION.RD
	1228	{{/code}}
77.1	1229
64.1	1230	OXC. jitter:
	1231
79.1	1232	{{code language="none"}}
	1233	FLASH.SYNC/LASER.LOCK.EXP/F2.PPL.OSC/CURRENT_INPUT_JITTER.RD
	1234	{{/code}}
64.1	1235
	1236
	1237
77.1	1238	FL24 Pulse resolved energy:
	1239
72.1	1240	OPCPA output (photodiode signal raw ADC trace 16000 samples):
64.1	1241
79.1	1242	{{code language="none"}}
	1243	/zraw/FLASH.LASER/FLASH2CPUULGAN1.ADCSCOPE/CH23.TD/dGroup
	1244	{{/code}}
64.1	1245
79.1	1246	(% style="letter-spacing:0.0px" %)Upper breadboard Photodiode (THG) burst (photodiode signal raw ADC trace 16000 samples)::
64.1	1247
79.1	1248	{{code language="none"}}
	1249	/zraw/FLASH.LASER/FLASH2CPUULGAN1.ADCSCOPE/CH26.TD/dGroup
	1250	{{/code}}
64.1	1251
72.1	1252	Upper breadboard Photodiode (THG) energy (analyzed signal. integration over pulses in the ADC trace. contains for each laser pulse the pulse energy in a.u.)
64.1	1253
79.1	1254	{{code language="none"}}
	1255	/zraw/FLASH.LASER/MOD24.PES/FL24_userPD/dGroup
	1256	{{/code}}
64.1	1257
	1258
77.1	1259	FL24 LAM (Laser Arrivaltime Monitor) pulse resolved data:
64.1	1260
72.1	1261	Signal of Photodiode1 - for experts only... (analyzed signal. integration over pulses in the ADC trace. )
	1262
79.1	1263	{{code language="none"}}
	1264	/zraw/FLASH.LASER/MOD24.PES/LAM.PD1/dGroup
	1265	{{/code}}
72.1	1266
	1267	Signal of Photodiode2 - for experts only... (analyzed signal. integration over pulses in the ADC trace.)
	1268
79.1	1269	{{code language="none"}}
	1270	/zraw/FLASH.LASER/MOD24.PES/LAM.PD2/dGroup
	1271	{{/code}}
72.1	1272
	1273	"Actual" LAM Signal - to be calibrated ...... (analyzed signal. integration over pulses in the ADC trace.)
	1274
79.1	1275	{{code language="none"}}
	1276	/zraw/FLASH.LASER/MOD24.PES/LAM.PDBAL/dGroup
	1277	{{/code}}
72.1	1278
79.1	1279	The delay feedback(% style="letter-spacing:0.0px" %)
75.1	1280
79.1	1281	{{code language="none"}}
	1282	FLASH.LASER/ULGAN1.DYNPROP/TCFIBER.DOUBLES/DOUBLE26
	1283	{{/code}}
64.1	1284
79.1	1285	The LAM delay feedback(% style="letter-spacing:0.0px" %) (the pulse energy signal, which is saved in the above but maybe it’s good to have this also as slow, in the case these two numbers are not the same the sysdc was active instead of the LAM):
75.1	1286
79.1	1287	{{code language="none"}}
	1288	FLASH.LASER/MOD24.PES/LAM.PDBAL/PULSEENERGY.MEAN
	1289	{{/code}}
75.1	1290
76.1	1291	LAM Delay line act:
75.1	1292
76.1	1293	{{code language="none"}}FLASH.SYNC/LAM.EXP.ODL/F2.MOD.AMC12/FMC0.MD22.1.POSITION.RD{{/code}}
	1294	LAM Delay line set:
75.1	1295
79.1	1296	{{code language="none"}}
	1297	FLASH.SYNC/LAM.EXP.ODL/F2.MOD.AMC12/FMC0.MD22.1.POSITION_SET.WR
	1298	{{/code}}
75.1	1299
76.1	1300	LAM Delay line encoder:
75.1	1301
79.1	1302	{{code language="none"}}
	1303	FLASH.SYNC/LAM.EXP.ODL/F2.MOD.AMC12/FMC0.MD22.1.ENCODER_POSITION.RD
	1304	{{/code}}
75.1	1305
76.1	1306	Temperature feedback:
75.1	1307
79.1	1308	{{code language="none"}}
	1309	FLASH.LASER/ULGAN1.DYNPROP/TCFIBER.DOUBLES/DOUBLE24
	1310	{{/code}}
75.1	1311
	1312	Feedback mode (if this is not =1 the delay FB is not active, then it’s either temp feedback controlled or failsave, maybe it’s good to have):
	1313
79.1	1314	{{code language="none"}}
	1315	FLASH.LASER/ULGAN1.DYNPROP/TCFIBER.INTS/INTEGER30
	1316	{{/code}}
75.1	1317
	1318
77.1	1319	FL24 Attenuator angle:
75.1	1320
79.1	1321	{{code language="none"}}
	1322	FLASH.FEL/FLAPP2BEAMLINES/MOTOR1.FL24/FPOS
	1323	{{/code}}
64.1	1324
77.1	1325	FL24 Polarization control:
64.1	1326
79.1	1327	{{code language="none"}}
	1328	FLASH.FEL/FLAPP2BEAMLINES/MOTOR14.FL24/FPOS
	1329	{{/code}}
64.1	1330
	1331	SysDC delay error:
	1332
79.1	1333	{{code language="none"}}
	1334	FLASH.LASER/ULGAN1.DYNPROP/TCFIBER.DOUBLES/DOUBLE26
	1335	{{/code}}
64.1	1336
	1337
	1338	Timing error: (these two need to be observed and both=0 means no error)
	1339
79.1	1340	{{code language="none"}}
	1341	FLASH/CPUULGAN1.TIMING/ULGAN1/dT_alarm
	1342	{{/code}}
64.1	1343
79.1	1344	{{code language="none"}}
	1345	FLASH/CPUULGAN1.TIMING/ULGAN1/dMPN
	1346	{{/code}}
64.1	1347
	1348	Laser error status:
	1349
	1350
77.1	1351	FL24 Virtual camera X and Y history, beam size: (use slow data)
64.1	1352
79.1	1353	{{code language="none"}}
	1354	FLASH.LASER/MOD24.BEAMPOS/UV.VF_BP/CENTER.X
	1355	{{/code}}
64.1	1356
79.1	1357	{{code language="none"}}
	1358	FLASH.LASER/MOD24.BEAMPOS/UV.VF_BP/CENTER.Y
	1359	{{/code}}
64.1	1360
79.1	1361	{{code language="none"}}
	1362	FLASH.LASER/MOD24.CAM/UV.14.VF/ROI_SPECTRUM.X.SIG
	1363	{{/code}}
64.1	1364
	1365	{{expand title="Parameters used until 2021"}}
79.1	1366	//{{code language="none"}}/FL2/Experiment/Pump probe laser/FL24/attenuator position{{/code}}always saved (PBD2)//
	1367	DOOCS prop : {{code language="none"}}FLASH.FEL/FLAPP2BEAMLINES/MOTOR1.FL24/FPOS{{/code}}
	1368	DAQ channel: {{code language="none"}}FLASH.FEL/FLAPP2BEAMLINES/MOTOR1.FL24/FPOS{{/code}}
	1369	desc: attenuation of the PPLaser in the FL24 hutch (rotation of a waveplate)
21.1	1370	units : deg.
	1371
12.1	1372
21.1	1373
79.1	1374	//{{code language="none"}}/FL2/Experiment/Pump probe laser/FL24/polarization position{{/code}}always saved (PBD2)//
	1375	DOOCS prop : {{code language="none"}}FLASH.FEL/FLAPP2BEAMLINES/MOTOR2.FL24/FPOS{{/code}}
	1376	DAQ channel: {{code language="none"}}FLASH.FEL/FLAPP2BEAMLINES/MOTOR2.FL24/FPOS{{/code}}
	1377	desc: attenuation of the PPLaser in the FL24 hutch (rotation of a waveplate)
21.1	1378	units : deg.
	1379
12.1	1380
79.1	1381	{{code language="none"}}/FL1/Experiment/Pump probe laser/laser delay readback{{/code}}
	1382	//always saved (PBD2)//
	1383	DOOCS prop : {{code language="none"}}FLASH.SYNC/LASER.LOCK.EXP/FLASH2.PPL1.OSC1/FMC0.MD22.0.POSITION.RD{{/code}}
21.1	1384	DAQ channel: {{code language="none"}}FLASH.SYNC/LASER.LOCK.EXP/FLASH2.PPL1.OSC1/FMC0.MD22.0.POSITION.RD{{/code}}
	1385	desc: delay of the Pump probe laser - measured by the read back position of the motor. There is also the set value available ( upto now these values are only updating every 1-2 seconds. There is no fast encoder property as on FLASH1 available)
	1386	units : ps )
	1387
12.1	1388
79.1	1389	{{code language="none"}}/FL1/Experiment/Pump probe laser/Synchronization/timing jitter RMS{{/code}}
	1390	//always saved (PBD)//
	1391	DOOCS prop : {{code language="none"}}FLASH.SYNC/LASER.LOCK.EXP/FLASH2.PPL1.OSC1/CURRENT_INPUT_JITTER.RD{{/code}}
	1392	DAQ channel: {{code language="none"}}FLASH.SYNC/LASER.LOCK.EXP/FLASH2.PPL1.OSC1/CURRENT_INPUT_JITTER.RD{{/code}}
22.1	1393	desc: rms jitter of the fs-Oscillator
	1394	units: fs
65.1	1395	{{/expand}}
21.1	1396
77.1	1397
	1398	==== FL 26 Pump Probe Laser (FLASH2) ====
	1399
79.1	1400	These are the parameters that can be saved in the FL2 User DAQ for the FL2 PP laser// FOR BEAMLINE FL26//
77.1	1401
	1402
	1403	User delay
	1404
	1405	Delay (set value):
	1406
79.1	1407	{{code language="none"}}
	1408	FLASH.SYNC/LASER.LOCK.EXP/F2.PPL.OSC/FMC0.MD22.0.POSITION_SET.WR
	1409	{{/code}}
77.1	1410
	1411	Delay (readback):
	1412
79.1	1413	{{code language="none"}}
	1414	FLASH.SYNC/LASER.LOCK.EXP/F2.PPL.OSC/FMC0.MD22.0.POSITION.RD
	1415	{{/code}}
77.1	1416
78.1	1417	Delay (encoder readback):
77.1	1418
79.1	1419	{{code language="none"}}
	1420	FLASH.SYNC/LASER.LOCK.EXP/F2.PPL.OSC/FMC0.MD22.0.ENCODER_POSITION.RD
	1421	{{/code}}
77.1	1422
	1423	OXC. jitter:
	1424
79.1	1425	{{code language="none"}}
	1426	FLASH.SYNC/LASER.LOCK.EXP/F2.PPL.OSC/CURRENT_INPUT_JITTER.RD
	1427	{{/code}}
77.1	1428
	1429
	1430	Parameters for FL26
	1431
78.1	1432	(% class="wrapped" %)
77.1	1433	\|(((
	1434	FL2PPL FL26 REMI Attenuation: HWP motor current position
	1435	)))\|(((
	1436	FLASH.FEL/FLAPP2BEAMLINES/MOTOR11.FL26B/FPOS
	1437	)))
	1438	\|(((
	1439	FL2PPL FL26 REMI Polarization: linear polarization angle
	1440	)))\|(((
	1441	FLASH.FEL/FLAPP2BEAMLINES/MOTOR12.FL26B/FPOS
	1442	)))
	1443	\|(((
	1444	FL2PPL FL26 REMI Diagnostics: NIR spectrum
	1445	)))\|(((
	1446	FLASH.LASER/MOD26.SPECT/REMI/DAQ_CHANNEL
	1447	)))
	1448	\|(((
	1449	FL2PPL FL26 REMI Diagnostics: photo diode input MOD2.6 - pulse energy mean
	1450	)))\|(((
	1451	FLASH.LASER/MOD26.PES/RE_OUT/PULSEENERGY.MEAN
	1452	)))
	1453	\|(((
	1454	FL2PPL FL26 REMI Diagnostics: photo diode input MOD2.6 - intra burst pulse energy
	1455	)))\|(((
	1456	FLASH.LASER/MOD26.PES/RE_OUT/DAQ_CHANNEL
	1457	)))
	1458	\|(((
	1459	FL2PPL FL26 REMI Diagnostics: photo diode input MOD2.6 - raw adc
	1460	)))\|(((
	1461	FLASH.LASER/TAMC532DMA/ULGAN1_S5/CH04.TD
	1462	)))
	1463	\|(((
	1464	FL2PPL FL26 REMI Diagnostics: photo diode input REMI - pulse energy mean
	1465	)))\|(((
	1466	FLASH.LASER/MOD26.PES/INC_BOX/PULSEENERGY.MEAN
	1467	)))
	1468	\|(((
	1469	FL2PPL FL26 REMI Diagnostics: photo diode input REMI - intra burst pulse energy
	1470	)))\|(((
	1471	FLASH.LASER/MOD26.PES/INC_BOX/DAQ_CHANNEL
	1472	)))
	1473	\|(((
	1474	FL2PPL FL26 REMI Diagnostics: photo diode input REMI - raw adc
	1475	)))\|(((
	1476	FLASH.LASER/TAMC532DMA/ULGAN1_S5/CH05.TD
	1477	)))
	1478	\|(((
	1479	FL2PPL FL26 REMI In coupling: filter wheel 1 position
	1480	)))\|(((
	1481	FLASH/MOD26.FW1/FLASH2MOD26/pos
	1482	)))
	1483	\|(((
	1484	FL2PPL FL26 REMI In coupling: filter wheel 2 position
	1485	)))\|(((
	1486	FLASH/MOD26.FW2/FLASH2MOD26/pos
	1487	)))
	1488	\|(((
	1489	FL2PPL FL26 REMI: Energy meter REMI incoupling breadboard
	1490	)))\|(((
	1491	FLASH.LASER/MOD26.OPHIRE/REINC.54/DAQ_CHANNEL
	1492	)))
	1493	\|(((
	1494	FL2PPL FL26 REMI Incoupling: focusing lens position
	1495	)))\|(((
	1496	FLASH.FEL/FLAPP2BEAMLINES/MOTOR3.FL26B/FPOS
	1497	)))
	1498	\|(((
	1499	FL2PPL FL26 REMI Incoupling: nearfield
	1500	)))\|(((
	1501	FLASH.LASER/MOD26.CAM/REINC.21.NF/DAQ_CHANNEL
	1502	)))
	1503	\|(((
	1504	FL2PPL FL26 REMI Incoupling: focus
	1505	)))\|(((
	1506	FLASH.LASER/MOD26.CAM/REINC.22.FF/DAQ_CHANNEL
	1507	)))
	1508	\|(((
	1509	FL2PPL FL26 REMI Drift: relative arrival time intra burst LAM balanced - calb. in the PES
	1510	)))\|(((
	1511	FLASH.LASER/MOD26.PES/LAM_DIFF/DAQ_CHANNEL
	1512	)))
	1513	\|(((
	1514	FL2PPL FL26 REMI Drift: forward signal (PD1) raw
	1515	)))\|(((
	1516	FLASH.LASER/TAMC532DMA/ULGAN1_S5/CH00.TD
	1517	)))
	1518	\|(((
	1519	FL2PPL FL26 REMI Drift: backward signal (PD2) raw
	1520	)))\|(((
	1521	FLASH.LASER/TAMC532DMA/ULGAN1_S5/CH01.TD
	1522	)))
	1523	\|(((
	1524	FL2PPL FL26 REMI Drift: mean relative burst arrival time - avarage of the calib value
	1525	)))\|(((
	1526	FLASH.LASER/MOD26.PES/LAM_DIFF/PULSEENERGY.MEAN
	1527	)))
	1528	\|(((
	1529	FL2PPL FL26 REMI Drift: delay line position (ODL of the LAM REMI)
	1530	)))\|(((
	1531	FLASH.FEL/FLAPP2BEAMLINES/MOTOR14.FL26B/FPOS
	1532	)))
	1533	\|(((
	1534	FL2PPL FL26 Laser Hutch: delay line position (ODL of the osc. Sync / user delay)
	1535	)))\|(((
	1536	FLASH.SYNC/LASER.LOCK.EXP/F2.PPL.OSC/FMC0.MD22.0.POSITION.RD
	1537	)))
	1538	\|(((
	1539	FL2PPL FL26 REMI Drift: delay line encoder position (ODL REMI raw value)
	1540	)))\|(((
	1541	FLASH.SYNC/LAM.EXP.ODL/F2.MOD.AMC12/FMC0.MD22.0.ENCODER_POSITION.RD
	1542	)))
	1543	\|(((
	1544	Jiiter between oscillator and MLO (inloop jitter osc. Sync)
	1545	)))\|(((
	1546	FLASH.SYNC/LASER.LOCK.EXP/F2.PPL.OSC/CURRENT_INPUT_JITTER.RD
	1547	)))
	1548	\|(((
	1549	Temperature controlled fiber (PWM signal to the temperature controlled fiber delay sysdc)
	1550	)))\|(((
	1551	FLASH.LASER/ULGAN1.DYNPROP/TCFIBER.DOUBLES/DOUBLE23
	1552	)))
	1553	\|(((
	1554	Temperature controlled fiber (Temp of the fiber delay sysdc)
	1555	)))\|(((
	1556	FLASH.LASER/ULGAN1.DYNPROP/TCFIBER.DOUBLES/DOUBLE24
	1557	)))
	1558	\|(((
	1559	Sydc feedback data if LAM is not activated (sysdc delay)
	1560	)))\|(((
	1561	FLASH.LASER/ULGAN1.DYNPROP/TCFIBER.DOUBLES/DOUBLE26
	1562	)))
	1563
21.1	1564	[[Contents>>doc:\|\|anchor="Contents"]]
	1565
	1566
23.1	1567	=== "/uncategorized/" ===
	1568
	1569	If parameters for an experiment are included on short notice the correct naming in the HDF5 may not be in time and the data will show up in /uncategorized/ with their DOOCS names
	1570
	1571
1.1	1572	=== HDF5 structure revisions ===
	1573
	1574	Starting with Beamblock 4, August 2018, the hierarchy of the HDF group names have been adapted to reflect the new situation at FLASH. FLASH2 is operating for users quite some time now. Therefore, both accelerators appear equally in their respective HDF groups, namely "/FL1" and "/FL2". The root group of proper, by run organised HDF files have an attribute called "version". This version attribute has changed from "0.2.x" to "0.3.x". The changes in detail:
	1575
	1576
	1577	* All FLASH1 related HDF groups moved to group "/FL1", i.e. a new prefix "/FL1" is added to their HDF path.
	1578	* The ambigious term "pulse" has been replaced by "train" to refer to "pulse train". Most notably, the dataset "/Timing/pulse ID" has changed to "/Timing/train ID".
	1579	* A number of inconsistent names have been streamlined. The relevant changes are listed in the following table.
	1580
45.1	1581	(% class="wrapped" %)
1.1	1582	\|=(((
4.1	1583	earlier HDF path (vers. 0.2)
1.1	1584	)))\|=(((
4.1	1585	is now (vers. 0.3)
1.1	1586	)))
	1587	\|(((
	1588	/Photon Diagnostic/GMD/Beam position/position BDA x
	1589	)))\|(((
	1590	/FL1/Photon Diagnostic/GMD/Beam position/position BDA horizontal
	1591	)))
	1592	\|(((
	1593	/Photon Diagnostic/GMD/Beam position/position BDA y
	1594	)))\|(((
	1595	/FL1/Photon Diagnostic/GMD/Beam position/position BDA vertical
	1596	)))
	1597	\|(((
	1598	/Photon Diagnostic/GMD/Beam position/position tunnel x
	1599	)))\|(((
	1600	/FL1/Photon Diagnostic/GMD/Beam position/position tunnel horizontal
	1601	)))
	1602	\|(((
	1603	/Photon Diagnostic/GMD/Beam position/position tunnel y
	1604	)))\|(((
	1605	/FL1/Photon Diagnostic/GMD/Beam position/position tunnel vertical
	1606	)))
	1607	\|(((
	1608	/Experiment/Pump probe laser/BPM/position x
	1609	)))\|(((
	1610	/FL1/Experiment/Pump probe laser/BPM/position horizontal
	1611	)))
	1612	\|(((
	1613	/Experiment/Pump probe laser/BPM/position y
	1614	)))\|(((
	1615	/FL1/Experiment/Pump probe laser/BPM/position vertical
	1616	)))
	1617	\|(((
	1618	/FL2/Photon Diagnostic/GMD/Beam position/Average/position hall horizontal
	1619	)))\|(((
	1620	/FL2/Photon Diagnostic/GMD/Average beam position/position hall horizontal
	1621	)))
	1622	\|(((
	1623	/FL2/Photon Diagnostic/GMD/Beam position/Average/position hall vertical
	1624	)))\|(((
	1625	/FL2/Photon Diagnostic/GMD/Average beam position/position hall vertical
	1626	)))
	1627	\|(((
	1628	/FL2/Photon Diagnostic/GMD/Beam position/Average/position tunnel horizontal
	1629	)))\|(((
	1630	/FL2/Photon Diagnostic/GMD/Average beam position/position tunnel horizontal
	1631	)))
	1632	\|(((
	1633	/FL2/Photon Diagnostic/GMD/Beam position/Average/position tunnel vertical
	1634	)))\|(((
	1635	/FL2/Photon Diagnostic/GMD/Average beam position/position tunnel vertical
	1636	)))
	1637	\|(((
	1638	/FL2/Photon Diagnostic/GMD/Average energy/hall
	1639	)))\|(((
	1640	/FL2/Photon Diagnostic/GMD/Average energy/energy hall
	1641	)))
	1642	\|(((
	1643	/FL2/Photon Diagnostic/GMD/Average energy/hall (raw)
	1644	)))\|(((
	1645	/FL2/Photon Diagnostic/GMD/Average energy/energy hall (raw)
	1646	)))
	1647	\|(((
	1648	/FL2/Photon Diagnostic/GMD/Average energy/tunnel
	1649	)))\|(((
	1650	/FL2/Photon Diagnostic/GMD/Average energy/energy tunnel
	1651	)))
	1652	\|(((
	1653	/FL2/Photon Diagnostic/GMD/Average energy/tunnel (raw)
	1654	)))\|(((
	1655	/FL2/Photon Diagnostic/GMD/Average energy/energy tunnel (raw)
	1656	)))
	1657	\|(((
	1658	/FL2/Photon Diagnostic/GMD/Beam position/Pulse resolved/hall x
	1659	)))\|(((
	1660	/FL2/Photon Diagnostic/GMD/Pulse resolved beam position/position hall horizontal
	1661	)))
	1662	\|(((
	1663	/FL2/Photon Diagnostic/GMD/Beam position/Pulse resolved/hall y
	1664	)))\|(((
	1665	/FL2/Photon Diagnostic/GMD/Pulse resolved beam position/position hall vertical
	1666	)))
	1667	\|(((
	1668	/FL2/Photon Diagnostic/GMD/Beam position/Pulse resolved/tunnel x
	1669	)))\|(((
	1670	/FL2/Photon Diagnostic/GMD/Pulse resolved beam position/position tunnel horizontal
	1671	)))
	1672	\|(((
	1673	/FL2/Photon Diagnostic/GMD/Beam position/Pulse resolved/tunnel y
	1674	)))\|(((
	1675	/FL2/Photon Diagnostic/GMD/Pulse resolved beam position/position tunnel vertical
	1676	)))
	1677
4.1	1678	[[Contents>>doc:\|\|anchor="Contents"]]
1.1	1679
79.1	1680
44.1	1681	{{/layout-cell}}
	1682	{{/layout-section}}
	1683	{{/layout}}

Wiki source code of The FLASH HDF5 structure

Applications

Navigation