evania
Uploaded by
23 SLIDES
356 VUES
230LIKES

Requirements from Application section

DESCRIPTION

This document provides an in-depth review of timing services requirements as outlined by S. Deghaye. It covers essential topics, including the nature of timing services, usage summaries, access methods via JAPC interface, non-functional requirements, and examples. Additionally, it addresses implementation constraints and discusses future evolution aspects of the InCA project. The aim is to ensure reliable, extensible timing service architecture that supports robust diagnostics and enhances user interface homogenization across control systems.

1 / 23

Télécharger la présentation

Requirements from Application section

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. Requirements from Application section Timing Review Stephane Deghaye 29/02/2008

  2. Agenda • What timing services • Usage summary • How to access the timing services • Interface • Non-functional requirements • Examples • Implementation constraints • Future evolution (InCA) • Summary Timing Review: Requirements from AP Section - S. Deghaye

  3. What timing services • Central timing events • Events distributed on the timing network • Telegram • Set of info on what the machines are doing • Run-time configuration • What is programmed (Sequence, BCD, SuperCycle) • What is played and why. • Static configuration • Info on the different concepts (machine, user, telegram groups...) • External conditions • Variables set externally conditioning the sequencing Timing Review: Requirements from AP Section - S. Deghaye

  4. Agenda • What timing services • Usage summary • How to access the timing services • Interface • Non-functional requirements • Examples • Implementation constraints • Future evolution (InCA) • Summary Timing Review: Requirements from AP Section - S. Deghaye

  5. Usage summary (1/2) • Central timing events • Connect to events to trigger computation. • Send events on request (LHC, Transaction). • For Logging, JAPC (Monitoring), SIS, Generic GUIs, Cesar... • Telegram • Reception of one or several telegram groups • Human readable format • For Logging, SIS, FixDisplay, GUIs (Generic/Specific), LASER... Timing Review: Requirements from AP Section - S. Deghaye

  6. Usage summary (2/2) • Run-time configuration • Retrieve SuperCylce length, active users. • Retrieve what was played and why (Normal/Spare). • For Fault Statistics (Logging), LSA, FixDisplay, Generic GUIs, Cesar... • Static configuration • List of available users, central events, machine, telegram groups... • For LSA, Sequencer, Generic GUIs... • External conditions • Acquisition and control • For Logging (read-only) and SIS (read/write) Timing Review: Requirements from AP Section - S. Deghaye

  7. Agenda • What timing services • Usage summary • How to access the timing services • Interface • Non-functional requirements • Examples • Implementation constraints • Future evolution (InCA) • Summary Timing Review: Requirements from AP Section - S. Deghaye

  8. How to access the timing services Interface • The timing services should be accessible through a JAPC interface • Why?  Homogenous view with the rest of the low-level control system • Usage of standard components • No need to learn a new API Timing Review: Requirements from AP Section - S. Deghaye

  9. How to access the timing services Non-functional requirements The JAPC implementation must be: • Reliable and easy to diagnose • Dedicated com & distribution should be avoided • Extensible • Add another piece of info should be fast • Able to use transparently a dedicated timing receiver • High reliability cases (SIS) Timing Review: Requirements from AP Section - S. Deghaye

  10. Agenda • What timing services • Usage summary • How to access the timing services • Interface • Non-functional requirements • Examples • Implementation constraints • Future evolution (InCA) • Summary Timing Review: Requirements from AP Section - S. Deghaye

  11. Example Possible use of the CPS user info (hypothetical structure) JAPC Parameter: “CPS-TELEGRAM/USER#CURRENT” Specific code Logging JAPC Monitoring Timing Review: Requirements from AP Section - S. Deghaye

  12. Agenda • What timing services • Usage summary • How to access the timing services • Interface • Non-functional requirements • Examples • Implementation constraints • Future evolution (InCA) • Summary Timing Review: Requirements from AP Section - S. Deghaye

  13. Implementation constraints • Not strictly AP business but... • Parameter structure needs to be defined in collaboration with AP. • Need to understand how the components we use in our systems work. • Side effect • Reliability • Diagnostics •  Strongly encouraged to use standard CO components such as FESA, CMW, SIS, Oracle... Timing Review: Requirements from AP Section - S. Deghaye

  14. Agenda • What timing services • Usage summary • How to access the timing services • Interface • Non-functional requirements • Examples • Implementation constraints • Future evolution (InCA) • Summary Timing Review: Requirements from AP Section - S. Deghaye

  15. Future evolution – InCA • Injection Control renovation going on • InCA will bring new concepts & features • Better integration of the high-level parts. • Some constraints might be relaxed E.g. The user name might be less visible • Not for tomorrow Timing Review: Requirements from AP Section - S. Deghaye

  16. Future evolution – InCA Appl. 1 Appl. 2 Appl. 3 Appl. 4 High-level parameter space Set PR.DHZ01 to 10 A on cycle LHC Pilot InCA Low-level parameter space Set PR.DHZ01 to 10 A on CPS:USER:SFTPRO Low-level parameter space Set PR.DHZ01 to 10 A on CPS:SLOT:6 FEC 1 FEC 2 FEC 3 FEC 4 Timing Review: Requirements from AP Section - S. Deghaye

  17. Agenda • What timing services • Usage summary • How to access the timing services • Interface • Non-functional requirements • Examples • Implementation constraints • Future evolution (InCA) • Summary Timing Review: Requirements from AP Section - S. Deghaye

  18. Summary • Set of timing services and their main usage identified • Central events • Telegram • Run-time & static configuration info. • External conditions • JAPC interface to these services required • Standard components must be used • High-reliability installations must be possible Timing Review: Requirements from AP Section - S. Deghaye

  19. Question ?Thank you for your attention Timing Review: Requirements from AP Section - S. Deghaye

  20. Example Subscription to the CPS user using JAPC public class TelegramListener implements ParameterValueListener{ /** * Starts the subscription on the telegram group given */ public void startMonitoring(String telegramGroupName){...} /* * Receives the updates and prints the result */ public void valueReceived(String parameterId, AcquiredParameterValue value){...} } Timing Review: Requirements from AP Section - S. Deghaye

  21. Example - startMonitoring /** * Starts the subscription on the telegram group given */ public void startMonitoring(String tlgGrpName){ try { ParameterFactory fact = ParameterFactory.newInstance(); Parameter parameter = fact.newParameter(tlgGrpName); SubscriptionHandle handle = parameter.createSubscription(null, this); handle.startMonitoring(); } catch (ParameterException e) { System.out.println("Can't subscribe to " + tlgGrpName); } } Timing Review: Requirements from AP Section - S. Deghaye

  22. Example - valueReceived /* * Receives the updates and prints the result */ public void valueReceived(String parameterId, AcquiredParameterValue value){ String user = ((MapParameterValue)value.getValue()).getString("value")); System.out.println("Got " + user + " from " + parameterId); } Timing Review: Requirements from AP Section - S. Deghaye

  23. Example - result TelegramListener() listener = new TelegramListener(); listener.startSubscription(“CPS-TELEGRAM/User”); -- Output example Got SFTPRO from CPS-TELEGRAM/User Got SFTPRO from CPS-TELEGRAM/User Got AD from CPS-TELEGRAM/User Timing Review: Requirements from AP Section - S. Deghaye

More Related