HOME ESR EXPERIMENTS LABS etc
E121 E127 E132 E125 E143 laser_cooling_2021 E142 Ê128 E146 E0052 E0018
  proton-capture on 118Te, Page 1 of 29  Not logged in ELOG logo
ID Date Author Category Subjectdown Year
  38   Tue Mar 10 09:41:26 2020 JanDetectorsx-ray background from BaF 
The BaF2 detectors planned to be installed at the target induce an additional background in the x-ray detectors sitting below inside the target chamber. 
We made test measurements with an x-ray detector for estimating the background in the region of interest for our K-REC measurements (35 to 50 keV).

For the interval [35-50 keV]:
Normal background level: 0.065 (s*keV)^-1
BaF2 in 5cm distance:    0.078 (s*keV)^-1
This is an increase by about 22%

Assuming an increase by 100% induced by 6 BaF2 in the vincinity of the Ge-detectors this seems acceptable.

However additional BaF-induced peaks are also visible at ~30 keV and ~60 keV. While these are not in the region of interest for the K-REC, we need to be aware of them!

spectra are available on the Frankfurt exp-astro Server at /home/glorius/e127/
  241   Mon Mar 23 12:30:39 2020 laszloAnalysiswith and without scraper 
  62   Wed Mar 18 09:53:28 2020 Laszlo, JanGeneralvacuum after opening gate valve 
Gate valve to DSSSD setup was opened on Tue 17.03. ~9:00

The vacuum on Wed 18.03. ~9:00 was
1.6e-10 mbar at DSSSD setup
1.0e-11 mbar at ESR dipole
  277   Thu Apr 23 19:09:58 2020 LaszloCalibrationtheoretical K-REC cross sections  
Find attached Andrey Surzhykov's calculations for the theta angle in respect to the beam direction (in lab. frame) vs. cross section for 124Xe54+ and 118Te52+.
The calculations made for collision with two H atoms with the accuracy of 1%. There are no molecular corrections done, but these corrections are within 1%.

The photon-emission is symmetrical in the azimuthal phi angle, but asymetric in theta. The K-REC cross section is given for each integer theta angle. The problem is that our 90° and 145° xray detectors cover more integer theta-angles --> The disk shaped entrance window of the Xray-detectors is sliced for each covered theta angles, and the CS values are averaged together with the weights of the area of the corresponding slice. The 35° det had a non-disk shaped slit collimator! Was it aligned vertical or horizontal or random? I assumed that it had a vertical position --> only cs at theta=35° needs to taken into account

90°145°35°
weighted cs_Xe [barn/sr]128,44441,96745,550
weighted cs_Te [barn/sr]118,61638,91841,740


For the steradian values I calculated the area of the entrance window of the Xray detectors and I divided it with the area of the sphere with radius = distance between source and det. If r=radius of the entrance window, D=distance between source and det.: covered steradian = r^2*pi/(4*pi*D^2) [%], covered steradian = 4Pi*[r^2*pi/(4*pi*D^2)] [4pi]. This is valid for the 90° and 145° Xray detectors. The area of 35° det. was calculated individually.

90°145°35°
sr [%]0,002370,000760,00002
sr [4pi]0,02980,00960,00030


I converted barn/sr to barn in the following way: steradian[4pi]*weigthed_cs [barn/sr] = weigthed_cs [barn]. I am not 100% sure if I need here the steradian in [4pi] or in [%].

90°145°35°
weighted cs_Xe [barn]3,82470,40120,0137
weighted cs_Te [barn]3,53210,37200,0125
  48   Sun Mar 15 17:13:21 2020 Laszlo, JanCalibrationthe x-ray gate issue 
We found a strange behaviour of our ADC gates for the x-ray detectors.
The setting as shown in the foto below corresponds to a delay of 5 us and a gate length of 15 us.
This is the only setting that produces nice spectra, even though the signals and gate are not aligned.
The setting is extremely sensitive to the delay 4 us still works but 3 or 7 us give already reduced energy values and beyond these values the spectra disapears.

For now it was decided to operate with this not-understood settings because the result is pretty good...
However, further investigation to understand whats happening would be desirable.

Additional note:
This effect appeared after using the new ortec SpecAmps. Before this we used old Tennelec Amps which delivered horrible resolution, but the gates and signals could be matched as expected at this time.
  291   Thu Apr 22 10:56:20 2021 JanDetectorstarget-chamber det. distances2021
