Last modified by sndueste on 2025/02/06 10:58
From version 1.1
edited by sendels
on 2019/08/09 12:46
Change comment: There is no comment for this version
To version 4.1
edited by cpassow
on 2020/04/23 17:41
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.sendels
1 +XWiki.cpassow
Content
... ... @@ -1,23 +5,11 @@
1 -* [[LINK to detailled infos from MSK~[~[image:url:http://hasfweb.desy.de/pub/TWiki/TWikiDocGraphics/external-link.gif~|~|width="13" height="12"~]~]>>url:http://mskwiki/index.php?title=BAM-DAQ_Channels||shape="rect"]]
2 -
3 -\\
4 -
5 5  * 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}}))
6 6  
7 7  \\
8 8  
9 9  * There are now (since March 2017) LOW and HIGH charge channels. for now the LOW_CHARGE Channel is the relavant one.
10 -
11 -\\
12 -
13 13  * bigger numbers indicate later arrivaltime of the electrons
14 -
15 -\\
16 -
17 17  * the arrivaltime sould be within -20 ps and +20 ps . otherwise there might be a problem ...
18 -
19 -\\
20 -
21 21  * There is a BAM status parameter: FLASH.SDIAG/BAM/4DBC3/BAM_STATUS.1 (the 1 indicates FLASH1)
22 22  ** bit 0 (value: 1) = data is valid,
23 23  ** bit 1 (value: 2) = at least 1 bunch is present,
... ... @@ -29,16 +29,13 @@
29 29  
30 30  * if DBC3 is not working then also 3DBC2 can be used. there is a linear correlation between BC2 and BC3
31 31  
32 -(from Marie: der groesste Drift-Beitrag kommt immer aus dem Injektor (also alles zw. Injektorlaser und ACC39) Einfluss von ACC23 ist deutlich kleiner. Im Mittel hat man einen linearen Zusammenhang zw. Ankunftszeit BC2 zu BC3.)
33 -
34 34  \\
35 35  
36 -\\
37 -
38 38  === more Info: ===
39 39  
40 40  \\
41 41  
26 +* [[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"]]
42 42  * [[talk by Marie (2011)>>attach:FLASH-seminar-2011_BAM_study_results.pdf]]
43 43  * contact: Marie Kristin Czwalinna
44 44  
... ... @@ -49,5 +49,19 @@
49 49  \\
50 50  
51 51  * the streak camera measures the delay between optical (amplified) laser and FEL (dipole radiation). - not in respect to the master clock !
52 -* streak camera ONLY delivers data which is averaged over seveal 10 seconds. there is NO shot to shot info.
37 +* streak camera ONLY delivers data which is averaged over several 10 seconds. there is NO shot to shot info.
53 53  * a larger value of the streak camera delay indicates that the optical laser comes later than the FEL (or FEL earlier than the laser ...)
39 +
40 +\\
41 +
42 +== Calculate pump-probe delay ==
43 +
44 +* BAM measurement: difference between electrons and timing system
45 +** the BAM signal has to be added, but it seems that the sign is the different for FLASH2
46 +** it is the best to test addition/subtraction and check the results on a step function (more/less sharp)
47 +
48 +* Streak camera: difference between electrons and optical laser
49 +** it is a slow signal and should only be used as a rolling average over multiple minutes
50 +** if you see a drift in the streak camera which you do not see in the BAM it is resulting from the optical laser
51 +** 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
52 +** addition/subtraction is dependent on the setup and have to be checked