ID |
Date |
Author |
Subject |
353
|
Fri Oct 27 10:04:31 2017 |
SG, RY | LISE++ file for BRIKEN1 |
Here attached the lise file for BRIKEN1 |
112
|
Sat Nov 5 03:18:13 2016 |
SG BCR RCF NTB | Gamma peaks in the overnight run, related to neutron inelastic scattering |
We looked at the overnight background run (161105_0935_BackgroundOvernight.root), There are gamma-peaks that could be related to neutron inerastic scattering. We identified 565, 596, 608 and 69 keV. They might be related to the effect of neutrons. If this is the correct assignment, this would mean at least some of the neutrons are not thermal when they interact with the germanium.
There was also significant drift in the Ge gain (seen on the pulser) this may effect the shape of these peaks.
Some gain drift was also seen on He preamps during this run. The cause is yet to be determined. It is also yet to be determined if these gain shifts are correlated. |
53
|
Wed Jul 20 16:40:57 2016 |
S. Go, J.Agramunt, A.Tolosa, J.L. Tain,... | CLOVER |
Calibration and resolution check
CLOVER detectors were calibrated in energy with 60Co and 137Cs
60Co source: 2530, 8.81E4Bq (16/03/2010)
137Cs source: CD393 (box), ?
Sources were placed at the center
Resolution(FWHM@1333keV):
G7 Blue:2.67keV
G7 Green: 2.84keV
G7 Red: 2.77keV
G7 Black: 2.64keV
D4 Blue: 3.60keV
D4 Green: 3.35keV
D4 Red: 3.41keV
D4 Black: 4.85keV (!?)
Efficiency calibration with 152Eu
Source place at the center
Source: 272 (09-7011), 1.062E4Bq (error:1.9%)@16/03/2010
File: 160719_2201_152Eu_028.dlt
Online: 160719_2201_152Eu_028.root
Attached 152Eu spectrum |
52
|
Wed Jul 20 16:12:58 2016 |
S. Go, ... | CLOVER |
Mounting of the CLOVER detectors in position
CLOVER G7: right of beam
CLOVER D4: left of beam
G7 crystals:
Beam ->
Back view:
Red Blue
Green Black
D4 crystals:
Beam ->
Front view:
Red Green
Blue Black
Photos of the arrangement with COVER detectors attached |
97
|
Tue Nov 1 13:00:55 2016 |
Roger Caballero | Eff callibration parameters for G7-Clover |
Efficiency calibration for the G7 clover (data acquired in July).
The attached plots show the parameters for the Jackel function (E[i]=Energy) using the points of a 152Eu source.
Roger
> Efficiency calibration
>
> File "cloversEff.ods" and "cloversEff.xls" contains the experimental efficiency from different measurements
> during July and October
> (G7 broke before Eu-152 measurement). We can assume the efficiency didn't change from July measurements to
> October measurements. |
99
|
Wed Nov 2 01:19:46 2016 |
Roger Caballero | Eff callibration parameters for D4-Clover |
Efficiency calibration for the D4 clover (data acquired in October).
The attached plots show the parameters for the Jackel function (E[i]=Energy) using the points of 152Eu, 60Co and 137Cs sources.
Roger
> Efficiency calibration
>
> File "cloversEff.ods" and "cloversEff.xls" contains the experimental efficiency from different measurements
> during July and October
> (G7 broke before Eu-152 measurement). We can assume the efficiency didn't change from July measurements to
> October measurements. |
100
|
Wed Nov 2 02:26:22 2016 |
Roger Caballero | Efficiency callibration calculator (Excel file) |
Attached the updated excel file. In the first sheet there is the calculator to calculate the efficiency from an given energy.
The Jackel function used is:
Double_t fun=TMath::Exp((par[0]+par[1]*TMath::Log(x[0])+par[2]*TMath::Log(x[0])*TMath::Log(x[0]))*2/TMath::Pi()*
(TMath::ATan(TMath::Exp(par[3]+par[4]*TMath::Log(x[0])+par[5]*TMath::Log(x[0])*TMath::Log(x[0]))))-25.);
> Efficiency calibration
>
> File "cloversEff.ods" and "cloversEff.xls" contains the experimental efficiency from different measurements
> during July and October
> (G7 broke before Eu-152 measurement). We can assume the efficiency didn't change from July measurements to
> October measurements. |
108
|
Fri Nov 4 03:37:27 2016 |
Roger Caballero | Energy calibration for Ge clovers |
Energy Calibration: See attached pdf
Detector Slope Offset
V2A7C1 0.00155643 0.0842245
V2A7C2 0.000658962 0.78685
V2A7C3 0.00153391 1.198
V2A7C4 0.00157933 0.483094
V2A7C5 0.000704268 0.31553
V2A7C6 NOT THERE
V2A7C7 0.00066837 0.465225
V2A7C8 0.000695872 0.678058
> Energy calibration for clovers, 152Eu
>
>
>
> The Eu source positioned in the center roughly.
> File name: 161103_1426_152Eu.root |
3
|
Fri Oct 31 12:58:49 2014 |
Robert Grzywacz | Entry test - preamps |
Here is a picture of one of our Mesytec preamplifiers. We have located all seven of them.
They have 16 input channels and a common SHV per board.
<p> <a href="141031_125516/24.png?lb=BRIKEN"><img border="0" alt="24.png" src="141031_125516/24.png?
lb=BRIKEN&thumb=1" name="att0" id="att0" /></a></p> |
347
|
Tue Oct 24 13:14:47 2017 |
RY | Calibration data for clovers |
for energy calibration with 152Eu source
171024_1858_152Eu_G7.root
171024_2112_152Eu_D4.root |
340
|
Sun Oct 22 05:15:26 2017 |
RG,RY,MS,ATD,JA,JLT | Check of YSO |
We start a systematic check of YSO in BRIKEN DACQ
WE check and correct a configuration file for YSO alone
Conf file: 171022_1306_YSO_Conf.xlsx
First measurement:
change the light pulser attenuation and check
changes of X and Y position
Root file: 171022_1314_pulserAtCenter.root
We change configuration file to remove amplitude
range condition to buil position
New configuration file:171022_1332_YSO_Conf.xlsx
Now start moving the light pulser position using a mask:
Light pulse position: Top Left Out
Root file: 171022_1335_pulseTopLeftOut.root
Light pulse position: Bottom Left Out
Root file: 171022_1341_pulseBottomLeftOut.root
Light pulse position: Bottom Right Out
Root file: 171022_1345_pulseBottomRightOut.root
Light pulse position: Top Right Out
Root file:171022_1350_pulseTopRightOut.root
Light pulse position: Top Left In
Root file: 171022_1401_pulseTopLetIn.root
Light pulse position: Bottom Left In
Root file: 171022_1406_pulseBottomLeftIn.root
Light pulse position: Bottom Right In
Root file: 171022_1410_pulseBottomRightIn.root
Light pulse position: Top Right In
Root file: 171022_1416_pulseTopRightIn.root
Now we ramp the PMT high voltage starting at 600V:
600V, 650V, 700V, 750V, 800V, 900V, 950V, 1000V, 1050V, 1100V, 1150V
Pulser at Top Left Out
Root file: 171022_1445_HVramp_pulseTopLeftOut.root |
345
|
Mon Oct 23 09:43:00 2017 |
RG, RY, MS, SG, AT | 137Cs YSO |
measurement of 137Cs with YSO
after matching the gains of the
HighGain channels
YSO detector was inside the black box, outside the matrix.
The source was placed in front of the YSO
First measurement
Start: 15:14
End: 16:55
RootFile: 171023_1655_137CsYSO.root
Second measurement (same conditions )
Start: 16:55
Run number: 070
End: 17:41
File: 171023_1655_137CsYSO_070.dlt
RootFile: 171023_1655_1741_137CsYSO_070.root
The 137Cs source is weak; the rate of the YSO detector was about 50Hz (without source is 10Hz). |
346
|
Tue Oct 24 03:08:23 2017 |
RG, RY, MS, JA, RCF, SG, AT | light pulser YSO |
light pulser measurement
SN's pulse generator 20ns width |
348
|
Wed Oct 25 01:02:14 2017 |
RG | Status of the YSO array |
The presently used detector has 48x48x5 mm3 YSO array with 1x1mm2 segments. They are separated with ESR. We use H8500 pspmt and 2 mm quartz diffuser with rough edges. Coupling is done with sylgard. Anger logic uses a conventional resistive network with 1kohm and we have 4 position signals and dynode. The position signals (xa,xb,ya,yb) are split in Low gain branch connected directly to 5V range input in Struck and High gain branch, which uses Phillips fast amplifier to boost the gain. The use of the amplifiers enables to operate the detector at low PSPMT gain and should give us a chance to work with the strong light produced by the implant. The implant signals were simulated using blue diode and a pulse generator. We observed significant drift of the position for very large pulses, but this was for now attributed to be the pulse shape effect due to the use of the diode and reltively slow pulser.
YSO for now should run at -700 V. The maximum operating voltage is 1200V and should not be exceeded. At 1200 V the ions induced signals may saturate our electronics.
Tuesday evening:
Detector remounted in the pedestal and aligned with WASABI with 1mm+1.5mm spacers. The pedestal is 25.8 mm tall and the box is 60 mm tall. We checked also the orientation of the spectra and chose AIDA convention (look upstream). With this pedestal the front of the box is centered with the back of the clover leaf.
Wednestay morning:
I opened the detector and rewrapped it with new teflon tape. I noticed a small piece if sylgard peeled off, which may explain why the we had some edge effect yesterday. The detector was remounted on the new pedestal which will allow it to be positioned at the center of the clover. The signals looked OK on the oscilloscope.
|
227
|
Thu Mar 30 07:41:58 2017 |
RCF PV SN CG JA | Run 15 |
Date: 30/03/2017
Start: 16:05
BRIKEN run: 15
AIDA Run: R16_231
BigRIPS run: 157
DLT:170330_1605_Mg40_015.dlt
BRIKEN Rate: 4
F11 Rate: 13
Date: 30/03/2017
Stop: 17:21
BRIKEN run:15
AIDA Run: r16_252
BigRIPS run: 157
Root file:170330_1605_1721_B015_Mg40.root
OBSERVATIONS: |
214
|
Wed Mar 29 18:16:58 2017 |
RCF | 40Mg Run 002 |
Date: 30/03/2017
Start: 02:16
BRIKEN run: 002
AIDA Run: R16_4
BigRIPS run: 143
DLT: 170330_0216_Mg40_002.dlt
BRIKEN Rate: 6cps
F11 Rate: 13
Date: 30/03/2017
Stop: 02:38 (bigrips started new file 15 minutes ago)
BRIKEN run:002
AIDA Run:R16_5
BigRIPS run:144
Online not erased since JL left. Just Start File.
Root file: HISTOGRAMS NOT SAVED FOR THIS RUN
Observation: AIDA recovered at 02:15
Synchronization plot not generated. Some screenshots rom terminals attached. AIDA terminal has additional messages and between both terminals (AIDA/BIGRIPS) there is a constant offset apparently. |
215
|
Wed Mar 29 18:42:25 2017 |
RCF | 40Mg Run 003 |
Date: 30/03/2017
Start: 02:39
BRIKEN run: 003
AIDA Run: R16_5
BigRIPS run: 144
DLT: 170330_0239_Mg40_003.dlt
BRIKEN Rate: 4cps
F11 Rate: 12
(First part of the run in the rate histogram was overlapping the previous data. The reason is not understood).
Date: 30/03/2017
Stop: 03:27
BRIKEN run:003
AIDA Run:R16_21
BigRIPS run:145 (just started)
Online not erased.
Root file:170330_0216_0326_B003_Mg40.root (accumulated with previous root)
Syncronization terminals on screenshots to compare with previous run. Due to the updates on each terminal are not with the same frequency it is hard to observe in the screenshots, but on live seems to be constant. |
216
|
Wed Mar 29 19:31:21 2017 |
RCF | 40Mg Run 004 |
Date: 30/03/2017
Start: 03:29
BRIKEN run: 004
AIDA Run: R16_22
BigRIPS run: 145
DLT: 170330_0329_Mg40_004.dlt
BRIKEN Rate: 3.5cps
F11 Rate: 13
Date: 30/03/2017
Stop: 04:25
BRIKEN run:004
AIDA Run:R16_37
BigRIPS run:145
Online not erased.
Root file:170330_0216_0425_B004_Mg40.root (accumulated with previous root)
Syncronization: Difference of timestamps seems to be constant between AIDA and BIGRIPS values observed on terminals |
217
|
Wed Mar 29 20:27:53 2017 |
RCF | 40Mg Run005 |
Date: 30/03/2017
Start: 04:29
BRIKEN run: 005
AIDA Run: R16_38
BigRIPS run: 146
DLT: 170330_0429_Mg40_005.dlt
BRIKEN Rate: 3.5cps
F11 Rate: 13
Date: 30/03/2017
Stop: 05:31
BRIKEN run:005
AIDA Run:R16_54
BigRIPS run:146
Root file:170330_0429_0531_B005_Mg40.root
OBSERVATIONS:
04:29 -> Beginning of the run Shunji and Liu removed the degrader. For this reason I erased the online
histograms from previous runs.
04:50 -> It looks like AIDA is still seeing "nothing". Shunji and Liu put the degrader back again at 13mm Al deg.
During the run: Syncronization: Difference of timestamps between AIDA and BIGRIPS observed on terminals constant. |
218
|
Wed Mar 29 21:34:20 2017 |
RCF | 40Mg Run 006 |
Date: 30/03/2017
Start: 05:42
BRIKEN run: 006
AIDA Run: R16_57
BigRIPS run: 147
DLT: 170330_0542_Mg40_006.dlt
BRIKEN Rate: 3.5cps
F11 Rate: 12
Date: 30/03/2017
Stop: 06:43
BRIKEN run:006
AIDA Run:R16_73
BigRIPS run:147
Root file:170330_0429_0643_B006_Mg40.root (accumulated)
OBSERVATIONS:
Carbon foil changed at the beginning of this run.
AIDA is still seeing "nothing" Liu changes the distance of the Al degrader from 13mm to 11mm.
Syncronization: Difference of timestamps between AIDA and BIGRIPS observed on terminals remains constant.
6:40: BIGRIPS stop the run and they ar doing calibrations for 20-30 minutes. |