This is the lookup table for the distance of each x-ray detector to the target.
See attached foto for explanation.

It is the same values as in 2020: https://elog.gsi.de/esr/E127/36

Detector A (dA) [mm] B (dB) [mm] C (dC) [mm] calculate result [mm]
35° 136.0 (1.0) 20.0 (0.2) 450.0 (0.5) C + B - A 334.0 (?)
90° 76.0 (0.5) 20.0 (0.2) 447.0/2 = 223.5 (1.0) C + B - A 167.5 (?)
145° 165.0 (1.0) 20.0 (0.2) 450.0 (0.5) C + B - A 305.0 (?)

Errors are estimated after measurement, final errorbars have to be double checked!
  130   Sat Mar 21 14:52:05 2020 LaszloGeneraltarget optimization 
previous position of the beam at target was -3mm (for the night position)
max. intensity position of the beam at target 1s -1mm. --> now it is set to this position

now Ulli also increasing the density of the jet. Right now Ulli is warming the noozle. --> takes 1hour roughly.
Earlier: 1.4E13
Now: 
  68   Fri Mar 20 01:21:00 2020 LaszloGeneraltarget is switched on event based 
  147   Sat Mar 21 21:36:06 2020 JanRunstarget incident 
in run 66 or 67 we had a single ESR cycle for which the target didn't switch off for new injection and deceleration etc.
Very likely the DAQ also didn't get an OFF signal and collected OFF data to the TRIGGER=1 (ON data) branch.
As a consequence we collected about ~100 counts on the Si in one shot, which was about ~20 counts before this shot.

attached:
1.picture of the target density and beam current at this time.
  201   Sun Mar 22 18:35:43 2020 Laszlo target dropped aagain 
there was a drop again from 8.6e13 to 7e13 in the target density
  361   Fri May 21 10:00:51 2021 JanAcceleratortarget bump2021
The target overlap was optimized on xray and si rates.
The setting now is -10mm in SC9
  198   Sun Mar 22 17:45:07 2020 LaszloGeneralswitching to primary beam 
We have finished the measurement with the fragments.

Now Yury will setup up a primary beam through the FRS, but without target in FRS.
We are hoping for increased intensity and stable gas target.
The plan is to make a measurement with and without the scraper in order to see the effect of scraping the Rutherford scattering.
  64   Thu Mar 19 15:09:29 2020 JanGeneralstarting off with DSSSD 
here is my short guide how to start with the measurement as soon as we have a beam available.

0. ESR timing in DAQ (maybe Uwe can also assist here)
    - when the cycle is running already, even for tuning, you can try to make the cabling for ESR timing (jet ON/OFF)
    - replace the gate generator signals by the ESR timing signals in the Messhütte and check UDP reader (E127_rates)
    - the settings for ESR timing (event & machine) depend on the cycle, talk to Sergey or so, its the same settings as for the target in HKR
    - with the current cycle this would be: ON-{machine 11, event 55}, OFF-{machine 13, event 55}
    - the event for end of this process is alway 55
    - if it works all tpat rates should be switching from upper to lower panel with the ESR cycle in the rate monitor (as they do now with the gate generator)

Once the tuning is finished:

1. optimize target ON/measurement time
    - switch target to event and use the same machines/events as above
    - check number of ions in ESR at ON and OFF and lifetime of beam
    - we should measure for a drop of a factor of 3-4 roughly i would say
    - e.g. start with 2e5 and stop with 5e4
   - if we start with more, we can measure longer

1. without target,  put in Si detector (GE01DD4AS in device controle) to max-in position
    - see if it disturbs the ESR cycle (discuss optimization with ESR guys if necessary)
    - we should also check vacuum in ring (i think this can be done remotely, ask Markus, Sergey or so)

