Last modified by sndueste on 2025/02/06 10:58
From version 7.1
edited by cpassow
on 2020/04/24 10:43
Change comment: There is no comment for this version
To version 13.1
edited by sndueste
on 2025/02/05 11:22
Change comment: Renamed back-links.

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.cpassow
1 +XWiki.sndueste
Content
... ... @@ -1,62 +1,76 @@
1 -* the relevant data is the Arrivaltime FLASH.SDIAG/BAM/4DBC3/LOW_CHARGE_ARRIVAL_TIME
2 -* besides the arivaltime from FLASH1 there is also the FLASH2/3 electron arrival time saved. The BAM data is saved for the complete RF pulse. First bunches are from FLASH1 then there is a gap for switching and then there is a second part for FLASH2 (starting at the FLASH2 start time (recorded in DAQ as {{code language="none"}}/FL2/Timing/start time flash2{{/code}}))
1 +== Some general stuff: ==
3 3  
4 -\\
3 +* (% style="color:#000000" %)There are several BAMs in FLASH. Essentially one in the accelerator section  (FL0.DBC2, Previously: 4DBC3) and one close to the respective undulator section (FL1.SFELC and FL2.SEED5).
4 +* (% style="color:#000000" %)The BAM measures the arrival time for each single electron bun in the bunch train (for working principle see [[MSK SDiag Projects>>url:https://confluence.desy.de/display/SDiagPublic/MSK+SDiag+Projects||shape="rect" style="color: rgb(0,0,0);"]] or literature listed below)   
5 +* The data format of the BAM has been completely altered in the 2022 shutdown
6 +* (% style="color:#003366" %)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 ...
7 +* (% style="color:#003366" %)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)
8 +* (% style="color:#003366" %)(typically) Bigger numbers indicate later arrival time of the electrons
9 +* (% style="color:#003366" %)The arrival time should be within -20 ps and +20 ps - otherwise there might be a problem ...
10 +* (((
11 +(% style="color:#003366" %)The actual time t0 = 0ps is an arbitrary offset which is only changed after setting up the system after, e.g., a maintenance time, and has no relevance.
12 +)))
13 +* (((
14 +(% style="color:#003366" %)What one usually does, after defining/finding time zero in the experiment, is either observe the relative changes for a single bunch during the course of the measurement run compared to the starting point, or (in addition) observe the relative deviation across all bunches within the same bunch train.
15 +)))
16 +* (((
17 +(% style="color:#003366" %)Those deviations and drifts happen usually only in the order of 50fs to 200fs; depending on the machine setup.
18 +)))
19 +* (((
20 +(% style="color:#003366" %)The short-term timing jitter (over several 100 trains) for each individual bunch, i.e. the standard deviation from their mean value, is usually ~~ 20fs.
21 +)))
22 +* (((
23 +(% style="color:#003366" %)The actual measurement resolution of a BAM can be - currently - as good as 3fs, for each bunch in the full train.
24 +)))
5 5  
6 -* There are now (since March 2017) LOW and HIGH charge channels. for now the LOW_CHARGE Channel is the relavant one.
7 -* bigger numbers indicate later arrivaltime of the electrons
8 -* the arrivaltime sould be within -20 ps and +20 ps . otherwise there might be a problem ...
9 -* There is a BAM status parameter: FLASH.SDIAG/BAM/4DBC3/BAM_STATUS.1 (the 1 indicates FLASH1)
10 -** bit 0 (value: 1) = data is valid,
11 -** bit 1 (value: 2) = at least 1 bunch is present,
12 -** bit 2 (value: 4) = calibration is on,
13 -** bit 3 (value: 8) = internal feedback is on,
14 -** bit 4 (value: 16) = tuning mode is on
26 +== Data structure ==
15 15  
16 -\\
28 +* (% style="color:#000000" %)The details about the functionality and the data structure can be found on the page:  (%%)**[[ BAM Data Structure>>https://xwiki.desy.de/xwiki/bin/view/SDiag/How-to%20articles/BAM%20Data%20Structure/||shape="rect"]]**
29 +* also see  [[doc:FLASHUSER.Data Acquisition and controls.DAQ and controls overview.Offline data analysis (DAQ).The FLASH HDF5 structure.WebHome]]
30 +* an example for the correction of pump-probe delay [[can be found here>>https://xwiki.desy.de/xwiki/bin/view/FLASHUSER/Data%20Acquisition%20and%20controls/Data%20Access%20at%20FLASH%20%28DAQ%2C%20gpfs%2C...%29/Offline%20data%20analysis%20%28DAQ%29/Collection%20of%20HDF5%20sample%20data%20from%20different%20beamlines/]]
17 17  
18 -* if DBC3 is not working then also 3DBC2 can be used. there is a linear correlation between BC2 and BC3
32 += Publications related to BAM =
19 19  
20 -=== more Info to the BAM: ===
34 +=== BAM principle ===
21 21  
22 -* [[LINK to detailed infos from MSK (may only work inside DESY network)(% class="confluence-embedded-file-wrapper confluence-embedded-manual-size" %)~[~[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||rel="nofollow" shape="rect" class="external-link"]]
23 -* [[talk by Marie (2011)>>attach:FLASH-seminar-2011_BAM_study_results.pdf]]
24 -* contact: Marie Kristin Czwalinna
36 +1. (% style="color:#172b4d" %)A. Angelovski, et al.(%%)
37 +(% style="text-align:left" %)//Evaluation of the cone-shaped pickup performance for low charge sub-10 fs arrival-time measurements at free electron laser facilities//(%%)
38 +(% style="color:#172b4d" %)Phys. Rev. ST Accel. Beams (% style="text-align:left" %)**18**(% style="color:#172b4d" %), 012801 (2015)(%%)
39 +[[https:~~/~~/doi.org/10.1103/PhysRevSTAB.18.012801>>url:https://doi.org/10.1103/PhysRevSTAB.18.012801||rel="nofollow" shape="rect" style="text-align: left;"]]
25 25  
26 -\\
41 +=== Two publications showing how to use the BAM data to improve the time resolution: ===
27 27  
28 -= General information for the data analysis of pump-probe experiments =
29 -
30 -\\
31 -
32 -please have a close look to the publication:
33 -
34 -Evgeny Savelyev, et al,  //Jitter-Correction for IR/UV-XUV Pump-Probe Experiments at the FLASH Free-Electron Laser//,
43 +1. Evgeny Savelyev, et al, 
44 +//Jitter-Correction for IR/UV-XUV Pump-Probe Experiments at the FLASH Free-Electron Laser//,
35 35  New J. Phys. **19**, 043009 (2017), [[https:~~/~~/doi.org/10.1088/1367-2630/aa652d>>url:https://doi.org/10.1088/1367-2630/aa652d||shape="rect"]]
46 +1. (((
47 +Dennis Mayer, Fabiano Lever and Markus Gühr,
48 +//Data analysis procedures for time-resolved x-ray photoelectron spectroscopy at a SASE free-electron-laser//,
49 +J. Phys. B: At. Mol. Opt. Phys. **55**, 054002 (2022); [[https:~~/~~/doi.org/10.1088/1361-6455/ac3c91>>url:https://doi.org/10.1088/1361-6455/ac3c91||shape="rect" style="text-decoration: none;"]]
50 +)))
36 36  
37 -describing in detail the usage of BAM, streak camera and delay line data in order to get the actual time axis as reliable as possible.
52 +=== Publications showing the correlation between the values measured by the BAM and the XUV pulse arrival time ===
38 38  
39 -\\
54 +1. (% style="color:#000000" %)//** Description of the FLASH synchronization system**//(%%)
55 +(% style="color:#000000" %)S. Schulz, et al.(%%)
56 +(% style="text-align:left" %)//Femtosecond all-optical synchronization of an X-ray free-electron laser//(% style="color:#000000" %),(%%)
57 +(% style="color:#000000" %)Nature Communications (% style="text-align:left" %)**6**(% style="color:#000000" %), 5938 (2015); (%%)[[http:~~/~~/dx.doi.org/10.1038/ncomms6938>>url:http://dx.doi.org/10.1038/ncomms6938||shape="rect" style="text-decoration: none;text-align: left;"]]
58 +
59 +1. //**Showing a correlation of 11 fs rms between BAM and XUV arrival time**//
60 +R. Ivanov, et al to be published 2022  
61 +
62 +1. (((
63 +//**Showing a correlation of 20 fs rms between BAM and XUV arrival time**//
64 +R. Ivanov, J. Liu, G. Brenner, M. Brachmanski and S. Düsterer,
65 +//FLASH free-electron laser single-shot temporal diagnostic: terahertz-field-driven streaking//,
66 +Special Issue (PhotonDiag2017),
67 +J. Synchrotron Rad.** 25**, 26-31 (2018);[[ https:~~/~~/doi.org/10.1107/S160057751701253X>>url:https://doi.org/10.1107/S160057751701253X||shape="rect" style="text-decoration: none;"]]
68 +)))
69 +1. (((
70 +//**Study of arrival time fluctuations**//
71 +Ivette J. Bermúdez Macias, Stefan Düsterer, Rosen Ivanov, Jia Liu, Günter Brenner, Juliane Rönsch-Schulenburg, Marie K. Czwalinna, and Mikhail V. Yurkov,
72 +//Study of temporal, spectral, arrival time and energy fluctuations of SASE FEL pulses//,
73 +Optics Express 29, 10491-10508 (2021); [[https:~~/~~/doi.org/10.1364/OE.419977>>url:https://doi.org/10.1364/OE.419977||shape="rect" style="text-decoration: none;"]]
74 +)))
40 40  
41 -Here is a summary of the ideas:
42 -
43 -== Streak camera info ==
44 -
45 -* the streak camera measures the delay between optical (amplified) laser and FEL (dipole radiation). - not in respect to the master clock !
46 -* streak camera ONLY delivers data which is averaged over several 10 seconds. There is NO shot to shot info.
47 -* a larger value of the streak camera delay (typically) indicates that the optical laser comes later than the FEL (or FEL earlier than the laser ...)
48 -
49 -\\
50 -
51 -\\
52 -
53 -{{info title="Correction of pump-probe delay"}}
54 -* BAM measurement: difference between electrons and timing system
55 -** usually the BAM signal has to be added to the delay ...
56 -** it is the best to test addition/subtraction and check the results on a step function (more/less sharp) - if there is no change of the data with + and - there is anyway something wrong. please contact your local contact for more information / help
57 -* Streak camera: difference between electrons and optical laser
58 -** it is a slow signal and should only be used as a rolling average over multiple minutes
59 -** if you see a drift in the streak camera which you do not see in the BAM it is resulting from the optical laser
60 -** if this (BAM - streak camera signal) is significant e.g. 200 fs over 1 h, it means the drift compensation was probably off and it should be compensated
61 -** addition/subtraction is dependent on the setup and have to be checked
62 -{{/info}}
76 +
BAM-basics and outlook-2018_DESY-template_16-9Format.pdf
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +3.7 MB
Content
FLASH-seminar-2011_BAM_study_results.pdf
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +2.1 MB
Content