alcap-org / AlcapDAQ

Alcap DAQ
alcap-org.github.io
8 stars 0 forks source link

Dead time in Ge #236

Closed jrquirk closed 10 years ago

jrquirk commented 10 years ago

Has anyone looked at the dead time due to transistor resets in the germanium? I want to try to not duplicate too much effort.

I would like to

thnam commented 10 years ago

I have some code on that. Will write something up here or on the wiki.

thnam commented 10 years ago

It seems to me that the dead time due to the reset pulses is not significant. The bigger dead time is from the long pulse length.

thnam commented 10 years ago

I plotted the time interval between two consecutive pulses on the Ge-S channel. This plot should give us an estimation of count rate, and in case of reset, a bump around 2 ms. Plot from calibration runs 3375, 3378, 3379: ge_cal_rate_pulselength

Some observations:

The interval plot from one of SiR2 runs: sir2_ges_self_tdiff The counting rate was higher, 514 cps. The number of resets should increase linearly (?) with the count rate, so correction for them would be about 0.28%.

The random summing correction increases exponentially with the count rate. Also higher count rate makes the average pulse length longer, to 57 us in this case. Then the correction factor is 1.06 for this SiR2 run.

The plot above is from one SiR2 run (2119). I can imagine that making that plots for all runs could give us another mean to check the muon flux fluctuation.

Another note is that the bump at 200 us did not show up here. The wiring was different: in early SiR2 runs, only Ge-S was on UH CAEN; later we attached Ge-F on the WFD. This is why I suspect that bump would come from the common trigger.

millerj2111 commented 10 years ago

Hi Nam, Did you look at the spacing only within midas events, not between successive midas events? --Jim

Date: Fri, 19 Sep 2014 11:46:14 From: Nam notifications@github.com Reply-To: alcap-org/AlcapDAQ <reply@reply.gi thub.com> To: alcap-org/AlcapDAQ AlcapDAQ@noreply.github.com Subject: Re: [AlcapDAQ] Dead time in Ge (#236)

I plotted the time interval between two consecutive pulses on the Ge-S channel. This plot should give us an estimation of count rate, and in case of reset, a bump around 2 ms. Plot from calibration runs 3375, 3378, 3379: ge_cal_rate_pulselength

Some observations:

  • average pulse length was about 45.7 us;
  • time interval plot has exponential shape, the count rate was about ~ 240 cps. This count rate and the pulse length above give an estimation of correction for random summing: $e^{2\times \textrm{rate} \times \textrm{pulse length} = 1.02$
  • two bumps:
    • one at ~ 2 ms, corresponds to reset pulses. Total number of resets was 2335, so the dead time due to this was ~ 4.6 s. This is small (0.14%) compare to total measurement period of 3245 s (number of blocks x block length). Its contribution is small compare to 2% from random summing above.
    • one at 200 us. I don't know what it is but suspect that it has something to do with triggering by other channel. The peak looks like Gaussian.

The interval plot from one of SiR2 runs: sir2_ges_self_tdiff The counting rate was higher, 514 cps. The number of resets should increase linearly (?) with the count rate, so correction for them would be about 0.28%.

The random summing correction increases exponentially with the count rate. Also higher count rate makes the average pulse length longer, to 57 us in this case. Then the correction factor is 1.06 for this SiR2 run.

The plot above is from one SiR2 run (2119). I can imagine that making that plots for all runs could give us another mean to check the muon flux fluctuation.

Another note is that the bump at 200 us did not show up here. The wiring was different: in early SiR2 runs, only Ge-S was on UH CAEN; later we attached Ge-F on the WFD. This is why I suspect that bump would come from the common trigge.


Reply to this email directly or view it on GitHub: https://github.com/alcap-org/AlcapDAQ/issues/236#issuecomment-56195031

millerj2111 commented 10 years ago

Hi Nam, How do you get a Ge peak near the 2p-1s of Al from Pb212? What is teh mechansim? Thanks. --Jim

Date: Fri, 19 Sep 2014 11:46:14 From: Nam notifications@github.com Reply-To: alcap-org/AlcapDAQ <reply@reply.gi thub.com> To: alcap-org/AlcapDAQ AlcapDAQ@noreply.github.com Subject: Re: [AlcapDAQ] Dead time in Ge (#236)

I plotted the time interval between two consecutive pulses on the Ge-S channel. This plot should give us an estimation of count rate, and in case of reset, a bump around 2 ms. Plot from calibration runs 3375, 3378, 3379: ge_cal_rate_pulselength

Some observations:

  • average pulse length was about 45.7 us;
  • time interval plot has exponential shape, the count rate was about ~ 240 cps. This count rate and the pulse length above give an estimation of correction for random summing: $e^{2\times \textrm{rate} \times \textrm{pulse length} = 1.02$
  • two bumps:
    • one at ~ 2 ms, corresponds to reset pulses. Total number of resets was 2335, so the dead time due to this was ~ 4.6 s. This is small (0.14%) compare to total measurement period of 3245 s (number of blocks x block length). Its contribution is small compare to 2% from random summing above.
    • one at 200 us. I don't know what it is but suspect that it has something to do with triggering by other channel. The peak looks like Gaussian.

The interval plot from one of SiR2 runs: sir2_ges_self_tdiff The counting rate was higher, 514 cps. The number of resets should increase linearly (?) with the count rate, so correction for them would be about 0.28%.

The random summing correction increases exponentially with the count rate. Also higher count rate makes the average pulse length longer, to 57 us in this case. Then the correction factor is 1.06 for this SiR2 run.

The plot above is from one SiR2 run (2119). I can imagine that making that plots for all runs could give us another mean to check the muon flux fluctuation.

Another note is that the bump at 200 us did not show up here. The wiring was different: in early SiR2 runs, only Ge-S was on UH CAEN; later we attached Ge-F on the WFD. This is why I suspect that bump would come from the common trigge.


Reply to this email directly or view it on GitHub: https://github.com/alcap-org/AlcapDAQ/issues/236#issuecomment-56195031

jrquirk commented 10 years ago

Thank you Nam.You've answered all of my questions.

thnam commented 10 years ago

Hi Jim,

The lines in bold are most prominent background peaks; the 1st column is energy in keV, 3rd column is intensity in %, the 4th column is the related peaks. The 351 keV peak shows up all the time even in the runs without target.