2. make Si settings with beam (call me i can do things remotely)
    - voltage to 60 volts, use E127_epics (i would expect the current at ~1uA, if no light source is close by)
    - check picoscope for signals during entire cycle
    - picoscope: (ch1: E_x ,ch2: Ex, ch4: gate)
    - select central strip in y and 1st or 2nd x-strip as monitor output with epics (E127_epics > MSCF Si 1 & 2)
    - if you don't get any at all, switch on target in measurement cycle (or permantely)
    - still no nice signals? -> polarity is probably wrong, we need to switch MSCF of X and Y
    - during our measurement period, the signals should be well below 10V (goal for reaction ions ~6V)
    - adjust shaping time, gain, pole zero, threshold (epics) and Si-gate delay and length (e127.trlo) until you get nice histos
    - if you see large rates at injection or decelleration, we should try to shield detector with the scraper
    - put it as close as possible without disturbing the cycle, i.e. loosing more beam than without scraper
    - we can also move it by event (e.g. move in or out on start or end of machines 4,6,11,12,13) depending on when it disturbs

3. find beam position at detector
    - stop the cycle in SC 11
    - try to scrape it away by moving the detector our with small steps
    - you will need several injections, because if the short liftime, can get tedious
    - follow instructions and numbers here: https://elog.gsi.de/esr/E127/37

