Feedbacks from EN/STI A. Masi On behalf of EN-STI Mathieu Donze` Odd Oyvind Andreassen Adriaan Rijllart Paul Peronnard Salvatore Danzeca Mario Di Castro.

Slides:



Advertisements
Similar presentations
FESA 3 Implementation Status Stephane Deghaye BE/CO On behalf of the FESA team and many users.
Advertisements

Migrating to uPortal 2 at UBC Paul Zablosky University of British Columbia Copyright Paul Zablosky This work is the intellectual property of the.
BE-CO work for the TS Nov 8 Nov 11P.Charrue - BE/CO - LBOC1.
Sílvia Guivernau, CS Librarian, VTLS Europe Warsaw, June 2008 PUG – Polish Users ’ Group Meeting 2008 Migration Options & Planning.
Agile Testing with Testing Anywhere The road to automation need not be long.
Software Development, Programming, Testing & Implementation.
5205 – IT Service Delivery and Support
Wojciech Sliwinski for BE-CO group Special thanks to: E.Hatziangeli, K.Sigerud, P.Charrue, V.Baggiolini, M.Sobczak, M.Arruat, F.Ehm LHC Beam Commissioning.
1 © 2006 Cisco Systems, Inc. All rights reserved. Session Number Presentation_ID Using the Cisco Technical Support & Documentation Website for Security.
E. Hatziangeli – LHC Beam Commissioning meeting - 17th March 2009.
11 The Ultimate Upgrade Nicholas Garcia Bell Helicopter Textron.
Joel Bapaga on Web Design Strategies Technologies Commercial Value.
Term 2, 2011 Week 3. CONTENTS The physical design of a network Network diagrams People who develop and support networks Developing a network Supporting.
All Experimenters Meetings Windows 7 Migration 1 April 18, 2011 W7 AEM Presentation.
Software Engineering Modern Approaches
W. Sliwinski – eLTC – 7March08 1 LSA & Safety – Integration of RBAC and MCS in the LHC control system.
By Anthony W. Hill & Course Technology1 Common End User Problems.
Legacy systems overview DT Legacy System definition “Legacy system is deficiency in a system in terms of its suitability to the business, its Platform.
1 ISA&D7‏/8‏/ ISA&D7‏/8‏/2013 Systems Development Life Cycle Phases and Activities in the SDLC Variations of the SDLC models.
 To explain the importance of software configuration management (CM)  To describe key CM activities namely CM planning, change management, version management.
Searchlets Customer: Paul English Advisor: Prof. Ethan Bolker Team : Satish, Di, Quan
1 G A A new Document Control System “A new system to manage LIGO documents” Stuart Anderson Melody Araya David Shoemaker 29 September, 2008
Upgrading to IBM Cognos 10
EGEE is a project funded by the European Union under contract IST Testing processes Leanne Guy Testing activity manager JRA1 All hands meeting,
Software Development Software Testing. Testing Definitions There are many tests going under various names. The following is a general list to get a feel.
Proposal for Decisions 2007 Work Baseline M.Jonker for the Cocost* * Collimation Controls Steering Team.
Roles Committees Meetings
UNICOS-PVSS evolution Hervé Milcent (EN-ICE-SCD) 06/09/2010.
Stephane Deghaye (AB/CO) ATC/ABOC days.
CERN Equipment Management Integrates Safety Aspects EDMS Doc Eva Sanchez-Corral Mena, Stephan Petit / CERN 1 CERN Equipment Management Integrates.
20th September 2004ALICE DCS Meeting1 Overview FW News PVSS News PVSS Scaling Up News Front-end News Questions.
Status Report – Injection Working Group Working group to find strategy for more efficient start-up of injectors and associated facilities after long stops.
A MOVEMENT CONTROL SYSTEM FOR ROMAN POTS AT THE LHC Ben Farnham, Sylvain Ravat, Federico Ravotti, Mario Deile, Patrick Fassnacht, Odd Oyvind Andreassen,
Wojciech Sliwinski for the BE-CO Middleware team: Wojciech Buczak, Joel Lauener Radoslaw Orecki, Ilia Yastrebov, Vitaliy Rapp (GSI)
T HE BE/CO T ESTBED AND ITS USE FOR TIMING AND SOFTWARE VALIDATION 22 June BE-CO-HT Jean-Claude BAU.
LHC Collimators Low Level Control Commissioning Status A Masi, LHC Collimators Low Level Control Commissioning Status LHC Collimators Low Level Control.
Wojciech Sliwinski BE/CO for the RBAC team 25/04/2013.
Debriefing of controls re-commissioning for injectors after LS1 TC 09 October 2014.
Nov, F. Di Maio, M.Vanden Eynden1 CO Proposal concerning AB Front-End Software Responsibilities First detailed proposal based on the global Front-end.
CERN Raul Murillo Garcia BE-CO LS1 review – TE-EPC feedback BE-CO LS1 review TE-EPC feedback Raul Murillo Garcia on behalf of TE-EPC Daniel Calcoen Stephen.
K.Hanke – PS/SPS Days – 19/01/06 K.Hanke - PS/SPS Days 19/01/06 Recommissioning Linac2/PSB/ISOLDE from CCC  remote operation from CCC  upgrades & changes.
BE-CO-DO - Development tools (Eclipse, CBNG, Artifactory, …) - Atlassian (Jira, Wikis, Bamboo, Crucible), CO Testbed - DIAMON/LASER - JMS (Java messaging.
Team now comfortable with > 80k lines of inherited code Controller Ported to run on new 64 bit Proliant machine Re-engineered Orbit Trigger delivery (now.
1 Chapter 12 Configuration management This chapter is extracted from Sommerville’s slides. Text book chapter 29 1.
What is a level of test?  Defined by a given Environment  Environment is a collection of people, hard ware, software, interfaces, data etc.
Strategy to achieve smooth upgrades during operations Vito Baggiolini BE/CO 1.
BE-CO review Looking back at LS1 CERN /12/2015 Delphine Jacquet BE/OP/LHC Denis Cotte BE/OP/PS 1.
Oman College of Management and Technology Course – MM Topic 7 Production and Distribution of Multimedia Titles CS/MIS Department.
LS1 Review P.Charrue. Audio/Video infrastructure LS1 saw the replacement of BI and RF analog to digital video transport Was organised in close collaboration.
POST-ACCOR renovations until LS2 – DEBRIEFING – Marine Pace, CO3 – 17 September 2015 Input from Chris, Marc, Stephen, Stephane, Wojtek.
FESA S. Deghaye for the FESA team BE/CO. What happened since April? followed by “Our plans”
MPE and BE-CO Collaborations  MPE and BE-CO collaborations Jean-Christophe Garnier 01/12/2015 On behalf of TE-MPE.
22/09/05CO Review: FESA IssuesJJ Gras [AB-BDI-SW] 1/18 AB-CO Review FESA  The Functionality  The Tools  The Documentation  The Support  Maintenance.
Final Report – Injector Re- Commissioning Working Group (IRWG) Working group to find strategy for more efficient start-up of injectors and associated facilities.
LS1 – View from Applications BE-CO LS1 review – 1 December 2015 Greg Kruk on behalf of the Applications section.
Proposal: Use of ECRs for “Controls” Changes and Renovations Rende Steerenberg, Samy Chemli, Marine Gourber-Pace, Klaus Hanke, Verena Kain, Bettina Mikulec,
Industrial Control Engineering ADE Rapid Application Development Environment.
JIRA in BE-CO for Exploitation Marine BI Seminar 20 November
Software tools for digital LLRF system integration at CERN 04/11/2015 LLRF15, Software tools2 Andy Butterworth Tom Levens, Andrey Pashnin, Anthony Rey.
Dave Barney, CERN. Tracking Tools: Introduction  Main Purpose: to keep track of all incidents & interventions at point 5  Interlocks – reasons & follow-up.
Feedback on Controls from 2015 Operation Marine Pace, on behalf of BE-CO. Evian Workshop Dec 2015 Marine Pace, BE-CO -Evian Workshop 2015.
Review for Eclipse Release Review | © 2012 by Review for Eclipse Committers, made available under the EPL v1.0 1 Review for Eclipse (R4E) 0.11 Release.
Chapter 9 Testing the System 9.1 Principles of System Testing Focus A: The objective of unit and integration ensure the code implemented the design.
LS1 Review BE-CO-SRC Section Contributions from: A.Radeva, J.C Bau, J.Betz, S.Deghaye, A.Dworak, F.Hoguin, S.Jensen, I.Koszar, J.Lauener, F.Locci, W.Sliwinski,
V4.
C/C++ Build tools & Testbed
BE-CO LS1 review View from TE/ABT/EC
FESA evolution and the vision for Front-End Software
Migrating Oracle Forms Using Oracle Application Express
11/23/2018 3:03 PM © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN.
Presentation transcript:

Feedbacks from EN/STI A. Masi On behalf of EN-STI Mathieu Donze` Odd Oyvind Andreassen Adriaan Rijllart Paul Peronnard Salvatore Danzeca Mario Di Castro Mark Butcher

