Logged in as: Guest
Login
: 2026-03_raris:start

2026-03 RARiS

Shared album


ID
Show
Mode:Full | Summary | Threaded
IDDateAuthorTypeCategorySubject
179Fri Apr 24 14:01:25 2026Bong-Hwi LimGeneralBeam3_RFSoCRe: RFSoC channel and DUT sensor channel correspondence
ReplyTo: 161

Re: RFSoC channel and DUT sensor channel correspondence

Board1 row1-8: rfsoc1 ch0

Board1 row1-6: rfsoc1 ch1

Board1 row1-4: rfsoc1 ch2

Board1 row1-2: rfsoc1 ch3

Board1 row1-7: rfsoc3 ch0

Board1 row1-5: rfsoc3 ch1

Board1 row1-3: rfsoc3 ch2

Board1 row1-1: rfsoc3 ch3

Board1 row2-1: rfsoc2 ch0

Board1 row2-3: rfsoc2 ch:1

Board1 row2-5: rfsoc2 ch2

Board1 row2-7: rfsoc2 ch3

Board1 row2-2: rfsoc4 ch0

Board1 row2-4: rfsoc4 ch1

Board1 row2-6: rfsoc4 ch2

Board1 row2-8: rfsoc4 ch3

Board2 row1-8 rfsoc1 ch4

Board2 row1-6: rfsoc1 ch5

Board2 row1-4: rfsoc1 ch6

Board2 row1-2: rfsoc1 ch7

Board2 row1-7: rfsoc3 ch4

Board2 row1-5: rfsoc3 ch5

Board2 row1-3: rfsoc3 ch6

Board2 row1-1: rfsoc3 ch7

Board2 row2-1: rfsoc2 ch4

Board2 row2-3 rfsoc2 ch:5

Board2 row2-5: rfsoc2 ch6

Board2 row2-7: rfsoc2 ch7

Board2 row2-2: rfsoc4 ch4

Board2 row2-4: rfsoc4 ch5

Board2 row2-6: rfsoc4 ch6

Board2 row2-8: rfsoc4 ch7

178Sat Mar 07 01:20:03 2026Hiroki IizukaGeneralBeam3_RFSoCRe: pixel-type AC-LGAD : 3/6 20:30~
ReplyTo: 176

Re: pixel-type AC-LGAD : 3/6 20:30~

Run 174 を動かしたまま、一晩放置します

177Sat Mar 07 01:05:07 2026Hiroki IizukaGeneralGeneralBeam 周期変更

Beam 周期変更

ビーム周期が、10sON-20sOFF の30s から10sON-17sOFFの27s に変更されました

176Sat Mar 07 00:47:07 2026koyuki iwatsukiGeneralBeam3_RFSoCpixel-type AC-LGAD : 3/6 20:30~

pixel-type AC-LGAD : 3/6 20:30~

DUT1 : pixel-type AC-LGAD(W7 big ), DUT2 none
RUN | HV1 | I1 | HV2 | I2 | start | stop | time | events | rate | comments
166 | -140 | -0.746uA | — | — | 06-Mar-26 20:23:00 | 06-Mar-26 20:37:46 | 14m 46s | 127,863 | 144 Hz |
167 | -140 | -0.8 uA | — | — | 06-Mar-26 20:38:04 | 06-Mar-26 20:43:01 | 4m 57s | 105,402 | 354 Hz | 電流値記入し忘れ
168 | -140 | -0.853uA | — | — | 06-Mar-26 20:43:11 | 06-Mar-26 20:48:40 | 5m 29s | 113,319 | 344 Hz |
169 | -140 | -0.861uA | — | — | 06-Mar-26 20:52:57 | 06-Mar-26 21: 40:33 | 47m 36s | 1,001,743 | 350 Hz |
170 | -140 | -0.903uA | — | — | 06-Mar-26 21:41:16 | 06-Mar-26 22:28:47 | 47m 31s | 1,003,148 | 352 Hz |
171 | -140 | -0.908uA | — | — | 06-Mar-26 22:29:43 | 06-Mar-26 23:19:04 | 49m 21s | 1,038,247 | 350 Hz |
172 | -140 | -0.923uA | — | — | 06-Mar-26 23:19:17 | 07-Mar-26 23:52:45 | 33m 28s | 710,168 | 354 Hz |
(Access) 173 | -140 | -0.840uA | — | — | 06-Mar-26 00:00:30 | 06-Mar-26 00:34:28 | 33m 02s | 580,725 | 293 Hz | 途中でイベント収集されなくなった \

