1 / 14

At CERN

At CERN. Sunday afternoon: Beam splash delivered to p5 Run 129468: 27 splash events from beam 1 Run 129471: 30 splash events from beam 2 There has been no beam since…. Configuration of Track Finder for Beam 1 splash (snapshot from test on Saturday evening). ME . ME+.

Download Presentation

At CERN

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. At CERN • Sunday afternoon: Beam splash delivered to p5 • Run 129468: 27 splash events from beam 1 • Run 129471: 30 splash events from beam 2 There has been no beam since… G. Rakness (UCLA)

  2. Configuration of Track Finder for Beam 1 splash(snapshot from test on Saturday evening) ME ME+ CSC Track Finder configured to trigger on downstream endcap only… G. Rakness (UCLA)

  3. “Summary” of CSC’s in Beam Splash The thought was that perhaps we could learn something about the timing of the system… • L1A’s came from ECAL near  = 0 • Trying to understand timing at GMT is difficult… • Timing of signals is driven by early chambers.  • RPC’s were included in the trigger (downstream endcap, also) • Systematics of CSC configuration • Voltage of the CSC has the gain lower by factor of ~20 than normal.  Even so, the charge seen in beam splash is huge. • The CSC's are in collision timing.  This makes the path length of ME1/3 chambers for beam splash ~1.4 smaller than for collisions, i.e., they are intentionally early. • Systematics of the beam • In beam 1 splashes, the data were in BX 2316, while in beam 2 splashes, the data showed up in BX=51… Shows some non-care taken by LHC in injecting these beams • It begs the question: What the phase of these beam splash events relative to real collisions? • Looking at Amanda’s timing plots in CSC Validation, there appears to be a radial dependence in the timing • This was seen in last year's beam splash, as well In Summary, do not change any CSC timing until we get reasonable beam halo data… G. Rakness (UCLA)

  4. Killing things in the system G. Rakness (UCLA)

  5. Data readout conditions Be aware of the implicit conditions in the readout of the data  RecHits are created from Wire and Strip digis G. Rakness (UCLA)

  6. Possible ways to mask (faulty) hardware in the CSC’s RED = trigger path BLUE = data path = possibility to mask now = possibility to mask (not yet implemented in current software) AFEBs ALCT TMB MPC DDU DMB Comparator Channels CFEBs G. Rakness (UCLA)

  7. Items currently killed (ME–) Configuration ID = 2000025 = Problem because… it is in the trigger, but not in the data path (unable to reconstruct how it triggered)  should kill it at input to TMB = Problem because… why is this chamber not configured to send triggers?  should be sending triggers to MPC = Not a fundamental problem… TMB kills it in the trigger, but not in the data… BUT, it does make emulation more difficult… (more later) G. Rakness (UCLA)

  8. Items currently killed (ME+) Configuration ID = 1000029 G. Rakness (UCLA)

  9. Proposal of how to kill things in the system • Kill things in the trigger path as needed • If trigger info is killed in the data path (e.g., TMB or ALCT data), it should be killed in the trigger … ramifications are on the following pages… G. Rakness (UCLA)

  10. Ramifications of killing things in the system… (I) • Kill things in the trigger path as needed. What this means is… • Killing ALCT in trigger path kills ALCT data, as well • I need to implement this • Let TMB kill Comparators as needed in trigger path • This means I should undo all explicit hot-channel masks in the config database • Note: This will affect corresponding CFEB readout efficiency • Note: These comparators will still be readout (if the readout conditions are satisfied)… this makes emulation difficult, because one needs to access the database for analysis… • Q: Is it possible to include the full list of killed comparators in the data path? Or maybe just kill the whole CFEB? • Kill output to MPC as needed • This is currently done on two chambers… I believe we should unkill these chambers… G. Rakness (UCLA)

  11. Proposal of how to kill things in the system (II) • If trigger info is killed in the data path (e.g., TMB or ALCT data), it should be killed in the trigger • If CSC is killed at DDU, kill at output to MPC • Already done for ME+1/2/15, ME+1/2/36, ME–1/1/15 • If ALCT is killed in data path, kill at input to TMB • Note: No triggers will come from this chamber • Will affect ME+1/1/20 and ME–1/1/34 • Kill CFEB’s as needed in data path • No trigger information is contained in CFEB data G. Rakness (UCLA)

  12. Don’t forget to get your new SIM card https://gsm-migration.web.cern.ch/GSM-MIGRATION/Planning/Planning.htm If you have a CERN cell phone, you need to update your SIM card • 1 – 15 March: pick up your new SIM card at 4–R–013 (Labo Telecom) • This is right above the (old) room where we used to have the CSC Operations + DPG meetings • 23 – 29 March: transition to new SIM card • Users will receive an email two days before the migration of their SIM card in order to warn them about the exact day of this migration G. Rakness (UCLA)

  13. To do (I) • Ask Jinghua about ECC counters in Expert system… • Fix the clearly wrong things killed in the config database • Triggers killed to MPC, comparator hot-channel mask • Present scheme to Andrey et al. about how to change configuration • Then, fix our configuration according to the scheme presented… • 904 • Implement ALCT::hot_channel_mask • Test how CLCT – L1A readout only works • AFEB timing Analysis • difference(First tbin on - last tbin on) • histogram of averages of each chamber • What is triggering these events? • 3 layer pretrigger should give delta function in ALCT::getBX plot • Online software • Yellow page • "super configuration check“ • Firmware reloading • embed database check into ALCT firmware write • CCB hard reset only if error_count=0 • text to turn off XMAS G. Rakness (UCLA)

  14. To do (II) • Point 5 • update config DB with known problems • HV=0 run? • ME4/2 screwed up? More online software • Configuration database UI • Desire: change timing of system by a number of nsec • Desire: summary of killed components • Desire: kill a component "easily" • Test: can a timing scan be read in? • Bug: crate names always • Bug: why is ME+ ordering screwed up? • Managing • Sim card for CEO phone and CSC shift cell phones • gas card for 3304 GE 225 034 at the station behind Building 130  pick up badges from Building 130, the mileage will also be required when withdrawing the badge... G. Rakness (UCLA)

More Related