1 / 7

Muon Piquet Report Week 16

Muon Piquet Report Week 16. Nikolai Bondar / Burkhard Schmidt Tuesday, April 26, 2011. Inefficiency in M3.  Fixing requires uploading new timing recipes  Should be done as soon as possible, definitely before the May 3, when the MD starts .

lonato
Download Presentation

Muon Piquet Report Week 16

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. Muon Piquet Report Week 16 Nikolai Bondar / Burkhard Schmidt Tuesday, April 26, 2011

  2. Inefficiency in M3  Fixing requires uploading new timing recipes  Should be done as soon as possible, definitely before the May 3, when the MD starts

  3. Problem during 8 hours of fill 1732 with 3 chambers in M4R2 Run 90092 (before the problem was fixed) Lost about 10% in J/Psi Rate, hence about 10% In muon trigger efficiency Run 90095 (after the problem was fixed)

  4. Problem with configuration • Apparently the configuration was not loaded correctly at the beginning of the fill (when the detector was configured).  Reconfiguring solved the problem • Unfortunately it was done very late • A similar problem occurred during fill 1735 in M5R2 (again 3 chambers). • This time it happened towards the end of the fill. • It was quickly spotted and the system was reconfigured. Only 15 min of data-taking were affected. • Why are this things happening all over a sudden this year? • It happened also ~2 weeks ago, see logbook entries 1713 and 1714

  5. Problem with problem with fiber link TMUDAC: OpticalLinks - Input optical links error in processor 4. Optical links should be tested  Contact L0Muon group

  6. HV recipes • New HV recipes have been uploaded on Sunday morning by Giovanni/Oleg • No trips any longer due to too tight trip values in M1

  7. Chamber trips fill 1717-1737

More Related