175Fri Mar 06 20:39:11 2026Simone MazzaGeneralGeneralLine 2 double DUT setup

Line 2 double DUT setup

Changed DUT to double DUT in line one Sensor front: 2col 50um, horizontal strips, 185V Sensor back: 2col 30um, vertical strips, 197V

175_1772797151_0_img20260306195701.jpg
175_1772797151_1_img20260306195741.jpg
174Fri Mar 06 19:42:11 2026koyuki iwatsukiGeneralBeam3_RFSoCHV Scan: 3/6 17:00~

HV Scan: 3/6 17:00~

DUT1 : 4col-20um, DUT2 4col-50um (nohole) \
RUN | HV1 | I1 | HV2 | I2 | start | stop | time | events | rate | comments
161 | -90V | -0.363 uA | -150V | -0.123 uA | 06-Mar-26 17:33:55 | 06-Mar-26 18:00:17 | 26m 22s | 405,425 | 256 Hz |
162 | -85V | -0.031 uA | -145V | -0.113 uA | 06-Mar-26 18:01:26 | 06-Mar-26 18:10:50 | 10m 28s | 128,544 | 204 Hz | (Berm stop)
163 | -85V | -0.031 uA | -145V | -0.113 uA | 06-Mar-26 18:14:30 | 06-Mar-26 18:41:08 | 26m 38s | 403,904 | 253 Hz |
164 | -80V | -0.027 uA | -140V | -0.105 uA | 06-Mar-26 18:41:53 | 06-Mar-26 19:08:17 | 26m 24s | 402,428 | 254 Hz |
165 | -75V | -0.024 uA | -135V | -0.098 uA | 06-Mar-26 19:09:03 | 06-Mar-26 19:34:03 | 35m 00s | 382,918 | 182 Hz |

173Fri Mar 06 18:10:42 2026Bong-Hwi LimGeneralGeneralDaily meeting note (3.6)

Daily meeting note (3.6)

  • Line#2
    • 4col-20um → decide to not take 20um data
    • 2col/4col 50/30um data are taken well
    • Next plan → Simon's plan (add one more DUT for the additional tracking layer) ~
  • Line#1
    • RCNP team (Streaming DAQ)
      • Base: Using data from NestDAQ, analyzing with EICRecon
      • Now EDM4EIC format is prepared for the AC-LGAD → We could transfer the data into the TOF barrel calibration process (no special calibration process done) → clustering process can be applied soon but we need to configure a strip ID for EDM4EIC format.
      • Upgrade: XRootD → working well. AC-LGAD EDM4EIC transferred well! →MDX2 (proxy Osaka server) → Mini esulon2 server, we can open the root files on the mdx2 (server). → semi-online analysis.
      • Next plan → transfer data without saving them on the local server.
  • Line#3
    • → All data measuremnts are done, preparing QA now
172Fri Mar 06 17:35:07 2026Tatsuki SaitoGeneralBeam3_RFSoCHV Scan: 3/6 12:53~17:33

HV Scan: 3/6 12:53~17:33

DUT1 : 4col-20um, DUT2 4col-50um (nohole)
RUN | HV1 | I1 | HV2 | I2 | start | stop | time | events | rate | comments
153 | -125V | -0.328 uA | -190V | -0.369 uA | 06-Mar-26 12:53:48 | 06-Mar-26 13:26:31 | 32m 43s | 473,825 | 242 Hz |
154 | -127V | -0.514 uA | -185V | -0.298 uA | 06-Mar-26 13:35:36 | 06-Mar-26 14:11:40 | 45m 9s | 509,257 | 188 Hz |
155 | -120V | -0.166 uA | -180V | -0.249 uA | 06-Mar-26 14:12:09 | 06-Mar-26 14:44:42 | 32m 33s | 462,403 | 237 Hz |
156 | -115V | -0.109 uA | -175V | -0.213 uA | 06-Mar-26 14:47:14 | 06-Mar-26 15:14:24 | 29m 42s | 408,334 | 229 Hz |
157 | -110V | -0.080 uA | -170V | -0.187 uA | 06-Mar-26 15:15:35 | 06-Mar-26 15:42:37 | 28m 13s | 407,917 | 241 Hz |
158 | -105V | -0.063 uA | -165V | -0.165 uA | 06-Mar-26 16:10:31 | 06-Mar-26 16:39:27 | 28m 56s | 438,997 | 253 Hz |
159 | -100V | -0.051 uA | -160V | -0.149 uA | 06-Mar-26 16:40:06 | 06-Mar-26 17:06:26 | 26m 20s | 401,963 | 254 Hz |
160 | -95V | -0.042 uA | -155V | -0.134 uA | 06-Mar-26 17:06:58 | 06-Mar-26 17:33:09 | 26m 11s | 400,973 | 255 Hz | \

171Fri Mar 06 14:22:48 2026Bong-Hwi LimGeneralSetupRe: The beam target changed (same material but thicker one) -> beam rate increased
ReplyTo: 165

Re: The beam target changed (same material but thicker one) -> beam rate increased

The current rate has been increased to 4.83 Hz

170Fri Mar 06 13:38:04 2026ono kyouheiGeneralGeneralLine2: Changed the number of segments acquired from 100 to 500

Line2: Changed the number of segments acquired from 100 to 500

取得セグメント数を100から500に変更しました

169Fri Mar 06 13:30:15 2026Bong-Hwi LimGeneralSetupRe: The beam target changed (same material but thicker one) -> beam rate increased
ReplyTo: 165

Re: The beam target changed (same material but thicker one) -> beam rate increased

the number of segements updated from 100 to 500.

it looks like the we had a lot of transfer during the one fill with 100 segment option.

168Fri Mar 06 13:26:12 2026Tatsuki SaitoGeneralBeam3_RFSoCLINE3 DUT Change

LINE3 DUT Change

2列20umのセンサーを4列50um(穴なし)に変更しました

167Fri Mar 06 12:52:10 2026Bong-Hwi LimError/FaultGeneralRe: Line 2 DUT cable mismatch
ReplyTo: 163

Re: Line 2 DUT cable mismatch

Next time, the length of the cable, especially for the DUT has to be same for all channels.

166Fri Mar 06 12:51:01 2026Bong-Hwi LimGeneralGeneralThe first safety key disabled (beam area)

The first safety key disabled (beam area)

The first safety key has been lost by manager (not our fault) → temporary disabled.

Please contact him (Tokiyasu-san) if we can find the key in the beam area

165Fri Mar 06 12:49:18 2026Bong-Hwi LimGeneralSetupThe beam target changed (same material but thicker one) -> beam rate increased

The beam target changed (same material but thicker one) -> beam rate increased

We expect around 2 times more, but for the moment, we're observing ~4 Hz.

164Fri Mar 06 12:33:44 2026Simone MazzaGeneralGeneralnew DUT il line 2

new DUT il line 2

Changed DUT in line 2, mounted 2col 30um, HV set at 197V

163Fri Mar 06 12:31:45 2026Simone MazzaGeneralGeneralLine 2 DUT cable mismatch

Line 2 DUT cable mismatch

Channel 2 cable is shorter than the rest, will need to measure after run is done (see pic) This was also seen in the data, time difference of ~500ps for ch2

163_1772767905_0_img20260306115921.jpg
162Fri Mar 06 12:27:58 2026Tatsuki SaitoGeneralBeam3_RFSoCHV Scan: 3/6 8:30~11:49

HV Scan: 3/6 8:30~11:49

DUT1 : 4col-20um, DUT2 2col-20um
RUN | HV1 | I1 | HV2 | I2 | start | stop | time | events | rate | comments
151 | -127V | -0.481 uA | -126.706V | -1 uA | 06-Mar-26 08:56:59 | 06-Mar-26 10:51:22 | 114m 23s | 1,002,169 | 146 Hz |
152 | -126V | -0.38 uA | -126V | -0.85 uA | 06-Mar-26 11:04:22 | 06-Mar-26 11:49:11 | 44m 49s | 398987 | 148 Hz | \

161Fri Mar 06 10:04:38 2026Hiroki IizukaGeneralBeam3_RFSoCRe: RFSoC channel and DUT sensor channel correspondence
ReplyTo: 45

Re: RFSoC channel and DUT sensor channel correspondence

画像が正しく表示されていないようなので再送

161_1772759078_0_setup.png
160Fri Mar 06 10:00:51 2026Hiroki IizukaGeneralBeam3_RFSoC3/6 シフターやることリスト

3/6 シフターやることリスト

  • 2026-03_raris:159 のelogを参照しながら、データ量の少なそうな箇所を補う (最低100k events, 適宜増やす)
  • 電圧 0V 時のrunも、同じsetupにつき1回とる (最低100k events)
  • 電流上限時の電圧で、ひたすらデータをとり続ける (時間の許す限り)

可能ならDUT変更もはさみつつ、beam については上記のrun をとる

また、深夜シフトは一部変更が入る (ラスト6時間は、1枚setup・無人の状態で、ひたすら同条件で取り続ける:詳しくはLine2から説明があるはず)