18/10/21 START: 16:58
18/10/21 STOP: 19:09
Background measurements. Checking noise!
Pulser is totally disconnected.


** Configuration file: 
181016_Conf_BrikenFull.xlsx


ROOT file: 
By mistake no online saved!


DLT files:
181021_1410_bckgn_NOpulser_highThr_071.dlt

Comment: 
- Clovers were placed outside the moderator
- AIDA not inside the moderator.
- Without In beam PE shielding.

18/10/20 START: 20:30 approx 
18/10/21 STOP: 11:20

** Configuration file: 
181016_Conf_BrikenFull.xlsx


ROOT file:
181020_2030_bckgn_pulser_highThr.root

Comment: 
- Clovers were placed outside the moderator
- AIDA not inside the moderator.
- Without In beam PE shielding.

18/10/21 START: 14:10
18/10/21 STOP: 16:41
Background measurements. Checking noise!
Pulser is connected to all preamps.


** Configuration file: 
181016_Conf_BrikenFull.xlsx


ROOT file: 
181021_1410_bckgn_pulser_highThr.root

DLT files:
181021_1410_bckgn_pulser_highThr_070.dlt


Comment: 
- Clovers were placed outside the moderator
- AIDA not inside the moderator.
- Without In beam PE shielding.

18/10/19 START: 08:31
18/10/19 STOP: 10:50

Configuration file: 181016_Conf_BrikenFull.xlsx


ROOT file: 181019_1050_Bkg.root
DLT: 181019_0830_bckg_035.dlt


Comment: 
- Clovers OUT of the moderator. 
- AIDA not inside the moderator.
- Without In beam PE shielding.

Little noise in some tubes:
He039, He053, He121
We tried to improve the noise by moving cables around
but it didnt work. So we leave as it is. 

***** CHECK DATA, CHANGE OF CONFIGURATION WITHOUT RESTARTING GASIFIC70

 According to the reply from Japan Radioisotope Association, the accuracy of the Cf-252's intensity is +0%/-15%.

( "+0%" is important, because 3.7 MBq is a standard limit for radio-active sources  in Japan.)

The PB-5 Pulse generator labeled "Pulser 2" and the 428F Linear Fan in-out labeled "Clover G7" from BRIKEN NIM crate have to be returned to the RIBF electronics pool because the 
borrowing time is expired.

For the Pulser 2, the external trigger input and pulse output cables were labeled before removing the module.

   - Attachment 1: Original position and cabling of the pulser. The serial number of the pulser is 052010010247 
   - Attachment 2: A picture of the crate after removing the pulser.
   - Attachment 3: Original Pulser setting.

The Linear Fan in-out was replaced with a new module (same version 428F), which can be used for a long time. The position of the input and output cables in the module were kept 
unchanged.

   - Attachment 4: Original position and cabling of the Linear Fan in-out module. The serial number of the original module is 051999070282
   - Attachment 5: New Linear Fan in-out module after replacement.
   - Attachment 6: Oscilloscope view of the 10kHZ NIM test input signal (blue) and output signal (yellow) of the old Linear fan in-out module.
   - Attachment 7: Oscilloscope view of the 10kHZ NIM test input signal (blue) and output signal (yellow) of the new Linear fan in-out module.

We have performed a successful test of the integration of independent DAQ systems based on a correlation 
scalar counted from a common clock signal. The principles of the integration method are described in the 
following AIDA elog entry: https://elog.ph.ed.ac.uk/AIDA/29

