Changes for page The FLASH HDF5 structure
Last modified by sndueste on 2025/02/06 10:55
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Objects (0 modified, 1 added, 0 removed)
Details
- Page properties
-
- Parent
-
... ... @@ -1,0 +1,1 @@ 1 +FLASHUSER.Data Acquisition and controls.DAQ and controls overview.Offline data analysis (DAQ).WebHome - Content
-
... ... @@ -99,7 +99,7 @@ 99 99 * The currently developed option for large data sets: [[the FAB package>>url:https://hasfcpkg.desy.de/fab/fab.html||shape="rect"]] ... see below 100 100 * and for smaller projects: (% class="Object" %)[[https:~~/~~/gitlab.desy.de/christopher.passow/flash-daq-hdf>>url:https://gitlab.desy.de/christopher.passow/flash-daq-hdf||shape="rect"]] 101 101 102 -(% class="Object" %)See also the collection of Demo data and sample scripts : [[doc: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:FLASHUSER.Data Acquisition and controls.DAQ and controls overview.Offline data analysis (DAQ).Collection of HDF5 sample data from different beamlines.WebHome]] and [[doc:FLASHUSER.Data Acquisition and controls.DAQ and controls overview.Offline data analysis (DAQ).DEMO - Working with FLASH data.WebHome]] 103 103 {{/info}} 104 104 {{/layout-cell}} 105 105 {{/layout-section}} ... ... @@ -402,8 +402,8 @@ 402 402 ===== 403 403 arrival time (BAM) ===== 404 404 405 -{{info title="BAM information: updates 2022"}} 406 -* 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"]]405 +{{info title="BAM information: updates 2022 (status 2025)"}} 406 +* see: [[Info collection about the BAMs and how to use the BAM data>>doc:FLASHUSER.jddd-linked help pages.Info collection for the BAM.WebHome||shape="rect"]] 407 407 * The data format of the BAM has been completely altered in the 2022 shutdown 408 408 * before 2022 BAMs were always saving the arrival time information for each 1µs bucked regardless if there were electrons in the accelerator or not. IN addition the arrival times for FL1 and FL2 were saved in the same parameter ... 409 409 * THIS is now different. There are new parameters saving only the arrival times for pulses that go to FL1 and to FL2 (in detail: first time slot of the accelerator and second) ... ... @@ -411,7 +411,7 @@ 411 411 ** acc: 4DBC3 → FL0.DBC2 412 412 ** FL1: 1SFELC → FL1.SFELC 413 413 ** FL2: FL2XTDS → (% style="color:#172b4d" %)FL2.SEED5 414 -* for more Info: [[LINK to detailed infos from MSK>> url:https://confluence.desy.de/display/SDiagPublic/BAM+Data+Structure||shape="rect"]]414 +* for more Info: [[LINK to detailed infos from MSK>>doc:SDiag.How-to articles.BAM Data Structure.WebHome||shape="rect"]] 415 415 * [[Link a collection of papers related to the BAM and the analysis of pump-probe experiments>>doc:FLASHUSER.Additional helpful things.FLASH beamlines and instruments references.WebHome]] 416 416 * a recent [[talk about the working principle of the BAM>>attach:BAM-basics and outlook-2018_DESY-template_16-9Format.pdf]] 417 417 {{/info}} ... ... @@ -946,17 +946,18 @@ 946 946 arrival time (BAM) ===== 947 947 948 948 {{info title="BAM information: updates 2022"}} 949 -* 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"]]949 +* see: [[Info collection about the BAMs and how to use the BAM data>>doc:FLASHUSER.jddd-linked help pages.Info collection for the BAM.WebHome||shape="rect"]] 950 950 * The data format of the BAM has been completely altered in the 2022 shutdown 951 -* before 2022 BAMs were always saving the arrival time information for each 1µs bucked regardless if there were electrons in the accelerator or not. I addition the arrival times for FL1 and FL2 were saved in the same parameter ... 951 +* before 2022 BAMs were always saving the arrival time information for each 1µs bucked regardless if there were electrons in the accelerator or not. IN addition the arrival times for FL1 and FL2 were saved in the same parameter ... 952 952 * THIS is now different. There are new parameters saving only the arrival times for pulses that go to FL1 and to FL2 (in detail: first time slot of the accelerator and second) 953 953 * There has been also a renaming (and relocation) of the BAMs. 954 954 ** acc: 4DBC3 → FL0.DBC2 955 955 ** FL1: 1SFELC → FL1.SFELC 956 -** FL2: 8FL2XTDS → (% style="color:#172b4d" %)FL2.SEED5957 -* for more Info: [[LINK to detailed infos from MSK>> url:https://confluence.desy.de/display/SDiagPublic/BAM+Data+Structure||shape="rect"]]956 +** FL2: FL2XTDS → (% style="color:#172b4d" %)FL2.SEED5 957 +* for more Info: [[LINK to detailed infos from MSK>>doc:SDiag.How-to articles.BAM Data Structure.WebHome||shape="rect"]] 958 958 * [[Link a collection of papers related to the BAM and the analysis of pump-probe experiments>>doc:FLASHUSER.Additional helpful things.FLASH beamlines and instruments references.WebHome]] 959 959 * a recent [[talk about the working principle of the BAM>>attach:BAM-basics and outlook-2018_DESY-template_16-9Format.pdf]] 960 +* 960 960 {{/info}} 961 961 962 962 {{expand title="Discontinued BAM format (used until end 2021)"}} ... ... @@ -1012,30 +1012,16 @@ 1012 1012 units: fs (bigger numbers (typically) indicate later arrival times of the electrons). 1013 1013 1014 1014 1015 -(% style="color:#f f6600" %)DBC2/error(HDF5 name not yet implemented - see zraw){{code language="none"}}/FL2/Electron Diagnostic/BAM/{{/code}}(%%)1016 +DBC2/error (% style="color:#f39c12" %)(HDF5 name not yet implemented - see zraw)(%%)/FL2/Electron Diagnostic/BAM/ 1016 1016 //always saved (PBD)// 1017 -(% style="color:#000000" %)E.bamError{{code language="none"}}DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIM{{/code}}(%%) 1018 -(% style="color:#000000" %)FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.BAMERROR{{code language="none"}}DAQ channel: {{/code}}(%%) 1019 -desc: If the value is 0 , the BAM is working well. If it is non-zero there is a problem !! 1020 - 1021 - 1022 -(% style="color:#ff6600" %)DBC2/status (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL2/Electron Diagnostic/BAM/{{/code}}(%%) 1023 -//always saved (PBD)// 1024 -(% style="color:#000000" %)E..bamStatus.//2//{{code language="none"}}DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIM{{/code}}(%%) 1025 -(% style="color:#000000" %): FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.BAMSTATUS.2{{code language="none"}}DAQ channel{{/code}}(%%) 1026 -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 1027 - 1028 - 1029 -DBC2/error (HDF5 name not yet implemented - see zraw)/FL2/Electron Diagnostic/BAM/ 1030 -//always saved (PBD)// 1031 1031 DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.bamError.2 1032 1032 DAQ channel: FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.BAMERROR.2 1033 1033 desc: If the value is 0 , the BAM is working well. If it is non-zero there is a problem !! 1034 1034 1035 -DBC2/status (HDF5 name not yet implemented - see zraw)/FL 1/Electron Diagnostic/BAM/1022 +DBC2/status (% style="color:#e67e22" %)(HDF5 name not yet implemented - see zraw)(%%)/FL2/Electron Diagnostic/BAM/ 1036 1036 //always saved (PBD)// 1037 -DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME. .bamStatus.//1//1038 -DAQ channel: FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.BAMSTATUS. 11024 +DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.bamStatus.//2// 1025 +DAQ channel: FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.BAMSTATUS.2 1039 1039 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 1040 1040 1041 1041 ... ... @@ -1064,18 +1064,17 @@ 1064 1064 units: fs (bigger numbers (typically) indicate later arrival times of the electrons). 1065 1065 1066 1066 1067 - (% style="color:#172b4d" %)SEED5(% style="color:#ff6600" %)/error(HDF5 name not yet implemented - see zraw){{code language="none"}}/FL2/Electron Diagnostic/BAM/{{/code}}(%%)1054 +FL2.SEED5/error (% style="color:#f39c12" %)(HDF5 name not yet implemented - see zraw)(%%)/FL2/Electron Diagnostic/BAM/ 1068 1068 //always saved (PBD)// 1069 - (% style="color:#172b4d" %)**FL2.SEED5**(% style="color:#000000" %)E.bamError{{code language="none"}}DOOCS prop : FLASH.SDIAG/BAM//ARRIVAL_TIM{{/code}}(%%)1070 - (%style="color:#000000" %):FLASH.SDIAG/BAM/(% style="color:#172b4d" %)**FL2.SEED5**(% style="color:#000000" %)/ARRIVAL_TIME.BAMERROR{{code language="none"}}DAQ channel{{/code}}(%%)1071 -desc: 1056 +DOOCS prop : FLASH.SDIAG/BAM/FL2.SEED5/ARRIVAL_TIME.bamError.2 1057 +DAQ channel: FLASH.SDIAG/BAM/FL2.SEED5/ARRIVAL_TIME.BAMERROR.2 1058 +desc: If the value is 0 , the BAM is working well. If it is non-zero there is a problem !! 1072 1072 1073 - 1074 -(% style="color:#172b4d" %)SEED5(% style="color:#ff6600" %)/status (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL2/Electron Diagnostic/BAM/{{/code}}(%%) 1060 +FL2.SEED5/status (% style="color:#e67e22" %)(HDF5 name not yet implemented - see zraw)(%%)/FL2/Electron Diagnostic/BAM/ 1075 1075 //always saved (PBD)// 1076 - (% style="color:#172b4d" %)**FL2.SEED5**(% style="color:#000000" %)E.bamStatus.//2//{{code language="none"}}DOOCS prop : FLASH.SDIAG/BAM//ARRIVAL_TIM{{/code}}(%%)1077 - (%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}}(%%)1078 -desc: 1062 +DOOCS prop : FLASH.SDIAG/BAM/FL2.SEED5/ARRIVAL_TIME.bamStatus.//2// 1063 +DAQ channel: FLASH.SDIAG/BAM/FL2.SEED5/ARRIVAL_TIME.BAMSTATUS.2 1064 +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 1079 1080 1080 1081 1081 [[Contents>>doc:||anchor="Contents"]]
- URLShortener.Code.URLShortenerClass[0]
-