4. last things
    - ignore BaF for now
    - check that x-rays are working, spectra okay? resolution?
    - check rates during ON (x-rays: some 100 Hz each, Si: low, probably below 100Hz) and OFF (below 100Hz for all but BaF)
    - check deadtime, do we need downscaling for any detector? (i would not expect this, BaF is downscaled already, don't worry)

5. first runs
     - measure with and without scraper to confirm that Rutherford is under controle
     - how long? > depends on the statistics
     - try to see a clean effect of scraping, e.g. by the Si-plot E_ion vs x_position (Laszlo)
  22   Wed Sep 25 13:03:46 2019 LaszloAnalysissimulations on 118Te+p 
I have made some simulations at 8AMeV, 7AMeV and 4AMeV energies for the main 118Te + p reaction channels. For the
Rutherford simulations credits to Yuanming! For each energy there are 3 simulations: without the scraper, with the
scraper (online), scraper (online) + E-truncation (offline). The scraper is treated as an "ideal scraper" meaning
that there is no scattering at the edges (maybe worth a GEANT4?). The slit position is at -3cm from the beam, the vertical
length is 7cm (centralized). The following channels are combined in the
simulation:

-8AMeV:
  Rutherford
  pg channel, 5cascade model. Photon emission is treated isotropically
  pn channel, including: -->gs, -->1-->gs, -->2-->gs, -->3-->gs, -->3-->1-->gs, -->4-->1-->gs, -->5-->3-->gs,
-->5-->3-->1-->gs, -->5-->4-->1-->gs decay chains with their weights. Neutron and photon emission is treated isotropically.

-7AMeV:
  Rutherford
  pg channel, 4cascade model. Photon emission is treated isotropically

-4AMeV:
  Rutherford
  pg channel, 3cascade model. Photon emission is treated isotropically


The detector position is -2.5cm from the beam in the radial direction and centered vertically with a 45° tilt. 
The cross section values for pg and pn, the pn channel mixing, and the pg cascade number is based on TALYS simulations.
The other two input parameters are the luminosity and the measurement time. For the simulation, a little
pessimistic (or realistic?) scenario is taken: L = 10^24 cm-2s-1, and t = 10^4 s. From this values, from the N=CS*L*t
equation, the pg counts (based on the TALYS
cross sections) are the following: 8AMeV ~267, 7AMeV ~163, 4AMeV ~5! This means that to reach the Gamow-window
energies is challenging, but with a well-working scraper it is not impossible to reach.


As it is visible, the 8AMeV 118Te(p,g) case is very similar to the 7AMeV 124Xe case. The p,n threshold is
somewhere ~7.5MeV.
  360   Fri May 21 01:17:37 2021 LaszloAnalysissimple analysis code2021
//a simple code (template) for offline analysis
//made by Laszlo, serves as a simple demonstration for enthusiastic shifters
//it creates a "no double counting Si 2D pos" histo
//usage:
//
//save the file as eg. "simple_code.c"
//root -l
//.L simple_code.c++
//run()
//when counter finished: ".q"

#define INPUT1 "input.root"//first unpack the lmd, then give the path of the unpacked .root file.

#define OUTPUT "./"//folder of the output. minimum input: "./"

#define ROOT_NAME "dummy.root"//name of the output

#include <cmath>
#include <string>
#include <sstream>
#include <cstdlib>
#include <cstdio>
#include <ctime>
#include <fstream>
#include <iostream>
#include <stdint.h>
#include "TROOT.h"
#include "TAttText.h"
#include "TAxis.h"
#include "TCanvas.h"
#include "TChain.h"
#include "TCut.h"
#include "TF1.h"
#include "TFile.h"
#include "TGraph.h"
#include "TGraphAsymmErrors.h"
#include "TGraphErrors.h"
#include "TH1.h"
#include "TH2.h"
#include "THistPainter.h"
#include "TKey.h"
#include "TLatex.h"
#include "TLegend.h"
#include "TMath.h"
#include "TMatrixD.h"
#include "TMinuit.h"
#include "TMultiGraph.h"
#include "TNtuple.h"
#include "TPave.h"
#include "TPaveText.h"
#include "TPoint.h"
#include "TRandom.h"
#include "TRint.h"
#include "TStyle.h"
#include "TString.h"
#include "TTree.h"
#include "TH1F.h"
#include "TH2F.h"
#include "TSystem.h"
#include "TProfile.h"
#include "TVirtualFitter.h"
#include "TCanvas.h"
#include "TLegend.h"
#include "TColor.h"
#include <time.h>

using namespace std;

inline bool exists_test0 (const std::string& name) {
    ifstream f(name.c_str());
    return f.good();
}

///////////////////////////////////////////////////////////////////////////////////////////////

void loop(TChain *fChain){
	
	//setting pedestal values
	int PEDESTAL_LOW=400;
	int PEDESTAL_HIGH=8000;
	

	//this normally should be in a separate header, branches are defined.
	UInt_t          trigger;
	fChain->SetBranchAddress("TRIGGER",&trigger);
	UInt_t          E_SiY[17];
	UInt_t          E_SiX[17];
	UInt_t          t_SiY[17];
	UInt_t          t_SiX[17];
	for(int a=1;a<17;a++){
		fChain->SetBranchAddress(Form("E_SiY%d",a),&E_SiY[a]);
		fChain->SetBranchAddress(Form("E_SiX%d",a),&E_SiX[a]);
		fChain->SetBranchAddress(Form("t_SiY%d",a),&t_SiY[a]);
		fChain->SetBranchAddress(Form("t_SiX%d",a),&t_SiX[a]);
	}

	//creating histos
	TH2D *h_pos_si_xy=new TH2D("h_pos_si_xy", "h_pos_si_xy",16,0.5,16.5,16,0.5,16.5);

	//creating and initializing some variables used in the event loop (for "no double counting")
	int r_pos_x=0,r_pos_y=0;
	int dc_Ex_max=-999;
	int dc_Ey_max=-999;
	
	
	Long64_t nentries = fChain->GetEntries();
	Long64_t nbytes = 0;

	//starting the entry loop
	for (Long64_t i=0; i<nentries;i++){

		nbytes += fChain->GetEntry(i);
		//event countdown
		if ((float(i)/100000.)==int(i/100000)){cout << "event: " << i << " \tof " << nentries << endl;}


		if(trigger==1){//trigger 1 = TargetON

			dc_Ex_max=-999;
			dc_Ey_max=-999;

			for(int i_x=1;i_x<17;i_x++){
				for(int i_y=1;i_y<17;i_y++){

					if( ((int)t_SiX[i_x])>0 && ((int)t_SiY[i_y])>0){
						if( PEDESTAL_LOW<((int)E_SiX[i_x]) && PEDESTAL_HIGH>((int)E_SiX[i_x]) &&
						    PEDESTAL_LOW<((int)E_SiY[i_y]) && PEDESTAL_HIGH>((int)E_SiY[i_y])){

							//assign the hit to StripX and StripY where the most energy is deposited (rel. Ecalibration is needed, but roughly ok)
							if(dc_Ex_max<((int)E_SiX[i_x]) && dc_Ey_max<((int)E_SiY[i_y])){
								r_pos_x=i_x;
								r_pos_y=i_y;
								dc_Ex_max=E_SiX[i_x];
								dc_Ey_max=E_SiY[i_y];
							}
						
						}
					}
					
				}
			}

			//Filling pos. histo
			if(dc_Ex_max!=-999 && dc_Ey_max!=-999){h_pos_si_xy	-> Fill(r_pos_x,r_pos_y);}
			
		}//trigger==1

	}//entry loop
	

	//writing out the root output file
	TFile *graphfile = TFile::Open((OUTPUT + (string)("") + ROOT_NAME).c_str(), "RECREATE");
	graphfile -> mkdir("map");
	graphfile -> cd("map");
	h_pos_si_xy -> Write();
	graphfile -> Close();

}//loop

//////////////////////////////////////////////////////////////////////////////////////////////////////////////

void run(){

    const char *command = new char[1000];

    char filename[100];
    TChain *fChain = new TChain("h101");

    sprintf(filename,INPUT1);

    if(exists_test0(INPUT1) && exists_test0(OUTPUT)){

    cout<<"\033[0;37m//loading run: "<<filename << "\033[0m" <<endl;
    fChain->Add(filename);

    loop(fChain);
    }
    else{cout<<"\033[0;31mError 404: non-existing INPUT1 or OUTPUT file!\033[0m" <<endl;}

	command = "rm  *.so";
	gSystem->Exec(command);
	command = "rm  *.d";
	gSystem->Exec(command);

	return;
}

int main(){
    run();
    return(0);
}
  30   Thu Dec 5 10:57:57 2019 Jan, LaszloDetectorssetting up the DSSD with beam 
This is a brief how-to about getting the DSSSD set up with stored beam and target in the ESR.

The main goals
1. adjust timing signals to TDC-range
2. adjust energy signals to ADC-range
3. optimize energy resolution

The signal chain is the following:

det [32ch.] > preamp [2x16ch] > 2x MSCF shapers [16ch]
  244   Mon Mar 23 13:26:59 2020 JanAnalysisruns_90to99 SCRAPER RESULTS 
With scraper, we have roughly 150-200 (p,g) counts now.

X-rays look fine!
  251   Mon Mar 23 14:32:03 2020 JanAnalysisruns_100to104 NO-SCRAPER RESULTS 
Without scraper, we have very few (p,g) counts, hard to get numbers quickly, maybe ~50.

X-rays look fine!
  5   Fri Apr 5 05:46:20 2019 JanDAQrunning DRASI for (p,g) 
We now have a drasi DAQ running for our (p,g) experiments.
The RIO we have it installed right now is: r4l-58
It shall be used with the user <litv-exp>

The DAQ-controle shall be done from lxg1275 inside a SCREEN SESSION named "daq"
tab 0 >> drasi 
tab 1 >> logger
tab 2 >> rate
tab 3 >> stream server
tab 4 >> file writing (optional)

To check and control running daq:

login on lxg1275
> ssh litv-exp@lxg1275

enter screen session
> screen -x daq

DRASI
go to tab 0
> ctrl-a 0 
should be quite, no errors showing, no terminal outputs
full restart proceedure
> ssh r4l-58
> cd esrdaq_2018/r4l-58
> ./start.sh (for det. triggered daq)
> ./pulser.sh (for internal pulser trigger)
> ctrl-c (for killing daq)

LOGGER
go to tab 1
> ctrl-a 1
should be quite, no errors showing, no terminal outputs
full restart proceedure
> ssh r4l-58
> cd esrdaq_2018/r4l-58
> ./logger.sh

RATE MONITOR
go to tab 2
> ctrl-a 2
rates should update each second
"incr" should be event rate per sec 
"send" column should be reasonable value if data is written
full restart proceedure
> ssh r4l-58
> cd esrdaq_2018/r4l-58
> ./rate.sh

EMPTY STREAM SERVER
go to tab 3
> ctrl-a 3 
empty stream should be running  
number of processed events should keep increasing
you should see the number of clients connected
full restart proceedure (on lxg1275)
> empty stream://r4l-58 --server=stream:6002

WRITE A FILE
can be done by litv-exp from any lgx-machine
ROOT FILE:
> e127_unpack --stream=lxg1275 --ntuple=RAW,/data.local1/e127/pre_data/file.root
LMD FILE:
> e127_unpack --stream=lxg1275 --output=/data.local1/e127/pre_data/test.lmd
 
  123   Sat Mar 21 12:06:50 2020 LaszloGeneralrun61 - SCRAPER moved out 
we want to see any change on the Silicon count rate, because we will have now also Rutherford scattering. 
ELOG V3.1.5-fc6679b