Glossary

CMS

TRIDAS

  • ACM Access Control Module
  • CI Controller Interface
  • CCU Communication and Control Unit
  • GCT Global Calorimeter Trigger
  • EMM Error Management Module
  • FSM Finite State Machine
  • PAC Pattern Comparator
  • RCM Response Control Module
  • RCT Regional Calorimeter Trigger (L1)
  • TTC Trigger Timing and Control
  • SLink simple link interface, is a high-performance data acquisition standard developed at CERN for collecting information from particle accelerators and other sources, see http://en.wikipedia.org/wiki/S-LINK

RPC specific

  • CCS Clock and Control System
  • DCC Data Concertrator Card
  • GB Ghost Buster
  • LB Link Boards receive the RPC signals transmitted through copper cables, more
  • LBox Link System / Chambers
  • LMux The LMux and NMux is a chipset based on ATM Multiplex/De-multiplex. It is a PHY multiplexer. It is used in line cards for low cost broadband multiserviceaccess platform constructed over point-to-point serial backplanes.
  • SB Splitter Board. Receives optical signals and converts them to the electrical ones (up to 10 inputs and 16 outputs)
  • SC Splitter Crate. Receives the data devoted to one Trigger Crate from Link System and distributes them to the Trigger Boards (up to 3 different boards)
  • TTU Technical Trigger Unit, https://twiki.cern.ch/twiki/bin/view/CMS/RpcTTUemulator
  • RTS RPC Trigger Supervisor
  • SC Sorter Crate
  • TC Trigger Crates
  • TTU Technical Trigger Unit, more

DB

  • OCCI Oracle C++ Call Interface
  • OMDS on-line master data storage, located in IP5; this relational database contains the configurations, conditions, equipment management, and detector geometry databases, as well as the LHC data. The (electronics) Logbook, which at the moment is file-based may be added to the OMDS once it become DB (Oracle) based. (https://twiki.cern.ch/twiki/bin/view/CMS/DBTaskForce)
  • PopCon transfers the conditions objects from a user-defined data source to the off-line database. It is the developer's responsibility to provide the code which handles the data source and to specify the destination for the data. One should instantiate his/her objects, provide the IOV information for such objects and configure the database output module. Once the objects are built, the PopCon application writes the data to the specified database. Subdetector code must not access the target output database. It only passes the objects to the output module.
  • PVSS Process Vizualisation and Control System (Prozessvisualisierungs und Steuerungs-System)

CMS misc

  • IOV Interval of Validity (IOV) is the contiguous (in time) set of events for which calibration or alignment data are to be used in reconstruction, more

-- NikolayDarmenov - 12 Feb 2009

Edit | Attach | Watch | Print version | History: r8 < r7 < r6 < r5 < r4 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r8 - 2009-09-07 - unknown
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Main All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright &© 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback