1 / 13

Status of High Level Trigger in the TB

Status of High Level Trigger in the TB. IFAE Atlas Meeting Ester Segura 27th July 2004. IFAE Atlas Meeting Martine Bosman 14th September 2004. ATLAS Trigger and DAQ. Trigger. DAQ. Calo MuTrCh. Other detectors. 40 MHz. 40 MHz. D E T. LVL1.

crwys
Télécharger la présentation

Status of High Level Trigger in the TB

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. Status of High Level Triggerin the TB IFAE Atlas Meeting Ester Segura 27th July 2004 IFAE Atlas Meeting Martine Bosman 14th September 2004

  2. ATLAS Trigger and DAQ Trigger DAQ Calo MuTrCh Other detectors 40 MHz 40 MHz D E T LVL1 FE Pipelines 2.5 s RoI Lvl1 acc = 75 kHz Read-Out Drivers ROD ROD ROD RoI data = 1-2% 75 kHz 120 GB/s 120 GB/s Read-Out Links H L T D A T A F L O W ~ 10 ms ROS Read-Out Buffers RoI requests RoI Builder LVL2 ROB ROB ROB L2 Supervisor L2 N/work L2 Proc Unit ROIB L2SV Read-Out Sub-systems L2N L2P ~2+4 GB/s Lvl2 acc = ~3 kHz Dataflow Manager EB ~3 kHz EBN DFM Event Building N/work ~ sec Event Filter Sub-Farm Input SFI ~4 GB/s Event Builder EFP Event Filter Processors EFP Event Filter N/work EFN EFP EFP Sub-Farm Output EFacc = ~0.2 kHz SFO ~ 200 Hz ~ 300 MB/s

  3. Aims of HLT at TB As a Service (EF): Run monitoring algorithms at EF. Provide coherent histogramming service (Gatherer). As a Client (LVL2 & EF): Integrate & Test LVL1 + LVL2 +EF (as many aspects as possible). Aim: fully test both slides ( and e/).

  4. LVL2 status Tested algorithmic framework: • LVL2 algorithm requested data from ROS. • Accept decision sent to DFM to start EB and recording. • Concentrating in slice: • MDT + TGC + RPC + LVL1 + LVL2 + DFM + EB • Running monitoring from muFast at LVL2, online. (histograms collected by the Gatherer) (Werner, Haimo, Per, Andre, Andre dos Anjos, Paulo)

  5. Event Filter status end of July • EF segments have been prepared for nearly all the subsystems (TileCal, MDT, Calo,...). • Monitoring inside Athena has been tested (TileCal). • Other monitoring algorithms ready to be run. • Moved from 8.2.x to 8.4.0 succesfully. • Update Online configuration Database to use the new Athena version. • Changed from txt job options to python scripts. • Many technical tests being done last week. (Gatherer: Patricia, Carlos, Pilar, Cristobal PT: Sergey, Martine, Ester EF: A. Negri (DF), S. Wheeler (supervision) )

  6. HLT Monitoring status End of July Monitoring algorithms tested at LVL2 and EF. Gatherer collects histograms and sends them to IS server. Gatherer histograms can be displayed by PMPresenter. Histograms from single Athena nodes can be displayed. More monitoring algorithms can be easily added!

  7. Work on Configuration during August: Restructuration of Online Configuration Database organization for HLT ( allow to use different configuration for different processes) (Sergei, Andre Fully automatic configuration tool to generate environment variables (LD_LIBRARY_PATH,PYTHONPATH, ect ..) (Sergei). Configuration of athenaPT to run algorithms: EF uses now a script to produce environment variables for an OKS segment  fully automatic configuration tool. What has been done by IFAE during August

  8. What has been done by IFAE during August HLT/DF: Evolution of packages (Ester, Sergei) • Modifications of the Answer (EFResult) in the PT-PTClient: a string (eg, “Accepted”) + a bit pattern of 128 bits (PESA answer). (DF-00-10-00) • Get run number from TDAQ om prepareForRun transition • Follow transition from Offline from 8.4.0  8.5.0  8.7.0 N.B. Difficult to follow constant evolution of Offline Software: minor version number change can mean major change in code ; Offline and Online/Dataflow are separate worlds that use common base libraries (ex. Boost, Python, Root but without synchronizing changes...)

  9. PT Controller load Config Steering Factory Implemented in: configure PTConf new EFHLT Interface Physics Analysis Framework methods to obtain configuration info load DLL with implementation of abstract interface configure prepareForRun prepareForRun Worker new start m_Steering::process While not stopped loop stop stop unconfigure unconfigure

  10. PSC Worker EFEventLoopMgr process (FullEventFragment) robDataProvider setNextEvent (RawEvent* re) pass pointer to FullEventFragment fills RobMap with all ROBF* execute new (EventInfo) ByteStreamAddress Calls all top algorithms and OutputSvc execute methods: EFHandler OutputSvc MinimalEventLoopMgr executeEvent ByteStreamEFHandlerOutputSvc putEvent(RawEvent* re) set pointer to EFSubDetFragment getAnswer EFDecision EFResult getEFBitPattern EFBitPattern EFSubDetector fragment

  11. Latest news (I) E-mail of thursday 22th July: “Dear colleagues, Today in the morning we have tested by the first time the Event Filter running together with the LVL1 and the LVL2. The configuration was the following: MDT + LVL1 + LVL2 + EF + Gatherer. We were triggering on cosmic rays. At the EF we run the monitoring algorithm from the muons. If you are interested, you can have a look at the screenshots in the directory /afs/cern.ch/user/c/conde/public/L1L2EF. We have recored one run that you can find in /scsi_disk/rundata/daq_SFO61_lvl2_test_1l2pu_cosmics_0600541_file01.dat Best regards, Andre, Werner, Haimo, Andrea, Cibran and Patricia”

  12. Latest news (3 September) Image of the play_daq (DAQ Run Control)) Running: EF (Tilecal and LArgon) + Gatherer

More Related