Changes for page The FLASH HDF5 structure
Last modified by sndueste on 2025-11-19 14:51
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 9 added, 0 removed)
- FSLADAQ-DAQParameterlistFL23-2.pdf
- FSLADAQ-DAQParameterlistFL24-2.pdf
- FSLADAQ-DAQParameterlistFL24.pdf
- FSLADAQ-DAQParameterlistPPlaser.pdf
- FSLADAQ-DAQParameterlistPiGLET-300424-1356-986.pdf
- FSLADAQ-DAQParameterlistPiGLET.pdf
- FSLADAQ-DAQParameterlistULGAN-2.pdf
- FSLADAQ-FL23.pdf
- Screenshot 2024-05-17 094435.png
Details
- Page properties
-
- Parent
-
... ... @@ -1,0 +1,1 @@ 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 ~[~[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"]]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"]] 14 14 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"]]15 +To download the HDF5 Viewer click [[here>>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,7 +68,6 @@ 68 68 {{layout-cell}} 69 69 * ADC data as example for **fast** **data** (10 Hz): 70 70 71 - 72 72 [[image:attach:image2020-11-16_15-26-28.png||height="250"]] 73 73 {{/layout-cell}} 74 74 ... ... @@ -100,31 +100,33 @@ 100 100 * The currently developed option for large data sets: [[the FAB package>>url:https://hasfcpkg.desy.de/fab/fab.html||shape="rect"]] ... see below 101 101 * 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"]] 102 102 103 -(% class="Object" %)See also the collection of Demo data and sample scripts : [[doc:FLASHUSER.Data Acquisition and controls.D ataAccessatFLASH (DAQ, gpfs,\.\.\.).Offline data analysis (DAQ).Collection of HDF5 sample data from different beamlines.WebHome]] and [[doc:FLASHUSER.Data Acquisition and controls.DataAccessatFLASH (DAQ, gpfs,\.\.\.).Offline data analysis (DAQ).DEMO - Working with FLASH data.WebHome]]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]] 104 104 {{/info}} 105 105 {{/layout-cell}} 106 106 {{/layout-section}} 106 +{{/layout}} 107 107 108 -{{layout-section ac:type="single"}} 109 -{{layout-cell}} 110 - 111 111 109 + 112 112 == Complete list of recordable parameters == 113 113 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 - 112 +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"]]. 116 116 117 117 == Most popular FLASH parameters and their names in HDF5, DOOCS and (raw) DAQ == 118 118 119 119 {{id name="DOOCSparameters"/}} 120 120 121 -Note, the HDF group and data set names apply to our HDF tree version since vers. 0.3.0. 122 122 123 - 124 124 === FLASH1 === 125 125 126 -==== Beamline info (FLASH1) ==== 127 127 122 +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. 123 + 124 +The previously used naming scheme (2024 and before) can be found here: 125 + 126 +{{expand expanded="false" title="FLASH1 Naming scheme used until 2024"}} 127 +==== (% id="cke_bm_8853497S" style="display:none" %) (%%)Beamline info (FLASH1) ==== 128 + 128 128 {{code language="none"}}/FL1/Beamlines/Attenuator/pressure{{/code}} 129 129 //always saved (PBD)// 130 130 DOOCS prop : {{code language="none"}}FLASH.FEL/GAS_DOSING/FL1.ATTENUATOR/PRESSURE{{/code}} ... ... @@ -131,7 +131,6 @@ 131 131 DAQ channel: {{code language="none"}}FLASH.FEL/GAS_DOSING/FL1.ATTENUATOR/PRESSURE{{/code}} 132 132 desc: set pressure in the gas attenuator 133 133 units: mbar 134 - 135 135 136 136 {{code language="none"}}/FL1/Beamlines/BL/Fast shutter/open{{/code}} 137 137 //always saved (PBD)// ... ... @@ -151,17 +151,15 @@ 151 151 //always saved (PBD)// 152 152 DOOCS prop : {{code language="none"}}TTF2.FEL/BLFILTERS1/FILTER1/FW.MOTOR.POS{{/code}} 153 153 DAQ channel: {{code language="none"}}TTF2.FEL/BLFILTERS1/FILTER1/FW.MOTOR.POS{{/code}} 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]] 154 +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]] 155 155 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:FLASHUSER.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:FS-FLASH USER tmp.jddd-linked help pages.Filter-Units.Filter wheels in FLASH1 and FLASH2.WebHome]] 163 163 units: degree 164 - 165 165 166 166 {{code language="none"}}/FL1/Beamlines/PG/Filters/position filter 1{{/code}} 167 167 //always saved (PBD)// ... ... @@ -169,7 +169,6 @@ 169 169 DAQ channel: {{code language="none"}}TTF2.FEL/BDAF1/BDA.F1/FW.MOTOR.POS{{/code}} 170 170 desc: Position of the PG filter wheel 1 171 171 units: degree 172 - 173 173 174 174 {{code language="none"}}/FL1/Beamlines/PG/Filters/position filter 2{{/code}} 175 175 //always saved (PBD)// ... ... @@ -177,7 +177,6 @@ 177 177 DAQ channel: {{code language="none"}}TTF2.FEL/BDAF2/BDA.F2/FW.MOTOR.POS{{/code}} 178 178 desc: Position of the PG filter wheel 2 179 179 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:FLASHUSER.jddd-linked help pages.Calibrating the pulse resolved (electron) data from GMD.WebHome]]** 211 +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]]** 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:FLASHUSER.jddd-linked help pages.Calibrating the pulse resolved (electron) data from GMD.WebHome]]** 218 +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]]** 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:FLASHUSER.jddd-linked help pages.Calibrating the pulse resolved (electron) data from GMD.WebHome]]** 234 +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]]** 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:FLASHUSER.jddd-linked help pages.Calibrating the pulse resolved (electron) data from GMD.WebHome]]** 241 +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]]** 246 246 {{/expand}} 247 247 248 248 ... ... @@ -250,8 +250,8 @@ 250 250 251 251 {{code language="none"}}/FL1/Photon Diagnostic/GMD/Average energy/energy tunnel{{/code}} 252 252 //always saved (PBD)// 253 -(% style="color:#000000" %)DOOCS prop : {{code language="none"}}FLASH.FEL/XGM.PHOTONFLUX/FL1.TUNNEL/PHOTONFLUX.UJ{{/code}} (%%)254 -(% style="color:#000000" %)DAQ channel: {{code language="none"}}FLASH.FEL/XGM.PHOTONFLUX/FL1.TUNNEL/PHOTONFLUX.UJ{{/code}}249 +(% style="color:#000000" %)DOOCS prop : {{code language="none"}}FLASH.FEL/XGM.PHOTONFLUX/FL1.TUNNEL/PHOTONFLUX.UJ{{/code}} (%%) 250 +(% style="color:#000000" %)DAQ channel: {{code language="none"}}FLASH.FEL/XGM.PHOTONFLUX/FL1.TUNNEL/PHOTONFLUX.UJ{{/code}} 255 255 256 256 desc : calibrated average SASE Energy/pulse measured in the TUNNEL upstream the gas attenuator 257 257 units : microJ ... ... @@ -260,15 +260,14 @@ 260 260 {{code language="none"}}/FL1/Photon Diagnostic/GMD/Pulse resolved energy/energy tunnel{{/code}} 261 261 //always saved (PBD)// 262 262 263 -(% style="color:#000000" %)DOOCS prop : 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}} 259 +(% style="color:#000000" %)DOOCS prop : (%%) 260 +(% 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}} 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:FLASHUSER.jddd-linked help pages.Calibrating the pulse resolved (electron) data from GMD.WebHome]]** 263 +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]]** 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 - 272 272 273 273 1. **Intensity per pulse** (a.u. (more or less µJ )) 274 274 1. Intensity per pulse (auxillary GMD) - not used ... ... @@ -282,8 +282,7 @@ 282 282 The pulse energy and the error are plotted for the first bunch of the pulse trains saved in this 283 283 file 284 284 285 - 286 -[[image:attach:image2021-2-9_10-51-6.png||height="250"]] 280 + [[image:image2021-2-9_10-51-6.png]] 287 287 288 288 289 289 {{/info}} ... ... @@ -403,8 +403,8 @@ 403 403 ===== 404 404 arrival time (BAM) ===== 405 405 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"]]400 +{{info title="BAM information: updates 2022 (status 2025)"}} 401 +* 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"]] 408 408 * The data format of the BAM has been completely altered in the 2022 shutdown 409 409 * 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 ... 410 410 * 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) ... ... @@ -412,8 +412,8 @@ 412 412 ** acc: 4DBC3 → FL0.DBC2 413 413 ** FL1: 1SFELC → FL1.SFELC 414 414 ** FL2: FL2XTDS → (% style="color:#172b4d" %)FL2.SEED5 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]] 409 +* for more Info: [[LINK to detailed infos from MSK>>doc:SDiag.How-to articles.BAM Data Structure.WebHome||shape="rect"]] 410 +* [[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]] 417 417 * a recent [[talk about the working principle of the BAM>>attach:BAM-basics and outlook-2018_DESY-template_16-9Format.pdf]] 418 418 {{/info}} 419 419 ... ... @@ -457,9 +457,9 @@ 457 457 458 458 (% style="color:#ff6600" %)DBC2/error (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL1/Electron Diagnostic/BAM/{{/code}}(%%) 459 459 //always saved (PBD)// 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: Ifthevalueis0,theBAMisworkingwell.Ifitisnon-zerothereisaproblem!!454 +DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIM(% style="color:#000000" %)E.bamError.1(%%) 455 +DAQ channel: (% style="color:#000000" %)FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.BAMERROR.1(%%) 456 +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 463 463 464 464 465 465 (% style="color:#ff6600" %)DBC2/status (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL1/Electron Diagnostic/BAM/{{/code}}(%%) ... ... @@ -475,8 +475,8 @@ 475 475 476 476 //always saved (PBD)// 477 477 (% style="color:#172b4d" %)**FL1.SFELC**(%%) 478 -(% style="color:#000000" %)channel: FLASH.SDIAG/BAM/(% style="color:#172b4d" %)FL1.SFELC(% style="color:#000000" %)/ARRIVAL_TIME.ABSOLUTE.SA1.COMP 479 -{{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). 472 +(% style="color:#000000" %)channel: FLASH.SDIAG/BAM/(% style="color:#172b4d" %)FL1.SFELC(% style="color:#000000" %)/ARRIVAL_TIME.ABSOLUTE.SA1.COMP(%%) 473 +(% 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). 480 480 units: fs (bigger numbers (typically) indicate later arrival times of the electrons). 481 481 482 482 ... ... @@ -512,7 +512,6 @@ 512 512 DAQ channel: {{code language="none"}}PBD.BEAM.PROF.ML/DAQ.OUT.PROF.CCCED{{/code}} 513 513 desc: temporal profile of electron bunch, y axis in Ampers (FLASH1) 514 514 units: pixel 515 - 516 516 517 517 {{code language="none"}}/FL1/Electron Diagnostic/Electron bunch profile/Expert stuff/TDS calibration constant{{/code}} 518 518 //always saved (PBD) - IF LOLA is ON and ACTIVATED in the PBD DAQ (talk to expert)// ... ... @@ -520,7 +520,6 @@ 520 520 DAQ channel: = PBD.BEAM.PROF.ML/CCT= 521 521 desc: TDS calibration constant for the x-axis of the profiles: fs per pixel 522 522 units: fs per pixel 523 - 524 524 525 525 {{code language="none"}}/FL1/Electron Diagnostic/Electron bunch profile/TDS profile width rms{{/code}} 526 526 //always saved (PBD) - IF LOLA is ON and ACTIVATED in the PBD DAQ (talk to expert)// ... ... @@ -536,8 +536,7 @@ 536 536 DOOCS prop : {{code language="none"}}TTF2.DAQ/ENERGY.DOGLEG/E_INTRA_MEAN/VAL{{/code}} 537 537 DAQ channel: {{code language="none"}}PBD.ENERGY.DOGLEG/E_MEAN{{/code}} 538 538 desc: electron bunch energy (average over the bunch train) 539 -units: (% class="twikiNewLink" %)MeV(%%) 540 - 531 +units: (% class="twikiNewLink" %)MeV 541 541 542 542 {{code language="none"}}/FL1/Electron Diagnostic/Electron energy/pulse resolved energy{{/code}} 543 543 //always saved (PBD)// ... ... @@ -553,26 +553,27 @@ 553 553 DAQ channel: {{code language="none"}}PBD.ENERGY.DOGLEG/LAMBDA_MEAN{{/code}} 554 554 desc: Wavelength calculated by the electron bunch energy (average over the bunch train) (FLASH1) 555 555 units: nm 556 - 557 557 558 558 [[Contents>>doc:||anchor="Contents"]] 559 559 560 560 551 +==== ==== 552 + 553 + 561 561 ==== Timing information, rep rate etc. (FLASH1) ==== 562 562 563 563 ===== bunch repetition rate ===== 564 564 565 -{{code language="none"}}/ FL1/Timing/repetition rate{{/code}}558 +{{code language="none"}}/Timing/repetition rate{{/code}} 566 566 //always saved (PBD)// 567 567 DOOCS prop : {{code language="none"}}FLASH.DIAG/TIMER/FLASHCPUTIME1.0/REP_RATE_KHZ.1{{/code}} 568 -DAQ channel: {{code language="none"}} TTF2.UTIL/LASER.CONTROL/GUN/PULSE_FREQ{{/code}}561 +DAQ channel: {{code language="none"}}FLASH.DIAG/TIMER/FLASHCPUTIME1.0/REP_RATE_KHZ.1{{/code}} 569 569 desc: repetition rate of the bunches / pulses within the burst (FLASH1) 570 570 units: kHz 571 - 572 572 573 573 ===== set number of pulses ===== 574 574 575 -(% style="color:#ff6600" %)(HDF5 name not yet implemented - see zraw)(% style="color:#ff0000" %){{code language="none"}}/ FL1/Timing/set number of bunches {{/code}}(%%)567 +(% style="color:#ff6600" %)(HDF5 name not yet implemented - see zraw)(% style="color:#ff0000" %){{code language="none"}}/Timing/set number of bunches {{/code}}(%%) 576 576 //always saved (PBD)// 577 577 DOOCS prop : {{code language="none"}}FLASH.DIAG/TIMINGINFO/TIME1.BUNCH_FIRST_INDEX.1 [4th number]{{/code}} 578 578 DAQ channel: {{code language="none"}}FLASH.DIAG/TIMINGINFO/TIME1.BUNCH_FIRST_INDEX.1 [4th number]{{/code}} ... ... @@ -587,7 +587,6 @@ 587 587 DAQ channel: {{code language="none"}}TTF2.DIAG/PBD.TOROID.ML/12EXP{{/code}} 588 588 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) 589 589 units: 590 - 591 591 592 592 ===== actual pulse pattern recorded after the undulator ===== 593 593 ... ... @@ -597,7 +597,6 @@ 597 597 DAQ channel: {{code language="none"}}TTF2.DIAG/PBD.TOROID.ML/12EXP{{/code}} 598 598 desc: The bunch pattern as function of time in a burst recorded by toroid diagnostic BEHIND the undulator. (FLASH1) 599 599 units: 600 - 601 601 602 602 ===== Train ID ===== 603 603 ... ... @@ -607,24 +607,34 @@ 607 607 DAQ channel: {{code language="none"}}none{{/code}} 608 608 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 !) 609 609 units: 610 - 611 611 612 -===== Train time ===== 601 +===== (% style="color:#e67e22" %)Train time(%%) ===== 613 613 614 -{{code language="none"}}/Timing/train time{{/code}} 603 +(% style="color:#e67e22" %){{code language="none"}}/Timing/train time{{/code}} 615 615 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 616 616 units: d h min s cs 617 - 618 618 619 -{{code language="none"}}/Timing/time stamp{{/code}} 607 +(% style="color:#e67e22" %){{code language="none"}}/Timing/time stamp{{/code}} 620 620 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 621 621 second column: microseconds 622 622 third column: Train ID of FLASH 623 - 624 624 625 - [[Contents>>doc:||anchor="Contents"]]612 +currently it is saved as Unix time in : /zraw/FLASH.DIAG/TIMINGINFO/TIME1.BUNCH_FIRST_INDEX.1/dGroup/time 626 626 614 +{{expand expanded="false" title="Timestamp help for python"}} 615 + import time 627 627 617 +# epoch time is found in /zraw/FLASH.DIAG/TIMINGINFO/TIME1.BUNCH_FIRST_INDEX.1/dGroup/time #!!! a leading 1 has to be added !!! 618 +# 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 619 +epoch_time = 1709051499.17 # Replace with your epoch time 620 + 621 +formatted_time = time.strftime('%Y-%m-%d %H:%M:%S', time.gmtime(epoch_time)) 622 +print(formatted_time) 623 +{{/expand}} 624 + 625 + 626 + 627 + 628 628 ==== Pump Probe Laser (FLASH1) ==== 629 629 630 630 **PIGLET (PG laser)** ... ... @@ -631,34 +631,17 @@ 631 631 632 632 **{{code language="none"}}/FL1/Experiment/Pump probe laser{{/code}}** 633 633 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 634 +{{info width="30%"}} 635 +list of saved parameters status May 2024 (up to now the parameters can be found in /zraw/ ... ) 640 640 641 - **BL - Hidralaser**637 +Download the PDF: 642 642 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 +{{view-file att--filename="FSLADAQ-DAQParameterlistPiGLET.pdf"}}{{/view-file}} 661 661 641 + 642 + 643 +{{/info}} 644 + 662 662 {{expand title="Parameters used until 2021"}} 663 663 {{code language="none"}} 664 664 /FL1/Experiment/Pump probe laser/laser attenuation ... ... @@ -715,7 +715,7 @@ 715 715 716 716 ===== GHz ADCs ===== 717 717 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 +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]]** 719 719 //saved on DEMAND in the user DAQ// 720 720 \\The HDF5 names for the ADC traces are depending on the beamline : 721 721 \\PG Beamline: ... ... @@ -757,10 +757,9 @@ 757 757 * {{code language="none"}}number of samples{{/code}}: total number of samples recorded for each 10 Hz trigger 758 758 759 759 [[Contents>>doc:||anchor="Contents"]] 743 +{{/expand}} 760 760 761 761 762 - 763 - 764 764 === FLASH2 === 765 765 766 766 There is analog to FLASH1 a permanently running "PhotonDagnostic DAQ FLASH2" (PBD2) and 2 User DAQs ... ... @@ -768,15 +768,12 @@ 768 768 ==== Beamline info (FLASH2) ==== 769 769 770 770 {{code language="none"}}/FL2/Beamlines/Attenuator/pressure {{/code}} 771 -(% style="color:#000000" %)//always saved (PBD2)// (%%) 772 772 (% style="color:#000000" %)DOOCS prop : {{code language="none"}}FLASH.FEL/ATT.GAS_DOSING/FL2.HALL/PRESSURE{{/code}} (%%) 773 773 (% style="color:#000000" %)DAQ channel: {{code language="none"}}FLASH.FEL/ATT.GAS_DOSING/FL2.HALL/PRESSURE{{/code}} (%%) 774 774 (% style="color:#000000" %)desc: set pressure in the gas attenuator (%%) 775 -(% style="color:#000000" %)units: mbar(%%) 776 - 756 +(% style="color:#000000" %)units: mbar 777 777 778 778 {{code language="none"}}/FL2/Beamlines/FL20/Shutter/open{{/code}} 779 -//always saved (PBD2)// 780 780 DOOCS prop : {{code language="none"}}FLASH.FEL/ADC.SIS.FL2FS/FL20.SHUTTER/CH00.TD{{/code}} 781 781 DAQ channel: {{code language="none"}}FLASH.FEL/ADC.SIS.FL2FS/FL20.SHUTTER{{/code}} 782 782 desc: BL Beamline Fast shutter state: 1 is open, 0 is closed ( for technical reasons there are 100 vales of this state saved ...) ... ... @@ -784,18 +784,15 @@ 784 784 785 785 786 786 {{code language="none"}}/FL2/Beamlines/Filter wheel/position wheel 1{{/code}} 787 -//always saved (PBD2)// 788 788 DOOCS prop : {{code language="none"}}FLASH.FEL/FL20H.PH.MOTOR/MOTOR1.MOT3/FPOS{{/code}} 789 789 DAQ channel: FLASH.FEL/FL20H.PH.MOTOR/MOTOR1.MOT3/FPOS 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]]** 768 +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]]** 791 791 units: degree 792 - 793 793 794 794 /FL2/Beamlines/Filter wheel/position wheel 2 795 -always saved (PBD2) 796 796 DOOCS prop : {{code language="none"}}FLASH.FEL/FL20H.PH.MOTOR/MOTOR2.MOT3/FPOS{{/code}} 797 797 DAQ channel: {{code language="none"}}FLASH.FEL/FL20H.PH.MOTOR/MOTOR2.MOT3/FPOS{{/code}} 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]] 774 +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]] 799 799 units: degree 800 800 801 801 ... ... @@ -808,7 +808,6 @@ 808 808 ==== Photon Diagnostics SASE ([[XGMD>>url:http://photon-science.desy.de/facilities/flash/photon_diagnostics/gmd_intensity_and_position/index_eng.html||shape="rect"]] - FLASH2) ==== 809 809 810 810 {{code language="none"}}/FL2/Photon Diagnostic/GMD/Average energy/energy tunnel{{/code}} 811 -//always saved (PBD2)// 812 812 DOOCS prop : {{code language="none"}}FLASH.FEL/XGM.PHOTONFLUX/FL2.TUNNEL/PHOTONFLUX.UJ{{/code}} 813 813 DAQ channel:{{code language="none"}} FLASH.FEL/XGM.PHOTONFLUX/FL2.TUNNEL/PHOTONFLUX.UJ{{/code}} 814 814 desc : calibrated average ( ~~ 20 sec averaging time ) SASE Energy/pulse measured in the TUNNEL before the attenuator (ion current) ... ... @@ -816,15 +816,13 @@ 816 816 817 817 818 818 {{code language="none"}}/FL2/Photon Diagnostic/GMD/Pulse resolved energy/energy tunnel{{/code}} 819 -//always saved (PBD2)// 820 820 DOOCS prop : {{code language="none"}}FLASH.FEL/XGM.INTENSITY/FL2.TUNNEL/INTENSITY.TD{{/code}} 821 821 DAQ channel: {{code language="none"}}FLASH.FEL/XGM.INTENSITY/FL2.TUNNEL/INTENSITY.TD{{/code}} 822 822 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) 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]]** 797 +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]]** 824 824 825 825 {{info title="GMD pulse resolved data structure"}} 826 826 For every pulse in the pulse train the information is saved: 827 - 828 828 829 829 1. **Intensity per pulse** (a.u. (more or less µJ )) 830 830 1. Intensity per pulse (auxillary GMD) - not used ... ... @@ -852,7 +852,6 @@ 852 852 853 853 854 854 {{code language="none"}}/FL2/Photon Diagnostic/GMD/Average Beam position/position tunnel horizontal{{/code}} 855 -//always saved (PBD2)// 856 856 DOOCS prop : {{code language="none"}}FLASH.FEL/XGM.POSMON/FL2.TUNNEL/IX.POS{{/code}} 857 857 DAQ channel: {{code language="none"}}FLASH.FEL/XGM.POSMON/FL2.TUNNEL/IX.POS{{/code}} 858 858 desc : the Average ( ~~ 20 sec averaging time ) Beam position of the photon Beam determined by the GMD (tunnel, x=horizontal) ... ... @@ -860,7 +860,6 @@ 860 860 861 861 862 862 {{code language="none"}}/FL2/Photon Diagnostic/GMD/Average Beam position/position tunnel vertical{{/code}} 863 -//always saved (PBD2)// 864 864 DOOCS prop : {{code language="none"}}FLASH.FEL/XGM.POSMON/FL2.TUNNEL/IY.POS{{/code}} 865 865 DAQ channel: {{code language="none"}}FLASH.FEL/XGM.POSMON/FL2.TUNNEL/IY.POS{{/code}} 866 866 desc : the Average ( ~~ 20 sec averaging time ) Beam position of the photon Beam determined by the GMD (tunnel, x=horizontal) ... ... @@ -868,7 +868,6 @@ 868 868 869 869 870 870 /FL2/Photon Diagnostic/GMD/Pulse resolved beam position/position tunnel x 871 -always saved (PBD2) 872 872 DOOCS prop : FLASH.FEL/XGM.BPM/FL2.HALL/X.TD 873 873 DAQ channel: FLASH.FEL/XGM.BPM/FL2.HALL:2 874 874 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 ...) ... ... @@ -888,7 +888,6 @@ 888 888 889 889 890 890 {{code language="none"}}/FL2/Photon Diagnostic/Wavelength/OPIS tunnel/Processed/mean photon energy{{/code}} 891 -// saved opon request (PBD2)// 892 892 DOOCS prop : {{code language="none"}}FLASH.UTIL/STORE/FL2.TUNNEL.OPIS/VAL042{{/code}} 893 893 DAQ channel:{{code language="none"}} FLASH.UTIL/STORE/FL2.TUNNEL.OPIS/VAL042{{/code}} 894 894 desc : mean photon energy ( ~~ 1 sec averaging time ) measured in the TUNNEL for a specific bunch out of the bunch train (via photoelectron spectroscopy) ... ... @@ -896,7 +896,6 @@ 896 896 897 897 898 898 {{code language="none"}}/FL2/Photon Diagnostic/Wavelength/OPIS tunnel/Processed/mean wavelength{{/code}} 899 -// saved opon request (PBD2)// 900 900 DOOCS prop : {{code language="none"}}FLASH.UTIL/STORE/FL2.TUNNEL.OPIS/VAL040{{/code}} 901 901 DAQ channel:{{code language="none"}} FLASH.UTIL/STORE/FL2.TUNNEL.OPIS/VAL040{{/code}} 902 902 desc : mean wavelength ( ~~ 1 sec averaging time ) measured in the TUNNEL for a specific bunch out of the bunch train (via photoelectron spectroscopy) ... ... @@ -904,7 +904,6 @@ 904 904 905 905 906 906 {{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}} 907 -// saved opon request (PBD2)// 908 908 DOOCS prop : {{code language="none"}}FLASH.UTIL/STORE/FL2.TUNNEL.OPIS/VAL060{{/code}} 909 909 DAQ channel:{{code language="none"}} FLASH.UTIL/STORE/FL2.TUNNEL.OPIS/VAL060{{/code}} 910 910 desc : The bunch number of the bunch used for the wavelength calculation ... ... @@ -923,7 +923,6 @@ 923 923 ===== bunch charge ===== 924 924 925 925 {{code language="none"}}/FL2/Electron Diagnostic/Bunch charge/after undulator{{/code}} 926 -//always saved (PBD2)// 927 927 DOOCS prop : {{code language="none"}}FLASH.DIAG/PBD2.TOROID.ML/9FL2BURN/CHARGE.FLASH2{{/code}} 928 928 DAQ channel: {{code language="none"}}FLASH.DIAG/PBD2.TOROID.ML/9FL2BURN/CHARGE.FLASH2{{/code}} 929 929 desc: electron bunch charge FLASH2 (average value for each bunchtrain). ... ... @@ -933,7 +933,6 @@ 933 933 ===== electron bunch energy ===== 934 934 935 935 {{code language="none"}}/FL2/Electron Diagnostic/Electron energy/energy of first bunch/behind undulators{{/code}} 936 -//always saved (PBD2)// 937 937 DOOCS prop : {{code language="none"}}FLASH.DIAG/BEAM_ENERGY_MEASUREMENT/FL2XTDS/ENERGY.FLASH2{{/code}} 938 938 DAQ channel: (% style="color:#5e6c84" %)TTF2.DAQ/PBD2.BEAM.ENERGY.MEAS.ML.COPY/FL2XTDS.ENERGY.FLASH2{{code language="none"}}{{/code}}(%%) 939 939 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 ... ... @@ -941,11 +941,10 @@ 941 941 (% style="letter-spacing:0.0px" %)units: (% class="twikiNewLink" %)MeV 942 942 943 943 944 -(% style="color: rgb(94,108,132);font-weight: 600;letter-spacing: 0 .0px;" %)945 -undulator settings 909 +(% style="color: rgb(94, 108, 132); font-weight: 600; letter-spacing: 0px;" %) 910 +===== undulator settings ===== 946 946 947 947 {{code language="none"}}/FL2/Electron Diagnostic/Undulator setting/set wavelength{{/code}} 948 -//always saved (PBD2)// 949 949 DOOCS prop : {{code language="none"}}TTF2.FEEDBACK/FL2.WAVELENGTHCONTROL/FLASH2/WAVELENGTH{{/code}} 950 950 DAQ channel: {{code language="none"}}TTF2.FEEDBACK/FL2.WAVELENGTHCONTROL/FLASH2/WAVELENGTH{{/code}} 951 951 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 % ... ... ... @@ -952,7 +952,6 @@ 952 952 units: nm 953 953 954 954 {{code language="none"}}/FL2/Electron Diagnostic/Undulator setting/SASE14 gap{{/code}} 955 -//always saved (PBD2)// 956 956 DOOCS prop : {{code language="none"}}FLASH.UTIL/FL2.UND.MOTOR/FL2SASE14/GAP{{/code}} 957 957 DAQ channel: {{code language="none"}}FLASH.UTIL/FL2.UND.MOTOR/FL2SASE14/GAP{{/code}} 958 958 desc: gap value of the undulators. This can be used to follow up how many undulators were closed and if there was a taper ... ... @@ -963,17 +963,17 @@ 963 963 ===== 964 964 arrival time (BAM) ===== 965 965 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"]]929 +{{info title="BAM information: updates 2022 (status 2025)"}} 930 +* 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"]] 968 968 * The data format of the BAM has been completely altered in the 2022 shutdown 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 ... 932 +* 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 ... 970 970 * 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) 971 971 * There has been also a renaming (and relocation) of the BAMs. 972 972 ** acc: 4DBC3 → FL0.DBC2 973 973 ** FL1: 1SFELC → FL1.SFELC 974 -** FL2: 8FL2XTDS → (% style="color:#172b4d" %)FL2.SEED5975 -* 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]] 937 +** FL2: FL2XTDS → (% style="color:#172b4d" %)FL2.SEED5 938 +* for more Info: [[LINK to detailed infos from MSK>>doc:SDiag.How-to articles.BAM Data Structure.WebHome||shape="rect"]] 939 +* [[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]] 977 977 * a recent [[talk about the working principle of the BAM>>attach:BAM-basics and outlook-2018_DESY-template_16-9Format.pdf]] 978 978 {{/info}} 979 979 ... ... @@ -994,12 +994,11 @@ 994 994 desc: Electron bunch arrival time measured with the BAM in the accelerator (pulse resolved data) 995 995 units: ps (bigger numbers indicate later arrivaltime of the electrons) 996 996 997 -{{info title=" 998 -BAM hints"}} 960 +{{info title="BAM hints"}} 999 999 * The BAM 4DBC3 measures the arrivaltime of** FLASH 1 and FLASH2** in the same data set (thus also sorted in at /FL1/ !). 1000 1000 * 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 1001 1001 ** 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 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]] 964 +* [[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]] 1003 1003 * [[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"]] 1004 1004 * a recent [[talk about the working principle of the BAM>>attach:BAM-basics and outlook-2018_DESY-template_16-9Format.pdf]] 1005 1005 {{/info}} ... ... @@ -1031,20 +1031,20 @@ 1031 1031 units: fs (bigger numbers (typically) indicate later arrival times of the electrons). 1032 1032 1033 1033 1034 -(% style="color:#f f6600" %)DBC2/error(HDF5 name not yet implemented - see zraw){{code language="none"}}/FL2/Electron Diagnostic/BAM/{{/code}}(%%)996 +DBC2/error (% style="color:#f39c12" %)(HDF5 name not yet implemented - see zraw)(%%)/FL2/Electron Diagnostic/BAM/ 1035 1035 //always saved (PBD)// 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 !!998 +DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.bamError.2 999 +DAQ channel: FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.BAMERROR.2 1000 +desc: If the value is 0 , the BAM is working well. If it is non-zero there is a problem !! 1039 1039 1040 - 1041 -(% style="color:#ff6600" %)DBC2/status (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL2/Electron Diagnostic/BAM/{{/code}}(%%) 1002 +DBC2/status (% style="color:#e67e22" %)(HDF5 name not yet implemented - see zraw)(%%)/FL2/Electron Diagnostic/BAM/ 1042 1042 //always saved (PBD)// 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 sufficient1004 +DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.bamStatus.//2// 1005 +DAQ channel: FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.BAMSTATUS.2 1006 +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 1046 1046 1047 1047 1009 + 1048 1048 ====== **BAM FL2.SEED5**{{code language="none"}}{{/code}} ====== 1049 1049 1050 1050 /FL2/Electron Diagnostic/BAM/**SEED5**(% style="color:#ff6600" %)/electron bunch arrival time (HDF5 name not yet implemented - see zraw) ... ... @@ -1069,18 +1069,17 @@ 1069 1069 units: fs (bigger numbers (typically) indicate later arrival times of the electrons). 1070 1070 1071 1071 1072 - (% style="color:#172b4d" %)SEED5(% style="color:#ff6600" %)/error(HDF5 name not yet implemented - see zraw){{code language="none"}}/FL2/Electron Diagnostic/BAM/{{/code}}(%%)1034 +FL2.SEED5/error (% style="color:#f39c12" %)(HDF5 name not yet implemented - see zraw)(%%)/FL2/Electron Diagnostic/BAM/ 1073 1073 //always saved (PBD)// 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 !!1036 +DOOCS prop : FLASH.SDIAG/BAM/FL2.SEED5/ARRIVAL_TIME.bamError.2 1037 +DAQ channel: FLASH.SDIAG/BAM/FL2.SEED5/ARRIVAL_TIME.BAMERROR.2 1038 +desc: If the value is 0 , the BAM is working well. If it is non-zero there is a problem !! 1077 1077 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}}(%%) 1040 +FL2.SEED5/status (% style="color:#e67e22" %)(HDF5 name not yet implemented - see zraw)(%%)/FL2/Electron Diagnostic/BAM/ 1080 1080 //always saved (PBD)// 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 sufficient1042 +DOOCS prop : FLASH.SDIAG/BAM/FL2.SEED5/ARRIVAL_TIME.bamStatus.//2// 1043 +DAQ channel: FLASH.SDIAG/BAM/FL2.SEED5/ARRIVAL_TIME.BAMSTATUS.2 1044 +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 1084 1084 1085 1085 1086 1086 [[Contents>>doc:||anchor="Contents"]] ... ... @@ -1124,7 +1124,6 @@ 1124 1124 DAQ channel: {{code language="none"}}FLASH.DIAG/PBD2.TOROID.ML/3GUN/NUMBEROFBUNCHES.FLASH2{{/code}} 1125 1125 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) 1126 1126 units: 1127 - 1128 1128 1129 1129 ===== actual pulse pattern recorded after the undulator ===== 1130 1130 ... ... @@ -1134,7 +1134,6 @@ 1134 1134 DAQ channel: {{code language="none"}}FLASH.DIAG/PBD2.TOROID.ML/9FL2BURN.PULSEPATTERN{{/code}} 1135 1135 desc: The bunch pattern as function of time in a burst recorded by toroide diagnostic BEHIND the undulator. (FLASH2) 1136 1136 units: 1137 - 1138 1138 1139 1139 ===== Train ID ===== 1140 1140 ... ... @@ -1144,26 +1144,40 @@ 1144 1144 DAQ channel: {{code language="none"}}none{{/code}} 1145 1145 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 !) 1146 1146 units: 1147 - 1148 1148 1149 -===== Train time ===== 1107 +===== (% style="color:#e67e22" %)Train time(%%) ===== 1150 1150 1151 -//always saved (PBD2)// 1152 -{{code language="none"}}/Timing/train time{{/code}} 1109 +(% style="color:#e67e22" %)//always saved (PBD2)//(%%) 1110 +(% style="color:#e67e22" %){{code language="none"}}/Timing/train time{{/code}} 1153 1153 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 1154 1154 units: d h min s cs 1155 - 1156 1156 1157 1157 {{code language="none"}} 1158 1158 /Timing/time stamp 1159 1159 {{/code}} 1160 1160 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 1118 +(% style="color:#e67e22" %)//always saved (PBD2)//(%%) 1119 +(% 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 1163 1163 second column: microseconds 1164 1164 third column: Train ID of FLASH 1165 - 1166 1166 1123 + 1124 +(% 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 1125 + 1126 +{{expand expanded="false" title="Timestamp help for python"}} 1127 + import time 1128 + 1129 +# epoch time is found in /zraw/FLASH.DIAG/TIMINGINFO/TIME1.BUNCH_FIRST_INDEX.1/dGroup/time #!!! a leading 1 has to be added !!! 1130 +# 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 1131 +epoch_time = 1709051499.17 # Replace with your epoch time 1132 + 1133 +formatted_time = time.strftime('%Y-%m-%d %H:%M:%S', time.gmtime(epoch_time)) 1134 +print(formatted_time) 1135 +{{/expand}} 1136 + 1137 + 1138 + 1139 + 1167 1167 [[Contents>>doc:||anchor="Contents"]] 1168 1168 1169 1169 ... ... @@ -1177,7 +1177,7 @@ 1177 1177 1178 1178 ===== GHz ADCs ===== 1179 1179 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]]** 1153 +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]]** 1181 1181 //saved on DEMAND in the user DAQ// 1182 1182 \\Up to now there are 4 channels available at FL24 1183 1183 \\\\{{code language="none"}}/FL2/Experiment/MTCA-EXP1/ADQ412 GHz ADC/CH00/TD{{/code}} ... ... @@ -1212,11 +1212,32 @@ 1212 1212 1213 1213 1214 1214 1215 -==== FL 24Pump Probe Laser (FLASH2) ====1188 +==== Pump Probe Laser (FLASH2) ==== 1216 1216 1217 -These are the parameters that can be saved in the FL2 User DAQ for the FL2 PP laser//** FOR BEAMLINE FL24**// 1190 +{{info width="30%"}} 1191 +list of saved parameters status May 2024 (up to now the parameters can be found in /zraw/ ... ) 1218 1218 1193 +[[attach:FSLADAQ-DAQParameterlistULGAN-2.pdf||target="_blank"]] 1219 1219 1195 +[[attach:FSLADAQ-DAQParameterlistFL23-2.pdf||target="_blank"]] 1196 + 1197 +[[attach:FSLADAQ-DAQParameterlistFL24-2.pdf||target="_blank"]] 1198 + 1199 + 1200 +{{view-file att--filename="FSLADAQ-DAQParameterlistFL23-2.pdf"}}{{/view-file}} 1201 + 1202 + 1203 +{{view-file att--filename="FSLADAQ-DAQParameterlistFL23-2.pdf"}}{{/view-file}} 1204 + 1205 + 1206 +{{view-file att--filename="FSLADAQ-DAQParameterlistFL24-2.pdf"}}{{/view-file}} 1207 + 1208 + 1209 +{{/info}} 1210 + 1211 +{{expand title="Laser parameters used until 2023"}} 1212 +These are the parameters that can be saved in the FL2 User DAQ for the FL2 PP laser//** FOR BEAMLINE FL24**// 1213 + 1220 1220 **User delay** 1221 1221 1222 1222 Delay (set value): ... ... @@ -1570,11 +1570,10 @@ 1570 1570 )))|((( 1571 1571 FLASH.LASER/ULGAN1.DYNPROP/TCFIBER.DOUBLES/DOUBLE26 1572 1572 ))) 1567 +{{/expand}} 1573 1573 1574 1574 1575 -[[Contents>>doc:||anchor="Contents"]] 1576 1576 1577 - 1578 1578 === "/uncategorized/" === 1579 1579 1580 1580 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 ... ... @@ -1589,7 +1589,6 @@ 1589 1589 * 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". 1590 1590 * A number of inconsistent names have been streamlined. The relevant changes are listed in the following table. 1591 1591 1592 - 1593 1593 (% class="wrapped" %) 1594 1594 |=((( 1595 1595 earlier HDF path (vers. 0.2) ... ... @@ -1687,10 +1687,4 @@ 1687 1687 /FL2/Photon Diagnostic/GMD/Pulse resolved beam position/position tunnel vertical 1688 1688 ))) 1689 1689 1690 - 1691 1691 [[Contents>>doc:||anchor="Contents"]] 1692 - 1693 - 1694 -{{/layout-cell}} 1695 -{{/layout-section}} 1696 -{{/layout}}
- FSLADAQ-DAQParameterlistFL23-2.pdf
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.rangeadm - Size
-
... ... @@ -1,0 +1,1 @@ 1 +32.1 KB - Content
- FSLADAQ-DAQParameterlistFL24-2.pdf
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.rangeadm - Size
-
... ... @@ -1,0 +1,1 @@ 1 +37.6 KB - Content
- FSLADAQ-DAQParameterlistFL24.pdf
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.rangeadm - Size
-
... ... @@ -1,0 +1,1 @@ 1 +37.2 KB - Content
- FSLADAQ-DAQParameterlistPPlaser.pdf
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.rangeadm - Size
-
... ... @@ -1,0 +1,1 @@ 1 +33.9 KB - Content
- FSLADAQ-DAQParameterlistPiGLET-300424-1356-986.pdf
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.rangeadm - Size
-
... ... @@ -1,0 +1,1 @@ 1 +157.0 KB - Content
- FSLADAQ-DAQParameterlistPiGLET.pdf
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.rangeadm - Size
-
... ... @@ -1,0 +1,1 @@ 1 +157.0 KB - Content
- FSLADAQ-DAQParameterlistULGAN-2.pdf
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.rangeadm - Size
-
... ... @@ -1,0 +1,1 @@ 1 +34.8 KB - Content
- FSLADAQ-FL23.pdf
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.rangeadm - Size
-
... ... @@ -1,0 +1,1 @@ 1 +28.6 KB - Content
- Screenshot 2024-05-17 094435.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.rangeadm - Size
-
... ... @@ -1,0 +1,1 @@ 1 +172.4 KB - Content