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
-
... ... @@ -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,68 +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 - (% style="color:rgb(255,102,0);" %)DBC2/electron bunch arrivaltime{{codelanguage="none"}}/FL1/ElectronDiagnostic/BAM/{{/code}}(%%)460 - //always saved(PBD)//461 - DOOCSprop:FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.absolute.SA1462 - DAQchannel:(%style="color:rgb(255,102,0);"%)FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.absolute.SA1(%%)463 - desc:Electron buncharrivaltime measured with theBAM insidetheaccelerator(afterbunch compressor 2) - Itshows a verygood correlationto the arrival timeXUV pulses in the experiment (see help). The SA1 indicatesthe dataisrecordedforthe first time slotLASh,typically usedor FLASH1464 - units: fs (biggernumbers (typically) indicate later arrival times ofthe electrons).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}} 465 465 466 466 \\ 467 467 468 -(% style="color: rgb(255,102,0);" %)DBC2/error{{code language="none"}}/FL1/Electron Diagnostic/BAM/{{/code}}(%%) 469 -//always saved (PBD)// 470 -DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIM(% style="color: rgb(0,0,0);" %)E.bamError(%%) 471 -DAQ channel: (% style="color: rgb(255,102,0);" %)FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.BAMERROR(%%) 472 -desc: If the value is 0 , the BAM is working well. If it is non-zero there is a problem !! 473 - 474 -\\ 475 - 476 -(% style="color: rgb(255,102,0);" %)DBC2/error{{code language="none"}}/FL1/Electron Diagnostic/BAM/{{/code}}(%%) 477 -//always saved (PBD)// 478 -DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIM(% style="color: rgb(0,0,0);" %)E..bamStatus.//1//(%%) 479 -DAQ channel: (% style="color: rgb(255,102,0);" %)FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.BAMSTATUS(%%) 480 -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 481 - 482 -\\ 483 - 484 -(% style="color: rgb(23,43,77);" %)SFELC(% style="color: rgb(255,102,0);" %)/electron bunch arrival time{{code language="none"}}/FL1/Electron Diagnostic/BAM/{{/code}}(%%) 485 -//always saved (PBD)// 486 -DOOCS prop : FLASH.SDIAG/BAM/(% style="color: rgb(23,43,77);" %)FL1.SFELC(%%)/ARRIVAL_TIME.absolute.SA1 487 -DAQ channel: (% style="color: rgb(255,102,0);" %)FLASH.SDIAG/BAM/(% style="color: rgb(255, 102, 0); color: rgb(23, 43, 77)" %)FL1.SFELC(% style="color: rgb(255,102,0);" %)/ARRIVAL_TIME.absolute.SA1 (%%) 488 -desc: Electron bunch arrival time measured with the BAM before the undulator (pulse resolved data). This one was newly installed in 2020. The SA1 indicates the data is recorded for the first time slot at FLASh, typically used for FLASH1 489 -units: fs (bigger numbers (typically) indicate later arrival times of the electrons). 490 - 491 -\\ 492 - 493 -(% style="color: rgb(23,43,77);" %)SFELC(% style="color: rgb(255,102,0);" %)/error{{code language="none"}}/FL1/Electron Diagnostic/BAM/{{/code}}(%%) 494 -//always saved (PBD)// 495 -DOOCS prop : FLASH.SDIAG/BAM/(% style="color: rgb(23,43,77);" %)FL1.SFELC(%%)/ARRIVAL_TIM(% style="color: rgb(0,0,0);" %)E.bamError(%%) 496 -DAQ channel: (% style="color: rgb(255,102,0);" %)FLASH.SDIAG/BAM/(% style="color: rgb(255, 102, 0); color: rgb(23, 43, 77)" %)FL1.SFELC(% style="color: rgb(255,102,0);" %)/ARRIVAL_TIME.BAMERROR(%%) 497 -desc: If the value is 0 , the BAM is working well. If it is non-zero there is a problem !! 498 - 499 -\\ 500 - 501 -(% style="color: rgb(23,43,77);" %)SFELC(% style="color: rgb(255,102,0);" %)/error{{code language="none"}}/FL1/Electron Diagnostic/BAM/{{/code}}(%%) 502 -//always saved (PBD)// 503 -DOOCS prop : FLASH.SDIAG/BAM/(% style="color: rgb(23,43,77);" %)FL1.SFELC(%%)/ARRIVAL_TIM(% style="color: rgb(0,0,0);" %)E..bamStatus.//1//(%%) 504 -DAQ channel: (% style="color: rgb(255,102,0);" %)FLASH.SDIAG/BAM/(% style="color: rgb(255, 102, 0); color: rgb(23, 43, 77)" %)FL1.SFELC(% style="color: rgb(255,102,0);" %)/ARRIVAL_TIME.BAMSTATUS(%%) 505 -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 506 - 507 -\\ 508 - 509 -\\ 510 - 511 511 ===== electron beam profile ===== 512 512 513 513 {{code language="none"}}/FL1/Electron Diagnostic/Electron bunch profile/TDS profile{{/code}} ... ... @@ -601,7 +601,7 @@ 601 601 //always saved (PBD)// 602 602 DOOCS prop : {{code language="none"}}TTF2.DIAG/PBD.TOROID.ML/12EXP/CHARGE.TD{{/code}} 603 603 DAQ channel: {{code language="none"}}TTF2.DIAG/PBD.TOROID.ML/12EXP{{/code}} 604 -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) 605 605 units: 606 606 \\ 607 607 ... ... @@ -634,22 +634,6 @@ 634 634 635 635 ==== Pump Probe Laser (FLASH1) ==== 636 636 637 -**PIGLET (PG laser)** 638 - 639 -**{{code language="none"}}/FL1/Experiment/Pump probe laser{{/code}}** 640 - 641 -FLASH.LASER/FLACPUPGLASER1.PULSEENERGY/DIAG1out/PULSEENERGY.MEAN 642 -FLASH.LASER/FLACPUPGLASER1.PULSEENERGY/PG1_incoupl/PULSEENERGY.MEAN 643 -FLASH.LASER/FLACPUPGLASER1.PULSEENERGY/PG2_incoupl/PULSEENERGY.MEAN 644 - 645 - 646 -FLASH.SYNC/LASER.LOCK.EXP/FLASH1.MOD1.PG.OSC/FMC0.MD22.1.ENCODER_POSITION.RD 647 -FLASH.SYNC/LASER.LOCK.EXP/FLASH1.MOD1.PG.OSC/FMC0.MD22.1.ENCODER_POSITION_RAW.RD 648 -FLASH.SYNC/LASER.LOCK.EXP/FLASH1.MOD1.PG.OSC/FMC0.MD22.1.POSITION.RD 649 - 650 -\\ 651 - 652 -{{expand title="Parameters used until 2021"}} 653 653 {{code language="none"}}/FL1/Experiment/Pump probe laser/laser attenuation{{/code}} 654 654 655 655 //always saved (PBD)// ... ... @@ -690,15 +690,10 @@ 690 690 //always saved (PBD)// 691 691 DOOCS prop : {{code language="none"}}TTF2.FEL/TDOLFEL/TDOLFEL/STREAK.CAM.TIME{{/code}} 692 692 DOOCS prop : {{code language="none"}}TTF2.FEL/TDOLFEL/TDOLFEL/STREAK.CAM.TIME{{/code}} 693 -desc: delay time between the optical laser and the FEL units: ps 694 -{{/expand}} 610 +desc: delaytime between the optical laser and the FEL units: ps 695 695 696 696 \\ 697 697 698 -\\ 699 - 700 -\\ 701 - 702 702 [[Contents>>doc:||anchor="Contents"]] 703 703 704 704 \\ ... ... @@ -705,7 +705,7 @@ 705 705 706 706 ==== User Data (FLASH1) ==== 707 707 708 -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. 709 709 710 710 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 711 711 ... ... @@ -733,13 +733,13 @@ 733 733 {{code language="none"}}/FL1/Experiment/BL3/ADQ412 GHz ADC/CH03/TD{{/code}} 734 734 735 735 DOOCS prop : {{code language="none"}}FLASH.FEL/ADC.ADQ.PG/EXP1.CH00/CH00.TD or CH00.DAQ.TD{{/code}} 736 -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. 737 737 DAQ channel: {{code language="none"}}FLASH.FEL/ADC.ADQ.PG/EXP1.CH00{{/code}} 738 738 739 739 In addition there are also additional parameters saved like: 740 740 741 741 * {{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. 742 -* {{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 743 743 * {{code language="none"}}error (ADC):{{/code}} 0 indicates that there was no error 744 744 745 745 ===== MHz ADCs ===== ... ... @@ -752,7 +752,7 @@ 752 752 In addition there are also additional parameters saved like: 753 753 754 754 * {{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. 755 -* {{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 756 756 757 757 [[Contents>>doc:||anchor="Contents"]] 758 758 ... ... @@ -913,7 +913,7 @@ 913 913 // saved opon request (PBD2)// 914 914 DOOCS prop : {{code language="none"}}FLASH.UTIL/STORE/FL2.TUNNEL.OPIS/VAL040{{/code}} 915 915 DAQ channel:{{code language="none"}} FLASH.UTIL/STORE/FL2.TUNNEL.OPIS/VAL040{{/code}} 916 -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) 917 917 units : nm 918 918 919 919 \\ ... ... @@ -927,11 +927,11 @@ 927 927 928 928 \\ 929 929 930 -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"]]) 931 931 932 932 \\ 933 933 934 -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 ... 935 935 936 936 \\ 937 937 ... ... @@ -950,21 +950,8 @@ 950 950 951 951 \\ 952 952 953 -===== electronbunchenergy=====865 +===== undulator settings ===== 954 954 955 -{{code language="none"}}/FL2/Electron Diagnostic/Electron energy/energy of first bunch/behind undulators{{/code}} 956 -//always saved (PBD2)// 957 -DOOCS prop : {{code language="none"}}FLASH.DIAG/BEAM_ENERGY_MEASUREMENT/FL2XTDS/ENERGY.FLASH2{{/code}} 958 -DAQ channel: (% style="color: rgb(94,108,132);" %)TTF2.DAQ/PBD2.BEAM.ENERGY.MEAS.ML.COPY/FL2XTDS.ENERGY.FLASH2{{code language="none"}}{{/code}}(%%) 959 -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 960 - 961 -(% style="letter-spacing: 0.0px;" %)units: (% class="twikiNewLink" %)MeV 962 - 963 -\\ 964 - 965 -(% style="color: rgb(94,108,132);font-weight: 600;letter-spacing: 0.0px;" %) 966 -undulator settings 967 - 968 968 {{code language="none"}}/FL2/Electron Diagnostic/Undulator setting/set wavelength{{/code}} 969 969 //always saved (PBD2)// 970 970 DOOCS prop : {{code language="none"}}TTF2.FEEDBACK/FL2.WAVELENGTHCONTROL/FLASH2/WAVELENGTH{{/code}} ... ... @@ -982,27 +982,8 @@ 982 982 The gap values are saved for all 12 undulators (Nr 3 to 14). Undulator 14 is the one closest to the experimental hall. 983 983 984 984 ===== 985 -arrival time (BAM)=====884 +arrival time ===== 986 986 987 -{{info title="BAM information: updates 2022"}} 988 -* 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"]] 989 -* The data format of the BAM has been completely altered in the 2022 shutdown 990 -* 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 ... 991 -* 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) 992 -* There has been also a renaming (and relocation) of the BAMs. 993 -** acc: 4DBC3 → FL0.DBC2 994 -** FL1: 1SFELC → FL1.SFELC 995 -** FL2: 8FL2XTDS → (% style="color: rgb(23,43,77);" %)FL2.SEED5 996 -* for more Info: [[LINK to detailed infos from MSK>>url:https://confluence.desy.de/display/SDiagPublic/BAM+Data+Structure||shape="rect"]] 997 -* [[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]] 998 -* a recent [[talk about the working principle of the BAM>>attach:BAM-basics and outlook-2018_DESY-template_16-9Format.pdf]] 999 -{{/info}} 1000 - 1001 -\\ 1002 - 1003 -{{expand title="Discontinued BAM format (used until end 2021)"}} 1004 -(% style="color: rgb(0,0,0);" %)**Discontinued BAM data recording ** 1005 - 1006 1006 {{code language="none"}}/FL2/Electron Diagnostic/BAM/8FL2XTDS/electron bunch arrival time (low charge){{/code}} 1007 1007 //always saved (PBD2)// 1008 1008 DOOCS prop : {{code language="none"}}FLASH.SDIAG/BAM/8FL2XTDS/LOW_CHARGE_ARRIVAL_TIME{{/code}} ... ... @@ -1027,60 +1027,8 @@ 1027 1027 * [[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"]] 1028 1028 * a recent [[talk about the working principle of the BAM>>attach:BAM-basics and outlook-2018_DESY-template_16-9Format.pdf]] 1029 1029 {{/info}} 1030 -{{/expand}} 1031 1031 1032 -(% style="color: rgb(255,102,0);" %)DBC2/electron bunch arrival time{{code language="none"}}/FL1/Electron Diagnostic/BAM/{{/code}}(%%) 1033 -//always saved (PBD)// 1034 -DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.ABSOLUTE 1035 -DAQ channel: (% style="color: rgb(255,102,0);" %)FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.ABSOLUTE(%%) 1036 -desc: Electron bunch arrival time measured with the BAM inside the accelerator (after bunch compressor 2) - It shows a very good correlation to the arrival time of the XUV pulses in the experiment (see help). typically used for FLASH2 1037 -units: fs (bigger numbers (typically) indicate later arrival times of the electrons). 1038 1038 1039 -\\ 1040 - 1041 -(% style="color: rgb(255,102,0);" %)DBC2/error{{code language="none"}}/FL1/Electron Diagnostic/BAM/{{/code}}(%%) 1042 -//always saved (PBD)// 1043 -DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIM(% style="color: rgb(0,0,0);" %)E.bamError(%%) 1044 -DAQ channel: (% style="color: rgb(255,102,0);" %)FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.BAMERROR(%%) 1045 -desc: If the value is 0 , the BAM is working well. If it is non-zero there is a problem !! 1046 - 1047 -\\ 1048 - 1049 -(% style="color: rgb(255,102,0);" %)DBC2/error{{code language="none"}}/FL1/Electron Diagnostic/BAM/{{/code}}(%%) 1050 -//always saved (PBD)// 1051 -DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIM(% style="color: rgb(0,0,0);" %)E..bamStatus.//2//(%%) 1052 -DAQ channel: (% style="color: rgb(255,102,0);" %)FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.BAMSTATUS(%%) 1053 -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 1054 - 1055 -\\ 1056 - 1057 -(% style="color: rgb(23,43,77);" %)SEED5(% style="color: rgb(255,102,0);" %)/electron bunch arrival time{{code language="none"}}/FL1/Electron Diagnostic/BAM/{{/code}}(%%) 1058 -//always saved (PBD)// 1059 -DOOCS prop : FLASH.SDIAG/BAM/(% style="color: rgb(23,43,77);" %)FL2.SEED5(%%)/ARRIVAL_TIME.ABSOLUTE 1060 -DAQ channel: (% style="color: rgb(255,102,0);" %)FLASH.SDIAG/BAM/(% style="color: rgb(255, 102, 0); color: rgb(23, 43, 77)" %)FL2.SEED5(% style="color: rgb(255,102,0);" %)/ARRIVAL_TIME.ABSOLUTE(%%) 1061 -desc: Electron bunch arrival time measured with the BAM before the undulator (pulse resolved data). This one was newly installed in 2020. 1062 -units: fs (bigger numbers (typically) indicate later arrival times of the electrons). 1063 - 1064 -\\ 1065 - 1066 -(% style="color: rgb(23,43,77);" %)SEED5(% style="color: rgb(255,102,0);" %)/error{{code language="none"}}/FL1/Electron Diagnostic/BAM/{{/code}}(%%) 1067 -//always saved (PBD)// 1068 -DOOCS prop : FLASH.SDIAG/BAM/(% style="color: rgb(23,43,77);" %)FL2.SEED5(%%)/ARRIVAL_TIM(% style="color: rgb(0,0,0);" %)E.bamError(%%) 1069 -DAQ channel: (% style="color: rgb(255,102,0);" %)FLASH.SDIAG/BAM/(% style="color: rgb(255, 102, 0); color: rgb(23, 43, 77)" %)FL2.SEED5(% style="color: rgb(255,102,0);" %)/ARRIVAL_TIME.BAMERROR(%%) 1070 -desc: If the value is 0 , the BAM is working well. If it is non-zero there is a problem !! 1071 - 1072 -\\ 1073 - 1074 -(% style="color: rgb(23,43,77);" %)SEED5(% style="color: rgb(255,102,0);" %)/error{{code language="none"}}/FL1/Electron Diagnostic/BAM/{{/code}}(%%) 1075 -//always saved (PBD)// 1076 -DOOCS prop : FLASH.SDIAG/BAM/(% style="color: rgb(23,43,77);" %)FL2.SEED5(%%)/ARRIVAL_TIM(% style="color: rgb(0,0,0);" %)E..bamStatus.//2//(%%) 1077 -DAQ channel: (% style="color: rgb(255,102,0);" %)FLASH.SDIAG/BAM/(% style="color: rgb(255, 102, 0); color: rgb(23, 43, 77)" %)FL2.SEED5(% style="color: rgb(255,102,0);" %)/ARRIVAL_TIME.BAMSTATUS(%%) 1078 -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 1079 - 1080 -\\ 1081 - 1082 -\\ 1083 - 1084 1084 [[Contents>>doc:||anchor="Contents"]] 1085 1085 1086 1086 \\ ... ... @@ -1207,80 +1207,7 @@ 1207 1207 1208 1208 There may be more information available from the "Laser DAQ". laese contact your Laser Local Contact. 1209 1209 1210 -\\ 1211 1211 1212 -**User delay** 1213 - 1214 -Delay (set value): 1215 - 1216 -{{code language="none"}}FLASH.SYNC/LASER.LOCK.EXP/F2.PPL.OSC/FMC0.MD22.0.POSITION_SET.WR{{/code}} 1217 - 1218 -Delay (encoder readback): 1219 - 1220 -{{code language="none"}}FLASH.SYNC/LASER.LOCK.EXP/F2.PPL.OSC/FMC0.MD22.0.POSITION.RD{{/code}} 1221 - 1222 -OXC. jitter: 1223 - 1224 -{{code language="none"}}FLASH.SYNC/LASER.LOCK.EXP/F2.PPL.OSC/CURRENT_INPUT_JITTER.RD{{/code}} 1225 - 1226 -\\ 1227 - 1228 -**Pulse resolved energy:** 1229 - 1230 -1a) OPCPA output: 1231 - 1232 -{{code language="none"}}FLASH.LASER/TAMC532DMA/ULGAN1/CH23.TD{{/code}} 1233 - 1234 -1b) OPCPA energy from PES (only fast channel): 1235 - 1236 -FLASH.LASER/CPUULGAN1.PULSEENERGY/OPCPA_Output/DAQ_CHANNEL 1237 - 1238 -2a) Upper breadboard Photodiode (THG) burst: 1239 - 1240 -{{code language="none"}}FLASH.LASER/TAMC532DMA/ULGAN1/CH26.TD{{/code}} 1241 - 1242 -2b) Upper breadboard Photodiode (THG) energy (in-coupling user photodiode, fast) 1243 - 1244 -{{code language="none"}}FLASH.LASER/MOD24.PES/FL24_userPD/DAQ_CHANNEL{{/code}} 1245 - 1246 -\\ 1247 - 1248 -**Attenuator angle:** 1249 - 1250 -{{code language="none"}}FLASH.FEL/FLAPP2BEAMLINES/MOTOR1.FL24/FPOS{{/code}} 1251 - 1252 -**Polarization control:** 1253 - 1254 -{{code language="none"}}FLASH.FEL/FLAPP2BEAMLINES/MOTOR14.FL24/FPOS{{/code}} 1255 - 1256 -**SysDC delay error:** 1257 - 1258 -{{code language="none"}}FLASH.LASER/ULGAN1.DYNPROP/TCFIBER.DOUBLES/DOUBLE26{{/code}} 1259 - 1260 -\\ 1261 - 1262 -**Timing error: (these two need to be observed and both=0 means no error)** 1263 - 1264 -{{code language="none"}}FLASH/CPUULGAN1.TIMING/ULGAN1/dT_alarm{{/code}} 1265 - 1266 -{{code language="none"}}FLASH/CPUULGAN1.TIMING/ULGAN1/dMPN{{/code}} 1267 - 1268 -**Laser error status:** 1269 - 1270 -\\ 1271 - 1272 -**Virtual camera X and Y history, beam size: (use slow data)** 1273 - 1274 -{{code language="none"}}FLASH.LASER/MOD24.BEAMPOS/UV.VF_BP/CENTER.X{{/code}} 1275 - 1276 -{{code language="none"}}FLASH.LASER/MOD24.BEAMPOS/UV.VF_BP/CENTER.Y{{/code}} 1277 - 1278 -{{code language="none"}}FLASH.LASER/MOD24.CAM/UV.14.VF/ROI_SPECTRUM.X.SIG{{/code}} 1279 - 1280 -\\ 1281 - 1282 -{{expand title="Parameters used until 2021"}} 1283 - 1284 1284 {{code language="none"}}/FL2/Experiment/Pump probe laser/FL24/attenuator position{{/code}}//always saved (PBD2)// 1285 1285 DOOCS prop : {{code language="none"}}FLASH.FEL/FLAPP2BEAMLINES/MOTOR1.FL24/FPOS{{/code}} 1286 1286 DAQ channel: {{code language="none"}}FLASH.FEL/FLAPP2BEAMLINES/MOTOR1.FL24/FPOS{{/code}} ... ... @@ -1313,7 +1313,6 @@ 1313 1313 DAQ channel: {{code language="none"}}FLASH.SYNC/LASER.LOCK.EXP/FLASH2.PPL1.OSC1/CURRENT_INPUT_JITTER.RD{{/code}} 1314 1314 desc: rms jitter of the fs-Oscillator 1315 1315 units: fs 1316 -{{/expand}} 1317 1317 1318 1318 [[Contents>>doc:||anchor="Contents"]] 1319 1319