Scope LHC Collimators FESA class upgrade to FESA 3 Beam Stoppers consolidation project RADMON ver. 6 FESA 3 class AD target controls consolidation North Area Targets controls consolidation Recommissioning movable devices in injectors chain, LHC and experimental area Hardware commissioning LabView tools

Machine Control Coordinators (MCC) BE-CO reference person for controls services need, commissioning coordination, periodical check of the development plan Dry runs Good activities coordination. The BE-CO organization ensured that all the needed services were available in time for the dry- run Smooth Upgrades Good initiative. It allowed the impact of controls upgrades on our equipment to be evaluated. The same model can be used for a new FESA release to check the backward compatibility What worked well in LS1

FESA 3 LHC Collimator FESA class was the first one to be migrated to FESA 3 FESA 3 was available in a stable release to be used for development only well after the beginning of the LS1 The first release on 22/05/2013 was not really usable for the development because of lack of tools (i.e. migration tools, CCDB editor) The LHC collimator class upgrade started with the version The upgrade was not smooth. Migration with automatic tool failed. We decided for a complete re-development to take advantage also of the new features (i.e. rolling buffer). Several bugs slowed down the development (e.g. FESA-5659, FESA- 5110, FESA-5088, FESA-4536, FESA-4333, FESA-4286). LHC Collimator class was a good Beta tester for the new FESA 3 !!!!FESA-5659FESA- 5110FESA-5088FESA-4536FESA-4333FESA-4286 What could have worked better

