1 / 10

COMETE Status

COMETE Status. Synopsis. Reminder: Comete & ATK Software architecture Migration status from ATK to Comete Evolutions. GUI. Flamenco Foxtrot Baladi. GlobalSCREEN Salsa. ATKPanel. Mambo. Widgets. ATKWidgetSoleil Fork JLChart Fork NumberImageViewer Fork ImageJViewer. ATKWidget

nakia
Download Presentation

COMETE Status

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. COMETE Status

  2. Synopsis • Reminder: Comete & ATK Software architecture • Migration status from ATK to Comete • Evolutions

  3. GUI Flamenco Foxtrot Baladi GlobalSCREEN Salsa ATKPanel Mambo Widgets ATKWidgetSoleil Fork JLChart Fork NumberImageViewer Fork ImageJViewer ATKWidget JLChart NumberImageViewer ImageJViewer Fork JLChart Fork JLChart Data source Archiving DB Api Nexus4Tango Api TangORB Api Old software architecture

  4. GUI Flamenco Foxtrot Baladi GlobalSCREEN Salsa ATKPanel Mambo Widgets ATKWidget JLChart NumberImageViewer ImageJViewer CometeWidget ChartViewer ImageViewer Data Access Object NexusDAOFactory TangoDAOFactory ArchivingDAOFactory Data source TangORB Api Nexus4TangoApi Archiving DB Api Software architecture

  5. Status • Comete is now deployed on every SOLEIL beamline • The last 3 runs, we have ported ~80% of GUI applications to Comete: • First phase: Tango control software (identified as low risk) • Second phase: Data reduction applications • Third phase: GlobalScreen is 100% Comete compliant and integrates Comete application from the two first phases. • These phases helped us to identify some issues on Comete first releases and some improvements

  6. The future of Comete • Data model simplification • New API services: • DataReduction • Refreshing strategies

  7. DataReduction Current Architecture Next Architecture Comete Widgets Comete Widgets getFittedData() getData() Data Reduction Engine <Source>DAO getData() <Source>DAO

  8. Refreshing Strategies • The refreshing strategy is context dependant. • The API cannot determine which refreshing strategy is the best • COMETE will allow the developper to choose the prefered strategy: • Refresh by device • Refresh by attribute • Refresh by data type • Do not refresh (wait for HMI requests) • Other implementations • COMETE will share the refreshers inside the JVM: • If two Comete widget request data from Tango, Comete API will generate only one Tango request. • Huge performance improvement in SCADA systems

  9. Refreshing Strategies ATK Tuning on position attribute on the MARS Beamline (80 position attributes) Comete Widgets Comete Core Attribute Refresher Motor1 Motor3 Motor2 Motor<n> position position position position

  10. TUMBA (MCA bean) connected to MCA Device (~30 attributes) Comete Widgets Comete Core Device Refresher XMAP Device Accumulate channel00 channel01 channel02 channel03 ….

More Related