1 / 4

integration in HLT

integration in HLT. M. Biglietti G. Cataldi. We are investigating the possibility of using Moore as an algorithm in HLT environment. Status of Moore in HLT First results using the steering Future plans. Status of Moore in HLT Our first step has been accomplished

isaiah-wooten
Télécharger la présentation

integration in HLT

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. integration in HLT M. Biglietti G. Cataldi We are investigating the possibility of using Moore as an algorithm in HLT environment. Status of Moore in HLT First results using the steering Future plans

  2. Status of Moore in HLT • Our first step has been accomplished The TrigMoore package is now in CVS, under: offline/Trigger/TrigAlgorithms/TrigMoore • It contains: • A topAlgorithm that • inherits from the Steering Algorithm: HLTAlgo. • has pointers to the Standard Moore Algorithms and services. • does not use Trigger Element and assume that the sequence is always valid. • A share directory where there are jobOptions, xml and other amenities needed in order to run • The package is ready for tagging in 6.0.1

  3. First results using Moore in HLT • A first test has been performed using: • lxplus36 – Pentium III 800 MHz 256 MB (opt) • Average on 500 events t -1 t -1-xxx no tracks MooSummary MooMakePhiSegments MooMakeCrudeRZSegments MooMakeRoads MooMakeTracks MooAlgs • t-1 Average execution time without the 1st event • t-1-xxx Average execution time without the 1st event and a xxx problematic event • no tracks Average execution time without MooMakeTracks

  4. Future Plans • Use of Trigger information as soon as they become available. • Use of a 32-bit word produced from MuCTPI (work starting this week) In order to retrieve a search region in Phi and fill PhiSegments

More Related