1 / 12

LHC LOGGING

LHC LOGGING. Ronny BILLEN & Maciej PERYT. SL/MR/DBS - LHC-IAS. Outline. Launching of the LHC Logging project Mandate, scope and objectives Timeline of the project, resources Context: where does logging fit in? Basic functionalities Filtering of data

abdalla
Download Presentation

LHC LOGGING

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. LHC LOGGING Ronny BILLEN & Maciej PERYT SL/MR/DBS - LHC-IAS

  2. Outline • Launching of the LHC Logging project • Mandate, scope and objectives • Timeline of the project, resources • Context: where does logging fit in? • Basic functionalities • Filtering of data • Interfacing to other systems • The time issue • Architectural design, use of technologies • Conclusions

  3. Project launch • Started on 17-Sep-2001 launched as sub-project of LHC-CP • R. Billen (SL) M. Peryt (LHC) initial resources http://lhc-logging.web.cern.ch/lhc-logging/

  4. Mandate, scope, objectives • Analysis, design, procurement of Logging Facilities for future LHC Controls System • Information management for LHC performance improvement • Meet INB requirements for recording beam history • Make available long term statistics for management • Avoid duplicate logging efforts • Within the scope is: • Analyze experience, capture requirements • Implement first version to support QRL controls • Investigate interface with Alarms and Post-Mortem systems • Objectives • Establish logging facility for QRL, scalable to LHC • Major project review after validation for QRL

  5. Arrival Fellow Today Architectural Design Published Logging Project Launch 2001Q3 2001Q4 User Requirements Collected 2002Q1 2002Q2 2002Q3 2002Q4 2003Q1 2003Q2 User Interfaces Published Functional Specification Published System Needed by QRL Users System Available for QRL Users Project Timeline

  6. LHC equipment Off-line Analysis OPERATORS Data input, storage & output Data providers Data users LHC Logging Database QRL CRYOGENICS Run-time Logging Data Selected Logging Data EXPERTS VACUUM Gen. SERVICES MANAGERS OTHERS … Selected Alarms Data AD-HOC USERS Selected Post-Mortem Data Logging Context ALARMS system POST-MORTEM system

  7. Functionalities • Logging data = Time-Series data + Meta-data • Time-Series = 2D {Timestamp, Value} • Meta-data describes Time-Series • Data values of all normal types • Timestamps with sub-second precision possible • Derived time-series with formula or algorithm applied • Physical values from raw values • Aggregate information like subtotals, averages • Logged data remains persistent • Data output tool with charting and filing options • User profile data kept to store preferences for data visualization

  8. Data filtering • The final objective of the central logging facility in LHC operational performance • In discussion with the data provider, advice will be given with respect to appropriate data input filtering • Depending on system concerned • May imply summary data, averages, sampling,… • For data output filtering options will be foreseen as well

  9. Interfacing to other systems • Correlate Alarms data to logging data • Event type data • Start/End time of an alarm • Character string data • Well-defined naming schema to be respected • Combine Post-Mortem data to logging data • Only loosely coupled systems • High frequency data  timestamp accuracy • Large volume data  filtering • Well-defined naming schema to be respected • Data exchange with industrial systems (SCADA) • Logging of their data  standardized • Visualizing logging data in PVSS trending tool  why not?

  10. The TIME issue • The data provider will procure to the logging system time-stamped data, i.e. the Time-Series • The responsibility for the correctness of the time remains with the data provider • All data providers should have a synchronized time-stamping facility • The use of UTC, Local Time, Time-zone, Summer-time (till 2006 at least)must be defined at LHC-CP level • It will be difficult to correlate data with different time-stamp accuracy (and to indicate different accuracies)

  11. Architecture & Technology • The architectural design phase will start in a few weeks • Established Technologies will be used…

  12. Conclusions • The LHC Logging project is firmly launched • The systems involved in QRL are the first real clients • The Logging System must be scalable for LHC • Milestones have been respected so far • The architectural design phase is about to start • The extra 6 months are warmly welcomed for the implementation phase • That’s all folks!

More Related