The configuration of the setup we used in the RIKEN test is described by the attached figure:
DAQcorrelation_diagram.pdf. The chosen solution was to use a 25 MHz clock generated by the MACB modules of 
AIDA, which was distributed to the other two systems by a SIS36/38xx module in the BRIKEN VME crate (a 
slightly modified versio of the method proposed by PCS in AIDA Elog#29).

The correlation can be monitored online using the MIDAS DataXfer and DataSpy toolkits 
(http://npg.dl.ac.uk/MIDAS/DataAcq/Data.html). Each system operates a DataRelay program that sends a data 
stream consisting only of IDs and time-stamps to a common DataSink (this requires a DataRelay code that 
does 
some filtering of the raw data). The scheme is shown in the attached diagram (DAQsoftware.pdf).

The DataPeek_Merge and SyncCheck codes use C++11 for parallelization of tasks, which is a helpful feature 
to
improve the efficiency of finding coincidences between the correlation pulses. Thus,  the code will not 
run 
in PCs with any Linux version. For example, it requires version 7 of ScientificLinux, which installed in 
the 
PC being used for BRIKEN DAQ control that will stay at RIBF for the time being.


++ SYNCHRONIZATION RESULTS ++

The figure correlation_25Hz.png shows a correlation plot for the BRIKEN+RIBF+AIDA running with 
correlations 
done by a pulser at 25 Hz. A large fraction of the pulsers appear in the double-coincidence plots (top 
row; 
same plots, except the 'Partial' one is automatically cleared every ~10seconds).

The bottom plots show the pair-wise correlations between BRIKEN and RIBF or AIDA. BRIKEN was defined as 
the
'master' in this test, but current version of the program is flexible to select any stream as the master 
one.

The second figure (correlation_random.png) shows the same test, but using a non-periodic pulser to trigger 
the correlation scalar. We observed the same level of synchronization (peaks look broader because of the 
zoom level).

A scaning with 252Cf along the Z-axis of the neutron detector is carried out. The setup is similar to the scaning carried out in October 2016.

Observations:

- Clovers are put inside the detector without voltage.

- AIDA detector is out of the moderator.

- Position in Z is given with respect to the moderator side opposite to AIDA.

- The shielding for in-beam neutrons is mounted. It corresponds to HDPE 2.5cm + 1mm Cd + 20cm HDPE. The distance moderator to shieldind is 34.6mm

- There are two additional neutron sources in the Hall, aprox 10m from the detector. One 241AmBe (30mC) and 244Cm/O13 (500mC). Both sources produce an increase of the neutron background up to approx1n/s (x10 higher).

- Datafiles are located in the dac computer, path:

/data/1706FinalCalibrations/170615_Zscanning

MEASUREMENTS

Configuration file: 170615_Conf_BrikenFull_AfterCrisis.xlsx

0) A background measurement is carried out previous to the Zscan.

FILE: 170615_1100_Bkg.root

1) Z=25mm;  Start 11:13             Stop 11:23

FILES:   170615_1113_Zscan_252Cf_25mm_000.dlt, 170615_1113_1123_Zscan_252Cf_25mm.root

2) Z=50mm;  Start      11:25       Stop  11:34

FILES:  170615_1125_Zscan_252Cf_50mm_001.dlt, 170615_11125_1134_Zscan_252Cf_50mm.root

3) Z=75mm;  Start     11:37        Stop  11:46

FILES:  170615_1137_Zscan_252Cf_75mm_002.dlt,    170615_1137_1146_Zscan_252Cf_75mm.root

4) Z=100mm;  Start 13:25            Stop   13:33

FILES:    170615_1325_Zscan_252Cf_100mm_003.dlt      170615_1325_1333_Zscan_252Cf_100mm.root

5) Z=125mm;  Start       13:36      Stop   13:44

FILES:    170615_1335_Zscan_252Cf_125mm_004.dlt   170615_1335_1344_Zscan_252Cf_125mm.root

6) Z=150mm;  Start       13:51      Stop   13:59

FILES:    170615_1351_Zscan_252Cf_150mm_005.dlt       170615_1351_1359_Zscan_252Cf_150mm.root

7) Z=175mm;  Start     14:01        Stop   14:09

FILES:    170615_1401_Zscan_252Cf_175mm_006.dlt    170615_1401_1409_Zscan_252Cf_175mm.root

8) Z=200mm;  Start     14:12        Stop   14:21

FILES:    170615_1412_Zscan_252Cf_200mm_007.dlt        170615_1412_1421_Zscan_252Cf_200mm.root

9) Z=225mm;  Start     14:24        Stop   14:31

FILES:    170615_1424_Zscan_252Cf_225mm_008.dlt       170615_1424_1431_Zscan_252Cf_225mm.root

10) Z=250mm;  Start      14:33       Stop   14:40

FILES:    170615_1433_Zscan_252Cf_250mm_009.dlt            170615_1433_1440_Zscan_252Cf_250mm.root

11) Z=275mm;  Start    14:43         Stop   14:50

FILES:    170615_1443_Zscan_252Cf_275mm_010.dlt        170615_1443_1450_Zscan_252Cf_275mm.root

12) Z=300mm;  Start      14:54       Stop   15:01

FILES:    170615_1454_Zscan_252Cf_300mm_011.dlt           170615_1454_1501_Zscan_252Cf_300mm.root

13) Z=325mm;  Start      15:04       Stop   15:11

FILES:    170615_1504_Zscan_252Cf_325mm_012.dlt            170615_1504_1511_Zscan_252Cf_325mm.root

14) Z=350mm;  Start      15:14       Stop   15:22

FILES:    170615_1514_Zscan_252Cf_350mm_013.dlt       170615_1514_1522_Zscan_252Cf_350mm.root

