1 / 43

Distributed Information Services for Control Systems: Enhancing Experimental Physics Facility Collaboration

The DISCS (Distributed Information Services for Control Systems) project aims to tackle the integration challenges faced by experimental physics facilities (EPFs) during their design, construction, commissioning, operation, and maintenance phases. By developing configurable, collaborative services, DISCS facilitates seamless data sharing among heterogeneous systems. Collaborations span multiple international laboratories, including Brookhaven National Lab and the European Spallation Source. Through a modular and scalable architecture, DISCS strives to unify operations, ensuring that diverse teams can work cohesively despite varying priorities and technological platforms.

konala
Télécharger la présentation

Distributed Information Services for Control Systems: Enhancing Experimental Physics Facility Collaboration

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. DISCS - Distributed Information Services for Control Systems FRIB-NSCL, East Lansing, Michigan, USA. Eric Berryman

  2. Overview • Problem • Vision • Collaborators • Architecture • Development Methodology • Domains & Modules • Current Status • Conclusion

  3. The Problem

  4. Problem Statement • Disparate and Heterogeneous Systems Used During The Design, Construction, Commissioning, Operation, and Maintenance of an Experimental Physics Facility (EPF) • No Way to Share Data

  5. Problem Illustration

  6. DISCS

  7. DISCS Vision To Develop Collaborating Services That Any Experimental Physics Facility Can Easily Configure, Use, And Extend For Its Design, Commissioning, Operation, And Maintenance

  8. DISCS – Scope I

  9. DISCS – Scope II

  10. DISCS Collaborators • Brookhaven National Lab, USA • Cosylab, Slovenia • European Spallation Source, Sweden • Facility for Rare Isotope Beam, USA • Institute for High Energy Physics, China

  11. DISCS Challenges • Integration Of Myriad Databases • Multiple Teams From Different Labs • Geographically Dispersed Collaboration • Labs Have Different Priorities • Labs Have Different Schedules • Labs Have Different Technology Platforms • Differing Software-engineering Processes

  12. DISCS – Architecture

  13. DISCS Architecture • Application layer • Operator interfaces • High-level applications • Libraries • Service layer • Access to data • Programming Interface • Data layer • Managed data • Instrument data • No direct access

  14. EPICS V4 - DISCS

  15. Development Methodology • I – Divide • Entire System Is Broken Down Into Smaller Loosely-coupled Parts Or Domains • II – Develop • Each Domain Is Implemented Independently • III – Frame • Application Programming Interfaces Are Developed • IV – Integrate • Domains Are Integrated Check Paper For Details

  16. DISCS Modules • Module: An Implementation Of A Domain

  17. DISCS - Status

  18. DISCS Status

  19. DISCS - Screenshots

  20. Logbook: Web Client

  21. Logbook: CSS Client

  22. Logbook: pyOlog

  23. eTraveler – List of Travelers

  24. eTraveler – DevicesIntegration with Configuration Module

  25. Configuration: Component Tree

  26. Configuration: Magnet Measurement

  27. Configuration: Live Signals (PV)

  28. Screenshots – Configuration Module

  29. Configuration: Component Relationships

  30. Configuration: Component Relationships

  31. Configuration: Lattice

  32. Lattice-Model: Beamlines

  33. Naming Convention – Name Elements Name Elements Are Parts of A Name: System, Subsystem, Device Type etc

  34. Naming Convention – Submit Requests Submit Requests to Add, Modify, or Delete Name Elements

  35. Naming Convention – Process Requests

  36. Naming Convention - Reports

  37. Screenshots – Unit Conversion

  38. Screenshots – Save/Restore

  39. Cables – Normal View

  40. Cables – Manager View

  41. Cables - Types

  42. Conclusion • Described An Information Services Framework For Accelerator Design, Commissioning, Operation, And Maintenance • Discussed Challenges To Collaborative Development • Acknowledgements: • IRMIS, Control System Studio, EPICS V4, ChannelFinder, and PVManager Teams • DISCS Website: http://discs.openepics.org

  43. Thank you! “Nine people can’t make a baby in a month.” – Fred Brooks, The Mythical Man-Month “Computer science is no more about computers than astronomy is about telescopes” – Edsger W Dijkstra

More Related