| ID |
Date |
Author |
Category |
Subject |
|
107
|
Tue Mar 31 20:32:05 2020 |
Ragan | General | 203Tl80+ 200Hg79+ 205Tl81+ |
Below in the schottky spectrum, on left is 203Tl80+ contamination, in middel is 200Hg79+ contamination and on right most is 205Tl81+.
These contaminations cannot be seen on CsISiPHOS but can only be seen on schottky.
The goal now is to get rid of these contaminations by putting slits. |
| Attachment 1: 85AD7203-736C-4531-BA80-D045CC690BED.jpeg
|
|
|
108
|
Tue Mar 31 20:50:05 2020 |
Ragan | General | 200Hg79+ 205Tl81+ |
203Tl80+ impurity is removed by moving scrapper inside ESR.
Only 220Hg79+ is left now |
| Attachment 1: 31E7D028-F469-4BFF-B683-203821C174E9.jpeg
|
|
|
109
|
Tue Mar 31 21:07:05 2020 |
Ragan | General | Separation of 203Tl80+ and 200Hg79+ using scrapper in ESR |
It can be seen in the video how 203Tl80+ (on extreme left) and then 200Hg79+ (in middle originally) is separted from 205Tl81+ by using scrapper in ESR.
Now, we want 205Pb81+ mixed with 205Tl81+ to be separated as much as possible in FRS. |
| Attachment 1: 06B012F5-5435-41D7-AD82-4A5FDADF281E.MOV
|
|
113
|
Thu Apr 2 02:36:48 2020 |
Ragan | General | Stochastic cooling and orbit problem |
On 1 April by 5 pm, we could stop the stochastic cooling after the stacking process and also change the orbit of the Tl beam to centre.
Thanks to the efforts by the ESR team ! |
|
117
|
Thu Apr 2 06:25:13 2020 |
Ragan | Runs | Template |
beam: 205Tl81+ (no scraping)
energy: 400 MeV/u
storage time: ___ hrs
purpose: data with TARGET ON
Detector position (CsISiPHOS): out of the ring
Detector position (MWPC): mm
run start at ___ , first file: run____.lmd
file running: ____.lmd
_______________________________________________________________________________
time when accumulation starts: __:__
time when storage starts: __:__
time when storage ends: __:__
I_cooler during storage time: __ mA
I_cooler = __ mA
I_SIS: ___
ESR particles after stacking: ___
Number of stackings: __
Target ON density: _____
Target on time: __:__
Target off time: __:__
Target on time for measurement: 10 mins (by local mode)
NTCAp file:
SC_2020-04-01______________
\IQ_2020-04-01_____________
IQ rate: 8 MS/s
(saved in drive : __)
copy and repeat the above (below the line) for every storage time measurement |
|
121
|
Thu Apr 2 15:24:15 2020 |
Ragan | General | How to know whether electron cooling is working |
For Alle and Kuehler the bottom left status should look like as shown in pictures below. |
| Attachment 1: IMG_8238.JPG
|
|
| Attachment 2: IMG_8239.JPG
|
|
|
143
|
Sat Apr 4 03:06:12 2020 |
Ragan | General | Instructions if electron cooler goes off during long storage time measurements |
Please read the attachment. |
| Attachment 1: electron_cooler.pdf
|
|
|
169
|
Mon Apr 6 20:03:50 2020 |
Ragan | General | Experiment finished )) |
E121 experiment is finished with the last 10 hours measurement at 19:47 ))
Many thanks to everyone for there significant contributions )) |
|
170
|
Thu Apr 9 11:16:35 2020 |
Ragan | General | Measurements done in the experiment |
|
| Attachment 1: storage11.pdf
|
|
| Attachment 2: storage12.pdf
|
|
| Attachment 3: storage13.pdf
|
|
|
173
|
Mon Apr 20 11:17:18 2020 |
Ragan | General | Logbook |
|
| Attachment 1: logbook.pdf
|
|
| Attachment 2: combined_FRS.pdf
|
|
| Attachment 3: combined_data.pdf
|
|
|
183
|
Sun May 30 12:09:00 2021 |
Ragan | General | NTCAP |
Attached is the info given by Carsten.
The instructions to operate NTCAP are given on https://wiki.gsi.de/ESR_EXP/ManualOfNTCAP |
| Attachment 1: ntcap_carsten.pdf
|
|
|
182
|
Mon Mar 29 16:31:09 2021 |
Pierre-Michel | DAQ | cross section |
(1.393*^-8 + 3.18*^-13 + 4.707*^-8)/4.707*^-8 = 1.29595 |
| Attachment 1: Pb81onAr.png
|
|
|
34
|
Sat Mar 28 13:09:11 2020 |
Mei,Yury, Tino, Ragan, Ruijiu | General | Shift plan |
From Yury,
For now, measure the beam life time with 3 different electron current in the e-cooler,i.e. 200mA(default), 10mA, and 20mA. For each current, 4 sets of 30mins long measurements shall be taken.
Starting from 9pm Helmut and Sergey will come for setting up FRS |
|
14
|
Fri Feb 21 11:30:52 2020 |
Laszlo | General | Shift plan |
e127: https://docs.google.com/spreadsheets/d/14m8WcCq1erx6HqWJRK7TLbCx121IkjqGa5l-frf4YjI/edit#gid=0
e121: https://docs.google.com/spreadsheets/d/10MUzA5-Ilf2WzCyNj8u_KSG6yzPg0e4vtZGGPFB3K-k/edit#gid=0 |
|
1
|
Thu Sep 13 11:32:17 2018 |
Jan Glorius | Collaboration | Proposal |
| Attached is the beam time proposal submitted and accepted by the G-PAC in 2017. |
| Attachment 1: E121_Litvinov.pdf
|
|
| Attachment 2: E121_Approval.pdf
|
|
|
4
|
Fri Dec 7 10:56:04 2018 |
Jan Glorius | SlowControl | EPICS ioc on raspberry |
We have an EPCIS server (ioc) running on our raspberry (ext-027377). It talks to our MesyTec modules (MSCF shapers, MHV4 high-voltages).
In principal it should be running all the time, but here is the manual how to check/start it:
-login on GSI-linux using <litv-exp> user
-type in console: e121pi (alias for: 'ssh -X litv-exp@ext-027377.gsi.de')
-open the "mrcc" screen session: screen -x mrcc
-if the ioc is running you will see here terminal outputs like:
| Quote: | cbLow: Active ringpi:mrcc:mhv2:getRcStatus
cbLow: Active ringpi:mrcc:mhv2:getCurrent1 |
-if this is not the case, you have to restart the ioc:
- <Ctrl>+c to end any running ioc (if it has errors)
- the command to start the ioc: e121_ioc (alias for '/home/litv-exp/epics/mrcc_ioc/bin/linux-arm/mrcc /home/litv-exp/epics/mrcc_ioc/iocBoot/iocmrcc/start_ringpi.cmd')
- now the terminal outputs should be as quoted above (errors show up in red)
- finally <Ctrl>+a d to exit the screen session |
|
5
|
Fri Dec 7 11:39:41 2018 |
Jan Glorius | SlowControl | GUI for remote control of MSCF+MHV4 |
We have a GUI for remote controlling our MesyTec modules MSCF16 and MHV4 for E121 experiment.
Here is the instructions to run it:
1. login to GSI-linux using <litv-exp> user
2. get the EPICS environment by typing in terminal: epicsfind
3. type in terminal: GUIe121 (alias for 'medm -x /u/litv-exp/E121/medm/e121.adl')
if you get the message: 'medm: command not found' you didn't load the EPICS environment (2.)
The GUI is more or less self-explaining.
Be sure to follow this procedure when changing a value (e.g. threshold for MSCF):
1. click on small text-panel with value
2. leave mouse pointer inside panel
3. change value by typing
4. press enter |
|
9
|
Tue May 28 08:36:14 2019 |
Jan | DAQ | MBS start & RFIO server |
You need a DAQ-PC and the RIO crate computer.
All of the DAQ proceedures laid out here are operated from inside the DAQ screen session.
Right now for e121 the following DAQ-setup is used: (might change in the future)
DAQ-PC: lxg0155
screen session: e121_daq @ lxg0155
RIO: r4l-47
DAQ dir: /esr/usr/litv-exp/2019Munich-Det
The most important commands:
on DAQ-PC
mbs - start mbs DAQ
rawDispRFIO64 - start RFIO server
in MBS shell
@startup - initialize MBS (only inside DAQ dir)
@connect - connect RFIO server (only if server running)
@runstart - open file for data writing
@runstop - close file
start acq - start DAQ
show acq - status of DAQ
show file - status of current file/RFIO server
The full proceedure for the DAQ:
- on DAQ-PC enter screen session:
litv-exp@lxg____:~$ screen -x e121_daq or create new screen session if non is exisiting:litv-exp@lxg____:~$ screen -S e121_daq - inside screen: go to 1st tab (MBS) and login to RIO if not yet done:
<Ctrl-a 0>
litv-exp@lxg____:~$ ssh r4l-47
- on RIO reset and start MBS
R4L-47 litv-exp > cd 2019Munich-Det
R4L-47 litv-exp > resl
R4L-47 litv-exp > mbs
mbs > @startup
- inside screen go to 2nd tab (RFIO)
<Ctrl-a 1> or create 2nd tab if not exisiting<Ctrl-a c> - start RFIO server on DAQ-PC
litv-exp@lxg____:~$ cd /u/litv-exp/rfio
litv-exp@lxg____:~$ ./rawDispRFIO64-wheezy
-I- 64 bit RFIO test server (lxg0155) listening on port 1974
forks './rawServRFIO64-wheezy' for each client request - inside screen go to 1st tab and connect MBS to RFIO server
<Ctrl-a 0>
mbs > @connect
mbs> show file
mbs> -R4L-47 :transport :Name of output device = RFIO
-R4L-47 :transport :current tape label = lxg0155 , opened
-R4L-47 :transport :current file name = , closed
-R4L-47 :transport : 0.000 MBytes written to tape
-R4L-47 :transport : 0.000 MBytes written to current file - start acquisition
mbs > start acq
mbs > show acq
...
-R4L-47 :util :Name of output device = RFIO
-R4L-47 :util :RFIO server lxg0155, file CLOSED
-R4L-47 :util : 0.000 [MB] written to tape, 0.000 to file
-R4L-47 :util :--------------------------------------------------------------
-R4L-47 :util :Collected: 61.1451 MB, 1866 Buffers, 131990 Events.
-R4L-47 :util :Rate : 33 KB/s, 1 Buffers/s, 71 Events/s
-R4L-47 :util :-------------------------------------------------------------- - open file / start a run
mbs > @runstart
-R4L-47 :transport :open file at server lxg0155::
-R4L-47 :transport :/data.local1/E121/predata/e121_run_1239.lmd - close file / stop a run
mbs > @runstop
-R4L-47 :transport :Rfio server lxg0155: closed file after 0.262 MB written:
-R4L-47 :transport :-I- remote output file /data.local1/E121/predata/e121_run_1239.lmd closed
mbs> -R4L-47 :transport :/data.local1/E121/predata/e121_run_1239.lmd
|
|
10
|
Wed Jun 26 16:20:31 2019 |
Jan | DAQ | unpacker: lmd > root |
I have written an unpacker for the lmd data taken with the current daq-system for E121.
The crate configuration is as follows:
ADC1 channels 1-32 (Caen 785)
ADC2 channels 1-32 (Caen 785)
ADC3 channels 1-32 (Caen 785)
SCALER channels 1-32 (Caen 830)
The unpacker binary can be found here
/u/litv-exp/unpacker/unpackexps/E121/E121
The current spec file is attached.
To convert lmd-files to root-files, please use it as follows:litv-exp@lxg___: E121_unpacker /path/to/file.lmd --ntuple=RAW,/path/to/new_file.root |
| Attachment 1: E121.spec
|
// -*- C++ -*-
ADC(start)
{
MEMBER(DATA12 data[32]);
list(0 <= ch < 32)
{
UINT32 item NOENCODE
{
0_15: channel;
16_27: value;
28_31: 0;
ENCODE(data[channel - start], (value=value));
}
}
}
SCALER(start)
{
MEMBER(DATA32 data[32]);
list(0 <= ch < 32)
{
UINT32 high NOENCODE
{
0_15: channel;
16_31: value;
}
UINT32 low NOENCODE
{
0_15: channel;
16_31: value;
}
ENCODE(data[(high.channel / 2) - start], (value=(high.value << 16) | low.value));
}
}
SUBEVENT(ESR)
{
adc[0] = ADC(start = 0);
adc[1] = ADC(start = 32);
adc[2] = ADC(start = 64);
select optional {
scaler[0] = SCALER(start = 0x100);
}
}
EVENT
{
esr = ESR(type = 10, subtype = 1);
}
#include "det_mapping.hh"
|
| Attachment 2: det_mapping.hh
|
SIGNAL( ADC1_1, esr.adc[0].data[0],
ADC1_32, esr.adc[0].data[31], DATA12);
SIGNAL( ADC2_1, esr.adc[1].data[0],
ADC2_32, esr.adc[1].data[31], DATA12);
SIGNAL( ADC3_1, esr.adc[2].data[0],
ADC3_32, esr.adc[2].data[31], DATA12);
//SIGNAL( SC_1, esr.scaler[0].data[0],
// SC_32, esr.scaler[0].data[31],DATA32);
|
|
62
|
Sun Mar 29 23:48:12 2020 |
Jan | Analysis | run0251: E_spectra for CsISiPhos |
This is a collection of energy spectra of the CsISiPhos detectors from run0251 with primary beam.
There is no good spectra for n-side of Si-pad 1! |
| Attachment 1: dE_vs_E.png
|
|
| Attachment 2: dE_vs_E_peak.png
|
|
| Attachment 3: E_dssd1.png
|
|
| Attachment 4: E_dssd2.png
|
|
| Attachment 5: E_dssd3.png
|
|
| Attachment 6: E_dssd4.png
|
|
| Attachment 7: E_CsI1.png
|
|
| Attachment 8: E_CsI2.png
|
|
| Attachment 9: E_pad1_n.png
|
|
| Attachment 10: E_pad2_n.png
|
|
| Attachment 11: E_pad3_n.png
|
|
| Attachment 12: E_pad4_n.png
|
|
| Attachment 13: E_pad5_n.png
|
|
| Attachment 14: E_pad6_n.png
|
|