Changes for page The FLASH HDF5 structure
Last modified by sndueste on 2025/02/06 10:55
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -21,7 +21,7 @@ 21 21 22 22 or you can use 23 23 24 -{{code language="none"}}> sil x view{{/code}}24 +{{code language="none"}}> silix{{/code}} 25 25 26 26 \\ 27 27 ... ... @@ -79,9 +79,9 @@ 79 79 {{/layout-cell}} 80 80 81 81 {{layout-cell}} 82 -* The //average// FEL pulse energy as example for the **slow** **data** .Here thedatais not saved with 10 Hz - thus notfor every FEL pulse train. The data is typically saved with 1 Hz ifthevalues arechanging (liketheFELenergy) and every about 20 sec if there is no change for longer time ( e.g.motorset values)82 +* The //average// FEL pulse energy as example for the **slow** **data** (different e.g. 1 Hz): 83 83 84 - ( asexample only every 10th train ID is listed in the HDF group "index")84 + ( every 10th train ID is listed in the HDF group "index") 85 85 86 86 \\ 87 87 ... ... @@ -103,12 +103,12 @@ 103 103 104 104 {{layout-section ac:type="single"}} 105 105 {{layout-cell}} 106 -{{info}} 107 -=== Reference implementation (Python) === 106 +{{info title="Sample scripts in python"}} 107 +=== Sample scripts / Reference implementation (Python) === 108 108 109 - (imperative) (% class="Object" %)[[https:~~/~~/gitlab.desy.de/christopher.passow/flash-daq-hdf>>url:https://gitlab.desy.de/christopher.passow/flash-daq-hdf||shape="rect"]]109 +[[~[~[image:attach:binder_badge.png~|~|thumbnail="true" width="120"~]~]>>url:https://mybinder.org/v2/git/https%3A%2F%2Fgitlab.desy.de%2Fchristopher.passow%2Fflash-daq-hdf/master||shape="rect"]] 110 110 111 -(% class="Object" %) (object oriented)[[https:~~/~~/gitlab.desy.de/christopher.passow/fdh-builder>>url:https://gitlab.desy.de/christopher.passow/fdh-builder.git||shape="rect"]]111 +(% class="Object" %)[[https:~~/~~/gitlab.desy.de/christopher.passow/flash-daq-hdf>>url:https://gitlab.desy.de/christopher.passow/flash-daq-hdf||shape="rect"]] 112 112 {{/info}} 113 113 {{/layout-cell}} 114 114 {{/layout-section}} ... ... @@ -115,8 +115,6 @@ 115 115 116 116 {{layout-section ac:type="single"}} 117 117 {{layout-cell}} 118 - 119 - 120 120 == Complete list of recordable parameters == 121 121 122 122 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~|~|width="13" height="12"~]~]>>url:https://stash.desy.de/projects/CS/repos/pah/browse/src/camp/data/channel2HdfName.dat||shape="rect"]]. ... ... @@ -208,7 +208,8 @@ 208 208 209 209 ==== Photon Diagnostics SASE ([[GMD>>url:http://photon-science.desy.de/facilities/flash/photon_diagnostics/gmd_intensity_and_position/index_eng.html||shape="rect"]]) ==== 210 210 211 -{{expand title="Discontinued GMD format (used until 2021)"}} 209 +\\ 210 + 212 212 (% style="color: rgb(0,0,0);" %)**Discontinued GMD data recording / evaluation (VME + PhotonFlux ML server)** 213 213 214 214 {{code language="none"}}/FL1/Photon Diagnostic/GMD/Average energy/energy tunnel{{/code}} ... ... @@ -256,11 +256,10 @@ 256 256 DAQ channel: {{code language="none"}}PBD.PHFLUX/BDA.ENERGYPULSE.FF{{/code}} 257 257 desc :Energy per pulse BDA (from e-) - uncorrected values. There are also values saved if there was no beam ... just background noise 258 258 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]]** 259 -{{/expand}} 260 260 261 261 \\ 262 262 263 -(% style=" letter-spacing: 0px; color: rgb(0,since2021) GMD data recording / evaluation (sameformatasFLASH2 and XFEL)**261 +(% style="color: rgb(0,0,0);" %)**NEW (2021) GMD data recording / evaluation (MTCA, analog to FLASH2 and XFEL)** 264 264 265 265 {{code language="none"}}/FL1/Photon Diagnostic/GMD/Average energy/energy tunnel{{/code}} 266 266 //always saved (PBD)// ... ... @@ -418,27 +418,8 @@ 418 418 units: nC 419 419 420 420 ===== 421 -arrival time (BAM)=====419 +arrival time ===== 422 422 423 -{{info title="BAM information: updates 2022"}} 424 -* 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"]] 425 -* The data format of the BAM has been completely altered in the 2022 shutdown 426 -* 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 ... 427 -* 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) 428 -* There has been also a renaming (and relocation) of the BAMs. 429 -** acc: 4DBC3 → FL0.DBC2 430 -** FL1: 1SFELC → FL1.SFELC 431 -** FL2: FL2XTDS → (% style="color: rgb(23,43,77);" %)FL2.SEED5 432 -* for more Info: [[LINK to detailed infos from MSK>>url:https://confluence.desy.de/display/SDiagPublic/BAM+Data+Structure||shape="rect"]] 433 -* [[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]] 434 -* a recent [[talk about the working principle of the BAM>>attach:BAM-basics and outlook-2018_DESY-template_16-9Format.pdf]] 435 -{{/info}} 436 - 437 -\\ 438 - 439 -{{expand title="Discontinued BAM format (used until end 2021)"}} 440 -(% style="color: rgb(0,0,0);" %)**Discontinued BAM data recording ** 441 - 442 442 {{code language="none"}}/FL1/Electron Diagnostic/BAM/4DBC3/electron bunch arrival time (low charge){{/code}} 443 443 //always saved (PBD)// 444 444 DOOCS prop : {{code language="none"}}FLASH.SDIAG/BAM/4DBC3/LOW_CHARGE_ARRIVAL_TIME{{/code}} ... ... @@ -446,94 +446,22 @@ 446 446 desc: Electron bunch arrival time measured with the BAM inside the accelerator - however shows a very good correlation to the arrivaltime of the XUV pulses in the experiment (pulse resolved data). 447 447 units: ps (bigger numbers indicate later arrivaltime of the electrons) 448 448 449 -\\ 450 - 451 451 {{code language="none"}}/FL1/Electron Diagnostic/BAM/1SFELC/electron bunch arrival time (low charge){{/code}} 452 452 //always saved (PBD)// 453 453 DOOCS prop : {{code language="none"}}FLASH.SDIAG/BAM/1SFELC/LOW_CHARGE_ARRIVAL_TIME{{/code}} 454 454 DAQ channel: {{code language="none"}}FLASH.SDIAG/BAM.DAQ/1SFELC.LOW_CHARGE_ARRIVAL_TIME{{/code}} 455 455 desc: Electron bunch arrival time measured with the BAM before the undulator (pulse resolved data). This one was newly installed in 2020. 456 -units: ps (bigger numbers indicate later arrival time of the electrons) 457 -{{/expand}} 433 +units: ps (bigger numbers indicate later arrivaltime of the electrons) 458 458 459 -====== **BAM FL0.DBC2**{{code language="none"}}{{/code}} ====== 435 +{{info title="BAM hints"}} 436 +* besides the arrivaltime from FLASH1 there is also the FLASH2/3 electron arrival time saved.In case of doubt ask your local contact 437 +* [[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]] 438 +* [[LINK to detailed infos from MSK (may only work inside DESY network~[~[image:url:http://hasfweb.desy.de/pub/TWiki/TWikiDocGraphics/external-link.gif~|~|width="13" height="12"~]~]>>url:http://www.desy.de/~~mbock/pages/BAM_daq_channel_descriptions.html||shape="rect"]] 439 +* a recent [[talk about the working principle of the BAM>>attach:BAM-basics and outlook-2018_DESY-template_16-9Format.pdf]] 440 +{{/info}} 460 460 461 -(% style="color: rgb(255,102,0);" %)**DBC2**/electron bunch arrival time (HDF5 name not yet implemented - see zraw)(%%) 462 -//always saved (PBD)// 463 -**FL0.DBC2** 464 -(% style="color: rgb(0,0,0);" %)channel: FLASH.SDIAG/BAM/**FL0.DBC2**/ARRIVAL_TIME.ABSOLUTE.SA1.COMP (%%) 465 -{{code language="none"}}/FL1/Electron Diagnostic/BAM/ DOOCS prop : FLASH.SDIAG/BAM//ARRIVAL_TIME.ABSOLUTE.SA1.COMPDAQ desc: Electron bunch arrival time measured with the BAM inside the accelerator (after bunch compressor 2). The property contains only the arrival time of the bunches sent to FL1 (e.g. if there are 30 bunches in FL1 the first 30 values are the arrival time the remaining numbers should be only 0). These are the same values as the "raw" data below - just "cleaned". The values{{/code}}(% style="font-family: SFMono-Medium , ~"SF Mono~" , ~"Segoe UI Mono~" , ~"Roboto Mono~" , ~"Ubuntu Mono~" , Menlo , Courier , monospace;letter-spacing: 0.0px;" %) show a very good correlation to the arrival time of the XUV pulses in the experiment (see help). 466 - 467 -{{code language="none"}}units: fs (bigger numbers (typically) indicate later arrival times of the electrons).{{/code}} 468 - 469 469 \\ 470 470 471 -(% style="color: rgb(255,102,0);" %)DBC2/electron bunch arrival time (raw) (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL1/Electron Diagnostic/BAM/{{/code}}(%%) 472 -//always saved (PBD)// 473 -DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.ABSOLUTE 474 -DAQ channel: (% style="color: rgb(0,0,0);" %)FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.ABSOLUTE (%%) 475 -desc: Electron bunch arrival time measured with the BAM inside the accelerator (after bunch compressor 2). Here the complete bunch train from the FEL is recorded (FLASH1 and FLASH2 pulses). Thus there are values from FLASH 1 in the first part. they may be separated by several "0" values if the reprate is different from 1 MHz ... - It shows a very good correlation to the arrival time of the XUV pulses in the experiment (see help). 476 -units: fs (bigger numbers (typically) indicate later arrival times of the electrons). 477 - 478 -\\ 479 - 480 -(% style="color: rgb(255,102,0);" %)DBC2/error (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL1/Electron Diagnostic/BAM/{{/code}}(%%) 481 -//always saved (PBD)// 482 -DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIM(% style="color: rgb(0,0,0);" %)E.bamError(%%) 483 -DAQ channel: (% style="color: rgb(0,0,0);" %)FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.BAMERROR(%%) 484 -desc: If the value is 0 , the BAM is working well. If it is non-zero there is a problem !! 485 - 486 -\\ 487 - 488 -(% style="color: rgb(255,102,0);" %)DBC2/status (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL1/Electron Diagnostic/BAM/{{/code}}(%%) 489 -//always saved (PBD)// 490 -DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIM(% style="color: rgb(0,0,0);" %)E..bamStatus.//1//(%%) 491 -DAQ channel(% style="color: rgb(0,0,0);" %): FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.BAMSTATUS.1(%%) 492 -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 493 - 494 -\\ 495 - 496 -====== **BAM FL1.SFELC**{{code language="none"}}{{/code}} ====== 497 - 498 -(% style="font-family: SFMono-Medium , ~"SF Mono~" , ~"Segoe UI Mono~" , ~"Roboto Mono~" , ~"Ubuntu Mono~" , Menlo , Courier , monospace;letter-spacing: 0.0px;" %)/FL1/Electron Diagnostic/BAM/**SFELC**(% style="color: rgb(255,102,0);" %)/electron bunch arrival time (HDF5 name not yet implemented - see zraw) 499 - 500 -//always saved (PBD)// 501 -(% style="color: rgb(23,43,77);" %)**FL1.SFELC**(%%) 502 -(% style="color: rgb(0,0,0);" %)channel: FLASH.SDIAG/BAM/(% style="color: rgb(0, 0, 0); color: rgb(23, 43, 77)" %)FL1.SFELC(% style="color: rgb(0,0,0);" %)/ARRIVAL_TIME.ABSOLUTE.SA1.COMP 503 -{{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 should be only 0). 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). 504 -units: fs (bigger numbers (typically) indicate later arrival times of the electrons). 505 - 506 -\\ 507 - 508 -\\ 509 - 510 -(% style="color: rgb(23,43,77);" %)SFELC(% style="color: rgb(255,102,0);" %)/electron bunch arrival time (raw) (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL1/Electron Diagnostic/BAM/{{/code}}(%%) 511 -//always saved (PBD)// 512 -DOOCS prop : FLASH.SDIAG/BAM/(% style="color: rgb(23,43,77);" %)FL1.SFELC(%%)/ARRIVAL_TIME.ABSOLUTE 513 -DAQ channel:** **(% style="color: rgb(0,0,0);" %)FLASH.SDIAG/BAM/FL1.SFELC/ARRIVAL_TIME.ABSOLUTE (%%) 514 -desc: Electron bunch arrival time measured with the BAM before the undulator (pulse resolved data). This one was newly installed in 2020. Here the complete bunch train from the FEL is recorded (FLASH1 and FLASH2 pulses). Thus there are values from FLASH 1 in the first part. they may be separated by several "0" values if the reprate is different from 1 MHz ... - It shows a very good correlation to the arrival time of the XUV pulses in the experiment (see help). 515 -units: fs (bigger numbers (typically) indicate later arrival times of the electrons). 516 - 517 -\\ 518 - 519 -(% style="color: rgb(23,43,77);" %)SFELC(% style="color: rgb(255,102,0);" %)/error (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL1/Electron Diagnostic/BAM/{{/code}}(%%) 520 -//always saved (PBD)// 521 -DOOCS prop : FLASH.SDIAG/BAM/(% style="color: rgb(23,43,77);" %)FL1.SFELC(%%)/ARRIVAL_TIM(% style="color: rgb(0,0,0);" %)E.bamError(%%) 522 -DAQ channel(% style="color: rgb(0,0,0);" %): FLASH.SDIAG/BAM/FL1.SFELC/ARRIVAL_TIME.BAMERROR(%%) 523 -desc: If the value is 0 , the BAM is working well. If it is non-zero there is a problem !! 524 - 525 -\\ 526 - 527 -(% style="color: rgb(23,43,77);" %)SFELC(% style="color: rgb(255,102,0);" %)/status (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL1/Electron Diagnostic/BAM/{{/code}}(%%) 528 -//always saved (PBD)// 529 -DOOCS prop : FLASH.SDIAG/BAM/(% style="color: rgb(23,43,77);" %)FL1.SFELC(%%)/ARRIVAL_TIM(% style="color: rgb(0,0,0);" %)E..bamStatus.//1//(%%) 530 -DAQ chann(% style="color: rgb(0,0,0);" %)el: FLASH.SDIAG/BAM/FL1.SFELC/ARRIVAL_TIME.BAMSTATUS.1(%%) 531 -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 532 - 533 -\\ 534 - 535 -\\ 536 - 537 537 ===== electron beam profile ===== 538 538 539 539 {{code language="none"}}/FL1/Electron Diagnostic/Electron bunch profile/TDS profile{{/code}} ... ... @@ -627,7 +627,7 @@ 627 627 //always saved (PBD)// 628 628 DOOCS prop : {{code language="none"}}TTF2.DIAG/PBD.TOROID.ML/12EXP/CHARGE.TD{{/code}} 629 629 DAQ channel: {{code language="none"}}TTF2.DIAG/PBD.TOROID.ML/12EXP{{/code}} 630 -desc: The bunch pattern as function of time in a burst recorded by toroid diagnostic BEHIND the undulator. (FLASH1) 537 +desc: The bunch pattern as function of time in a burst recorded by toroide diagnostic BEHIND the undulator. (FLASH1) 631 631 units: 632 632 \\ 633 633 ... ... @@ -660,43 +660,6 @@ 660 660 661 661 ==== Pump Probe Laser (FLASH1) ==== 662 662 663 -**PIGLET (PG laser)** 664 - 665 -**{{code language="none"}}/FL1/Experiment/Pump probe laser{{/code}}** 666 - 667 -FLASH.LASER/FLACPUPGLASER1.PULSEENERGY/DIAG1out/PULSEENERGY.MEAN 668 -FLASH.LASER/FLACPUPGLASER1.PULSEENERGY/PG1_incoupl/PULSEENERGY.MEAN 669 -FLASH.LASER/FLACPUPGLASER1.PULSEENERGY/PG2_incoupl/PULSEENERGY.MEAN 670 -FLASH.SYNC/LASER.LOCK.EXP/FLASH1.MOD1.PG.OSC/FMC0.MD22.1.ENCODER_POSITION.RD 671 -FLASH.SYNC/LASER.LOCK.EXP/FLASH1.MOD1.PG.OSC/FMC0.MD22.1.ENCODER_POSITION_RAW.RD 672 -FLASH.SYNC/LASER.LOCK.EXP/FLASH1.MOD1.PG.OSC/FMC0.MD22.1.POSITION.RD 673 - 674 -**BL - Hidra laser ** 675 - 676 -Property,Units,Description 677 -FLASH.LASER/MODBL.CAM/BL1.13.AC/DAQ_CHANNEL,'AU','FL1HIDRAPP1 Autocorrelation (IR) ROI readout' 678 -FLASH.LASER/MODBL.CAM/BL1.14.VF/DAQ_CHANNEL,'AU','FL1HIDRAPP1 Virtual Focus Camera (IR) ROI readout' 679 -FLASH.LASER/MODBL.SENSORBOARD/PDTRIG_CAMP/DAQ_CHANNEL,'au','FL1PPL Energy channels' 680 -FLASH.LASER/MODBL.SPECT/CAMP_IR/DAQ_CHANNEL,'au','FL1PPL BL Table Spectrum' 681 -FLASH.LASER/HIDRAPP1.SPECTRUM_ANALYSIS/CAMP_IR/DAQ_CHANNEL,'au','FL1PPL Spectrum Analysis' 682 -FLASH.SYNC/LASER.LOCK.EXP/F1.PPL.OSC/FMC0.MD22.1.POSITION.RD,'ps','FL1PPL Optical Delay Line (act)' 683 -FLASH.SYNC/LASER.LOCK.EXP/F1.PPL.OSC/FMC0.MD22.1.POSITION_SET.WR,'ps','FL1PPL Optical Delay Line (set)' 684 -FLASH.SYNC/LASER.LOCK.EXP/F1.PPL.OSC/FMC0.MD22.1.ENCODER_POSITION.RD,'ps','FL1PPL Optical Delay Line (Encoder Readback)' 685 -FLASH.FEL/FLAPPBEAMLINES.MOTOR/CAMP_Delayline/FPOS,'ps','FL1PPL NIR delay BL1 table (act)' 686 -FLASH.FEL/FLAPPBEAMLINES.MOTOR/CAMP_Delayline/FPOS.SET,'ps','FL1PPL NIR delay BL1 table (set)' 687 -FLASH.FEL/FLAPPBEAMLINES.MOTOR/CAMP.ATT/FPOS,'degree','FL1PPL Transmission degree (act)' 688 -FLASH.FEL/FLAPPBEAMLINES.MOTOR/CAMP.ATT/FPOS.SET,'degree','FL1PPL Transmission degree (set)' 689 -FLASH.FEL/FLAPPBEAMLINES.MOTOR/Camp_Focus_Lens/FPOS,'mm','FL1PPL Focus Mirror Stage Position (act)' 690 -FLASH.FEL/FLAPPBEAMLINES.MOTOR/Camp_Focus_Lens/FPOS.SET,'mm','FL1PPL Focus Mirror Stage Position (set)' 691 -FLASH.LASER/MODBL.FEEDFWD/BL1_Att/INPUT.Y,'%','FL1PPL Transmission rate' 692 -FLASH.SYNC/LASER.LOCK.EXP/F1.PPL.OSC/CURRENT_INPUT_JITTER.RD,'fs','FL1PPL Sync. Jitter' 693 -FLASH.SYNC/LASER.LOCK.EXP/F1.PPL.OSC/LOCK_STATUS.VALUE.RD,'au','FL1PPL Sync. Status' 694 - 695 -\\ 696 - 697 -\\ 698 - 699 -{{expand title="Parameters used until 2021"}} 700 700 {{code language="none"}}/FL1/Experiment/Pump probe laser/laser attenuation{{/code}} 701 701 702 702 //always saved (PBD)// ... ... @@ -737,8 +737,7 @@ 737 737 //always saved (PBD)// 738 738 DOOCS prop : {{code language="none"}}TTF2.FEL/TDOLFEL/TDOLFEL/STREAK.CAM.TIME{{/code}} 739 739 DOOCS prop : {{code language="none"}}TTF2.FEL/TDOLFEL/TDOLFEL/STREAK.CAM.TIME{{/code}} 740 -desc: delay time between the optical laser and the FEL units: ps 741 -{{/expand}} 610 +desc: delaytime between the optical laser and the FEL units: ps 742 742 743 743 \\ 744 744 ... ... @@ -748,7 +748,7 @@ 748 748 749 749 ==== User Data (FLASH1) ==== 750 750 751 -The data saved specifically for detectors at an experiment will show up in /Experiment/ there is a large number of options for cameras or monitoring ofslow properties (motor positions etc) for user experiments. For details please ask your local contact.620 +The data saved specifically for detectors at an experiment will show up in /Experiment/ there is a large number of options for cameras or monitoring pslow properties (motor positons etc) for user experiments. For details please ask your local contact. 752 752 753 753 NOTE: If parameters for an experiment are included on short notice the correct naming in the HDF5 may not be in time and the data will show up in /uncategorized/ with the DOOCS names 754 754 ... ... @@ -776,13 +776,13 @@ 776 776 {{code language="none"}}/FL1/Experiment/BL3/ADQ412 GHz ADC/CH03/TD{{/code}} 777 777 778 778 DOOCS prop : {{code language="none"}}FLASH.FEL/ADC.ADQ.PG/EXP1.CH00/CH00.TD or CH00.DAQ.TD{{/code}} 779 -here the {{code language="none"}}CH00.TD{{/code}} is the full ADC trace as it is sampled ( typically several 100.000 samples per pulse train) while the {{code language="none"}}CH00.DAQ.TD{{/code}} trace only has the number of samples which are sent to the DAQ OR if //grouping// is activated the {{code language="none"}}CH00.DAQ.TD{{/code}} con tains only the grouped spectra. To read the ADC trace with an online analysis program the {{code language="none"}}CH00.DAQ.TD{{/code}} is used preferably.648 +here the {{code language="none"}}CH00.TD{{/code}} is the full ADC trace as it is sampled ( typically several 100.000 samples per pulse train) while the {{code language="none"}}CH00.DAQ.TD{{/code}} trace only has the number of samples which are sent to the DAQ OR if //grouping// is activated the {{code language="none"}}CH00.DAQ.TD{{/code}} conatins only the grouped spectra. To read the ADC trace with an online analysis program the {{code language="none"}}CH00.DAQ.TD{{/code}} is used preferablly. 780 780 DAQ channel: {{code language="none"}}FLASH.FEL/ADC.ADQ.PG/EXP1.CH00{{/code}} 781 781 782 782 In addition there are also additional parameters saved like: 783 783 784 784 * {{code language="none"}}sample frequency{{/code}}: it shows the sample frequency in MHz (number of samples per µs). NOTE: the clock of the ADC is NOT synchronized to the FLASH timing system. Thus the number of samples between bunches in the bunch train may be not integer numbers which will be show up for long bunch trains. 785 -* {{code language="none"}}number of samples{{/code}}: total number of sam ples recorded for each 10 Hz trigger654 +* {{code language="none"}}number of samples{{/code}}: total number of samoles recorded for each 10 Hz trigger 786 786 * {{code language="none"}}error (ADC):{{/code}} 0 indicates that there was no error 787 787 788 788 ===== MHz ADCs ===== ... ... @@ -795,7 +795,7 @@ 795 795 In addition there are also additional parameters saved like: 796 796 797 797 * {{code language="none"}}sample frequency{{/code}}: it shows the sample frequency in MHz (number of samples per µs). NOTE: the clock of the ADC is NOT synchronized to the FLASH timing system. Thus the number of samples between bunches in the bunch train may be not integer numbers which will be show up for long bunch trains. 798 -* {{code language="none"}}number of samples{{/code}}: total number of sam ples recorded for each 10 Hz trigger667 +* {{code language="none"}}number of samples{{/code}}: total number of samoles recorded for each 10 Hz trigger 799 799 800 800 [[Contents>>doc:||anchor="Contents"]] 801 801 ... ... @@ -956,7 +956,7 @@ 956 956 // saved opon request (PBD2)// 957 957 DOOCS prop : {{code language="none"}}FLASH.UTIL/STORE/FL2.TUNNEL.OPIS/VAL040{{/code}} 958 958 DAQ channel:{{code language="none"}} FLASH.UTIL/STORE/FL2.TUNNEL.OPIS/VAL040{{/code}} 959 -desc : mean 828 +desc : meanwavelength ( ~~ 1 sec averaging time ) measured in the TUNNEL for a specific bunch out of the bunch train (via photoelectron spectroscopy) 960 960 units : nm 961 961 962 962 \\ ... ... @@ -970,11 +970,11 @@ 970 970 971 971 \\ 972 972 973 -If Opis is running typically on the the averaged data is saved. For several experiments it may make sense to save the information for each single bunch. This is up to now done by sav ing the complete ADC trace of the TOF setup. This is a huge amount of data and needs processing. This has to be performed after the beamtime in close contact to [[Markus Braune>>mailto:markus.braune@desy.de||shape="rect"]] ( responsible for [[OPIS>>url:http://photon-science.desy.de/facilities/flash/photon_diagnostics/opis_spectrometer/index_eng.html||shape="rect"]])842 +If Opis is running typically on the the averaged data is saved. For several experiments it may make sense to save the information for each single bunch. This is up to now done by savng the compleate ADC trace of the TOF setup. This is a huge amount of data and needs processing. This has to be performed after the beamtime in close contact to [[Markus Braune>>mailto:markus.braune@desy.de||shape="rect"]] ( respobsible for [[OPIS>>url:http://photon-science.desy.de/facilities/flash/photon_diagnostics/opis_spectrometer/index_eng.html||shape="rect"]]) 974 974 975 975 \\ 976 976 977 -In case OPIS was not operating there is still informat ion about the **set wavelength** for the undulators (see below) which may differ by up to 5 % from the actual wavelength due to different settings in the FEL ...846 +In case OPIS was not operating there is still informaton about the **set wavelength** for the undulators (see below) which may differ by up to 5 % from the actual wavelength due to different settings in the FEL ... 978 978 979 979 \\ 980 980 ... ... @@ -993,21 +993,8 @@ 993 993 994 994 \\ 995 995 996 -===== electronbunchenergy=====865 +===== undulator settings ===== 997 997 998 -{{code language="none"}}/FL2/Electron Diagnostic/Electron energy/energy of first bunch/behind undulators{{/code}} 999 -//always saved (PBD2)// 1000 -DOOCS prop : {{code language="none"}}FLASH.DIAG/BEAM_ENERGY_MEASUREMENT/FL2XTDS/ENERGY.FLASH2{{/code}} 1001 -DAQ channel: (% style="color: rgb(94,108,132);" %)TTF2.DAQ/PBD2.BEAM.ENERGY.MEAS.ML.COPY/FL2XTDS.ENERGY.FLASH2{{code language="none"}}{{/code}}(%%) 1002 -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: rgb(94,108,132);" %)extraction and septum in the beginning of FLASH2 1003 - 1004 -(% style="letter-spacing: 0.0px;" %)units: (% class="twikiNewLink" %)MeV 1005 - 1006 -\\ 1007 - 1008 -(% style="color: rgb(94,108,132);font-weight: 600;letter-spacing: 0.0px;" %) 1009 -undulator settings 1010 - 1011 1011 {{code language="none"}}/FL2/Electron Diagnostic/Undulator setting/set wavelength{{/code}} 1012 1012 //always saved (PBD2)// 1013 1013 DOOCS prop : {{code language="none"}}TTF2.FEEDBACK/FL2.WAVELENGTHCONTROL/FLASH2/WAVELENGTH{{/code}} ... ... @@ -1025,27 +1025,8 @@ 1025 1025 The gap values are saved for all 12 undulators (Nr 3 to 14). Undulator 14 is the one closest to the experimental hall. 1026 1026 1027 1027 ===== 1028 -arrival time (BAM)=====884 +arrival time ===== 1029 1029 1030 -{{info title="BAM information: updates 2022"}} 1031 -* 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"]] 1032 -* The data format of the BAM has been completely altered in the 2022 shutdown 1033 -* 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 ... 1034 -* 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) 1035 -* There has been also a renaming (and relocation) of the BAMs. 1036 -** acc: 4DBC3 → FL0.DBC2 1037 -** FL1: 1SFELC → FL1.SFELC 1038 -** FL2: 8FL2XTDS → (% style="color: rgb(23,43,77);" %)FL2.SEED5 1039 -* for more Info: [[LINK to detailed infos from MSK>>url:https://confluence.desy.de/display/SDiagPublic/BAM+Data+Structure||shape="rect"]] 1040 -* [[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]] 1041 -* a recent [[talk about the working principle of the BAM>>attach:BAM-basics and outlook-2018_DESY-template_16-9Format.pdf]] 1042 -{{/info}} 1043 - 1044 -\\ 1045 - 1046 -{{expand title="Discontinued BAM format (used until end 2021)"}} 1047 -(% style="color: rgb(0,0,0);" %)**Discontinued BAM data recording ** 1048 - 1049 1049 {{code language="none"}}/FL2/Electron Diagnostic/BAM/8FL2XTDS/electron bunch arrival time (low charge){{/code}} 1050 1050 //always saved (PBD2)// 1051 1051 DOOCS prop : {{code language="none"}}FLASH.SDIAG/BAM/8FL2XTDS/LOW_CHARGE_ARRIVAL_TIME{{/code}} ... ... @@ -1070,85 +1070,8 @@ 1070 1070 * [[LINK to detailed infos from MSK (may only work inside DESY network~[~[image:url:http://hasfweb.desy.de/pub/TWiki/TWikiDocGraphics/external-link.gif~|~|width="13" height="12"~]~]>>url:http://www.desy.de/~~mbock/pages/BAM_daq_channel_descriptions.html||shape="rect"]] 1071 1071 * a recent [[talk about the working principle of the BAM>>attach:BAM-basics and outlook-2018_DESY-template_16-9Format.pdf]] 1072 1072 {{/info}} 1073 -{{/expand}} 1074 1074 1075 -\\ 1076 1076 1077 -====== **BAM FL0.DBC2**{{code language="none"}}{{/code}} ====== 1078 - 1079 -(% style="color: rgb(255,102,0);" %)**DBC2**/electron bunch arrival time (HDF5 name not yet implemented - see zraw)(%%) 1080 -//always saved (PBD)// 1081 -**FL0.DBC2** 1082 -(% style="color: rgb(0,0,0);" %)channel: FLASH.SDIAG/BAM/**FL0.DBC2**/ARRIVAL_TIME.ABSOLUTE.SA2.COMP 1083 -{{code language="none"}}/FL2/Electron Diagnostic/BAM/ DOOCS prop : FLASH.SDIAG/BAM//ARRIVAL_TIME.ABSOLUTE.SA2.COMPDAQ {{/code}}(% style="letter-spacing: 0.0px;" %)desc: Electron bunch arrival time measured with the BAM inside the accelerator (after bunch compressor 2). The property contains only the arrival time of the bunches sent to FL2 (e.g. if there are 30 bunches in FL2 the first 30 values are the arrival time the remaining numbers should be only 0). 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). 1084 -units: fs (bigger numbers (typically) indicate later arrival times of the electrons). 1085 - 1086 -\\ 1087 - 1088 -(% style="color: rgb(255,102,0);" %)DBC2/electron bunch arrival time (raw) (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL2/Electron Diagnostic/BAM/{{/code}}(%%) 1089 -//always saved (PBD)// 1090 -{{code language="none"}}DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.ABSOLUTE{{/code}} 1091 -(% style="color: rgb(0,0,0);" %)FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.ABSOLUTE {{code language="none"}}DAQ channel: {{/code}}(%%) 1092 -desc: Electron bunch arrival time measured with the BAM inside the accelerator (after bunch compressor 2). Here the complete bunch train from the FEL is recorded (FLASH1 and FLASH2 pulses). Thus there are values from FLASH 2 in the second part. they may be separated by several "0" values if the reprate is different from 1 MHz ... - It shows a very good correlation to the arrival time of the XUV pulses in the experiment (see help). 1093 -units: fs (bigger numbers (typically) indicate later arrival times of the electrons). 1094 - 1095 -\\ 1096 - 1097 -(% style="color: rgb(255,102,0);" %)DBC2/error (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL2/Electron Diagnostic/BAM/{{/code}}(%%) 1098 -//always saved (PBD)// 1099 -(% style="color: rgb(0,0,0);" %)E.bamError{{code language="none"}}DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIM{{/code}}(%%) 1100 -(% style="color: rgb(0,0,0);" %)FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.BAMERROR{{code language="none"}}DAQ channel: {{/code}}(%%) 1101 -desc: If the value is 0 , the BAM is working well. If it is non-zero there is a problem !! 1102 - 1103 -\\ 1104 - 1105 -(% style="color: rgb(255,102,0);" %)DBC2/status (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL2/Electron Diagnostic/BAM/{{/code}}(%%) 1106 -//always saved (PBD)// 1107 -(% style="color: rgb(0,0,0);" %)E..bamStatus.//2//{{code language="none"}}DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIM{{/code}}(%%) 1108 -(% style="color: rgb(0,0,0);" %): FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.BAMSTATUS.2{{code language="none"}}DAQ channel{{/code}}(%%) 1109 -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 1110 - 1111 -\\ 1112 - 1113 -====== **BAM FL2.SEED5**{{code language="none"}}{{/code}} ====== 1114 - 1115 -/FL2/Electron Diagnostic/BAM/**SEED5**(% style="color: rgb(255,102,0);" %)/electron bunch arrival time (HDF5 name not yet implemented - see zraw) 1116 - 1117 -//always saved (PBD)// 1118 -(% style="color: rgb(23,43,77);" %)**FL2.SEED5**(%%) 1119 -(% style="color: rgb(0,0,0);" %)channel: FLASH.SDIAG/BAM/(% style="color: rgb(0, 0, 0); color: rgb(23, 43, 77)" %)**FL2.SEED5**(% style="color: rgb(0,0,0);" %)/ARRIVAL_TIME.ABSOLUTE.SA1.COMP 1120 -{{code language="none"}} DOOCS prop : FLASH.SDIAG/BAM//ARRIVAL_TIME.ABSOLUTE.SA1.COMPDAQ {{/code}}(%%)desc: Electron bunch arrival time measured with the BAM before the undulator (pulse resolved data). This one was newly installed in 2020.. The property contains only the arrival time of the bunches sent to FL2 (e.g. if there are 30 bunches in FL2 the first 30 values are the arrival time the remaining numbers should be only 0). 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). 1121 -units: fs (bigger numbers (typically) indicate later arrival times of the electrons). 1122 - 1123 -\\ 1124 - 1125 -\\ 1126 - 1127 -(% style="color: rgb(23,43,77);" %)SEED5(% style="color: rgb(255,102,0);" %)/electron bunch arrival time (raw) (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL2/Electron Diagnostic/BAM/{{/code}}(%%) 1128 -//always saved (PBD)// 1129 -(% style="color: rgb(23,43,77);" %)**FL2.SEED5**{{code language="none"}}DOOCS prop : FLASH.SDIAG/BAM//ARRIVAL_TIME.ABSOLUTE{{/code}}(%%) 1130 -**~ **(% style="color: rgb(0,0,0);" %)FLASH.SDIAG/BAM/(% style="color: rgb(0, 0, 0); color: rgb(23, 43, 77)" %)**FL2.SEED5**(% style="color: rgb(0,0,0);" %)/ARRIVAL_TIME.ABSOLUTE {{code language="none"}}DAQ channel:{{/code}}(%%) 1131 -desc: Electron bunch arrival time measured with the BAM before the undulator (pulse resolved data). This one was newly installed in 2020. Here the complete bunch train from the FEL is recorded (FLASH1 and FLASH2 pulses). Thus there are values from FLASH 2 in the second part. they may be separated by several "0" values if the reprate is different from 1 MHz ... - It shows a very good correlation to the arrival time of the XUV pulses in the experiment (see help). 1132 -units: fs (bigger numbers (typically) indicate later arrival times of the electrons). 1133 - 1134 -\\ 1135 - 1136 -(% style="color: rgb(23,43,77);" %)SEED5(% style="color: rgb(255,102,0);" %)/error (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL2/Electron Diagnostic/BAM/{{/code}}(%%) 1137 -//always saved (PBD)// 1138 -(% style="color: rgb(23,43,77);" %)**FL2.SEED5**(% style="color: rgb(0,0,0);" %)E.bamError{{code language="none"}}DOOCS prop : FLASH.SDIAG/BAM//ARRIVAL_TIM{{/code}}(%%) 1139 -(% style="color: rgb(0,0,0);" %): FLASH.SDIAG/BAM/(% style="color: rgb(0, 0, 0); color: rgb(23, 43, 77)" %)**FL2.SEED5**(% style="color: rgb(0,0,0);" %)/ARRIVAL_TIME.BAMERROR{{code language="none"}}DAQ channel{{/code}}(%%) 1140 -desc: If the value is 0 , the BAM is working well. If it is non-zero there is a problem !! 1141 - 1142 -\\ 1143 - 1144 -(% style="color: rgb(23,43,77);" %)SEED5(% style="color: rgb(255,102,0);" %)/status (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL2/Electron Diagnostic/BAM/{{/code}}(%%) 1145 -//always saved (PBD)// 1146 -(% style="color: rgb(23,43,77);" %)**FL2.SEED5**(% style="color: rgb(0,0,0);" %)E.bamStatus.//2//{{code language="none"}}DOOCS prop : FLASH.SDIAG/BAM//ARRIVAL_TIM{{/code}}(%%) 1147 -(% style="color: rgb(0,0,0);" %)el: FLASH.SDIAG/BAM/(% style="color: rgb(0, 0, 0); color: rgb(23, 43, 77)" %)**FL2.SEED5**(% style="color: rgb(0,0,0);" %)/ARRIVAL_TIME.BAMSTATUS.2{{code language="none"}}DAQ chann{{/code}}(%%) 1148 -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 1149 - 1150 -\\ 1151 - 1152 1152 [[Contents>>doc:||anchor="Contents"]] 1153 1153 1154 1154 \\ ... ... @@ -1275,80 +1275,7 @@ 1275 1275 1276 1276 There may be more information available from the "Laser DAQ". laese contact your Laser Local Contact. 1277 1277 1278 -\\ 1279 1279 1280 -**User delay** 1281 - 1282 -Delay (set value): 1283 - 1284 -{{code language="none"}}FLASH.SYNC/LASER.LOCK.EXP/F2.PPL.OSC/FMC0.MD22.0.POSITION_SET.WR{{/code}} 1285 - 1286 -Delay (encoder readback): 1287 - 1288 -{{code language="none"}}FLASH.SYNC/LASER.LOCK.EXP/F2.PPL.OSC/FMC0.MD22.0.POSITION.RD{{/code}} 1289 - 1290 -OXC. jitter: 1291 - 1292 -{{code language="none"}}FLASH.SYNC/LASER.LOCK.EXP/F2.PPL.OSC/CURRENT_INPUT_JITTER.RD{{/code}} 1293 - 1294 -\\ 1295 - 1296 -**Pulse resolved energy:** 1297 - 1298 -1a) OPCPA output: 1299 - 1300 -{{code language="none"}}FLASH.LASER/TAMC532DMA/ULGAN1/CH23.TD{{/code}} 1301 - 1302 -1b) OPCPA energy from PES (only fast channel): 1303 - 1304 -FLASH.LASER/CPUULGAN1.PULSEENERGY/OPCPA_Output/DAQ_CHANNEL 1305 - 1306 -2a) Upper breadboard Photodiode (THG) burst: 1307 - 1308 -{{code language="none"}}FLASH.LASER/TAMC532DMA/ULGAN1/CH26.TD{{/code}} 1309 - 1310 -2b) Upper breadboard Photodiode (THG) energy (in-coupling user photodiode, fast) 1311 - 1312 -{{code language="none"}}FLASH.LASER/MOD24.PES/FL24_userPD/DAQ_CHANNEL{{/code}} 1313 - 1314 -\\ 1315 - 1316 -**Attenuator angle:** 1317 - 1318 -{{code language="none"}}FLASH.FEL/FLAPP2BEAMLINES/MOTOR1.FL24/FPOS{{/code}} 1319 - 1320 -**Polarization control:** 1321 - 1322 -{{code language="none"}}FLASH.FEL/FLAPP2BEAMLINES/MOTOR14.FL24/FPOS{{/code}} 1323 - 1324 -**SysDC delay error:** 1325 - 1326 -{{code language="none"}}FLASH.LASER/ULGAN1.DYNPROP/TCFIBER.DOUBLES/DOUBLE26{{/code}} 1327 - 1328 -\\ 1329 - 1330 -**Timing error: (these two need to be observed and both=0 means no error)** 1331 - 1332 -{{code language="none"}}FLASH/CPUULGAN1.TIMING/ULGAN1/dT_alarm{{/code}} 1333 - 1334 -{{code language="none"}}FLASH/CPUULGAN1.TIMING/ULGAN1/dMPN{{/code}} 1335 - 1336 -**Laser error status:** 1337 - 1338 -\\ 1339 - 1340 -**Virtual camera X and Y history, beam size: (use slow data)** 1341 - 1342 -{{code language="none"}}FLASH.LASER/MOD24.BEAMPOS/UV.VF_BP/CENTER.X{{/code}} 1343 - 1344 -{{code language="none"}}FLASH.LASER/MOD24.BEAMPOS/UV.VF_BP/CENTER.Y{{/code}} 1345 - 1346 -{{code language="none"}}FLASH.LASER/MOD24.CAM/UV.14.VF/ROI_SPECTRUM.X.SIG{{/code}} 1347 - 1348 -\\ 1349 - 1350 -{{expand title="Parameters used until 2021"}} 1351 - 1352 1352 {{code language="none"}}/FL2/Experiment/Pump probe laser/FL24/attenuator position{{/code}}//always saved (PBD2)// 1353 1353 DOOCS prop : {{code language="none"}}FLASH.FEL/FLAPP2BEAMLINES/MOTOR1.FL24/FPOS{{/code}} 1354 1354 DAQ channel: {{code language="none"}}FLASH.FEL/FLAPP2BEAMLINES/MOTOR1.FL24/FPOS{{/code}} ... ... @@ -1381,7 +1381,6 @@ 1381 1381 DAQ channel: {{code language="none"}}FLASH.SYNC/LASER.LOCK.EXP/FLASH2.PPL1.OSC1/CURRENT_INPUT_JITTER.RD{{/code}} 1382 1382 desc: rms jitter of the fs-Oscillator 1383 1383 units: fs 1384 -{{/expand}} 1385 1385 1386 1386 [[Contents>>doc:||anchor="Contents"]] 1387 1387