Skip to Content

Changes for page The FLASH HDF5 structure

Last modified by sndueste on 2025-11-19 14:51
From version 94.1
edited by sndueste
on 2025-05-19 16:53
Change comment: Uploaded new attachment "image2021-2-9_10-51-6.png", version {1}
To version 79.1
edited by sndueste
on 2024-04-25 16:51
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
... ... @@ -10,9 +10,9 @@
10 10  
11 11  == General information about HDF5 ==
12 12  
13 -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"]]
14 14  
15 -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"]]
16 16  
17 17  For use on the DESY Maxwell or PAL (max-fsc or pal) **hdfview** is available in the xray module :
18 18  {{code language="none"}}> module load xray{{/code}}
... ... @@ -68,6 +68,7 @@
68 68  {{layout-cell}}
69 69  * ADC data as example for **fast** **data** (10 Hz):            
70 70  
71 +
71 71  [[image:attach:image2020-11-16_15-26-28.png||height="250"]]
72 72  {{/layout-cell}}
73 73  
... ... @@ -99,7 +99,7 @@
99 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 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"]]
101 101  
102 -(% class="Object" %)See also the collection of Demo data and sample scripts : [[doc:FS-FLASH USER tmp.Data Acquisition and controls 1.DAQ and controls overview.Offline data analysis (DAQ).Collection of HDF5 sample data from different beamlines.WebHome]] and [[doc:FS-FLASH USER tmp.Data Acquisition and controls 1.DAQ and controls overview.Offline data analysis (DAQ).DEMO - Working with FLASH data.WebHome]]
103 +(% 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]]
103 103  {{/info}}
104 104  {{/layout-cell}}
105 105  {{/layout-section}}
... ... @@ -110,24 +110,18 @@
110 110  
111 111  == Complete list of recordable parameters ==
112 112  
113 -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"]].
114 +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"]].
115 +
114 114  
115 115  == Most popular FLASH parameters and their names in HDF5, DOOCS and (raw) DAQ ==
116 116  
117 117  {{id name="DOOCSparameters"/}}
118 118  
121 +Note, the HDF group and data set names apply to our HDF tree version since vers. 0.3.0.
119 119  
123 +
120 120  === FLASH1 ===
121 121  
122 -
123 -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.
124 -
125 -The previously used naming scheme (2024 and before) can be found here:
126 -
127 -{{expand expanded="false" title="FLASH1 Naming scheme used until 2024"}}
128 -s
129 -{{/expand}}
130 -
131 131  ==== Beamline info (FLASH1) ====
132 132  
133 133  {{code language="none"}}/FL1/Beamlines/Attenuator/pressure{{/code}}
... ... @@ -136,6 +136,7 @@
136 136  DAQ channel: {{code language="none"}}FLASH.FEL/GAS_DOSING/FL1.ATTENUATOR/PRESSURE{{/code}}
137 137  desc: set pressure in the gas attenuator
138 138  units: mbar
134 +
139 139  
140 140  {{code language="none"}}/FL1/Beamlines/BL/Fast shutter/open{{/code}}
141 141  //always saved (PBD)//
... ... @@ -155,15 +155,17 @@
155 155  //always saved (PBD)//
156 156  DOOCS prop : {{code language="none"}}TTF2.FEL/BLFILTERS1/FILTER1/FW.MOTOR.POS{{/code}}
157 157  DAQ channel: {{code language="none"}}TTF2.FEL/BLFILTERS1/FILTER1/FW.MOTOR.POS{{/code}}
158 -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]]
154 +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]]
159 159  units: degree
156 +
160 160  
161 161  {{code language="none"}}/FL1/Beamlines/BL/Filters/BL filter wheel/position filter 2{{/code}}
162 162  //always saved (PBD)//
163 163  DOOCS prop : {{code language="none"}}TTF2.FEL/BLFILTERS2/FILTER2/FW.MOTOR.POS{{/code}}
164 164  DAQ channel: {{code language="none"}}TTF2.FEL/BLFILTERS2/FILTER2/FW.MOTOR.POS{{/code}}
165 -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]]
162 +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]]
166 166  units: degree
164 +
167 167  
168 168  {{code language="none"}}/FL1/Beamlines/PG/Filters/position filter 1{{/code}}
169 169  //always saved (PBD)//
... ... @@ -171,6 +171,7 @@
171 171  DAQ channel: {{code language="none"}}TTF2.FEL/BDAF1/BDA.F1/FW.MOTOR.POS{{/code}}
172 172  desc: Position of the PG filter wheel 1
173 173  units: degree
172 +
174 174  
175 175  {{code language="none"}}/FL1/Beamlines/PG/Filters/position filter 2{{/code}}
176 176  //always saved (PBD)//
... ... @@ -178,6 +178,7 @@
178 178  DAQ channel: {{code language="none"}}TTF2.FEL/BDAF2/BDA.F2/FW.MOTOR.POS{{/code}}
179 179  desc: Position of the PG filter wheel 2
180 180  units: degree
180 +
181 181  
182 182  {{code language="none"}}/FL1/Beamlines/PG/Filters/position filter 3{{/code}}
183 183  //always saved (PBD)//
... ... @@ -212,7 +212,7 @@
212 212  DOOCS prop : {{code language="none"}}TTF2.DAQ/PHFLUX/OUT34/VAL{{/code}}
213 213  DAQ channel: {{code language="none"}}PBD.PHFLUX/TUNNEL.ENERGYPULSE.USER{{/code}}
214 214  desc :Energy per pulse Tunnel (from e-) - the values are set to "0" if there was no SASE beam in the FEL
215 -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]]**
215 +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]]**
216 216  
217 217  {{code language="none"}}/FL1/Photon Diagnostic/GMD/Pulse resolved energy/energy tunnel (raw){{/code}}
218 218  //always saved (PBD)//
... ... @@ -219,7 +219,7 @@
219 219  DOOCS prop : {{code language="none"}}TTF2.DAQ/PHFLUX/OUT14/VAL{{/code}}
220 220  DAQ channel: {{code language="none"}}PBD.PHFLUX/TUNNEL.ENERGYPULSE.FF{{/code}}
221 221  desc :Energy per pulse Tunnel (from e-) - uncorrected values. There are also values saved if there was no beam ... just background noise
222 -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]]**
222 +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]]**
223 223  
224 224  {{code language="none"}}/FL1/Photon Diagnostic/GMD/Average energy/energy BDA{{/code}}
225 225  //always saved (PBD)//
... ... @@ -235,7 +235,7 @@
235 235  DOOCS prop : {{code language="none"}}TTF2.DAQ/PHFLUX/OUT35/VAL{{/code}}
236 236  DAQ channel: {{code language="none"}}PBD.PHFLUX/BDA.ENERGYPULSE.USER{{/code}}
237 237  desc :Energy per pulse BDA (from e-) - the values are set to "0" if there was no SASE beam in the FEL
238 -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]]**
238 +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]]**
239 239  
240 240  {{code language="none"}}/FL1/Photon Diagnostic/GMD/Pulse resolved energy/energy BDA (raw){{/code}}
241 241  //always saved (PBD)//
... ... @@ -242,7 +242,7 @@
242 242  DOOCS prop : {{code language="none"}}TTF2.DAQ/PHFLUX/OUT15/VAL{{/code}}
243 243  DAQ channel: {{code language="none"}}PBD.PHFLUX/BDA.ENERGYPULSE.FF{{/code}}
244 244  desc :Energy per pulse BDA (from e-) - uncorrected values. There are also values saved if there was no beam ... just background noise
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]]**
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:FLASHUSER.jddd-linked help pages.Calibrating the pulse resolved (electron) data from GMD.WebHome]]**
246 246  {{/expand}}
247 247  
248 248  
... ... @@ -264,10 +264,11 @@
264 264  {{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}}
265 265  
266 266  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)
267 -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]]**
267 +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]]**
268 268  
269 269  {{info title="GMD pulse resolved data structure"}}
270 270  For every pulse in the pulse train the information is saved:
271 +
271 271  
272 272  1. **Intensity per pulse** (a.u. (more or less µJ ))
273 273  1. Intensity per pulse (auxillary GMD) - not used
... ... @@ -402,8 +402,8 @@
402 402  =====
403 403  arrival time (BAM) =====
404 404  
405 -{{info title="BAM information: updates 2022 (status 2025)"}}
406 -* 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"]]
406 +{{info title="BAM information: updates 2022"}}
407 +* 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"]]
407 407  * The data format of the BAM has been completely altered in the 2022 shutdown
408 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 ...
409 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)
... ... @@ -411,8 +411,8 @@
411 411  ** acc:  4DBC3 → FL0.DBC2
412 412  ** FL1: 1SFELC →  FL1.SFELC
413 413  ** FL2: FL2XTDS → (% style="color:#172b4d" %)FL2.SEED5
414 -* for more Info: [[LINK to detailed infos from MSK>>doc:SDiag.How-to articles.BAM Data Structure.WebHome||shape="rect"]]
415 -* [[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]]
415 +* for more Info: [[LINK to detailed infos from MSK>>url:https://confluence.desy.de/display/SDiagPublic/BAM+Data+Structure||shape="rect"]]
416 +* [[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 416  * a recent  [[talk about the working principle of the BAM>>attach:BAM-basics and outlook-2018_DESY-template_16-9Format.pdf]]
417 417  {{/info}}
418 418  
... ... @@ -456,9 +456,9 @@
456 456  
457 457  (% style="color:#ff6600" %)DBC2/error (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL1/Electron Diagnostic/BAM/{{/code}}(%%)
458 458  //always saved (PBD)//
459 -DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIM(% style="color:#000000" %)E.bamError.1(%%)
460 -DAQ channel: (% style="color:#000000" %)FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.BAMERROR.1(%%)
461 -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
460 +DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIM(% style="color:#000000" %)E.bamError(%%)
461 +DAQ channel: (% style="color:#000000" %)FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.BAMERROR(%%)
462 +desc: If the value is 0 , the BAM is working well. If it is non-zero there is a problem !!
462 462  
463 463  
464 464  (% style="color:#ff6600" %)DBC2/status  (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL1/Electron Diagnostic/BAM/{{/code}}(%%)
... ... @@ -511,6 +511,7 @@
511 511  DAQ channel: {{code language="none"}}PBD.BEAM.PROF.ML/DAQ.OUT.PROF.CCCED{{/code}}
512 512  desc: temporal profile of electron bunch, y axis in Ampers (FLASH1)
513 513  units: pixel
515 +
514 514  
515 515  {{code language="none"}}/FL1/Electron Diagnostic/Electron bunch profile/Expert stuff/TDS calibration constant{{/code}}
516 516  //always saved (PBD) - IF LOLA is ON and ACTIVATED in the PBD DAQ (talk to expert)//
... ... @@ -518,6 +518,7 @@
518 518  DAQ channel: = PBD.BEAM.PROF.ML/CCT=
519 519  desc: TDS calibration constant for the x-axis of the profiles: fs per pixel
520 520  units: fs per pixel
523 +
521 521  
522 522  {{code language="none"}}/FL1/Electron Diagnostic/Electron bunch profile/TDS profile width rms{{/code}}
523 523  //always saved (PBD) - IF LOLA is ON and ACTIVATED in the PBD DAQ (talk to expert)//
... ... @@ -533,7 +533,8 @@
533 533  DOOCS prop : {{code language="none"}}TTF2.DAQ/ENERGY.DOGLEG/E_INTRA_MEAN/VAL{{/code}}
534 534  DAQ channel: {{code language="none"}}PBD.ENERGY.DOGLEG/E_MEAN{{/code}}
535 535  desc: electron bunch energy (average over the bunch train)
536 -units: (% class="twikiNewLink" %)MeV
539 +units: (% class="twikiNewLink" %)MeV(%%)
540 +
537 537  
538 538  {{code language="none"}}/FL1/Electron Diagnostic/Electron energy/pulse resolved energy{{/code}}
539 539  //always saved (PBD)//
... ... @@ -549,6 +549,7 @@
549 549  DAQ channel: {{code language="none"}}PBD.ENERGY.DOGLEG/LAMBDA_MEAN{{/code}}
550 550  desc: Wavelength calculated by the electron bunch energy (average over the bunch train) (FLASH1)
551 551  units: nm
556 +
552 552  
553 553  [[Contents>>doc:||anchor="Contents"]]
554 554  
... ... @@ -563,6 +563,7 @@
563 563  DAQ channel: {{code language="none"}}TTF2.UTIL/LASER.CONTROL/GUN/PULSE_FREQ{{/code}}
564 564  desc: repetition rate of the bunches / pulses within the burst (FLASH1)
565 565  units: kHz
571 +
566 566  
567 567  ===== set number of pulses =====
568 568  
... ... @@ -581,6 +581,7 @@
581 581  DAQ channel: {{code language="none"}}TTF2.DIAG/PBD.TOROID.ML/12EXP{{/code}}
582 582  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)
583 583  units:
590 +
584 584  
585 585  ===== actual pulse pattern recorded after the undulator =====
586 586  
... ... @@ -590,6 +590,7 @@
590 590  DAQ channel: {{code language="none"}}TTF2.DIAG/PBD.TOROID.ML/12EXP{{/code}}
591 591  desc: The bunch pattern as function of time in a burst recorded by toroid diagnostic BEHIND the undulator. (FLASH1)
592 592  units:
600 +
593 593  
594 594  ===== Train ID =====
595 595  
... ... @@ -599,34 +599,24 @@
599 599  DAQ channel: {{code language="none"}}none{{/code}}
600 600  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 !)
601 601  units:
610 +
602 602  
603 -===== (% style="color:#e67e22" %)Train time(%%) =====
612 +===== Train time =====
604 604  
605 -(% style="color:#e67e22" %){{code language="none"}}/Timing/train time{{/code}}
614 +{{code language="none"}}/Timing/train time{{/code}}
606 606  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
607 607  units: d h min s cs
617 +
608 608  
609 -(% style="color:#e67e22" %){{code language="none"}}/Timing/time stamp{{/code}}
619 +{{code language="none"}}/Timing/time stamp{{/code}}
610 610  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
611 611  second column: microseconds
612 612  third column: Train ID of FLASH
623 +
613 613  
614 -currently it is saved as Unix time in : /zraw/FLASH.DIAG/TIMINGINFO/TIME1.BUNCH_FIRST_INDEX.1/dGroup/time
615 -
616 -{{expand expanded="false" title="Timestamp help for python"}}
617 - import time
618 -
619 -# epoch time is found in /zraw/FLASH.DIAG/TIMINGINFO/TIME1.BUNCH_FIRST_INDEX.1/dGroup/time #!!! a leading 1 has to be added !!!
620 -# 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
621 -epoch_time = 1709051499.17 # Replace with your epoch time
622 -
623 -formatted_time = time.strftime('%Y-%m-%d %H:%M:%S', time.gmtime(epoch_time))
624 -print(formatted_time)
625 -{{/expand}}
626 -
627 -
628 628  [[Contents>>doc:||anchor="Contents"]]
629 629  
627 +
630 630  ==== Pump Probe Laser (FLASH1) ====
631 631  
632 632  **PIGLET (PG laser)**
... ... @@ -633,17 +633,34 @@
633 633  
634 634  **{{code language="none"}}/FL1/Experiment/Pump probe laser{{/code}}**
635 635  
636 -{{info width="30%"}}
637 -list of saved parameters status May 2024 (up to now the parameters can be found in /zraw/ ... )
634 +FLASH.LASER/FLACPUPGLASER1.PULSEENERGY/DIAG1out/PULSEENERGY.MEAN 
635 +FLASH.LASER/FLACPUPGLASER1.PULSEENERGY/PG1_incoupl/PULSEENERGY.MEAN 
636 +FLASH.LASER/FLACPUPGLASER1.PULSEENERGY/PG2_incoupl/PULSEENERGY.MEAN 
637 +FLASH.SYNC/LASER.LOCK.EXP/FLASH1.MOD1.PG.OSC/FMC0.MD22.1.ENCODER_POSITION.RD 
638 +FLASH.SYNC/LASER.LOCK.EXP/FLASH1.MOD1.PG.OSC/FMC0.MD22.1.ENCODER_POSITION_RAW.RD 
639 +FLASH.SYNC/LASER.LOCK.EXP/FLASH1.MOD1.PG.OSC/FMC0.MD22.1.POSITION.RD
638 638  
639 -Download the PDF:
641 +**BL - Hidra laser **
640 640  
641 -{{view-file att--filename="FSLADAQ-DAQParameterlistPiGLET.pdf"}}{{/view-file}}
643 +Property,Units,Description
644 +FLASH.LASER/MODBL.CAM/BL1.13.AC/DAQ_CHANNEL,'AU','FL1HIDRAPP1 Autocorrelation (IR) ROI readout'
645 +FLASH.LASER/MODBL.CAM/BL1.14.VF/DAQ_CHANNEL,'AU','FL1HIDRAPP1 Virtual Focus Camera (IR) ROI readout'
646 +FLASH.LASER/MODBL.SENSORBOARD/PDTRIG_CAMP/DAQ_CHANNEL,'au','FL1PPL Energy channels'
647 +FLASH.LASER/MODBL.SPECT/CAMP_IR/DAQ_CHANNEL,'au','FL1PPL BL Table Spectrum'
648 +FLASH.LASER/HIDRAPP1.SPECTRUM_ANALYSIS/CAMP_IR/DAQ_CHANNEL,'au','FL1PPL Spectrum Analysis'
649 +FLASH.SYNC/LASER.LOCK.EXP/F1.PPL.OSC/FMC0.MD22.1.POSITION.RD,'ps','FL1PPL Optical Delay Line (act)'
650 +FLASH.SYNC/LASER.LOCK.EXP/F1.PPL.OSC/FMC0.MD22.1.POSITION_SET.WR,'ps','FL1PPL Optical Delay Line (set)'
651 +FLASH.SYNC/LASER.LOCK.EXP/F1.PPL.OSC/FMC0.MD22.1.ENCODER_POSITION.RD,'ps','FL1PPL Optical Delay Line (Encoder Readback)'
652 +FLASH.FEL/FLAPPBEAMLINES.MOTOR/CAMP_Delayline/FPOS,'ps','FL1PPL NIR delay BL1 table (act)'
653 +FLASH.FEL/FLAPPBEAMLINES.MOTOR/CAMP_Delayline/FPOS.SET,'ps','FL1PPL NIR delay BL1 table (set)'
654 +FLASH.FEL/FLAPPBEAMLINES.MOTOR/CAMP.ATT/FPOS,'degree','FL1PPL Transmission degree (act)'
655 +FLASH.FEL/FLAPPBEAMLINES.MOTOR/CAMP.ATT/FPOS.SET,'degree','FL1PPL Transmission degree (set)'
656 +FLASH.FEL/FLAPPBEAMLINES.MOTOR/Camp_Focus_Lens/FPOS,'mm','FL1PPL Focus Mirror Stage Position (act)'
657 +FLASH.FEL/FLAPPBEAMLINES.MOTOR/Camp_Focus_Lens/FPOS.SET,'mm','FL1PPL Focus Mirror Stage Position (set)'
658 +FLASH.LASER/MODBL.FEEDFWD/BL1_Att/INPUT.Y,'%','FL1PPL Transmission rate'
659 +FLASH.SYNC/LASER.LOCK.EXP/F1.PPL.OSC/CURRENT_INPUT_JITTER.RD,'fs','FL1PPL Sync. Jitter'
660 +FLASH.SYNC/LASER.LOCK.EXP/F1.PPL.OSC/LOCK_STATUS.VALUE.RD,'au','FL1PPL Sync. Status'
642 642  
643 -
644 -
645 -{{/info}}
646 -
647 647  {{expand title="Parameters used until 2021"}}
648 648  {{code language="none"}}
649 649  /FL1/Experiment/Pump probe laser/laser attenuation
... ... @@ -700,7 +700,7 @@
700 700  
701 701  ===== GHz ADCs =====
702 702  
703 -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]]**
718 +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]]**
704 704  //saved on DEMAND in the user DAQ//
705 705  \\The HDF5 names for the ADC traces are depending on the beamline :
706 706  \\PG Beamline:
... ... @@ -757,7 +757,8 @@
757 757  (% style="color:#000000" %)DOOCS prop : {{code language="none"}}FLASH.FEL/ATT.GAS_DOSING/FL2.HALL/PRESSURE{{/code}} (%%)
758 758  (% style="color:#000000" %)DAQ channel:  {{code language="none"}}FLASH.FEL/ATT.GAS_DOSING/FL2.HALL/PRESSURE{{/code}} (%%)
759 759  (% style="color:#000000" %)desc: set pressure in the gas attenuator (%%)
760 -(% style="color:#000000" %)units: mbar
775 +(% style="color:#000000" %)units: mbar(%%)
776 +
761 761  
762 762  {{code language="none"}}/FL2/Beamlines/FL20/Shutter/open{{/code}}
763 763  //always saved (PBD2)//
... ... @@ -771,14 +771,15 @@
771 771  //always saved (PBD2)//
772 772  DOOCS prop : {{code language="none"}}FLASH.FEL/FL20H.PH.MOTOR/MOTOR1.MOT3/FPOS{{/code}}
773 773  DAQ channel: FLASH.FEL/FL20H.PH.MOTOR/MOTOR1.MOT3/FPOS
774 -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]]**
790 +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]]**
775 775  units: degree
792 +
776 776  
777 777  /FL2/Beamlines/Filter wheel/position wheel 2
778 778  always saved (PBD2)
779 779  DOOCS prop : {{code language="none"}}FLASH.FEL/FL20H.PH.MOTOR/MOTOR2.MOT3/FPOS{{/code}}
780 780  DAQ channel: {{code language="none"}}FLASH.FEL/FL20H.PH.MOTOR/MOTOR2.MOT3/FPOS{{/code}}
781 -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]]
798 +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]]
782 782  units: degree
783 783  
784 784  
... ... @@ -803,10 +803,11 @@
803 803  DOOCS prop : {{code language="none"}}FLASH.FEL/XGM.INTENSITY/FL2.TUNNEL/INTENSITY.TD{{/code}}
804 804  DAQ channel: {{code language="none"}}FLASH.FEL/XGM.INTENSITY/FL2.TUNNEL/INTENSITY.TD{{/code}}
805 805  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)
806 -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]]**
823 +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]]**
807 807  
808 808  {{info title="GMD pulse resolved data structure"}}
809 809  For every pulse in the pulse train the information is saved:
827 +
810 810  
811 811  1. **Intensity per pulse** (a.u. (more or less µJ ))
812 812  1. Intensity per pulse (auxillary GMD) - not used
... ... @@ -923,8 +923,8 @@
923 923  (% style="letter-spacing:0.0px" %)units: (% class="twikiNewLink" %)MeV
924 924  
925 925  
926 -(% style="color: rgb(94, 108, 132); font-weight: 600; letter-spacing: 0px;" %)
927 -===== undulator settings =====
944 +(% style="color: rgb(94,108,132);font-weight: 600;letter-spacing: 0.0px;" %)
945 +undulator settings
928 928  
929 929  {{code language="none"}}/FL2/Electron Diagnostic/Undulator setting/set wavelength{{/code}}
930 930  //always saved (PBD2)//
... ... @@ -945,17 +945,17 @@
945 945  =====
946 946  arrival time (BAM) =====
947 947  
948 -{{info title="BAM information: updates 2022 (status 2025)"}}
949 -* 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"]]
966 +{{info title="BAM information: updates 2022"}}
967 +* 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"]]
950 950  * The data format of the BAM has been completely altered in the 2022 shutdown
951 -* 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 ...
969 +* 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 ...
952 952  * 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)
953 953  * There has been also a renaming  (and relocation) of the BAMs.
954 954  ** acc:  4DBC3 → FL0.DBC2
955 955  ** FL1: 1SFELC →  FL1.SFELC
956 -** FL2: FL2XTDS → (% style="color:#172b4d" %)FL2.SEED5
957 -* for more Info: [[LINK to detailed infos from MSK>>doc:SDiag.How-to articles.BAM Data Structure.WebHome||shape="rect"]]
958 -* [[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]]
974 +** FL2: 8FL2XTDS → (% style="color:#172b4d" %)FL2.SEED5
975 +* for more Info: [[LINK to detailed infos from MSK>>url:https://confluence.desy.de/display/SDiagPublic/BAM+Data+Structure||shape="rect"]]
976 +* [[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]]
959 959  * a recent  [[talk about the working principle of the BAM>>attach:BAM-basics and outlook-2018_DESY-template_16-9Format.pdf]]
960 960  {{/info}}
961 961  
... ... @@ -976,11 +976,12 @@
976 976  desc: Electron bunch arrival time measured with the BAM  in the accelerator  (pulse resolved data)
977 977  units: ps (bigger numbers indicate later arrivaltime of the electrons)
978 978  
979 -{{info title="BAM hints"}}
997 +{{info title="
998 +BAM hints"}}
980 980  * The BAM 4DBC3 measures the arrivaltime of** FLASH 1 and FLASH2** in the same data set (thus also sorted in at /FL1/ !).
981 981  * 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 
982 982  ** 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
983 -* [[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]]
1002 +* [[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]]
984 984  * [[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"]]
985 985  * a recent  [[talk about the working principle of the BAM>>attach:BAM-basics and outlook-2018_DESY-template_16-9Format.pdf]]
986 986  {{/info}}
... ... @@ -1012,20 +1012,20 @@
1012 1012  units: fs (bigger numbers (typically) indicate later arrival times of the electrons).
1013 1013  
1014 1014  
1015 -DBC2/error (% style="color:#f39c12" %)(HDF5 name not yet implemented - see zraw)(%%)/FL2/Electron Diagnostic/BAM/
1034 +(% style="color:#ff6600" %)DBC2/error (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL2/Electron Diagnostic/BAM/{{/code}}(%%)
1016 1016  //always saved (PBD)//
1017 -DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.bamError.2
1018 -DAQ channel: FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.BAMERROR.2
1019 -desc: If the value is 0 , the BAM is working well. If it is non-zero there is a problem !!
1036 +(% style="color:#000000" %)E.bamError{{code language="none"}}DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIM{{/code}}(%%)
1037 +(% style="color:#000000" %)FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.BAMERROR{{code language="none"}}DAQ channel: {{/code}}(%%)
1038 +desc: If the value is 0 , the BAM is working well. If it is non-zero there is a problem !!
1020 1020  
1021 -DBC2/status  (% style="color:#e67e22" %)(HDF5 name not yet implemented - see zraw)(%%)/FL2/Electron Diagnostic/BAM/
1040 +
1041 +(% style="color:#ff6600" %)DBC2/status  (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL2/Electron Diagnostic/BAM/{{/code}}(%%)
1022 1022  //always saved (PBD)//
1023 -DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.bamStatus.//2//
1024 -DAQ channel: FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.BAMSTATUS.2
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
1043 +(% style="color:#000000" %)E..bamStatus.//2//{{code language="none"}}DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIM{{/code}}(%%)
1044 +(% style="color:#000000" %): FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.BAMSTATUS.2{{code language="none"}}DAQ channel{{/code}}(%%)
1045 +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 1026  
1027 1027  
1028 -
1029 1029  ====== **BAM FL2.SEED5**{{code language="none"}}{{/code}} ======
1030 1030  
1031 1031  /FL2/Electron Diagnostic/BAM/**SEED5**(% style="color:#ff6600" %)/electron bunch arrival time  (HDF5 name not yet implemented - see zraw)
... ... @@ -1050,17 +1050,18 @@
1050 1050  units: fs (bigger numbers (typically) indicate later arrival times of the electrons).
1051 1051  
1052 1052  
1053 -FL2.SEED5/error (% style="color:#f39c12" %)(HDF5 name not yet implemented - see zraw)(%%)/FL2/Electron Diagnostic/BAM/
1072 +(% style="color:#172b4d" %)SEED5(% style="color:#ff6600" %)/error (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL2/Electron Diagnostic/BAM/{{/code}}(%%)
1054 1054  //always saved (PBD)//
1055 -DOOCS prop : FLASH.SDIAG/BAM/FL2.SEED5/ARRIVAL_TIME.bamError.2
1056 -DAQ channel: FLASH.SDIAG/BAM/FL2.SEED5/ARRIVAL_TIME.BAMERROR.2
1057 -desc: If the value is 0 , the BAM is working well. If it is non-zero there is a problem !!
1074 +(% style="color:#172b4d" %)**FL2.SEED5**(% style="color:#000000" %)E.bamError{{code language="none"}}DOOCS prop : FLASH.SDIAG/BAM//ARRIVAL_TIM{{/code}}(%%)
1075 +(% style="color:#000000" %): FLASH.SDIAG/BAM/(% style="color:#172b4d" %)**FL2.SEED5**(% style="color:#000000" %)/ARRIVAL_TIME.BAMERROR{{code language="none"}}DAQ channel{{/code}}(%%)
1076 +desc: If the value is 0 , the BAM is working well. If it is non-zero there is a problem !!
1058 1058  
1059 -FL2.SEED5/status  (% style="color:#e67e22" %)(HDF5 name not yet implemented - see zraw)(%%)/FL2/Electron Diagnostic/BAM/
1078 +
1079 +(% style="color:#172b4d" %)SEED5(% style="color:#ff6600" %)/status  (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL2/Electron Diagnostic/BAM/{{/code}}(%%)
1060 1060  //always saved (PBD)//
1061 -DOOCS prop : FLASH.SDIAG/BAM/FL2.SEED5/ARRIVAL_TIME.bamStatus.//2//
1062 -DAQ channel: FLASH.SDIAG/BAM/FL2.SEED5/ARRIVAL_TIME.BAMSTATUS.2
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
1081 +(% style="color:#172b4d" %)**FL2.SEED5**(% style="color:#000000" %)E.bamStatus.//2//{{code language="none"}}DOOCS prop : FLASH.SDIAG/BAM//ARRIVAL_TIM{{/code}}(%%)
1082 +(% 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}}(%%)
1083 +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 1064  
1065 1065  
1066 1066  [[Contents>>doc:||anchor="Contents"]]
... ... @@ -1104,6 +1104,7 @@
1104 1104  DAQ channel: {{code language="none"}}FLASH.DIAG/PBD2.TOROID.ML/3GUN/NUMBEROFBUNCHES.FLASH2{{/code}}
1105 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)
1106 1106  units:
1127 +
1107 1107  
1108 1108  ===== actual pulse pattern recorded after the undulator =====
1109 1109  
... ... @@ -1113,6 +1113,7 @@
1113 1113  DAQ channel: {{code language="none"}}FLASH.DIAG/PBD2.TOROID.ML/9FL2BURN.PULSEPATTERN{{/code}}
1114 1114  desc: The bunch pattern as function of time in a burst recorded by toroide diagnostic BEHIND the undulator. (FLASH2)
1115 1115  units:
1137 +
1116 1116  
1117 1117  ===== Train ID =====
1118 1118  
... ... @@ -1122,40 +1122,26 @@
1122 1122  DAQ channel: {{code language="none"}}none{{/code}}
1123 1123  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 !)
1124 1124  units:
1147 +
1125 1125  
1126 -===== (% style="color:#e67e22" %)Train time(%%) =====
1149 +===== Train time =====
1127 1127  
1128 -(% style="color:#e67e22" %)//always saved (PBD2)//(%%)
1129 -(% style="color:#e67e22" %){{code language="none"}}/Timing/train time{{/code}}
1151 +//always saved (PBD2)//
1152 +{{code language="none"}}/Timing/train time{{/code}}
1130 1130  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
1131 1131  units: d h min s cs
1155 +
1132 1132  
1133 1133  {{code language="none"}}
1134 1134  /Timing/time stamp
1135 1135  {{/code}}
1136 1136  
1137 -(% style="color:#e67e22" %)//always saved (PBD2)//(%%)
1138 -(% 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
1161 +//always saved (PBD2)//
1162 +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
1139 1139  second column: microseconds
1140 1140  third column: Train ID of FLASH
1165 +
1141 1141  
1142 -
1143 -(% 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
1144 -
1145 -{{expand expanded="false" title="Timestamp help for python"}}
1146 - import time
1147 -
1148 -# epoch time is found in /zraw/FLASH.DIAG/TIMINGINFO/TIME1.BUNCH_FIRST_INDEX.1/dGroup/time #!!! a leading 1 has to be added !!!
1149 -# 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
1150 -epoch_time = 1709051499.17 # Replace with your epoch time
1151 -
1152 -formatted_time = time.strftime('%Y-%m-%d %H:%M:%S', time.gmtime(epoch_time))
1153 -print(formatted_time)
1154 -{{/expand}}
1155 -
1156 -
1157 -
1158 -
1159 1159  [[Contents>>doc:||anchor="Contents"]]
1160 1160  
1161 1161  
... ... @@ -1169,7 +1169,7 @@
1169 1169  
1170 1170  ===== GHz ADCs =====
1171 1171  
1172 -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]]**
1180 +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]]**
1173 1173  //saved on DEMAND in the user DAQ//
1174 1174  \\Up to now there are 4 channels available at FL24
1175 1175  \\\\{{code language="none"}}/FL2/Experiment/MTCA-EXP1/ADQ412 GHz ADC/CH00/TD{{/code}}
... ... @@ -1204,32 +1204,11 @@
1204 1204  
1205 1205  
1206 1206  
1207 -==== Pump Probe Laser (FLASH2) ====
1215 +==== FL 24 Pump Probe Laser (FLASH2) ====
1208 1208  
1209 -{{info width="30%"}}
1210 -list of saved parameters status May 2024 (up to now the parameters can be found in /zraw/ ... )
1211 -
1212 -[[attach:FSLADAQ-DAQParameterlistULGAN-2.pdf||target="_blank"]]
1213 -
1214 -[[attach:FSLADAQ-DAQParameterlistFL23-2.pdf||target="_blank"]]
1215 -
1216 -[[attach:FSLADAQ-DAQParameterlistFL24-2.pdf||target="_blank"]]
1217 -
1218 -
1219 -{{view-file att--filename="FSLADAQ-DAQParameterlistFL23-2.pdf"}}{{/view-file}}
1220 -
1221 -
1222 -{{view-file att--filename="FSLADAQ-DAQParameterlistFL23-2.pdf"}}{{/view-file}}
1223 -
1224 -
1225 -{{view-file att--filename="FSLADAQ-DAQParameterlistFL24-2.pdf"}}{{/view-file}}
1226 -
1227 -
1228 -{{/info}}
1229 -
1230 -{{expand title="Laser parameters used until 2023"}}
1231 1231  These are the parameters that can be saved in the FL2 User DAQ for the FL2 PP laser//** FOR BEAMLINE FL24**//
1232 1232  
1219 +
1233 1233  **User delay**
1234 1234  
1235 1235  Delay (set value):
... ... @@ -1583,10 +1583,11 @@
1583 1583  )))|(((
1584 1584  FLASH.LASER/ULGAN1.DYNPROP/TCFIBER.DOUBLES/DOUBLE26
1585 1585  )))
1586 -{{/expand}}
1587 1587  
1588 1588  
1575 +[[Contents>>doc:||anchor="Contents"]]
1589 1589  
1577 +
1590 1590  === "/uncategorized/" ===
1591 1591  
1592 1592   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
... ... @@ -1601,6 +1601,7 @@
1601 1601  * 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".
1602 1602  * A number of inconsistent names have been streamlined. The relevant changes are listed in the following table.
1603 1603  
1592 +
1604 1604  (% class="wrapped" %)
1605 1605  |=(((
1606 1606  earlier HDF path (vers. 0.2)
... ... @@ -1698,6 +1698,7 @@
1698 1698  /FL2/Photon Diagnostic/GMD/Pulse resolved beam position/position tunnel vertical
1699 1699  )))
1700 1700  
1690 +
1701 1701  [[Contents>>doc:||anchor="Contents"]]
1702 1702  
1703 1703  
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-DAQParameterlistFL24.pdf
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.rangeadm
Size
... ... @@ -1,1 +1,0 @@
1 -37.2 KB
Content
FSLADAQ-DAQParameterlistPPlaser.pdf
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.rangeadm
Size
... ... @@ -1,1 +1,0 @@
1 -33.9 KB
Content
FSLADAQ-DAQParameterlistPiGLET-300424-1356-986.pdf
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.rangeadm
Size
... ... @@ -1,1 +1,0 @@
1 -157.0 KB
Content
FSLADAQ-DAQParameterlistPiGLET.pdf
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.rangeadm
Size
... ... @@ -1,1 +1,0 @@
1 -157.0 KB
Content
FSLADAQ-DAQParameterlistULGAN-2.pdf
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.rangeadm
Size
... ... @@ -1,1 +1,0 @@
1 -34.8 KB
Content
FSLADAQ-FL23.pdf
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.rangeadm
Size
... ... @@ -1,1 +1,0 @@
1 -28.6 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