Configuration DB

• Configuration Paths
• Basic Principles
• Responsibilities
• Which Data to store?
• Structuring Data
• Bootstrap and an Example Structure

Configuration Paths

• multiple data-sources and destinations
  • EPICS IOC and client configuration
  • HL-Application configuration
• multiple platforms
  • for data-maintenance, -mining
• DB-structure is the organizing instance

Basic Principles

• make DB the unique data-source
  • everything that is possibly of interest for anyone at any time in the future should go into the DB
• avoid redundancies
  • cooperation DB-Admin & Data-Responsible
• clearly separate internal representation from user-views

Responsibilities

Which Data to store?

• Control System
  • Names, Types of Devices
  • configuration Parameters
• User Interface
  • Geometrical Information
• (high level) Applications
  • Additional Information (e.g. conversion factors)
  • Purpose-specific Attributes

Structuring Data

• Device specific
  • specifications
  • grouping
• Application Oriented
  • functional information
• Characteristic of Data
  • static (specs), variable (config), measurements

Bootstrap and an Example Structure

• Use a uniform bootstrap for each set of Tables -> Device Name
• Device Name could/should tell about
  • Type of device (magnet, power supply, valve ...)
  • Purpose of device (quadrupole, steerer ...)
  • Location of device (to ease fault detection)
  • Whatever seems useful...

Latest modification: 15 Jun 99 22:05:30 Thomas Birke Thomas Birke <[email protected]>