1 / 15

CO Proposal concerning AB Front-End Software Responsibilities

CO Proposal concerning AB Front-End Software Responsibilities. First detailed proposal based on the global Front-end proposal presented at CO3 on Nov 2, 2006. Contents. Foreword CO proposal for FE Software PS FE software Inventory Evolution. Foreword.

misae
Télécharger la présentation

CO Proposal concerning AB Front-End Software Responsibilities

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. CO Proposal concerning AB Front-End Software Responsibilities First detailed proposal based on the global Front-end proposal presented at CO3 on Nov 2, 2006 F. Di Maio, M.Vanden Eynden

  2. Contents • Foreword • CO proposal for FE Software • PS FE software • Inventory • Evolution F. Di Maio, M.Vanden Eynden

  3. Foreword • Four aspects to agree @ CO3 concerning Front-ends responsibilities • FE Software (this presentation) • FE Hardware (in progress …) • FE Configuration Management (not started) • FE First-line Responsibility (not started) • A clarification towards a department wide strategy rather than a “Big Bang” F. Di Maio, M.Vanden Eynden

  4. CO Proposal for FE Software • CO Responsibility • System Level SW • O/S definition, installation, support and evolution (LynxOS and LINUX SLC-x) • Device drivers and libraries for the list (to be reviewed @ CO3 …) of standard/generic HW modules (CTR-x, GFAs, DAC, ADCs, MIL-1553, WorldFIP, RS-232 line drivers, OASIS boards, etc) Clear commitment from CO to keep strong homogeneity and to offer a complete and well supported set of generic FE controls solutions F. Di Maio, M.Vanden Eynden

  5. CO Proposal for FE Software • CO Responsibility • FESA Framework • Specification, design, release (up to 3/year) and support of the framework, with full validation @ CO3 level • Strong support to developers during all development phases (fesa-support@cern.ch) : • Training: regular tutorials and hands-on for new developers • Design and coding: advice on implementation issues • Commissioning and quality insurance: code reviews, correct framework usage, etc (non-mandatory) • Operation: strong diagnostic tools and on-line support during normal working hours Strong commitment from CO to develop and offer extended support for FESA, as the agreed AB department front-end solution F. Di Maio, M.Vanden Eynden

  6. CO Proposal for FE Software • CO Responsibility • FESA Software • Software for the support of the list of standard/generic HW modules • Projects under full CO responsibility (BIC, OASIS) • Legacy GM Software • Classes under PS/CO responsibility only • Maintenance limited to corrections and adaptation (environment changes), no evolution. • Deployment of new instances CO remains responsible for the development and support of a significant amount of generic and project-based Front-end software F. Di Maio, M.Vanden Eynden

  7. CO Proposal for FE Software • Equipment Groups Responsibility • FESA Software • Develop software for the support of their specific hardware and instruments • Decide, in agreement with AB-OP, about the operational deployment of their software • Use CO support during all phases of development • Legacy GM Software • Replace with new FESA software when required (cf. next slides) Equipment groups are responsible for the development and operation of their front-end software F. Di Maio, M.Vanden Eynden

  8. PS Front-end SoftwareInventory • Source is the configuration DB • Each class: • A description • A creator (the initial author) • An “ABGroup”: the group in charge of the equipment. To be updated • All instances (FEC, accelerator) Note: GM adaptor classes can be identified F. Di Maio, M.Vanden Eynden

  9. PS Front-end SoftwareInventory • An excel file (here) with the ABGroup field initialized • To be checked and updated by the groups • Once done → configuration DB F. Di Maio, M.Vanden Eynden

  10. PS Front-end SoftwareInventory Group in charge of the equipment Changes from the DB Number of FECs “Shared” (more than one accelerator) F. Di Maio, M.Vanden Eynden

  11. PS Front-end SoftwareInventory F. Di Maio, M.Vanden Eynden

  12. PS Front-end SoftwareInventory • “specific” classes: only on one accelerator • GM+FESA in the 2007-2010 period • Remark: figures not corrected by removing FESA GM adapter classes F. Di Maio, M.Vanden Eynden

  13. PS Front-end Software Evolution • Phase I • GM->FESA when: • New equipment • New interface • New software required (problems or extension planned) • Renovate equipment and interfaces • Reverse the balance GM/FESA • Phase II • Homogenize / accelerator • Suppress GM I ? II F. Di Maio, M.Vanden Eynden

  14. PS Front-end Software Evolution • Transition I→II to be defined • Phase I : new FESA classes • Phase II: GM-> FESA migration • 0.25-0.5 FTE / FESA class with temporary staff (experience in BI & CO) • Number of FESA classes is not the current number of GM classes F. Di Maio, M.Vanden Eynden

  15. Conclusion • A practical proposal (clarification) for Front-End software responsibility and support • An inventory of the PS Front-End software and its possible evolutions • Feedback from each equipment group (CO3) is the next step towards a global agreement, especially concerning the PS complex • Next aspects to address: • Front-End Hardware • Front-End configuration management • Front-End first-line of responsibility F. Di Maio, M.Vanden Eynden

More Related