120 likes | 373 Views
Rack Wizard. LECC 2003 Frank Glege. Content. CMS databases - overview The equipment database The Rack Wizard. http. Introduction. Once the electronics will be finished it will have to be installed.
E N D
Rack Wizard LECC 2003 Frank Glege
Content • CMS databases - overview • The equipment database • The Rack Wizard Frank Glege - CERN
http Introduction • Once the electronics will be finished it will have to be installed. • Electronics installation of the size of a LHC experiment needs careful planning of the infrastructure. • After installation electronics components have to be tracked. • An efficient, easy to use tool is needed… Frank Glege - CERN
Database types • We will have 4 kinds of databases in CMS: • Construction databases • Holds all information about the sub detector construction up to the start of integration • Equipment management database • Holds all information to physically set up the detector and is used for asset tracking • Configuration database • Holds all information required to bring the detector in any running mode • Conditions database • Holds all information needed for event reconstruction Frank Glege - CERN
EMDB goals • Provide a single place for EM relevant data allowing for easy referencing • Fulfill the INB requirements • Provide an item history for asset tracking • Provide a set-up snapshot for electronics configuration • Allow for statistical analysis of equipment properties • Support installation logistics/procedures, e.g. labeling • Provide an “easy to use” user interface Frank Glege - CERN
Equipment management DB Conditions DB • Parts • (Detectors, Racks, electronic boards, cables, etc., including spares) • Location history for asset tracking / INB • Specific parameters • Locations • Geometrical position • Shape • Parent/children • … Configurations DB Bar code reader Logbook User authentication DB data handler (procedures) http XML Rack Wizard Label printer Graphical user interface Web front end Frank Glege - CERN
EMDB content ~13000 Frank Glege - CERN
EMDB interconnectivity • The EMDB information is tightly coupled to each other and to other detector parameters • Item location might define the electronics configuration parameters • Cables connect detector items and electronics boards • Putting all EM related data in one DB eases linking between components • The EMDB contains information needed by different services (electrical distribution, cooling, detector integration, etc..) • A prototype of a AUTO CAD connection is existing: A dynamically created AUTO CAD file, downloaded via the web, visualizes all cable paths Frank Glege - CERN
User interface • The Rack Wizard is used as GUI: • JAVA application • User authentication • Synoptic representation of items • Drag and drop mechanism • Copy/paste for racks and content • Enforces design rules • Provides statistical information • Eases configuration (estim. 1h per detector) • Independent MTF view of EMDB foreseen • Evaluated by ATLAS and LHCb Frank Glege - CERN
Rack Wizard • Separated in loader and main application • The loader is generic • Uses reflection to load main application • Assembles main application from classes in distributed locations => personalization • Main application provides infrastructure for individual item handlers • Item independent tree structure including navigation mechanism • Panel for item specific visualization • Database access mechanism • Label handling Frank Glege - CERN
Labels • CMS CSC cable label • CMS CSC detector label ME-3/2/36 Frank Glege - CERN
Item handlers • Define their relation to other item classes and reflect this to the hierarchy mechanism • Provide mostly synoptic visualization of item • Show visualization of the items parameter table • Offer item templates from a template container • Currently implemented item handlers: • Zone • Rack • Crate • Board • Channel • Cable • Detector part Frank Glege - CERN