1 / 9

MUID BTL Setup

MUID BTL Setup. May 19 , 2014 I. Nakagawa. BLT Check Out Runs. LiveTime Measurement for JSEB. South. North. Health Check Run#412239 (South). Data were taken via JSEB. Looks consistent with regular data taking. All spectra look good. Health Check Run#412245 (North).

barry-colon
Télécharger la présentation

MUID BTL Setup

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. MUID BTL Setup May 19, 2014 I. Nakagawa

  2. BLT Check Out Runs

  3. LiveTime Measurement for JSEB South North

  4. Health Check Run#412239 (South) Data were taken via JSEB. Looks consistent with regular data taking. All spectra look good.

  5. Health Check Run#412245 (North) Looks good except for dead zone

  6. Setup BLT Trigger (South) • MLU setup: • Make sure WCB2 power is on • rshphenixir5 • cd "/home/phnxmuid/blt" • phenixir5> ld < mlu • phenixir5> verify_all() -> response is confirmed to be OK • pcf file setting muid.s.pcf -> muid.s.pcf.BLT instead of muid.s.pcf.BASE • Plugged in BLT South 1D trigger into GTM module LEVEL1 input. Signal is TTL and taken from 688AL level adupter. • MUID South HVs are all up (Operation Voltage). • MUID South standalone data taking.

  7. Rate Challenge • Raw BLT trigger rate measured with Visual scaler = 41k/30sec = 1.2kHz which is consistent with Sanghwa’s previous measurements. However, other trigger logics may be fanned-in at level adupter 688. Should keep 1D trigger independent. • Run411739 shows unhealthy reconstruction. The data doesn’t seems to be OK. • All data taken via jseb cause segmentation fault with macro muidcosmic.C. MUID South Full HVs (all HV chains on)

  8. Reproducing Sanghwa’s Results Run#411973 Run#411973 New data 411971 was taken with the same BLT S1D cable and NIM module configurations as Sanghwaand demonstrates good agreement with her run.

  9. ry:rx distribution Run#401438 (Sanghwa) Run#411973 (Itaru) ry rx The both distribution shows heavy bias on top quadrants and consistent. High entry bins from overlapping panel regions.

More Related