1 / 22

The JCOP Framework Redesign

This article discusses the redesign of the JCOP Framework, including the shortcomings of the previous version and the new features implemented in the latest version. It also explores the application development process and provides insight into the current work being done by the framework team.

ccastaneda
Download Presentation

The JCOP Framework Redesign

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. The JCOP Framework Redesign Framework Team Framework Team

  2. Contents • Context • Shortcomings in Framework 1 • New features in Framework 2 • Application Development • Current work • Conclusions Framework Team

  3. Context • Version 1.0 released in June 2001 • Merge of COMPASS and JCOP Frameworks • Followed Architecture Design • Experience gained with usage of Framework and PVSS • LHC testbeams and integration activities • Fixed target experiments • LHC Cryo (UNICOS) • LHC Gas Control System (GCS) • Improved knowledge of hardware • Better understanding of requirements for LHC • Operation, Hardware Framework Team

  4. Shortcomings in FW 1 • Hierarchy based on pointers • Flexible concept • Misleading (FW and PVSS views differ) • Difficult to maintain coherency • Distributed systems • Framework tools not fully integrated • Overall application development concept missing • Perceived to be complex to set up • Easy to get lost in the documentation Framework Team

  5. Redesign • Request by Experiments in March/April 03 • Many discussions to define the scope • Representatives from all experiments • Difficult but constructive • Not always a “best approach” • Decisions by consensus • Scope and schedule defined by June 03 • No need for backwards compatibility • Experiments participated in development Framework Team

  6. Framework 2: Architecture Framework Team

  7. Framework 2: Features • All tools integrated in DEN • Standardized views/hierarchies • Hardware (DP name) • Logical (DP alias) • General for FSM and others (pointers) • Set up further simplified for non experts • Defaults for parameters wherever possible • Try to do as much as possible at creation time • Devices contain everything necessary to connect to hardware Framework Team

  8. Framerwork 2: Features (II) • Easy integration of new device types • Data driven device configuration • Consolidated common behaviour • E.g. Device library • Reorganization of files • Upgrade to PVSS 3.0 • Benefit from new features Framework Team

  9. FW 2: Distributed systems • DEN allows to browse remote Hardware and Logical Views • Other operations disabled (e.g. create, set up) • Chosen philosophy • Source of confusion • Current limitation of PVSS • Only FSM tree can cross system boundary Framework Team

  10. Framework Team

  11. Core Device Editor Navigator FSM LHCb development Device common facilities PVSS configs Devices Analog Digital CAEN Standard CERN hardware Wiener Contains Crate and Power Supply Commercial OPC server ELMB ATLAS development Released Components Framework Team

  12. Released Components: Tools • Installation • Independent installation of subcomponents • Trending • Template mechanism • Distributed systems • Trend tree updated • Configuration DB • Prototype based on Oracle • Access Control • Only API Framework Team

  13. Development Process • Introduction of Savannah • LCG development portal • Used to keep track of improvements/bugs • User can follow status • Report for each release • Remedy still main interface with the user. • Frequent releases • ~1-2 per month • Documentation Framework Team

  14. Application development (I) • Contact Experiment Central Team • Hardware to be used • Guidelines for development • Constraints to fit in DCS • Attend course • Standard hardware, OPC basics • PVSS & Framework • Best usage of tools • Experiment’s central team experts • IT/CO experts • Follow up of problems • Itcontrols.support@cern.ch • Experiment contact person Framework Team

  15. Application development (II) Integration of new devices Hardware View Logical View Config DB FSM behaviour Trending User libs & panels Framework Team

  16. Framework Team

  17. Framework Team

  18. Framework Team

  19. Current Work (I) • ISEG • ALICE development • Prototype exists • Rack control • CMS development just started • PS/SPS machine data • Upgrade to new core • Integration of Data Interchange Protocol (DIP) • Layer on top of DIM • PVSS driver/manager • First release June 04 • Configuration Database Tool • New version of DB schema • Performance measurements/optimizations Framework Team

  20. Current Work (II) • Performance measurements of PVSS configs • Measured different alternatives • ETM discussion and code review • Wizard to include new device types • New CAEN hardware • Easy system • CMS MDT custom system • Control of Wiener PL500 (ALICE HMPID) • Generic External Handler • Upgrade to PVSS 3.0 Framework Team

  21. Current Work (III) • Integration of XML parser • Evaluating DOM/SAX models • Gathering user requirements • Upgrade to PVSS 3.0 final • Minor changes foreseen Framework Team

  22. Conclusions • Redesign is one more step forward • Not a complete change in direction • Consensus among LHC experiments • Delivered in time • Open issues • Distributed systems • Archiving to Oracle • Commercial OPC servers • Crucial time to get subdetectors involved • Foresee a big effort on support • Detailed presentations of FW components • FSM, Trending, Configuration DB Framework Team

More Related