RDA 3 One of the main motivation for the LHC Collimator FESA class migration to FESA 3 was the resolution of the “slow clients” issue The first FESA 3 release with RDA3 support was released only on 18/08/2014 The Machine Critical Settings were supported only on 20/03/2015 with the FESA release !!!! What could have worked better

Front-ends upgrades The replacement of the old front-ends with the new ones and the consequent migration to SLC6 64 bit came only at the end of the LS1- LHC Collimators: only few months to test the software (i.e. Bug discovered during the commissioning on the DIM library compiled for 64 bit) RADMON: Installation and commissioning of the new devices in the injectors only at the last minute What could have worked better

Timber API to access Timber via LabView very slow- This issue had a direct impact on the speed of the Hardware commissioning !!!! Problems experienced for many years. It was an intermittent fault, reported in CALS-2709, CALS-2649 and with several s sent by ICE-MTA section and the hardware commissioning team (i.e. on , , , , , ) The issue was definitively fixed at the End of February 2015 at the end of the hardware commissioning !!! What could have worked better

Generic feedbacks Robotics projects (i.e. TIM) would appreciate to have Timber working for devices on GPN. A VPN on 3G mobile network is used for communication. This solution is available only on GPN. It would be really helpful to have a BE-CO test environment (i.e. clone on Open Stack) available on GPN to validate new developments on laboratory devices FESA navigator not an ideal tool for generic viewer. Could it be improved in the future ? What could have worked better

Generic feedbacks In addition to the official FESA course the old style on-site trainings would be highly appreciated – Documentation to be improved on the web site Dedicated and not shared FESA development machines would have reduced compilation time What could have worked better

Planning, communication and follow-up: Generally good. It was important the coordination work to ensure all the services available for the dry-runs Tools and processes: Jira and s tools were adequate. More flexibility on the FESA bug resolution would have been accepted EN-STI influence on setting deadlines: Negligible. To be improved (i.e. MCS support in RDA3) Planning & organisation

CO impact on our activities: LHC Collimator migration to FESA 3 and RDA 3 as well as RADMON new FESA 3 class development suffered from the immaturity of the new framework FESA Eclipse plugin, it’s not very user-friendly – time lost to fill-in the XML file Communication: Not clear backward compatibility or impact of new release of FESA 3 and RDA 3 Often bug fix is coupled with a new release For instance the concept of device Id was introduced with the FESA 3 release (2.3.0 plug in). This represented for us a big issue of backward compatibility since we were no longer anymore to use our automatic automatic FESA instantiation files generators (mandatory to apply modification on the instantiation of more than 500 devices) Quality and testing of the implemented changes: Many bugs discovered in FESA 3 gave the feeling that the validation is not performed on complex user cases – The test cases should be more representative Technical

BE-CO timeline and deadlines to develop big changes cannot be the same as the equipment groups. New changes have to be released in a stable and tested version well before the LS to be taken into account Make a clear distinction between bug fix and new release – Improve communication on the backward compatibility of new releases (i.e. information session) Hard deadline for a new release is a few months before the start of the hardware commissioning (i.e. analysis tools need to be operational and well tested for the HC) As for the FESA 2 end of life a migration plan should be defined with each equipment group to evaluate in advance the support needed and possible improvements of the existing tools (e.g. FESA Eclipse plugin) Outlook for LS2 and future long shutdowns