Skip to Content

Changes for page The FLASH HDF5 structure

Last modified by sndueste on 2025-11-19 14:51
From version 93.6
edited by sndueste
on 2025-05-19 16:49
Change comment: There is no comment for this version
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,21 +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 -
128 128  ==== Beamline info (FLASH1) ====
129 129  
130 130  {{code language="none"}}/FL1/Beamlines/Attenuator/pressure{{/code}}
... ... @@ -133,6 +133,7 @@
133 133  DAQ channel: {{code language="none"}}FLASH.FEL/GAS_DOSING/FL1.ATTENUATOR/PRESSURE{{/code}}
134 134  desc: set pressure in the gas attenuator
135 135  units: mbar
134 +
136 136  
137 137  {{code language="none"}}/FL1/Beamlines/BL/Fast shutter/open{{/code}}
138 138  //always saved (PBD)//
... ... @@ -152,15 +152,17 @@
152 152  //always saved (PBD)//
153 153  DOOCS prop : {{code language="none"}}TTF2.FEL/BLFILTERS1/FILTER1/FW.MOTOR.POS{{/code}}
154 154  DAQ channel: {{code language="none"}}TTF2.FEL/BLFILTERS1/FILTER1/FW.MOTOR.POS{{/code}}
155 -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]]
156 156  units: degree
156 +
157 157  
158 158  {{code language="none"}}/FL1/Beamlines/BL/Filters/BL filter wheel/position filter 2{{/code}}
159 159  //always saved (PBD)//
160 160  DOOCS prop : {{code language="none"}}TTF2.FEL/BLFILTERS2/FILTER2/FW.MOTOR.POS{{/code}}
161 161  DAQ channel: {{code language="none"}}TTF2.FEL/BLFILTERS2/FILTER2/FW.MOTOR.POS{{/code}}
162 -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]]
163 163  units: degree
164 +
164 164  
165 165  {{code language="none"}}/FL1/Beamlines/PG/Filters/position filter 1{{/code}}
166 166  //always saved (PBD)//
... ... @@ -168,6 +168,7 @@
168 168  DAQ channel: {{code language="none"}}TTF2.FEL/BDAF1/BDA.F1/FW.MOTOR.POS{{/code}}
169 169  desc: Position of the PG filter wheel 1
170 170  units: degree
172 +
171 171  
172 172  {{code language="none"}}/FL1/Beamlines/PG/Filters/position filter 2{{/code}}
173 173  //always saved (PBD)//
... ... @@ -175,6 +175,7 @@
175 175  DAQ channel: {{code language="none"}}TTF2.FEL/BDAF2/BDA.F2/FW.MOTOR.POS{{/code}}
176 176  desc: Position of the PG filter wheel 2
177 177  units: degree
180 +
178 178  
179 179  {{code language="none"}}/FL1/Beamlines/PG/Filters/position filter 3{{/code}}
180 180  //always saved (PBD)//
... ... @@ -209,7 +209,7 @@
209 209  DOOCS prop : {{code language="none"}}TTF2.DAQ/PHFLUX/OUT34/VAL{{/code}}
210 210  DAQ channel: {{code language="none"}}PBD.PHFLUX/TUNNEL.ENERGYPULSE.USER{{/code}}
211 211  desc :Energy per pulse Tunnel (from e-) - the values are set to "0" if there was no SASE beam in the FEL
212 -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]]**
213 213  
214 214  {{code language="none"}}/FL1/Photon Diagnostic/GMD/Pulse resolved energy/energy tunnel (raw){{/code}}
215 215  //always saved (PBD)//
... ... @@ -216,7 +216,7 @@
216 216  DOOCS prop : {{code language="none"}}TTF2.DAQ/PHFLUX/OUT14/VAL{{/code}}
217 217  DAQ channel: {{code language="none"}}PBD.PHFLUX/TUNNEL.ENERGYPULSE.FF{{/code}}
218 218  desc :Energy per pulse Tunnel (from e-) - uncorrected values. There are also values saved if there was no beam ... just background noise
219 -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]]**
220 220  
221 221  {{code language="none"}}/FL1/Photon Diagnostic/GMD/Average energy/energy BDA{{/code}}
222 222  //always saved (PBD)//
... ... @@ -232,7 +232,7 @@
232 232  DOOCS prop : {{code language="none"}}TTF2.DAQ/PHFLUX/OUT35/VAL{{/code}}
233 233  DAQ channel: {{code language="none"}}PBD.PHFLUX/BDA.ENERGYPULSE.USER{{/code}}
234 234  desc :Energy per pulse BDA (from e-) - the values are set to "0" if there was no SASE beam in the FEL
235 -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]]**
236 236  
237 237  {{code language="none"}}/FL1/Photon Diagnostic/GMD/Pulse resolved energy/energy BDA (raw){{/code}}
238 238  //always saved (PBD)//
... ... @@ -239,7 +239,7 @@
239 239  DOOCS prop : {{code language="none"}}TTF2.DAQ/PHFLUX/OUT15/VAL{{/code}}
240 240  DAQ channel: {{code language="none"}}PBD.PHFLUX/BDA.ENERGYPULSE.FF{{/code}}
241 241  desc :Energy per pulse BDA (from e-) - uncorrected values. There are also values saved if there was no beam ... just background noise
242 -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]]**
243 243  {{/expand}}
244 244  
245 245  
... ... @@ -261,10 +261,11 @@
261 261  {{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 262  
263 263  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)
264 -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]]**
265 265  
266 266  {{info title="GMD pulse resolved data structure"}}
267 267  For every pulse in the pulse train the information is saved:
271 +
268 268  
269 269  1. **Intensity per pulse** (a.u. (more or less µJ ))
270 270  1. Intensity per pulse (auxillary GMD) - not used
... ... @@ -399,8 +399,8 @@
399 399  =====
400 400  arrival time (BAM) =====
401 401  
402 -{{info title="BAM information: updates 2022 (status 2025)"}}
403 -* 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"]]
404 404  * The data format of the BAM has been completely altered in the 2022 shutdown
405 405  * 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 ...
406 406  * 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)
... ... @@ -408,8 +408,8 @@
408 408  ** acc:  4DBC3 → FL0.DBC2
409 409  ** FL1: 1SFELC →  FL1.SFELC
410 410  ** FL2: FL2XTDS → (% style="color:#172b4d" %)FL2.SEED5
411 -* for more Info: [[LINK to detailed infos from MSK>>doc:SDiag.How-to articles.BAM Data Structure.WebHome||shape="rect"]]
412 -* [[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]]
413 413  * a recent  [[talk about the working principle of the BAM>>attach:BAM-basics and outlook-2018_DESY-template_16-9Format.pdf]]
414 414  {{/info}}
415 415  
... ... @@ -453,9 +453,9 @@
453 453  
454 454  (% style="color:#ff6600" %)DBC2/error (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL1/Electron Diagnostic/BAM/{{/code}}(%%)
455 455  //always saved (PBD)//
456 -DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIM(% style="color:#000000" %)E.bamError.1(%%)
457 -DAQ channel: (% style="color:#000000" %)FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.BAMERROR.1(%%)
458 -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 !!
459 459  
460 460  
461 461  (% style="color:#ff6600" %)DBC2/status  (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL1/Electron Diagnostic/BAM/{{/code}}(%%)
... ... @@ -508,6 +508,7 @@
508 508  DAQ channel: {{code language="none"}}PBD.BEAM.PROF.ML/DAQ.OUT.PROF.CCCED{{/code}}
509 509  desc: temporal profile of electron bunch, y axis in Ampers (FLASH1)
510 510  units: pixel
515 +
511 511  
512 512  {{code language="none"}}/FL1/Electron Diagnostic/Electron bunch profile/Expert stuff/TDS calibration constant{{/code}}
513 513  //always saved (PBD) - IF LOLA is ON and ACTIVATED in the PBD DAQ (talk to expert)//
... ... @@ -515,6 +515,7 @@
515 515  DAQ channel: = PBD.BEAM.PROF.ML/CCT=
516 516  desc: TDS calibration constant for the x-axis of the profiles: fs per pixel
517 517  units: fs per pixel
523 +
518 518  
519 519  {{code language="none"}}/FL1/Electron Diagnostic/Electron bunch profile/TDS profile width rms{{/code}}
520 520  //always saved (PBD) - IF LOLA is ON and ACTIVATED in the PBD DAQ (talk to expert)//
... ... @@ -530,7 +530,8 @@
530 530  DOOCS prop : {{code language="none"}}TTF2.DAQ/ENERGY.DOGLEG/E_INTRA_MEAN/VAL{{/code}}
531 531  DAQ channel: {{code language="none"}}PBD.ENERGY.DOGLEG/E_MEAN{{/code}}
532 532  desc: electron bunch energy (average over the bunch train)
533 -units: (% class="twikiNewLink" %)MeV
539 +units: (% class="twikiNewLink" %)MeV(%%)
540 +
534 534  
535 535  {{code language="none"}}/FL1/Electron Diagnostic/Electron energy/pulse resolved energy{{/code}}
536 536  //always saved (PBD)//
... ... @@ -546,6 +546,7 @@
546 546  DAQ channel: {{code language="none"}}PBD.ENERGY.DOGLEG/LAMBDA_MEAN{{/code}}
547 547  desc: Wavelength calculated by the electron bunch energy (average over the bunch train) (FLASH1)
548 548  units: nm
556 +
549 549  
550 550  [[Contents>>doc:||anchor="Contents"]]
551 551  
... ... @@ -560,6 +560,7 @@
560 560  DAQ channel: {{code language="none"}}TTF2.UTIL/LASER.CONTROL/GUN/PULSE_FREQ{{/code}}
561 561  desc: repetition rate of the bunches / pulses within the burst (FLASH1)
562 562  units: kHz
571 +
563 563  
564 564  ===== set number of pulses =====
565 565  
... ... @@ -578,6 +578,7 @@
578 578  DAQ channel: {{code language="none"}}TTF2.DIAG/PBD.TOROID.ML/12EXP{{/code}}
579 579  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)
580 580  units:
590 +
581 581  
582 582  ===== actual pulse pattern recorded after the undulator =====
583 583  
... ... @@ -587,6 +587,7 @@
587 587  DAQ channel: {{code language="none"}}TTF2.DIAG/PBD.TOROID.ML/12EXP{{/code}}
588 588  desc: The bunch pattern as function of time in a burst recorded by toroid diagnostic BEHIND the undulator. (FLASH1)
589 589  units:
600 +
590 590  
591 591  ===== Train ID =====
592 592  
... ... @@ -596,34 +596,24 @@
596 596  DAQ channel: {{code language="none"}}none{{/code}}
597 597  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 !)
598 598  units:
610 +
599 599  
600 -===== (% style="color:#e67e22" %)Train time(%%) =====
612 +===== Train time =====
601 601  
602 -(% style="color:#e67e22" %){{code language="none"}}/Timing/train time{{/code}}
614 +{{code language="none"}}/Timing/train time{{/code}}
603 603  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
604 604  units: d h min s cs
617 +
605 605  
606 -(% style="color:#e67e22" %){{code language="none"}}/Timing/time stamp{{/code}}
619 +{{code language="none"}}/Timing/time stamp{{/code}}
607 607  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
608 608  second column: microseconds
609 609  third column: Train ID of FLASH
623 +
610 610  
611 -currently it is saved as Unix time in : /zraw/FLASH.DIAG/TIMINGINFO/TIME1.BUNCH_FIRST_INDEX.1/dGroup/time
612 -
613 -{{expand expanded="false" title="Timestamp help for python"}}
614 - import time
615 -
616 -# epoch time is found in /zraw/FLASH.DIAG/TIMINGINFO/TIME1.BUNCH_FIRST_INDEX.1/dGroup/time #!!! a leading 1 has to be added !!!
617 -# 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
618 -epoch_time = 1709051499.17 # Replace with your epoch time
619 -
620 -formatted_time = time.strftime('%Y-%m-%d %H:%M:%S', time.gmtime(epoch_time))
621 -print(formatted_time)
622 -{{/expand}}
623 -
624 -
625 625  [[Contents>>doc:||anchor="Contents"]]
626 626  
627 +
627 627  ==== Pump Probe Laser (FLASH1) ====
628 628  
629 629  **PIGLET (PG laser)**
... ... @@ -630,17 +630,34 @@
630 630  
631 631  **{{code language="none"}}/FL1/Experiment/Pump probe laser{{/code}}**
632 632  
633 -{{info width="30%"}}
634 -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
635 635  
636 -Download the PDF:
641 +**BL - Hidra laser **
637 637  
638 -{{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'
639 639  
640 -
641 -
642 -{{/info}}
643 -
644 644  {{expand title="Parameters used until 2021"}}
645 645  {{code language="none"}}
646 646  /FL1/Experiment/Pump probe laser/laser attenuation
... ... @@ -697,7 +697,7 @@
697 697  
698 698  ===== GHz ADCs =====
699 699  
700 -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]]**
701 701  //saved on DEMAND in the user DAQ//
702 702  \\The HDF5 names for the ADC traces are depending on the beamline :
703 703  \\PG Beamline:
... ... @@ -754,7 +754,8 @@
754 754  (% style="color:#000000" %)DOOCS prop : {{code language="none"}}FLASH.FEL/ATT.GAS_DOSING/FL2.HALL/PRESSURE{{/code}} (%%)
755 755  (% style="color:#000000" %)DAQ channel:  {{code language="none"}}FLASH.FEL/ATT.GAS_DOSING/FL2.HALL/PRESSURE{{/code}} (%%)
756 756  (% style="color:#000000" %)desc: set pressure in the gas attenuator (%%)
757 -(% style="color:#000000" %)units: mbar
775 +(% style="color:#000000" %)units: mbar(%%)
776 +
758 758  
759 759  {{code language="none"}}/FL2/Beamlines/FL20/Shutter/open{{/code}}
760 760  //always saved (PBD2)//
... ... @@ -768,14 +768,15 @@
768 768  //always saved (PBD2)//
769 769  DOOCS prop : {{code language="none"}}FLASH.FEL/FL20H.PH.MOTOR/MOTOR1.MOT3/FPOS{{/code}}
770 770  DAQ channel: FLASH.FEL/FL20H.PH.MOTOR/MOTOR1.MOT3/FPOS
771 -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]]**
772 772  units: degree
792 +
773 773  
774 774  /FL2/Beamlines/Filter wheel/position wheel 2
775 775  always saved (PBD2)
776 776  DOOCS prop : {{code language="none"}}FLASH.FEL/FL20H.PH.MOTOR/MOTOR2.MOT3/FPOS{{/code}}
777 777  DAQ channel: {{code language="none"}}FLASH.FEL/FL20H.PH.MOTOR/MOTOR2.MOT3/FPOS{{/code}}
778 -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]]
779 779  units: degree
780 780  
781 781  
... ... @@ -800,10 +800,11 @@
800 800  DOOCS prop : {{code language="none"}}FLASH.FEL/XGM.INTENSITY/FL2.TUNNEL/INTENSITY.TD{{/code}}
801 801  DAQ channel: {{code language="none"}}FLASH.FEL/XGM.INTENSITY/FL2.TUNNEL/INTENSITY.TD{{/code}}
802 802  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)
803 -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]]**
804 804  
805 805  {{info title="GMD pulse resolved data structure"}}
806 806  For every pulse in the pulse train the information is saved:
827 +
807 807  
808 808  1. **Intensity per pulse** (a.u. (more or less µJ ))
809 809  1. Intensity per pulse (auxillary GMD) - not used
... ... @@ -920,8 +920,8 @@
920 920  (% style="letter-spacing:0.0px" %)units: (% class="twikiNewLink" %)MeV
921 921  
922 922  
923 -(% style="color: rgb(94, 108, 132); font-weight: 600; letter-spacing: 0px;" %)
924 -===== undulator settings =====
944 +(% style="color: rgb(94,108,132);font-weight: 600;letter-spacing: 0.0px;" %)
945 +undulator settings
925 925  
926 926  {{code language="none"}}/FL2/Electron Diagnostic/Undulator setting/set wavelength{{/code}}
927 927  //always saved (PBD2)//
... ... @@ -942,17 +942,17 @@
942 942  =====
943 943  arrival time (BAM) =====
944 944  
945 -{{info title="BAM information: updates 2022 (status 2025)"}}
946 -* 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"]]
947 947  * The data format of the BAM has been completely altered in the 2022 shutdown
948 -* 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 ...
949 949  * 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)
950 950  * There has been also a renaming  (and relocation) of the BAMs.
951 951  ** acc:  4DBC3 → FL0.DBC2
952 952  ** FL1: 1SFELC →  FL1.SFELC
953 -** FL2: FL2XTDS → (% style="color:#172b4d" %)FL2.SEED5
954 -* for more Info: [[LINK to detailed infos from MSK>>doc:SDiag.How-to articles.BAM Data Structure.WebHome||shape="rect"]]
955 -* [[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]]
956 956  * a recent  [[talk about the working principle of the BAM>>attach:BAM-basics and outlook-2018_DESY-template_16-9Format.pdf]]
957 957  {{/info}}
958 958  
... ... @@ -973,11 +973,12 @@
973 973  desc: Electron bunch arrival time measured with the BAM  in the accelerator  (pulse resolved data)
974 974  units: ps (bigger numbers indicate later arrivaltime of the electrons)
975 975  
976 -{{info title="BAM hints"}}
997 +{{info title="
998 +BAM hints"}}
977 977  * The BAM 4DBC3 measures the arrivaltime of** FLASH 1 and FLASH2** in the same data set (thus also sorted in at /FL1/ !).
978 978  * 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 
979 979  ** 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
980 -* [[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]]
981 981  * [[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"]]
982 982  * a recent  [[talk about the working principle of the BAM>>attach:BAM-basics and outlook-2018_DESY-template_16-9Format.pdf]]
983 983  {{/info}}
... ... @@ -1009,20 +1009,20 @@
1009 1009  units: fs (bigger numbers (typically) indicate later arrival times of the electrons).
1010 1010  
1011 1011  
1012 -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}}(%%)
1013 1013  //always saved (PBD)//
1014 -DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.bamError.2
1015 -DAQ channel: FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.BAMERROR.2
1016 -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 !!
1017 1017  
1018 -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}}(%%)
1019 1019  //always saved (PBD)//
1020 -DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.bamStatus.//2//
1021 -DAQ channel: FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.BAMSTATUS.2
1022 -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
1023 1023  
1024 1024  
1025 -
1026 1026  ====== **BAM FL2.SEED5**{{code language="none"}}{{/code}} ======
1027 1027  
1028 1028  /FL2/Electron Diagnostic/BAM/**SEED5**(% style="color:#ff6600" %)/electron bunch arrival time  (HDF5 name not yet implemented - see zraw)
... ... @@ -1047,17 +1047,18 @@
1047 1047  units: fs (bigger numbers (typically) indicate later arrival times of the electrons).
1048 1048  
1049 1049  
1050 -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}}(%%)
1051 1051  //always saved (PBD)//
1052 -DOOCS prop : FLASH.SDIAG/BAM/FL2.SEED5/ARRIVAL_TIME.bamError.2
1053 -DAQ channel: FLASH.SDIAG/BAM/FL2.SEED5/ARRIVAL_TIME.BAMERROR.2
1054 -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 !!
1055 1055  
1056 -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}}(%%)
1057 1057  //always saved (PBD)//
1058 -DOOCS prop : FLASH.SDIAG/BAM/FL2.SEED5/ARRIVAL_TIME.bamStatus.//2//
1059 -DAQ channel: FLASH.SDIAG/BAM/FL2.SEED5/ARRIVAL_TIME.BAMSTATUS.2
1060 -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
1061 1061  
1062 1062  
1063 1063  [[Contents>>doc:||anchor="Contents"]]
... ... @@ -1101,6 +1101,7 @@
1101 1101  DAQ channel: {{code language="none"}}FLASH.DIAG/PBD2.TOROID.ML/3GUN/NUMBEROFBUNCHES.FLASH2{{/code}}
1102 1102  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)
1103 1103  units:
1127 +
1104 1104  
1105 1105  ===== actual pulse pattern recorded after the undulator =====
1106 1106  
... ... @@ -1110,6 +1110,7 @@
1110 1110  DAQ channel: {{code language="none"}}FLASH.DIAG/PBD2.TOROID.ML/9FL2BURN.PULSEPATTERN{{/code}}
1111 1111  desc: The bunch pattern as function of time in a burst recorded by toroide diagnostic BEHIND the undulator. (FLASH2)
1112 1112  units:
1137 +
1113 1113  
1114 1114  ===== Train ID =====
1115 1115  
... ... @@ -1119,40 +1119,26 @@
1119 1119  DAQ channel: {{code language="none"}}none{{/code}}
1120 1120  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 !)
1121 1121  units:
1147 +
1122 1122  
1123 -===== (% style="color:#e67e22" %)Train time(%%) =====
1149 +===== Train time =====
1124 1124  
1125 -(% style="color:#e67e22" %)//always saved (PBD2)//(%%)
1126 -(% style="color:#e67e22" %){{code language="none"}}/Timing/train time{{/code}}
1151 +//always saved (PBD2)//
1152 +{{code language="none"}}/Timing/train time{{/code}}
1127 1127  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
1128 1128  units: d h min s cs
1155 +
1129 1129  
1130 1130  {{code language="none"}}
1131 1131  /Timing/time stamp
1132 1132  {{/code}}
1133 1133  
1134 -(% style="color:#e67e22" %)//always saved (PBD2)//(%%)
1135 -(% 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
1136 1136  second column: microseconds
1137 1137  third column: Train ID of FLASH
1165 +
1138 1138  
1139 -
1140 -(% 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
1141 -
1142 -{{expand expanded="false" title="Timestamp help for python"}}
1143 - import time
1144 -
1145 -# epoch time is found in /zraw/FLASH.DIAG/TIMINGINFO/TIME1.BUNCH_FIRST_INDEX.1/dGroup/time #!!! a leading 1 has to be added !!!
1146 -# 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
1147 -epoch_time = 1709051499.17 # Replace with your epoch time
1148 -
1149 -formatted_time = time.strftime('%Y-%m-%d %H:%M:%S', time.gmtime(epoch_time))
1150 -print(formatted_time)
1151 -{{/expand}}
1152 -
1153 -
1154 -
1155 -
1156 1156  [[Contents>>doc:||anchor="Contents"]]
1157 1157  
1158 1158  
... ... @@ -1166,7 +1166,7 @@
1166 1166  
1167 1167  ===== GHz ADCs =====
1168 1168  
1169 -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]]**
1170 1170  //saved on DEMAND in the user DAQ//
1171 1171  \\Up to now there are 4 channels available at FL24
1172 1172  \\\\{{code language="none"}}/FL2/Experiment/MTCA-EXP1/ADQ412 GHz ADC/CH00/TD{{/code}}
... ... @@ -1201,32 +1201,11 @@
1201 1201  
1202 1202  
1203 1203  
1204 -==== Pump Probe Laser (FLASH2) ====
1215 +==== FL 24 Pump Probe Laser (FLASH2) ====
1205 1205  
1206 -{{info width="30%"}}
1207 -list of saved parameters status May 2024 (up to now the parameters can be found in /zraw/ ... )
1208 -
1209 -[[attach:FSLADAQ-DAQParameterlistULGAN-2.pdf||target="_blank"]]
1210 -
1211 -[[attach:FSLADAQ-DAQParameterlistFL23-2.pdf||target="_blank"]]
1212 -
1213 -[[attach:FSLADAQ-DAQParameterlistFL24-2.pdf||target="_blank"]]
1214 -
1215 -
1216 -{{view-file att--filename="FSLADAQ-DAQParameterlistFL23-2.pdf"}}{{/view-file}}
1217 -
1218 -
1219 -{{view-file att--filename="FSLADAQ-DAQParameterlistFL23-2.pdf"}}{{/view-file}}
1220 -
1221 -
1222 -{{view-file att--filename="FSLADAQ-DAQParameterlistFL24-2.pdf"}}{{/view-file}}
1223 -
1224 -
1225 -{{/info}}
1226 -
1227 -{{expand title="Laser parameters used until 2023"}}
1228 1228  These are the parameters that can be saved in the FL2 User DAQ for the FL2 PP laser//** FOR BEAMLINE FL24**//
1229 1229  
1219 +
1230 1230  **User delay**
1231 1231  
1232 1232  Delay (set value):
... ... @@ -1580,10 +1580,11 @@
1580 1580  )))|(((
1581 1581  FLASH.LASER/ULGAN1.DYNPROP/TCFIBER.DOUBLES/DOUBLE26
1582 1582  )))
1583 -{{/expand}}
1584 1584  
1585 1585  
1575 +[[Contents>>doc:||anchor="Contents"]]
1586 1586  
1577 +
1587 1587  === "/uncategorized/" ===
1588 1588  
1589 1589   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
... ... @@ -1598,6 +1598,7 @@
1598 1598  * 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".
1599 1599  * A number of inconsistent names have been streamlined. The relevant changes are listed in the following table.
1600 1600  
1592 +
1601 1601  (% class="wrapped" %)
1602 1602  |=(((
1603 1603  earlier HDF path (vers. 0.2)
... ... @@ -1695,6 +1695,7 @@
1695 1695  /FL2/Photon Diagnostic/GMD/Pulse resolved beam position/position tunnel vertical
1696 1696  )))
1697 1697  
1690 +
1698 1698  [[Contents>>doc:||anchor="Contents"]]
1699 1699  
1700 1700  
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