Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Cloak

When the laser is roughly centered on the X-ray spot (the laser should be on the order of 100-150 um  but this can vary between experiments with larger spots being possible), the X-ray beam needs to be made similar in size at the interaction point to the laser to maximize the signal, to make sure that the part of the target the laser sees is fully modified by the x-ray beam.  In order to do this at CXI, insert Be lenses at the DG2 location to focus the beam upstream of SC1 and produce a larger, divergent beam at the IP.

The DG2 lens screen is found in the DG2 section of CXI home. It is password protected with the usual CXI password.

The Be lenses will need to be aligned in both x and y using the DG2 YAG to monitor alignment. Then, the DG2 slits need to be narrowed such that there is no beam intensity outside the lens aperture.  If intensity remains outside of the lens aperture it will be focused to the 1.3 um spot size in the IP and damage the YAG at full intensity.

Beam on DG2 without lenses:

Beam on DG2 with lenses inserted but without slits narrowed:

Beam on DG2 with lenses inserted and with DG2 slits narrowed:

Expanded beam at IP YAG covering laser spot:

Open all gate valves and remove objects upstream of SC1 before bringing the beam to the IP. 

...

Since the beam is being refocused upstream of SC1 to make the larger beam, we could inadvertently place the focused beam on upstream diamond windows or other objects and damage them

Look at the beam on the clear YAG in SC1 (or the frosted YAG is fine for this as it allows for a check of the spatial overlap of the x-rays and optical laser)

The beam should be similar in size to the laser beam or the signal used for timing in SC1 will be low

...

Optional: Use the large beam at SC1 to align the DSB slits, SC1 jaws, and SC1 ap0 and ap1 motors to be roughly centered. 

...

It is easy, and the SC1 +Y jaw and DSB +Y slits are particularly useful for cleaning up scatter from the nozzle that may make the data quality worse

Toggle Cloak
Find t0 at the IP with a fine timing scan.

Cloak

The exact procedure for doing a fine timing scan tends to change often depending on the status of various scripts. Currently (as of Feb. 2022), the icxi script does not seem to work. A manual scan will always work if you cannot get an automated scan to work.

Set up Aquiris.




For the timing scan you will need  close to 100% transmission in the sample chamber (likely > 25%)

...

. This is required because the desired transmission change is driven by high intensity x-ray effects.

For the timing scan we (as of 22-Oct-2018) are using a timing scan in icxi (a hutch python instance)

Load icxi by typing "icxi" in any terminal on the cxi machines (cxi-daq, cxi-monitor, etc.)

Load the time scan by typing "%timescans" into the ipython terminal
Image Modified

The laser signal should be on the acqiris using the diode installed on the chamber door.  In the case of LS87 we were using

...

Channel 1 to look at the diode outside SC1 and we should strive for a peak height of ~1V to ensure that the cross correlation signal is strong.
Image Modified

For time scan, type "ts.scan_times(start_delay, end_delay, step_size, nevents_per_timestep=360, randomize=True)" in the icxi terminal
Image Modified

Before running the scan, a plot needs to be set up that plots the integrated laser intensity on the Acqiris vs the laser ns Target Time (LAS:FS5:VIT:FS_TGT_TIME_DIAL)
Image Modified

Set cursors both earlier and later than the laser peak on the Acqiris and in "Expr" under Expression manually add "a integral b" using the integral sign

Plot A integral b as a function of LAS:FS5:VIT:FS_TGT_TIME_DIAL and choose the hi and low values consistent with the scan.  The above example shows the typical final low and hi values chosen when we are very close to t0

The time scan, if done properly, will produce a plot that looks similar to the one below
Image Modified

What is identified as t0 is a never ending matter of debate. However, the majority of the time, the width of the falloff in transmission fairly closely matches the distribution of the jitter in arrival times. Since the measurements made here average many shots, we are sensitive to this jitter. The photoelectron release is assumed to be essentially instantaneous with the width driven by the time difference in propagation of the x-rays and the laser through the material and the jitter in the laser arrival time. Typically, the jitter dominates with a thin target like a 20 um YAG. If the measurement is jitter dominated, then the inflection point is the right choice for time zero. If it is determined that jitter is not the dominant factor in the width of the falloff in transmission, then one can determine a more suitable reference point earlier in time. Since the jitter is typically >200fs and approaching 400 fs, as was the case for the example here, then a 400 fs width of the drop as shown above makes the inflection point likely the right choice.  In the example from LS87 above, a t0 value of -400 fs would be a reasonable number (with -300 fs perhaps being a bit better)  with a +/- 100 error bar. One thing to be careful is in the past, we have seen "periodic jitter" where the timing would drift back and forth every 20-30 seconds with an amplitude of more than 1 ps sometimes. Under those circumstances, the phase of that "priodic jitter" when the scan is close to time zero could easily move the apparent t0 by a few 100fs. The measurements at every data point of the scan should ideally be longer than any periodic jitter period, if this situation is present on a given day.

The t0 value would be updated in the laser timing screen
Image Modified

In this example, the ns Target Time should be set to -400 fs to determine the value of the final timing number (LAS:FS5:VIT:FS_TGT_TIME, in the above image it is 4392.074100).

The ns Offset should be changed to be the value of LAS:FS5:VIT:FS_TGT_TIME.  Once this change is made the ns Target Time should reset automatically to 0.000000.

Once timing has been established in SC1, timing must be found at the time tool.  If the time tool delay stage position is roughly known, then timing at the time tool is relatively easy and you can skip to the time tool fine timing section.

Rough timing at the time tool

...