Skip to Content

Changes for page The FLASH HDF5 structure

Last modified by sndueste on 2025-11-19 14:51
From version 104.1
edited by sndueste
on 2025-11-19 14:51
Change comment: There is no comment for this version
To version 80.1
edited by sndueste
on 2024-04-30 14:08
Change comment: There is no comment for this version

Summary

Details

Page properties
Parent
... ... @@ -1,1 +1,0 @@
1 -FLASHUSER.Offline data analysis (DAQ).WebHome
Content
... ... @@ -1,3 +1,6 @@
1 +{{layout}}
2 +{{layout-section ac:type="single"}}
3 +{{layout-cell}}
1 1  == Contents ==
2 2  
3 3  
... ... @@ -7,9 +7,9 @@
7 7  
8 8  == General information about HDF5 ==
9 9  
10 -HDF5 is a data format maintained by the HDF group. For detailed general information see [[here>>url:https://portal.hdfgroup.org/display/support||shape="rect"]]
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"]]
11 11  
12 -To download the HDF5 Viewer click [[here>>url:https://portal.hdfgroup.org/display/support/Download+HDFView||shape="rect"]]
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"]]
13 13  
14 14  For use on the DESY Maxwell or PAL (max-fsc or pal) **hdfview** is available in the xray module :
15 15  {{code language="none"}}> module load xray{{/code}}
... ... @@ -58,17 +58,25 @@
58 58  {{/expand}}
59 59  
60 60  === HDF examples: ===
64 +{{/layout-cell}}
65 +{{/layout-section}}
61 61  
67 +{{layout-section ac:type="three_equal"}}
68 +{{layout-cell}}
62 62  * ADC data as example for **fast** **data** (10 Hz):            
63 63  
64 64  [[image:attach:image2020-11-16_15-26-28.png||height="250"]]
72 +{{/layout-cell}}
65 65  
74 +{{layout-cell}}
66 66  * 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}})
67 67  
68 68   ( as example only every 10th train ID is listed in the HDF group "index")
69 69  
70 70  [[image:attach:image2020-11-16_15-31-45.png||height="250"]]
80 +{{/layout-cell}}
71 71  
82 +{{layout-cell}}
72 72  * (((
73 73  //zraw// group contains the **original DAQ (DOOCS) names**
74 74  )))
... ... @@ -77,7 +77,11 @@
77 77  
78 78  
79 79  [[image:attach:image2020-11-16_16-26-3.png||height="400"]]
91 +{{/layout-cell}}
92 +{{/layout-section}}
80 80  
94 +{{layout-section ac:type="single"}}
95 +{{layout-cell}}
81 81  {{info}}
82 82  === There are different options that help you to work with the FLASH HDF5 data in Python ===
83 83  
... ... @@ -84,30 +84,31 @@
84 84  * The currently developed option for large data sets: [[the FAB package>>url:https://hasfcpkg.desy.de/fab/fab.html||shape="rect"]] ... see below
85 85  * 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"]]
86 86  
87 -(% class="Object" %)See also the collection of Demo data and sample scripts : [[Collection of HDF5 sample data from different beamlines>>doc:FLASHUSER.Offline data analysis (DAQ).Collection of HDF5 sample data from different beamlines.WebHome]] and [[DEMO - Working with FLASH data>>doc:FLASHUSER.Offline data analysis (DAQ).DEMO - Working with FLASH data.WebHome]]
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]]
88 88  {{/info}}
104 +{{/layout-cell}}
105 +{{/layout-section}}
89 89  
107 +{{layout-section ac:type="single"}}
108 +{{layout-cell}}
109 +
90 90  
91 -
92 92  == Complete list of recordable parameters ==
93 93  
94 -The complete list for the relation between DOOCS names and HDF5 names for the recordable parameters can be found in [[DESY's Repository>>url:https://stash.desy.de/projects/CS/repos/pah/browse/src/camp/data/channel2HdfName.dat||shape="rect"]].
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 +
95 95  
96 -== Most popular FLASH parameters and their names in HDF5, DOOCS and (.raw) DAQ ==
116 +== Most popular FLASH parameters and their names in HDF5, DOOCS and (raw) DAQ ==
97 97  
98 98  {{id name="DOOCSparameters"/}}
99 99  
120 +Note, the HDF group and data set names apply to our HDF tree version since vers. 0.3.0.
100 100  
122 +
101 101  === FLASH1 ===
102 102  
125 +==== Beamline info (FLASH1) ====
103 103  
104 -In the Shutdown 2024 / 2025  the complete photon diagnostic and experiment control was renewed and thus the Doocs names and also some HDF5 names had to be changed. The new naming will be documented here as soon as the systems are online again.
105 -
106 -The previously used naming scheme (2024 and before) can be found here:
107 -
108 -{{expand expanded="false" title="FLASH1 naming scheme used until 2024"}}
109 -==== (% id="cke_bm_8853497S" style="display:none" %) (%%)Beamline info (FLASH1) ====
110 -
111 111  {{code language="none"}}/FL1/Beamlines/Attenuator/pressure{{/code}}
112 112  //always saved (PBD)//
113 113  DOOCS prop : {{code language="none"}}FLASH.FEL/GAS_DOSING/FL1.ATTENUATOR/PRESSURE{{/code}}
... ... @@ -114,6 +114,7 @@
114 114  DAQ channel: {{code language="none"}}FLASH.FEL/GAS_DOSING/FL1.ATTENUATOR/PRESSURE{{/code}}
115 115  desc: set pressure in the gas attenuator
116 116  units: mbar
133 +
117 117  
118 118  {{code language="none"}}/FL1/Beamlines/BL/Fast shutter/open{{/code}}
119 119  //always saved (PBD)//
... ... @@ -133,15 +133,17 @@
133 133  //always saved (PBD)//
134 134  DOOCS prop : {{code language="none"}}TTF2.FEL/BLFILTERS1/FILTER1/FW.MOTOR.POS{{/code}}
135 135  DAQ channel: {{code language="none"}}TTF2.FEL/BLFILTERS1/FILTER1/FW.MOTOR.POS{{/code}}
136 -desc: Position of the BL filter wheel 1 - to correlate with the filter material please look [[here>>doc:FS-FLASH USER tmp.jddd-linked help pages.Filter-Units.Filter wheels in FLASH1 and FLASH2.WebHome]]
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]]
137 137  units: degree
155 +
138 138  
139 139  {{code language="none"}}/FL1/Beamlines/BL/Filters/BL filter wheel/position filter 2{{/code}}
140 140  //always saved (PBD)//
141 141  DOOCS prop : {{code language="none"}}TTF2.FEL/BLFILTERS2/FILTER2/FW.MOTOR.POS{{/code}}
142 142  DAQ channel: {{code language="none"}}TTF2.FEL/BLFILTERS2/FILTER2/FW.MOTOR.POS{{/code}}
143 -desc: Position of the BL filter wheel 2 - to correlate with the filter material please look [[here>>doc:FS-FLASH USER tmp.jddd-linked help pages.Filter-Units.Filter wheels in FLASH1 and FLASH2.WebHome]]
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]]
144 144  units: degree
163 +
145 145  
146 146  {{code language="none"}}/FL1/Beamlines/PG/Filters/position filter 1{{/code}}
147 147  //always saved (PBD)//
... ... @@ -149,6 +149,7 @@
149 149  DAQ channel: {{code language="none"}}TTF2.FEL/BDAF1/BDA.F1/FW.MOTOR.POS{{/code}}
150 150  desc: Position of the PG filter wheel 1
151 151  units: degree
171 +
152 152  
153 153  {{code language="none"}}/FL1/Beamlines/PG/Filters/position filter 2{{/code}}
154 154  //always saved (PBD)//
... ... @@ -156,6 +156,7 @@
156 156  DAQ channel: {{code language="none"}}TTF2.FEL/BDAF2/BDA.F2/FW.MOTOR.POS{{/code}}
157 157  desc: Position of the PG filter wheel 2
158 158  units: degree
179 +
159 159  
160 160  {{code language="none"}}/FL1/Beamlines/PG/Filters/position filter 3{{/code}}
161 161  //always saved (PBD)//
... ... @@ -190,7 +190,7 @@
190 190  DOOCS prop : {{code language="none"}}TTF2.DAQ/PHFLUX/OUT34/VAL{{/code}}
191 191  DAQ channel: {{code language="none"}}PBD.PHFLUX/TUNNEL.ENERGYPULSE.USER{{/code}}
192 192  desc :Energy per pulse Tunnel (from e-) - the values are set to "0" if there was no SASE beam in the FEL
193 -units : a.u. (more or less µJ but need to be calibrated with the "Average energy" for good precision) **[[see here for help>>doc:FS-FLASH USER tmp.jddd-linked help pages.Calibrating the pulse resolved (electron) data from GMD.WebHome]]**
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]]**
194 194  
195 195  {{code language="none"}}/FL1/Photon Diagnostic/GMD/Pulse resolved energy/energy tunnel (raw){{/code}}
196 196  //always saved (PBD)//
... ... @@ -197,7 +197,7 @@
197 197  DOOCS prop : {{code language="none"}}TTF2.DAQ/PHFLUX/OUT14/VAL{{/code}}
198 198  DAQ channel: {{code language="none"}}PBD.PHFLUX/TUNNEL.ENERGYPULSE.FF{{/code}}
199 199  desc :Energy per pulse Tunnel (from e-) - uncorrected values. There are also values saved if there was no beam ... just background noise
200 -units : a.u. (more or less µJ but need to be calibrated with the "Average energy" for good precision) **[[see here for help>>doc:FS-FLASH USER tmp.jddd-linked help pages.Calibrating the pulse resolved (electron) data from GMD.WebHome]]**
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]]**
201 201  
202 202  {{code language="none"}}/FL1/Photon Diagnostic/GMD/Average energy/energy BDA{{/code}}
203 203  //always saved (PBD)//
... ... @@ -213,7 +213,7 @@
213 213  DOOCS prop : {{code language="none"}}TTF2.DAQ/PHFLUX/OUT35/VAL{{/code}}
214 214  DAQ channel: {{code language="none"}}PBD.PHFLUX/BDA.ENERGYPULSE.USER{{/code}}
215 215  desc :Energy per pulse BDA (from e-) - the values are set to "0" if there was no SASE beam in the FEL
216 -units : a.u. (more or less µJ but need to be calibrated with the "Average energy" for good precision) **[[see here for help>>doc:FS-FLASH USER tmp.jddd-linked help pages.Calibrating the pulse resolved (electron) data from GMD.WebHome]]**
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]]**
217 217  
218 218  {{code language="none"}}/FL1/Photon Diagnostic/GMD/Pulse resolved energy/energy BDA (raw){{/code}}
219 219  //always saved (PBD)//
... ... @@ -220,7 +220,7 @@
220 220  DOOCS prop : {{code language="none"}}TTF2.DAQ/PHFLUX/OUT15/VAL{{/code}}
221 221  DAQ channel: {{code language="none"}}PBD.PHFLUX/BDA.ENERGYPULSE.FF{{/code}}
222 222  desc :Energy per pulse BDA (from e-) - uncorrected values. There are also values saved if there was no beam ... just background noise
223 -units : a.u. (more or less µJ but need to be calibrated with the "Average energy" for good precision)** [[see here for help>>doc:FS-FLASH USER tmp.jddd-linked help pages.Calibrating the pulse resolved (electron) data from GMD.WebHome]]**
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]]**
224 224  {{/expand}}
225 225  
226 226  
... ... @@ -228,8 +228,8 @@
228 228  
229 229  {{code language="none"}}/FL1/Photon Diagnostic/GMD/Average energy/energy tunnel{{/code}}
230 230  //always saved (PBD)//
231 -(% style="color:#000000" %)DOOCS prop : {{code language="none"}}FLASH.FEL/XGM.PHOTONFLUX/FL1.TUNNEL/PHOTONFLUX.UJ{{/code}} (%%)
232 -(% style="color:#000000" %)DAQ channel: {{code language="none"}}FLASH.FEL/XGM.PHOTONFLUX/FL1.TUNNEL/PHOTONFLUX.UJ{{/code}}
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}}
233 233  
234 234  desc : calibrated average SASE Energy/pulse measured in the TUNNEL upstream the gas attenuator
235 235  units : microJ
... ... @@ -238,14 +238,15 @@
238 238  {{code language="none"}}/FL1/Photon Diagnostic/GMD/Pulse resolved energy/energy tunnel{{/code}}
239 239  //always saved (PBD)//
240 240  
241 -(% style="color:#000000" %)DOOCS prop : (%%)
242 -(% style="color:#000000" %){{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}}
262 +(% style="color:#000000" %)DOOCS prop : 
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}}
243 243  
244 244  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)
245 -units : a.u. (more or less µJ but need to be calibrated with the "Average energy" for good precision)** [[see here for help>>doc:FS-FLASH USER tmp.jddd-linked help pages.Calibrating the pulse resolved (electron) data from GMD.WebHome]]**
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]]**
246 246  
247 247  {{info title="GMD pulse resolved data structure"}}
248 248  For every pulse in the pulse train the information is saved:
270 +
249 249  
250 250  1. **Intensity per pulse** (a.u. (more or less µJ ))
251 251  1. Intensity per pulse (auxillary GMD) - not used
... ... @@ -259,7 +259,8 @@
259 259  The pulse energy and the error are plotted for the first bunch of the pulse trains saved in this 
260 260  file
261 261  
262 - [[image:image2021-2-9_10-51-6.png]]
284 +
285 +[[image:attach:image2021-2-9_10-51-6.png||height="250"]]
263 263  
264 264  
265 265  {{/info}}
... ... @@ -379,8 +379,8 @@
379 379  =====
380 380  arrival time (BAM) =====
381 381  
382 -{{info title="BAM information: updates 2022 (status 2025)"}}
383 -* see: [[Info collection about the BAMs and how to use the BAM data>>doc:FS-FLASH USER tmp.jddd-linked help pages.Info collection for the BAM.WebHome||shape="rect"]]
405 +{{info title="BAM information: updates 2022"}}
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"]]
384 384  * The data format of the BAM has been completely altered in the 2022 shutdown
385 385  * 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 ...
386 386  * 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)
... ... @@ -388,8 +388,8 @@
388 388  ** acc:  4DBC3 → FL0.DBC2
389 389  ** FL1: 1SFELC →  FL1.SFELC
390 390  ** FL2: FL2XTDS → (% style="color:#172b4d" %)FL2.SEED5
391 -* for more Info: [[LINK to detailed infos from MSK>>doc:SDiag.How-to articles.BAM Data Structure.WebHome||shape="rect"]]
392 -* [[Link a collection of papers related to the BAM and the analysis of pump-probe experiments>>doc:FS-FLASH USER tmp.Additional helpful things1.FLASH beamlines and instruments references.WebHome]]
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]]
393 393  * a recent  [[talk about the working principle of the BAM>>attach:BAM-basics and outlook-2018_DESY-template_16-9Format.pdf]]
394 394  {{/info}}
395 395  
... ... @@ -433,9 +433,9 @@
433 433  
434 434  (% style="color:#ff6600" %)DBC2/error (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL1/Electron Diagnostic/BAM/{{/code}}(%%)
435 435  //always saved (PBD)//
436 -DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIM(% style="color:#000000" %)E.bamError.1(%%)
437 -DAQ channel: (% style="color:#000000" %)FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.BAMERROR.1(%%)
438 -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
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(%%)
461 +desc: If the value is 0 , the BAM is working well. If it is non-zero there is a problem !!
439 439  
440 440  
441 441  (% style="color:#ff6600" %)DBC2/status  (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL1/Electron Diagnostic/BAM/{{/code}}(%%)
... ... @@ -451,8 +451,8 @@
451 451  
452 452  //always saved (PBD)//
453 453  (% style="color:#172b4d" %)**FL1.SFELC**(%%)
454 -(% style="color:#000000" %)channel: FLASH.SDIAG/BAM/(% style="color:#172b4d" %)FL1.SFELC(% style="color:#000000" %)/ARRIVAL_TIME.ABSOLUTE.SA1.COMP(%%)
455 -(% style="color:#000000" %){{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).
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).
456 456  units: fs (bigger numbers (typically) indicate later arrival times of the electrons).
457 457  
458 458  
... ... @@ -488,6 +488,7 @@
488 488  DAQ channel: {{code language="none"}}PBD.BEAM.PROF.ML/DAQ.OUT.PROF.CCCED{{/code}}
489 489  desc: temporal profile of electron bunch, y axis in Ampers (FLASH1)
490 490  units: pixel
514 +
491 491  
492 492  {{code language="none"}}/FL1/Electron Diagnostic/Electron bunch profile/Expert stuff/TDS calibration constant{{/code}}
493 493  //always saved (PBD) - IF LOLA is ON and ACTIVATED in the PBD DAQ (talk to expert)//
... ... @@ -495,6 +495,7 @@
495 495  DAQ channel: = PBD.BEAM.PROF.ML/CCT=
496 496  desc: TDS calibration constant for the x-axis of the profiles: fs per pixel
497 497  units: fs per pixel
522 +
498 498  
499 499  {{code language="none"}}/FL1/Electron Diagnostic/Electron bunch profile/TDS profile width rms{{/code}}
500 500  //always saved (PBD) - IF LOLA is ON and ACTIVATED in the PBD DAQ (talk to expert)//
... ... @@ -510,7 +510,8 @@
510 510  DOOCS prop : {{code language="none"}}TTF2.DAQ/ENERGY.DOGLEG/E_INTRA_MEAN/VAL{{/code}}
511 511  DAQ channel: {{code language="none"}}PBD.ENERGY.DOGLEG/E_MEAN{{/code}}
512 512  desc: electron bunch energy (average over the bunch train)
513 -units: (% class="twikiNewLink" %)MeV
538 +units: (% class="twikiNewLink" %)MeV(%%)
539 +
514 514  
515 515  {{code language="none"}}/FL1/Electron Diagnostic/Electron energy/pulse resolved energy{{/code}}
516 516  //always saved (PBD)//
... ... @@ -526,27 +526,26 @@
526 526  DAQ channel: {{code language="none"}}PBD.ENERGY.DOGLEG/LAMBDA_MEAN{{/code}}
527 527  desc: Wavelength calculated by the electron bunch energy (average over the bunch train) (FLASH1)
528 528  units: nm
555 +
529 529  
530 530  [[Contents>>doc:||anchor="Contents"]]
531 531  
532 532  
533 -==== ====
534 -
535 -
536 536  ==== Timing information, rep rate etc.  (FLASH1) ====
537 537  
538 538  ===== bunch repetition rate =====
539 539  
540 -{{code language="none"}}/Timing/repetition rate{{/code}}
564 +{{code language="none"}}/FL1/Timing/repetition rate{{/code}}
541 541  //always saved (PBD)//
542 542  DOOCS prop : {{code language="none"}}FLASH.DIAG/TIMER/FLASHCPUTIME1.0/REP_RATE_KHZ.1{{/code}}
543 -DAQ channel: {{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}}
544 544  desc: repetition rate of the bunches / pulses within the burst (FLASH1)
545 545  units: kHz
570 +
546 546  
547 547  ===== set number of pulses =====
548 548  
549 -(% style="color:#ff6600" %)(HDF5 name not yet implemented - see zraw)(% style="color:#ff0000" %){{code language="none"}}/Timing/set number of bunches {{/code}}(%%)
574 +(% style="color:#ff6600" %)(HDF5 name not yet implemented - see zraw)(% style="color:#ff0000" %){{code language="none"}}/FL1/Timing/set number of bunches {{/code}}(%%)
550 550  //always saved (PBD)//
551 551  DOOCS prop : {{code language="none"}}FLASH.DIAG/TIMINGINFO/TIME1.BUNCH_FIRST_INDEX.1 [4th number]{{/code}}
552 552  DAQ channel: {{code language="none"}}FLASH.DIAG/TIMINGINFO/TIME1.BUNCH_FIRST_INDEX.1 [4th number]{{/code}}
... ... @@ -561,6 +561,7 @@
561 561  DAQ channel: {{code language="none"}}TTF2.DIAG/PBD.TOROID.ML/12EXP{{/code}}
562 562  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)
563 563  units:
589 +
564 564  
565 565  ===== actual pulse pattern recorded after the undulator =====
566 566  
... ... @@ -570,6 +570,7 @@
570 570  DAQ channel: {{code language="none"}}TTF2.DIAG/PBD.TOROID.ML/12EXP{{/code}}
571 571  desc: The bunch pattern as function of time in a burst recorded by toroid diagnostic BEHIND the undulator. (FLASH1)
572 572  units:
599 +
573 573  
574 574  ===== Train ID =====
575 575  
... ... @@ -579,34 +579,24 @@
579 579  DAQ channel: {{code language="none"}}none{{/code}}
580 580  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 !)
581 581  units:
609 +
582 582  
583 -===== (% style="color:#e67e22" %)Train time(%%) =====
611 +===== Train time =====
584 584  
585 -(% style="color:#e67e22" %){{code language="none"}}/Timing/train time{{/code}}
613 +{{code language="none"}}/Timing/train time{{/code}}
586 586  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
587 587  units: d h min s cs
616 +
588 588  
589 -(% style="color:#e67e22" %){{code language="none"}}/Timing/time stamp{{/code}}
618 +{{code language="none"}}/Timing/time stamp{{/code}}
590 590  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
591 591  second column: microseconds
592 592  third column: Train ID of FLASH
622 +
593 593  
594 -currently it is saved as Unix time in : /zraw/FLASH.DIAG/TIMINGINFO/TIME1.BUNCH_FIRST_INDEX.1/dGroup/time
624 +[[Contents>>doc:||anchor="Contents"]]
595 595  
596 -{{expand expanded="false" title="Timestamp help for python"}}
597 - import time
598 598  
599 -# epoch time is found in /zraw/FLASH.DIAG/TIMINGINFO/TIME1.BUNCH_FIRST_INDEX.1/dGroup/time #!!! a leading 1 has to be added !!!
600 -# The time and date of the start of the data taking in the HDF file is encoded in the filename - to roughly check the time
601 -epoch_time = 1709051499.17 # Replace with your epoch time
602 -
603 -formatted_time = time.strftime('%Y-%m-%d %H:%M:%S', time.gmtime(epoch_time))
604 -print(formatted_time)
605 -{{/expand}}
606 -
607 -
608 -
609 -
610 610  ==== Pump Probe Laser (FLASH1) ====
611 611  
612 612  **PIGLET (PG laser)**
... ... @@ -613,15 +613,10 @@
613 613  
614 614  **{{code language="none"}}/FL1/Experiment/Pump probe laser{{/code}}**
615 615  
616 -{{info width="30%"}}
633 +{{info}}
617 617  list of saved parameters status May 2024 (up to now the parameters can be found in /zraw/ ... )
618 618  
619 -Download the PDF:
620 -
621 -{{view-file att--filename="FSLADAQ-DAQParameterlistPiGLET.pdf"}}{{/view-file}}
622 -
623 -
624 -
636 +[[attach:FSLADAQ-DAQParameterlistPiGLET.pdf||target="_blank"]]
625 625  {{/info}}
626 626  
627 627  {{expand title="Parameters used until 2021"}}
... ... @@ -680,7 +680,7 @@
680 680  
681 681  ===== GHz ADCs =====
682 682  
683 -ADC traces of the (SPDevices 412) GHZ ADCs available for the users . More information about the ADCs can be found** [[here>>doc:FS-FLASH USER tmp.Data Acquisition and controls 1.Controls (DOOCS, jDDD,\.\.\.).MTCA ADCs.WebHome]]**
695 +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]]**
684 684  //saved on DEMAND in the user DAQ//
685 685  \\The HDF5 names for the ADC traces are depending on the beamline :
686 686  \\PG Beamline:
... ... @@ -722,9 +722,10 @@
722 722  * {{code language="none"}}number of samples{{/code}}: total number of samples recorded for each 10 Hz trigger
723 723  
724 724  [[Contents>>doc:||anchor="Contents"]]
725 -{{/expand}}
726 726  
727 727  
739 +
740 +
728 728  === FLASH2 ===
729 729  
730 730  There is analog to FLASH1 a permanently running "PhotonDagnostic DAQ FLASH2" (PBD2) and 2 User DAQs
... ... @@ -732,12 +732,15 @@
732 732  ==== Beamline info (FLASH2) ====
733 733  
734 734  {{code language="none"}}/FL2/Beamlines/Attenuator/pressure  {{/code}}
748 +(% style="color:#000000" %)//always saved (PBD2)// (%%)
735 735  (% style="color:#000000" %)DOOCS prop : {{code language="none"}}FLASH.FEL/ATT.GAS_DOSING/FL2.HALL/PRESSURE{{/code}} (%%)
736 736  (% style="color:#000000" %)DAQ channel:  {{code language="none"}}FLASH.FEL/ATT.GAS_DOSING/FL2.HALL/PRESSURE{{/code}} (%%)
737 737  (% style="color:#000000" %)desc: set pressure in the gas attenuator (%%)
738 -(% style="color:#000000" %)units: mbar
752 +(% style="color:#000000" %)units: mbar(%%)
753 +
739 739  
740 740  {{code language="none"}}/FL2/Beamlines/FL20/Shutter/open{{/code}}
756 +//always saved (PBD2)//
741 741  DOOCS prop : {{code language="none"}}FLASH.FEL/ADC.SIS.FL2FS/FL20.SHUTTER/CH00.TD{{/code}}
742 742  DAQ channel: {{code language="none"}}FLASH.FEL/ADC.SIS.FL2FS/FL20.SHUTTER{{/code}}
743 743  desc: BL Beamline Fast shutter state: 1 is open, 0 is closed ( for technical reasons there are 100 vales of this state saved ...)
... ... @@ -745,15 +745,18 @@
745 745  
746 746  
747 747  {{code language="none"}}/FL2/Beamlines/Filter wheel/position wheel 1{{/code}}
764 +//always saved (PBD2)//
748 748  DOOCS prop : {{code language="none"}}FLASH.FEL/FL20H.PH.MOTOR/MOTOR1.MOT3/FPOS{{/code}}
749 749  DAQ channel: FLASH.FEL/FL20H.PH.MOTOR/MOTOR1.MOT3/FPOS
750 -desc: Position of the BL filter wheel 1 - to correlate with the filter material please look **[[here>>doc:FS-FLASH USER tmp.jddd-linked help pages.Filter-Units.Filter wheels in FLASH1 and FLASH2.WebHome]]**
767 +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]]**
751 751  units: degree
769 +
752 752  
753 753  /FL2/Beamlines/Filter wheel/position wheel 2
772 +always saved (PBD2)
754 754  DOOCS prop : {{code language="none"}}FLASH.FEL/FL20H.PH.MOTOR/MOTOR2.MOT3/FPOS{{/code}}
755 755  DAQ channel: {{code language="none"}}FLASH.FEL/FL20H.PH.MOTOR/MOTOR2.MOT3/FPOS{{/code}}
756 -desc: Position of the BL filter wheel 2 - to correlate with the filter material please look [[here>>doc:FS-FLASH USER tmp.jddd-linked help pages.Filter-Units.Filter wheels in FLASH1 and FLASH2.WebHome]]
775 +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]]
757 757  units: degree
758 758  
759 759  
... ... @@ -766,6 +766,7 @@
766 766  ==== Photon Diagnostics SASE ([[XGMD>>url:http://photon-science.desy.de/facilities/flash/photon_diagnostics/gmd_intensity_and_position/index_eng.html||shape="rect"]] - FLASH2) ====
767 767  
768 768  {{code language="none"}}/FL2/Photon Diagnostic/GMD/Average energy/energy tunnel{{/code}}
788 +//always saved (PBD2)//
769 769  DOOCS prop : {{code language="none"}}FLASH.FEL/XGM.PHOTONFLUX/FL2.TUNNEL/PHOTONFLUX.UJ{{/code}}
770 770  DAQ channel:{{code language="none"}} FLASH.FEL/XGM.PHOTONFLUX/FL2.TUNNEL/PHOTONFLUX.UJ{{/code}}
771 771  desc : calibrated average ( ~~ 20 sec averaging time ) SASE Energy/pulse measured in the TUNNEL before the attenuator (ion current)
... ... @@ -773,13 +773,15 @@
773 773  
774 774  
775 775  {{code language="none"}}/FL2/Photon Diagnostic/GMD/Pulse resolved energy/energy tunnel{{/code}}
796 +//always saved (PBD2)//
776 776  DOOCS prop : {{code language="none"}}FLASH.FEL/XGM.INTENSITY/FL2.TUNNEL/INTENSITY.TD{{/code}}
777 777  DAQ channel: {{code language="none"}}FLASH.FEL/XGM.INTENSITY/FL2.TUNNEL/INTENSITY.TD{{/code}}
778 778  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)
779 -units : a.u. (more or less µJ but need to be calibrated with the "Average energy" for good precision)** [[see here for help>>doc:FS-FLASH USER tmp.jddd-linked help pages.Calibrating the pulse resolved (electron) data from GMD.WebHome]]**
800 +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]]**
780 780  
781 781  {{info title="GMD pulse resolved data structure"}}
782 782  For every pulse in the pulse train the information is saved:
804 +
783 783  
784 784  1. **Intensity per pulse** (a.u. (more or less µJ ))
785 785  1. Intensity per pulse (auxillary GMD) - not used
... ... @@ -807,6 +807,7 @@
807 807  
808 808  
809 809  {{code language="none"}}/FL2/Photon Diagnostic/GMD/Average Beam position/position tunnel horizontal{{/code}}
832 +//always saved (PBD2)//
810 810  DOOCS prop : {{code language="none"}}FLASH.FEL/XGM.POSMON/FL2.TUNNEL/IX.POS{{/code}}
811 811  DAQ channel: {{code language="none"}}FLASH.FEL/XGM.POSMON/FL2.TUNNEL/IX.POS{{/code}}
812 812  desc : the Average ( ~~ 20 sec averaging time ) Beam position of the photon Beam determined by the GMD (tunnel, x=horizontal)
... ... @@ -814,6 +814,7 @@
814 814  
815 815  
816 816  {{code language="none"}}/FL2/Photon Diagnostic/GMD/Average Beam position/position tunnel vertical{{/code}}
840 +//always saved (PBD2)//
817 817  DOOCS prop : {{code language="none"}}FLASH.FEL/XGM.POSMON/FL2.TUNNEL/IY.POS{{/code}}
818 818  DAQ channel: {{code language="none"}}FLASH.FEL/XGM.POSMON/FL2.TUNNEL/IY.POS{{/code}}
819 819  desc : the Average ( ~~ 20 sec averaging time ) Beam position of the photon Beam determined by the GMD (tunnel, x=horizontal)
... ... @@ -821,6 +821,7 @@
821 821  
822 822  
823 823  /FL2/Photon Diagnostic/GMD/Pulse resolved beam position/position tunnel x
848 +always saved (PBD2)
824 824  DOOCS prop : FLASH.FEL/XGM.BPM/FL2.HALL/X.TD
825 825  DAQ channel: FLASH.FEL/XGM.BPM/FL2.HALL:2
826 826  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 ...)
... ... @@ -840,6 +840,7 @@
840 840  
841 841  
842 842  {{code language="none"}}/FL2/Photon Diagnostic/Wavelength/OPIS tunnel/Processed/mean photon energy{{/code}}
868 +// saved opon request (PBD2)//
843 843  DOOCS prop : {{code language="none"}}FLASH.UTIL/STORE/FL2.TUNNEL.OPIS/VAL042{{/code}}
844 844  DAQ channel:{{code language="none"}} FLASH.UTIL/STORE/FL2.TUNNEL.OPIS/VAL042{{/code}}
845 845  desc : mean photon energy ( ~~ 1 sec averaging time ) measured in the TUNNEL for a specific bunch out of the bunch train (via photoelectron spectroscopy)
... ... @@ -847,6 +847,7 @@
847 847  
848 848  
849 849  {{code language="none"}}/FL2/Photon Diagnostic/Wavelength/OPIS tunnel/Processed/mean wavelength{{/code}}
876 +// saved opon request (PBD2)//
850 850  DOOCS prop : {{code language="none"}}FLASH.UTIL/STORE/FL2.TUNNEL.OPIS/VAL040{{/code}}
851 851  DAQ channel:{{code language="none"}} FLASH.UTIL/STORE/FL2.TUNNEL.OPIS/VAL040{{/code}}
852 852  desc : mean wavelength ( ~~ 1 sec averaging time ) measured in the TUNNEL for a specific bunch out of the bunch train (via photoelectron spectroscopy)
... ... @@ -854,6 +854,7 @@
854 854  
855 855  
856 856  {{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}}
884 +// saved opon request (PBD2)//
857 857  DOOCS prop : {{code language="none"}}FLASH.UTIL/STORE/FL2.TUNNEL.OPIS/VAL060{{/code}}
858 858  DAQ channel:{{code language="none"}} FLASH.UTIL/STORE/FL2.TUNNEL.OPIS/VAL060{{/code}}
859 859  desc : The bunch number of the bunch used for the wavelength calculation
... ... @@ -872,6 +872,7 @@
872 872  ===== bunch charge =====
873 873  
874 874  {{code language="none"}}/FL2/Electron Diagnostic/Bunch charge/after undulator{{/code}}
903 +//always saved (PBD2)//
875 875  DOOCS prop : {{code language="none"}}FLASH.DIAG/PBD2.TOROID.ML/9FL2BURN/CHARGE.FLASH2{{/code}}
876 876  DAQ channel: {{code language="none"}}FLASH.DIAG/PBD2.TOROID.ML/9FL2BURN/CHARGE.FLASH2{{/code}}
877 877  desc: electron bunch charge FLASH2 (average value for each bunchtrain).
... ... @@ -881,6 +881,7 @@
881 881  ===== electron bunch energy =====
882 882  
883 883  {{code language="none"}}/FL2/Electron Diagnostic/Electron energy/energy of first bunch/behind undulators{{/code}}
913 +//always saved (PBD2)//
884 884  DOOCS prop : {{code language="none"}}FLASH.DIAG/BEAM_ENERGY_MEASUREMENT/FL2XTDS/ENERGY.FLASH2{{/code}}
885 885  DAQ channel: (% style="color:#5e6c84" %)TTF2.DAQ/PBD2.BEAM.ENERGY.MEAS.ML.COPY/FL2XTDS.ENERGY.FLASH2{{code language="none"}}{{/code}}(%%)
886 886  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
... ... @@ -888,37 +888,39 @@
888 888  (% style="letter-spacing:0.0px" %)units: (% class="twikiNewLink" %)MeV
889 889  
890 890  
891 -(% style="color: rgb(94, 108, 132); font-weight: 600; letter-spacing: 0px;" %)
892 -===== undulator settings =====
921 +(% style="color: rgb(94,108,132);font-weight: 600;letter-spacing: 0.0px;" %)
922 +undulator settings
893 893  
894 -{{code language="none"}}/FL2/Electron Diagnostic/Undulator setting/set wavelength 1{{/code}}
895 -DOOCS prop : {{code language="none"}}FLASH.FEL/FL2.WAVELENGTHCONTROL/FLASH2.COLOR1/WAVELENGTH{{/code}}
896 -DAQ channel:  {{code language="none"}}FLASH.FEL/FL2.WAVELENGTHCONTROL/FLASH2.COLOR1/WAVELENGTH{{/code}}
897 -desc: Set value for the anticipated wavelength 1 . This parameter is used to set the undulator gap. It may however deviate from the actual wavelength by several % ... For 2 color operation there is also  the same parameter for COLOR 2
924 +{{code language="none"}}/FL2/Electron Diagnostic/Undulator setting/set wavelength{{/code}}
925 +//always saved (PBD2)//
926 +DOOCS prop : {{code language="none"}}TTF2.FEEDBACK/FL2.WAVELENGTHCONTROL/FLASH2/WAVELENGTH{{/code}}
927 +DAQ channel:  {{code language="none"}}TTF2.FEEDBACK/FL2.WAVELENGTHCONTROL/FLASH2/WAVELENGTH{{/code}}
928 +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 % ...
898 898  units: nm
899 899  
900 -{{code language="none"}}/FL2/Electron Diagnostic/Undulator setting/SASE13 gap{{/code}}
901 -DOOCS prop : {{code language="none"}}FLASH.UTIL/FL2.UND.MOTOR/FL2SASE13/GAP{{/code}}
902 -DAQ channel:  {{code language="none"}}FLASH.UTIL/FL2.UND.MOTOR/FL2SASE13/GAP{{/code}}
903 -desc: gap value of the undulators. This can be used to follow up how many undulators were closed and if there was a taper. 
931 +{{code language="none"}}/FL2/Electron Diagnostic/Undulator setting/SASE14 gap{{/code}}
932 +//always saved (PBD2)//
933 +DOOCS prop : {{code language="none"}}FLASH.UTIL/FL2.UND.MOTOR/FL2SASE14/GAP{{/code}}
934 +DAQ channel:  {{code language="none"}}FLASH.UTIL/FL2.UND.MOTOR/FL2SASE14/GAP{{/code}}
935 +desc: gap value of the undulators. This can be used to follow up how many undulators were closed and if there was a taper
904 904  units: mm
905 905  
906 -The gap values are saved for all 12 undulators (Nr 2 to 13). Undulator 13 is the one closest to the experimental hall.
938 +The gap values are saved for all 12 undulators (Nr 3 to 14). Undulator 14 is the one closest to the experimental hall.
907 907  
908 908  =====
909 909  arrival time (BAM) =====
910 910  
911 -{{info title="BAM information: updates 2022 (status 2025)"}}
912 -* see: [[Info collection about the BAMs and how to use the BAM data>>doc:FS-FLASH USER tmp.jddd-linked help pages.Info collection for the BAM.WebHome||shape="rect"]]
943 +{{info title="BAM information: updates 2022"}}
944 +* 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"]]
913 913  * The data format of the BAM has been completely altered in the 2022 shutdown
914 -* 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 ...
946 +* 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 ...
915 915  * 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)
916 916  * There has been also a renaming  (and relocation) of the BAMs.
917 917  ** acc:  4DBC3 → FL0.DBC2
918 918  ** FL1: 1SFELC →  FL1.SFELC
919 -** FL2: FL2XTDS → (% style="color:#172b4d" %)FL2.SEED5
920 -* for more Info: [[LINK to detailed infos from MSK>>doc:SDiag.How-to articles.BAM Data Structure.WebHome||shape="rect"]]
921 -* [[Link a collection of papers related to the BAM and the analysis of pump-probe experiments>>doc:FS-FLASH USER tmp.Additional helpful things1.FLASH beamlines and instruments references.WebHome]]
951 +** FL2: 8FL2XTDS → (% style="color:#172b4d" %)FL2.SEED5
952 +* for more Info: [[LINK to detailed infos from MSK>>url:https://confluence.desy.de/display/SDiagPublic/BAM+Data+Structure||shape="rect"]]
953 +* [[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]]
922 922  * a recent  [[talk about the working principle of the BAM>>attach:BAM-basics and outlook-2018_DESY-template_16-9Format.pdf]]
923 923  {{/info}}
924 924  
... ... @@ -943,7 +943,7 @@
943 943  * The BAM 4DBC3 measures the arrivaltime of** FLASH 1 and FLASH2** in the same data set (thus also sorted in at /FL1/ !).
944 944  * 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 
945 945  ** 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
946 -* [[Link a collection of papers related to the BAM and the analysis of pump-probe experiments >>doc:FS-FLASH USER tmp.Additional helpful things1.FLASH beamlines and instruments references.WebHome]]
978 +* [[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]]
947 947  * [[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"]]
948 948  * a recent  [[talk about the working principle of the BAM>>attach:BAM-basics and outlook-2018_DESY-template_16-9Format.pdf]]
949 949  {{/info}}
... ... @@ -975,20 +975,20 @@
975 975  units: fs (bigger numbers (typically) indicate later arrival times of the electrons).
976 976  
977 977  
978 -DBC2/error (% style="color:#f39c12" %)(HDF5 name not yet implemented - see zraw)(%%)/FL2/Electron Diagnostic/BAM/
1010 +(% style="color:#ff6600" %)DBC2/error (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL2/Electron Diagnostic/BAM/{{/code}}(%%)
979 979  //always saved (PBD)//
980 -DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.bamError.2
981 -DAQ channel: FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.BAMERROR.2
982 -desc: If the value is 0 , the BAM is working well. If it is non-zero there is a problem !!
1012 +(% style="color:#000000" %)E.bamError{{code language="none"}}DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIM{{/code}}(%%)
1013 +(% style="color:#000000" %)FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.BAMERROR{{code language="none"}}DAQ channel: {{/code}}(%%)
1014 +desc: If the value is 0 , the BAM is working well. If it is non-zero there is a problem !!
983 983  
984 -DBC2/status  (% style="color:#e67e22" %)(HDF5 name not yet implemented - see zraw)(%%)/FL2/Electron Diagnostic/BAM/
1016 +
1017 +(% style="color:#ff6600" %)DBC2/status  (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL2/Electron Diagnostic/BAM/{{/code}}(%%)
985 985  //always saved (PBD)//
986 -DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.bamStatus.//2//
987 -DAQ channel: FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.BAMSTATUS.2
988 -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
1019 +(% style="color:#000000" %)E..bamStatus.//2//{{code language="none"}}DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIM{{/code}}(%%)
1020 +(% style="color:#000000" %): FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.BAMSTATUS.2{{code language="none"}}DAQ channel{{/code}}(%%)
1021 +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
989 989  
990 990  
991 -
992 992  ====== **BAM FL2.SEED5**{{code language="none"}}{{/code}} ======
993 993  
994 994  /FL2/Electron Diagnostic/BAM/**SEED5**(% style="color:#ff6600" %)/electron bunch arrival time  (HDF5 name not yet implemented - see zraw)
... ... @@ -1013,17 +1013,18 @@
1013 1013  units: fs (bigger numbers (typically) indicate later arrival times of the electrons).
1014 1014  
1015 1015  
1016 -FL2.SEED5/error (% style="color:#f39c12" %)(HDF5 name not yet implemented - see zraw)(%%)/FL2/Electron Diagnostic/BAM/
1048 +(% style="color:#172b4d" %)SEED5(% style="color:#ff6600" %)/error (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL2/Electron Diagnostic/BAM/{{/code}}(%%)
1017 1017  //always saved (PBD)//
1018 -DOOCS prop : FLASH.SDIAG/BAM/FL2.SEED5/ARRIVAL_TIME.bamError.2
1019 -DAQ channel: FLASH.SDIAG/BAM/FL2.SEED5/ARRIVAL_TIME.BAMERROR.2
1020 -desc: If the value is 0 , the BAM is working well. If it is non-zero there is a problem !!
1050 +(% style="color:#172b4d" %)**FL2.SEED5**(% style="color:#000000" %)E.bamError{{code language="none"}}DOOCS prop : FLASH.SDIAG/BAM//ARRIVAL_TIM{{/code}}(%%)
1051 +(% style="color:#000000" %): FLASH.SDIAG/BAM/(% style="color:#172b4d" %)**FL2.SEED5**(% style="color:#000000" %)/ARRIVAL_TIME.BAMERROR{{code language="none"}}DAQ channel{{/code}}(%%)
1052 +desc: If the value is 0 , the BAM is working well. If it is non-zero there is a problem !!
1021 1021  
1022 -FL2.SEED5/status  (% style="color:#e67e22" %)(HDF5 name not yet implemented - see zraw)(%%)/FL2/Electron Diagnostic/BAM/
1054 +
1055 +(% style="color:#172b4d" %)SEED5(% style="color:#ff6600" %)/status  (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL2/Electron Diagnostic/BAM/{{/code}}(%%)
1023 1023  //always saved (PBD)//
1024 -DOOCS prop : FLASH.SDIAG/BAM/FL2.SEED5/ARRIVAL_TIME.bamStatus.//2//
1025 -DAQ channel: FLASH.SDIAG/BAM/FL2.SEED5/ARRIVAL_TIME.BAMSTATUS.2
1026 -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
1057 +(% style="color:#172b4d" %)**FL2.SEED5**(% style="color:#000000" %)E.bamStatus.//2//{{code language="none"}}DOOCS prop : FLASH.SDIAG/BAM//ARRIVAL_TIM{{/code}}(%%)
1058 +(% 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}}(%%)
1059 +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
1027 1027  
1028 1028  
1029 1029  [[Contents>>doc:||anchor="Contents"]]
... ... @@ -1067,6 +1067,7 @@
1067 1067  DAQ channel: {{code language="none"}}FLASH.DIAG/PBD2.TOROID.ML/3GUN/NUMBEROFBUNCHES.FLASH2{{/code}}
1068 1068  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)
1069 1069  units:
1103 +
1070 1070  
1071 1071  ===== actual pulse pattern recorded after the undulator =====
1072 1072  
... ... @@ -1076,6 +1076,7 @@
1076 1076  DAQ channel: {{code language="none"}}FLASH.DIAG/PBD2.TOROID.ML/9FL2BURN.PULSEPATTERN{{/code}}
1077 1077  desc: The bunch pattern as function of time in a burst recorded by toroide diagnostic BEHIND the undulator. (FLASH2)
1078 1078  units:
1113 +
1079 1079  
1080 1080  ===== Train ID =====
1081 1081  
... ... @@ -1085,40 +1085,26 @@
1085 1085  DAQ channel: {{code language="none"}}none{{/code}}
1086 1086  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 !)
1087 1087  units:
1123 +
1088 1088  
1089 -===== (% style="color:#e67e22" %)Train time(%%) =====
1125 +===== Train time =====
1090 1090  
1091 -(% style="color:#e67e22" %)//always saved (PBD2)//(%%)
1092 -(% style="color:#e67e22" %){{code language="none"}}/Timing/train time{{/code}}
1127 +//always saved (PBD2)//
1128 +{{code language="none"}}/Timing/train time{{/code}}
1093 1093  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
1094 1094  units: d h min s cs
1131 +
1095 1095  
1096 1096  {{code language="none"}}
1097 1097  /Timing/time stamp
1098 1098  {{/code}}
1099 1099  
1100 -(% style="color:#e67e22" %)//always saved (PBD2)//(%%)
1101 -(% style="color:#e67e22" %)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
1137 +//always saved (PBD2)//
1138 +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
1102 1102  second column: microseconds
1103 1103  third column: Train ID of FLASH
1141 +
1104 1104  
1105 -
1106 -(% id="cke_bm_2455529S" style="display:none" %) (%%)currently it is saved as Unix time in : /zraw/FLASH.DIAG/TIMINGINFO/TIME1.BUNCH_FIRST_INDEX.1/dGroup/time
1107 -
1108 -{{expand expanded="false" title="Timestamp help for python"}}
1109 - import time
1110 -
1111 -# epoch time is found in /zraw/FLASH.DIAG/TIMINGINFO/TIME1.BUNCH_FIRST_INDEX.1/dGroup/time #!!! a leading 1 has to be added !!!
1112 -# The time and date of the start of the data taking in the HDF file is encoded in the filename - to roughly check the time
1113 -epoch_time = 1709051499.17 # Replace with your epoch time
1114 -
1115 -formatted_time = time.strftime('%Y-%m-%d %H:%M:%S', time.gmtime(epoch_time))
1116 -print(formatted_time)
1117 -{{/expand}}
1118 -
1119 -
1120 -
1121 -
1122 1122  [[Contents>>doc:||anchor="Contents"]]
1123 1123  
1124 1124  
... ... @@ -1132,7 +1132,7 @@
1132 1132  
1133 1133  ===== GHz ADCs =====
1134 1134  
1135 -ADC traces of the (SPDevices 412) GHZ ADCs available for the users . More information about the ADCs can be found** [[here>>doc:FS-FLASH USER tmp.Data Acquisition and controls 1.Controls (DOOCS, jDDD,\.\.\.).MTCA ADCs.WebHome]]**
1156 +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]]**
1136 1136  //saved on DEMAND in the user DAQ//
1137 1137  \\Up to now there are 4 channels available at FL24
1138 1138  \\\\{{code language="none"}}/FL2/Experiment/MTCA-EXP1/ADQ412 GHz ADC/CH00/TD{{/code}}
... ... @@ -1167,30 +1167,19 @@
1167 1167  
1168 1168  
1169 1169  
1170 -==== Pump Probe Laser (FLASH2) ====
1191 +==== FL 24 Pump Probe Laser (FLASH2) ====
1171 1171  
1172 -{{info width="30%"}}
1193 +{{info}}
1173 1173  list of saved parameters status May 2024 (up to now the parameters can be found in /zraw/ ... )
1174 1174  
1175 -[[attach:FSLADAQ-DAQParameterlistULGAN-2.pdf||target="_blank"]]
1196 +[[attach:FSLADAQ-FL23.pdf||target="_blank"]]
1176 1176  
1177 -[[attach:FSLADAQ-DAQParameterlistFL23-2.pdf||target="_blank"]]
1198 +[[attach:FSLADAQ-DAQParameterlistFL24.pdf||target="_blank"]]
1178 1178  
1179 -[[attach:FSLADAQ-DAQParameterlistFL24-2.pdf||target="_blank"]]
1180 -
1181 -
1182 -{{view-file att--filename="FSLADAQ-DAQParameterlistFL23-2.pdf"}}{{/view-file}}
1183 -
1184 -
1185 -{{view-file att--filename="FSLADAQ-DAQParameterlistFL23-2.pdf"}}{{/view-file}}
1186 -
1187 -
1188 -{{view-file att--filename="FSLADAQ-DAQParameterlistFL24-2.pdf"}}{{/view-file}}
1189 -
1190 -internal link to parameter list: [[FS-LA DAQ - XWiki>>url:https://xwiki.desy.de/xwiki/bin/view/FSLADAQ/]]
1200 +[[attach:FSLADAQ-DAQParameterlistPPlaser.pdf||target="_blank"]]
1191 1191  {{/info}}
1192 1192  
1193 -{{expand title="Laser parameters used until 2023"}}
1203 +
1194 1194  These are the parameters that can be saved in the FL2 User DAQ for the FL2 PP laser//** FOR BEAMLINE FL24**//
1195 1195  
1196 1196  **User delay**
... ... @@ -1546,8 +1546,8 @@
1546 1546  )))|(((
1547 1547  FLASH.LASER/ULGAN1.DYNPROP/TCFIBER.DOUBLES/DOUBLE26
1548 1548  )))
1549 -{{/expand}}
1550 1550  
1560 +[[Contents>>doc:||anchor="Contents"]]
1551 1551  
1552 1552  
1553 1553  === "/uncategorized/" ===
... ... @@ -1662,3 +1662,8 @@
1662 1662  )))
1663 1663  
1664 1664  [[Contents>>doc:||anchor="Contents"]]
1675 +
1676 +
1677 +{{/layout-cell}}
1678 +{{/layout-section}}
1679 +{{/layout}}
FSLADAQ-DAQParameterlistFL23-2.pdf
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.rangeadm
Size
... ... @@ -1,1 +1,0 @@
1 -32.1 KB
Content
FSLADAQ-DAQParameterlistFL24-2.pdf
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.rangeadm
Size
... ... @@ -1,1 +1,0 @@
1 -37.6 KB
Content
FSLADAQ-DAQParameterlistULGAN-2.pdf
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.rangeadm
Size
... ... @@ -1,1 +1,0 @@
1 -34.8 KB
Content
Screenshot 2024-05-17 094435.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.rangeadm
Size
... ... @@ -1,1 +1,0 @@
1 -172.4 KB
Content