15) Z=375mm;  Start    15:24         Stop   15:31

FILES:    170615_1524_Zscan_252Cf_375mm_014.dlt              170615_1524_1531_Zscan_252Cf_375mm.root

16) Z=400mm;  Start     15:34        Stop   15:41

FILES:    170615_1533_Zscan_252Cf_400mm_015.dlt  170615_1533_1541_Zscan_252Cf_400mm.root

17) Z=425mm;  Start     15:44        Stop   15:57

FILES:    170615_1543_Zscan_252Cf_425mm_016.dlt           170615_1543_1557_Zscan_252Cf_425mm.root

18) Z=450mm;  Start      15:59       Stop   16:08

FILES:    170615_1559_Zscan_252Cf_450mm_017.dlt      170615_1559_Zscan_252Cf_450mm_017.dlt

YSO Tests 
Thresholds & calibrations



For HV between (500,600)V, the rate of visual scalers do not change. The current thresholds, 

Ch Thr
xa 130
xb 130
ya 130
yb 150
dy 90

Attachment 1: dynVSdynGated. 
>>Black, dyn signal
>>Red, dyn signal gated by 4 anodes (histo xpos)

Sun Jun 4 2017 11:16:45 VME crate #1 crashed
New configuration file of BRIKEN

Main changes: 
-VME address of digitizer V1A1 (now address #7, instead of #1)
-Digitizer for Ancillary now placed at VME crate #2, VME address #8

In the offline configuration file only these addresses can be changed, keeping the same Id

Check of Plastic and NaI veto detectors and DACQ settings


Plastic: 10x200x450mm**3, PMT: H1161, HV: -1200V, Anode2
Very small and short signal: width: 20ns, rise: 10ns, amplitude up to 10mV
We decided to put an amplifier to have more flexibility
Amp: Ortec 474 TFA, G: 10xmax, INT=200ns, DIF: 100ns
Signal: width: 200ns, height: 100mV
DACQ Trigger & EFIR: P=2, G:2

NaI: 2"x4"x16", PMT: ?, VD: 1410 (ORNL), HV: +800V
Signal: width: 400ns height: 15mV
DACQ trigger and EFIR: P=20, G=20

File: 161011_2330_PlasticNaI_137Cs.root
File: 161011_2335_PlasticNaI_60Co.root

Photo of the arrangement.
137Cs spectrum of both detectors.

Energy calibration of plastic and NaI detectors


137Cs source placed in the center of the arrangement:
two plastics on top of each other the four NaI
on the sides. See photo.

First measurement:
File: 161014_0015_137Cs_VetoDetCal.root

after calibration check measurement: 
File: 161014_0038_137Cs_VetoDet.root

60Co source: 161014_0047_60Co_VetoDet.root

See figures

ADC ranges at the moment:
Plast: 20 MeV
NaI: 20 MeV

In order to access to the synchronization test, we prepare two programs in the PC  briken1 ( 10.32.6.54).

To Launch the processes, in a terminal type: DataSink -i 3

In other terminal type SynCheck

By default this preform a test with difference RIBF-BRIKEN and AIDA-BRIKEN.

In case of BRIKEN is not running, the option "SynCheck -M 1" perform de differences AIDA-RIBF and BRIKEN-RIBF, and "SynCheck -M 2"  RIBF-AIDA and BRIKEN-AIDA

AIDA Data Relay:

The programming transmitting the data from AIDA to the DataSink includes an intermediate filtering step. This selects only correlation scalars from one module (and possibly ADC values from one channel in that module).

To run the program from aidas1 PC:

DataRelayFilter -n 10.32.6.54 -p 10307 -I 2
 

"-I 2" selects ID 2 as the one for the AIDA data stream, which must correspond to the one expected by the DataSink in the briken1 PC.

The attached screenshot show the terminal when running the code in verbose mode (-v 1), and also sending the ADC energy of the pulser in channel 10 of NNAIDA11 (adc ~38600 ch). This was for random pulser; for a fixed pulser delta will show constant value of delta (timestamp difference between consecutive correlationpulses).

We applied a bias voltage of 100 V to the dE detector

Current read = 0.660 uA

compare with https://elog.ph.ed.ac.uk/BRIKEN/190.  it is slighly lower.

Attachment 1-2:  signal and noise level from Co60 source for the dE top

Attachment 3-4: signal and noise level from Co60 source for the dE bottom

We used the laser to align the degrader (see attached photos)

According to the LISE calculation, equivalent effective thickness for 6 mm of Carbon target is 4.5 mm thick Aluminum.

Therefore, we've set the degrader system as follow:

It's here...it's rough...but it hopefully gets the job done

The Lower polyethylene pieces was swamped.

In the photo beam comes from the left.

We have tested possible change of the baseline in the digitizer due to the pulser connection. NO EFFECT has been
found!


Test for detector He086 ORNL:
He086_NoPulser_samples.png  -> Without pulser, baseline around 1000
He086_Pulser_samples.png    -> With pulser, baseline around 1000


Test for detector He001 UPC:
He001_Pulser_samples.png  -> With pulser, baseline around 1200
He001_NoPulser_samples.png  -> Without pulser, baseline around 1200


Test for detector He013 RIKEN:
He013_Pulser_samples.png  -> With pulser, baseline around 850
He013_NoPulser_samples.png  -> Without pulser, baseline around 850

To Launch the processes:

Open 4 terminals:

Terminal 1 (DataSink) type:

>ssh aida@d05

>cd /home/aida/DataPackage/DataSink/Linux64

>DataSink -i 3

Terminal 2 (SynCheck) type:

>ssh aida@d05

>cd /home/aida/SyncCheck

>./SynCheck

Terminal 3 (BigRIPS Data Relay) type:

>ssh aida@d05

>cd /home/aida/ribfts/ribftssender

>./ribftssender_mar17ca debug

(specific for current 40Ca parasitic run because we are not sending
a pulse signal to  BigRIPS as trigger but receiving triggers from
BigRIPS to create the pulses)

Terminal 4 (AIDA Data Relay) type:

>npg@aidas1
>DataRelayFilter -n 10.32.0.12 -p 10307 -I 2

"-I 2" selects ID 2 as the one for the AIDA data stream, 
which must correspond to the one expected by the DataSink in the d05 PC.
The programming transmitting the data from AIDA to the DataSink includes an 
intermediate filtering step. This selects only correlation scalers from one 
module (and possibly ADC values from one channel in that module).

Gasific MainWindow (Briken Data Relay):

   In the DAQ Control tab: Click "Start Sync Monitoring" button.

   In the pop up window set server ip and port (ip:10.32.0.12, port:10305)

By default this perform a check on the differences RIBF-BRIKEN and AIDA-BRIKEN.

In case that BRIKEN is not running, the option "SynCheck -M 1" check the differences 
AIDA-RIBF and BRIKEN-RIBF, while "SynCheck -M 2" checks RIBF-AIDA and BRIKEN-AIDA

To synchronize:

   In the Gasific MainWindow, DAQ Control tab: Click "Send Sync Pulse" button

We started the synchronization monitoring programs to check that
it is OK as can be seen in the figure below

We are using the same scheme used during Ahn parasitic run,
namely the synchronization check signal is the BigRIPS trigger
signal send by them to us (AIDA, BRIKEN).

The monitorization procedure is different from the one used
in 2016. The description to lauch the processes is described
here below and in the attached PDF.

***********

To Launch the processes:

Open 4 terminals:

Terminal 1 (DataSink) type:

>ssh aida@d05

>cd /home/aida/DataPackage/DataSink/Linux64

>DataSink -i 3

Terminal 2 (SynCheck) type:

>ssh aida@d05

>cd /home/aida/SyncCheck

>./SynCheck

Terminal 3 (BigRIPS Data Relay) type:

>ssh aida@d05

>cd /home/aida/ribfts/ribftssender

>./ribftssender_mar17ca debug

(specific for current 40Ca parasitic run because we are not sending
a pulse signal to  BigRIPS as trigger but receiving triggers from
BigRIPS to create the pulses)

Terminal 4 (AIDA Data Relay) type:

>npg@aidas1
>DataRelayFilter -n 10.32.0.12 -p 10307 -I 2

"-I 2" selects ID 2 as the one for the AIDA data stream, 
which must correspond to the one expected by the DataSink in the d05 PC.
The programming transmitting the data from AIDA to the DataSink includes an 
intermediate filtering step. This selects only correlation scalers from one 
module (and possibly ADC values from one channel in that module).

Gasific MainWindow (Briken Data Relay):

   In the DAQ Control tab: Click "Start Sync Monitoring" button.

   In the pop up window set server ip and port (ip:10.32.0.12, port:10305)

By default this perform a check on the differences RIBF-BRIKEN and AIDA-BRIKEN.

In case that BRIKEN is not running, the option "SynCheck -M 1" check the differences 
AIDA-RIBF and BRIKEN-RIBF, while "SynCheck -M 2" checks RIBF-AIDA and BRIKEN-AIDA

To synchronize:

   In the Gasific MainWindow, DAQ Control tab: Click "Send Sync Pulse" button