1 / 15

FPD Meeting Agenda

FPD Meeting Agenda. 1) Introduction, Shutdown, Trigger 20’ Andrew 2) Grounding Issues 15’ Duncan 3) Software Update 10’ Gilvan 4) DQ status+plans 5’ Marcia

dinesh
Télécharger la présentation

FPD Meeting Agenda

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. FPD Meeting Agenda • 1) Introduction, Shutdown, Trigger 20’ Andrew • 2) Grounding Issues 15’ Duncan • 3) Software Update 10’ Gilvan • 4) DQ status+plans 5’ Marcia • 5) Data analysis/mc update 10’ Duncan • 6) data samples update 10’ Mike • 7) automatic insertion? • AOB Dzero Collaboration Meeting Sep. 22, 2004

  2. 2004 Issues • Data taking with integrated Phase II • Obtaining new elastic data sample • LM+Trigger Commissioning/FPD triggers in global list • Automatic pot insertion • Halo/background reduction and modelling • Detector studies, alignment, resolution, cross talk, efficiency • Tracking alignment, acceptance, database, efficiency, lattice uncertainty, MC • Data handling and quality • L2+L3 Trigger Physics Goals • Published results on dN/dT and Z • Preliminary results on several physics topics including double pom Dzero Collaboration Meeting Sep. 22, 2004

  3. Primary Shutdown Work • Repair P2I and A2O (light leak?) • Investigate A1O first step in problems • A1 mux+spare mux tests (A1O+A1D motors coupled) • Camera repairs • Investigate any cabling/mapping problems • Replace veto counters and veto PMT's+survey • Survey before and after separator changes • Trigger Commissioning • Automatic Pot Insertion • Ground searches+repairs Dzero Collaboration Meeting Sep. 22, 2004

  4. Shutdown Schedule • up to 9/20 Grounding Issues • 9/24 A20,P2I,P1D removed • 9/25 veto scintillator arrives, to be machined by Phyillis • 9/25 to 10/7 Detector repairs+cable tests • 10/5-10/19 Helio does Mux work, motor adjustment, castle maintenance supervises separator work • 10/7-10/8 FPD survey • 10/11 Seperator work begins • 10/25 PMT’s arrive need to be tested • 11/11 Veto counters reinstalled • Trigger/LM Commissioning throughout • Automatic Pot Insertion throughout Dzero Collaboration Meeting Sep. 22, 2004

  5. Shutdown Issues/Duncan • Supervise cable tests • Cable tester tool needed, also accessing TPP signals • Backplane stabilization • Cu link repairs/ optical DFE/TM tests • 3 operational DFE’s • AFE cable replugging • Sequencer tests • Keep eye on veto counters • Grounding issues • Trigger Dzero Collaboration Meeting Sep. 22, 2004

  6. Shutdown Issues Andrew: • Veto counter parts+supervision • VME scalars/Elgar • Trigger progress • PMT testing facility • UTA control boxes Mike: • Detector removal, repairs, + reinstallation • P2I to A1O • A2 HV • Light leak training • LMB’s??? Dzero Collaboration Meeting Sep. 22, 2004

  7. FPD DAQ and Trigger Dzero Collaboration Meeting Sep. 22, 2004

  8. Trigger Team • Andrew Brandt (Trigger Logic/List/Oversight) • Duncan Brown (Trigger Implementation) • Mario Vaz (FPD DFE equations/TM firmware) • Wagner Carvalho (DFE equations/test vectors) • Ricardo Ramirez (FPD/DFE Interface) • Tom Fitzpatrick (FPD/DFE Interface/DFE Timing) • Brian Cox, Dave Mercer, Scott Kolya (LM) • Carlos Avila, Luis Mendoza (Stand-alone trigger) Dzero Collaboration Meeting Sep. 22, 2004

  9. 2004 Trigger Strategy • Input information: • Currently no global run trigger capability • Vertex board is delayed (may now be finished during shutdown) • DFE boards and TM work and ready to be commissioned • Main background not from pileup (multiple interactions) but from halo spray • Strategy: • Instead of calculating bin of  and t, use fiber hit patterns to demand 2 or 3 out • of 3 planes of each detector are hit. Replaces trigger scintillator, simpler algo • Use multiplicity cut to reject halo spray, code several multiplicity levels • NOTE fiber ADC threshold must be high enough to avoid noise, low enough • to retain efficiency and allow vetoing of halo • One advantage is pot positions not needed at trigger level • Issues: • Setting ADC threshold, need special run (and analysis) • Dealing with noisy channels, variable means, could initially set threshold high, • later load in mean pattern, known hot channels • Measure efficiency with jet triggers, scint triggers from special runs • Exposure groups, triggers in global run or separate global run Dzero Collaboration Meeting Sep. 22, 2004

  10. Exposure Groups etc. • For normalization purposes each trigger is assigned an exposure group • and live time is measured for that group—different beam conditions require • different groups • Only 8 exposure groups (6 used), we have more combos so must • operate outside exposure groups—new value NOLUM • Another issue is dynamic downloading, which allows multiple global runs • This would allow us to take elastic or other monitoring data in separate • global run, so as to avoid general reco; streaming and other issues with this • Once FPD DFE/TM is ready we are mostly restricted to dedicated special • runs until these other issues are resolved Dzero Collaboration Meeting Sep. 22, 2004

  11. Interim Plan • Proceed with DFE/TM debugging during shutdown • Elizabeth indicates NOLUM work will start in ~2 months+take • 2-4 weeks to complete • Since current FPD commissioning is special run intensive and • new elastic triggers with adjacent spectrometer veto have rates • around 1 Hz, we propose adding an elastic trigger to global list in • V13.x. • If we do this carefully it will only take one exposure group and allow • us to obtain good elastic sample at lums <40E30 Dzero Collaboration Meeting Sep. 22, 2004

  12. Trigger Progress • DFE/TM chain tested by Duncan with help from Jamieson and Jeff Temple, works with debugging Johnson counter firmware. Two of three DFE boards work, 3rd needs attention from Jamieson. Two DFE-to-TM Cables also need to be repaired during shutdown. Will eventually be replaced by optical links (should happen during shutdown). • Two versions of DFE firmware developed by Mario. Version 3: 1 spectrometer only (U5 chip), passes fine segment (2/3 and 3/3) and wide segment info to TM. This version was simulated, implemented, and tested successfully at combined test stand but failed at platform Version 4: 3 spectrometers on one DFE, includes some extra bits to simplify TM algorithms. This version failed some timing tests upon implementation and needs further development • V3 failures traced to delays between different inputs to DFE, Tom is working on solution similar to TM, which waits for all inputs before processing, in parallel Mario working on V4 firmware. 4. Ricardo is working on arbiter, which is necessary for V4 firmware; it adds outputs from 3 spectrometers to form 96 bit DFE word sent to TM. He has produced a 3-chip testbench to simulate full DFE 5. Jeff produced first version of TM firmware to operate with V3, Mario has version to operate with V4 (not yet implemented.) Dzero Collaboration Meeting Sep. 22, 2004

  13. V3 Trigger Manager (debugging) • The logic sets the output triggers named fpd[255..0]. • Triggers fpd[255..101] are set to ground • Trigger fpd0 is set to VCC • Triggers fpd[96..1] are set to the input signals: A[95..0] • fpd[100..97] are set according to conditions on va1, and va2, • which are defined as inputs A[30..28] and A[26..24], according to the • mapping we got from Ricardo. • The triggers are (va1=uvx in detector 1): • fpd97 -- Tight trigger; va1=va2=1 • fpd98 -- Loose trigger; va1>0, va2>0 • fpd99 -- Medium trigger: 0<va1<5, 0<va2<5 • fpd100 -- Dead trigger; va1=va2=0 Dzero Collaboration Meeting Sep. 22, 2004

  14. V4 TM Algorithm DFE will pass word for each spectrometer indicating coincidence of two detectors tight track: exactly 1 hit with 3/3 fine segments in each detector medium : >0 with 2/3 + <20 wide segement loose: => 0 with 2/3 + <20 wide segement At TM we would form terms DIFF=any spectrometer track DIFFQ=any quadrupole spectrometer track (could be false if >1 or 2 on A or P side) DIFFD=dipole track ELAS=AU-PD or AD-PU or AI-PO or AO-PI DPOM=AU-(PU or PI or PO) or AD-(PD or PI or PO) or AI-(PU or PI or PD) or AO-(PU or PD or PO)+DI -(PU or PD or PO or PI) OVER=AU-DI or AD-DI or AO-DI or AI-DI (over-constrained track for alignment) Dzero Collaboration Meeting Sep. 22, 2004

  15. FPD Trigger List Tentative L1 FPD trigger list (V14?) 1) elastic (diag opposite spectrometers) +GAPSN 2) soft diffraction (single spectrometers)+GAPS or GAPN 3) overconstrained track (pbar in quadrupole +dipole spectrometers)+GAPN 4) double pom (up-up, dn-dn etc.)+GAPSN if needed 5) CJT(2,3) + FPD Track (DIFFQ or DIFFD) +GAPS or GAPN if needed 6) CEM(1,3)? +FPD track +GAP? 7) TTK(1,?) +FPD track +GAP? 8) MU(1,x) +FPD track +GAP? Monitors may be necessary, will need to study with special runs. Also rates are unknown. If 4 (dpom) it is not low enough to run unprescaled we would need to repeat 5-8 with two FPD tracks. Possibly 1-3+any monitors are best done in a separate global run since they will not need general farm reconstruction. Dzero Collaboration Meeting Sep. 22, 2004

More Related