1 / 11

Post Mortem

Post Mortem. PM analysis tools. ASCII files. Binary files. PM server. PM Server (CMW). Binary data sent over CMW. CMW. PM Client. PM Client. PM Client. Systems. Other analysis tools. Browser. PIC. QPS. PC. Lynx OS. Lynx OS (FESA). Linux. Courtesy G.Kruk.

latona
Télécharger la présentation

Post Mortem

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. Post Mortem PM analysis tools ASCII files Binary files PM server PM Server (CMW) Binary data sent over CMW CMW PM Client PM Client PM Client Systems Other analysis tools Browser PIC QPS PC Lynx OS Lynx OS (FESA) Linux Courtesy G.Kruk

  2. Post Mortem (PM Client) PM Client functionality: • Wrapper to CMW client used by systems to send the PM data • Takes care of re-sending data in case of communication problems • Possibly saves data locally* in case of unsuccessful transfer or even before sending the data - What to do in a diskless system? • Possibly checks availability of the PM server (heart beat) • Possibly sends alarms to the Laser system in case of problems Courtesy G.Kruk

  3. Post Mortem (PM Client) Advantages of having the PM Client: • Decreases work which probably would have to be repeated in all systems • Simplifies and decreases testing (one code instead of several) • Takes care of correct formatting data sent to the server (all required fields, etc.) and decreases a risk that the server will receive unexpected data • If for some reason there is a need to modify the interface (protocol, data formatting, …) it will be modified (and tested) only once in the Client code instead of asking each system to adapt their code. • … Courtesy G.Kruk

  4. Post Mortem (Issues + further work) • Implementation of the PM Client (which seems to be a good idea) • Implementation of operational version of the PM Server • Data transfer over CMW (will be solved soon) • Define configurations and descriptors of the PM data sent by all involved systems (used to convert binary to ASCII files and possibly used by analysis tools) • Select the data that should be stored permanently (in a database) and • Write an appropriate application which will do it • Move the PM Server to an operational machine and provide space and directory structure Courtesy G.Kruk

  5. Post Mortem PM analysis tools ASCII files Binary files PM server PM Server (CMW) Binary data sent over CMW CMW PM Client PM Client PM Client Systems Browser Other analysis tools PIC QPS PC Lynx OS Lynx OS (FESA) Linux A B Courtesy G.Kruk

  6. interface A pm system <-> users • functionalities • visualisation of predefined sets of field variables • verification of the occurrence of the expected sequence of events • signal processing to identify properties of circuits such as time constants

  7. interface A pm system <-> users Courtesy A.Rijllart

  8. interface A pm system <-> users Courtesy A.Rijllart

  9. interface A pm system <-> users Courtesy A.Rijllart

  10. interface B pm system <-> client systems • functionalities • triggering • data transfer integrity • data format • not just SDDS, Rosali or binary • the existence & the tagging of the trigger • handling of multiple triggers • API definition • dimensioning i.e. definition of data rates and data volumes

  11. milestones • use cases • specification document • definition of interface A • definition of interface B • prototype • first release • beginning of power tests mid june 2005 mid july 2005 end july 2005 end october 2005 first week of december 2005 end july 2005 LHC-D-HCP-0006 Automated procedures for powering the superconducting circuits to nominal current

More Related