1 / 11

COOL for DCS

COOL for DCS. Current Status and Plans. Introduction. Current idea for ATLAS Other LHC experiments’ ideas Possibilities for collaboration? The Oracle Archive Ideas of possible mechanisms Conclusions. Oracle Archiving without PVSS API but with COOL API. LHC Conditions DBs.

leanna
Télécharger la présentation

COOL for DCS

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. COOL for DCS Current Status and Plans Jim Cook, PVSS/Conditions DB Interface

  2. Introduction • Current idea for ATLAS • Other LHC experiments’ ideas • Possibilities for collaboration? • The Oracle Archive • Ideas of possible mechanisms • Conclusions Jim Cook, PVSS/Conditions DB Interface

  3. Oracle Archiving without PVSS API but with COOL API Jim Cook, PVSS/Conditions DB Interface

  4. LHC Conditions DBs Alice has closest match to ATLAS. Possibility of added man-power Jim Cook, PVSS/Conditions DB Interface

  5. Signal PVSS PVSS COOL Conditions DB PVSS PVSS Oracle Archive PVSS Data Data COOL Data PVSS-COOL Process Configuration DIM-COOL Process LHCb System Overview Jim Cook, PVSS/Conditions DB Interface

  6. PVSS Oracle Archive • Uses trigger • Data inserted/updated in a single table • Trigger ‘takes’ this data and enters it into required table • Table always holds last value of element • Also contains timestamp and validity information • Array data in separate table • Also has a trigger • Identifiers used in database • Datapoint element names in separate table Jim Cook, PVSS/Conditions DB Interface

  7. Mechanism? (I) • ‘Overload’ trigger • Enter required data into table under our control • Temporary tables • Allow to grow to pre-defined size • Create new table and ‘close’ old one • Size can be tailored for optimum performance • Use block update feature of COOL • Possible to filter data at this time • External process • Signaled when temporary table is ‘closed’ • How to signal process? Jim Cook, PVSS/Conditions DB Interface

  8. Mechanism? (II) • External Process • Uses timer(s) for when to copy data • No signalling required • Retrieve data over last time-range • Use block update feature of COOL • Could filter data at this time • No additional code required in Archive itself Jim Cook, PVSS/Conditions DB Interface

  9. External Process • Read data from PVSS Oracle Archive • Use COOL API • Uses configuration information held in PVSS Oracle Archive • This implies this configuration information held in known datapoints that are archived • Mechanism (I) only • Remove temporary table(s) • Once data known to be in COOL, can drop temporary tables to save space Jim Cook, PVSS/Conditions DB Interface

  10. Signaling • Oracle Foreign Function Interface (FFI) • Unix (SUN) and Windows • Call shared library functions • Use sockets for platform independence? • Keep function small • Fast and simple • Send name of temporary table to process • Is this permitted on CERN servers? • External process polling • Intermittent check for value in DB • When ‘true’, process table indicated • Other ideas? Jim Cook, PVSS/Conditions DB Interface

  11. Conclusions and Questions • PVSS Oracle Archiving • Can be used now with some limitations • Un-user friendly setup • Trigger usage • Scalability and performance questions • Signaling • Push or Pull? • ‘Push’ would run on Oracle server • Mechanism • Both ideas presented need investigation before final decision made Jim Cook, PVSS/Conditions DB Interface

More Related