1 / 13

Beamline GUIs at ALBA

Beamline GUIs at ALBA. Guifre Cuni on behalf of the Controls Group. Common Controls Components. Networked equipments IPCs, VMs, Workstations, Terminal, Icepaps, EPS, electrometers Vacuum Gauges and IPs controllers, Pneumatic Valves, Tango DSs EPS Tango DSs Archiving Tango DSs

jamese
Download Presentation

Beamline GUIs at ALBA

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. Beamline GUIs at ALBA • Guifre Cuni • on behalf of the Controls Group

  2. Common Controls Components • Networked equipments • IPCs, VMs, Workstations, Terminal, Icepaps, EPS, electrometers • Vacuum • Gauges and IPs controllers, Pneumatic Valves, Tango DSs • EPS • Tango DSs • Archiving • Tango DSs • Alarms • Tango DSs • Device Pool Tango DS • Motors, counters, pseudos, acquisitions • MacroServer Tango DS • Procedures • CCDs • Basler, Tango DS ImgGrabber • Detectors • LIMA Tango DS

  3. Common GUI elements • Taurus (core + Qt) on top of PyTango • Taurusgui with custom ‘perspectives’ and panels • Macro execution GUI and/or CLI • Basic Acquisition definition (for scans) with channels, predefined plots, saved in Nexus • <taurusnews + demo + taurusgui example>

  4. Some Screenshots (I)

  5. Some Screenshots (II)

  6. Some Screenshots (III)

  7. Some Screenshots (IV)

  8. Some Screenshots (V)

  9. Some Screenshots (VI)

  10. Some Screenshots (VII)

  11. Experiment applications • Two beamlines have bought a complete End-Station setup with their own application • Two beamlines have said that current GUIs are enough for their experiments • One beamline is happy with the CLI and the macro framework provided • One beamline has not yet specified the needs • And BL13 – XALOC would like to have ‘all available tools for mx experiments’…

  12. Next steps for XALOC: • Integrate omega, musst card and Pilatus Detector in the control system in order to perform a data collection • Define particular perspectives to mimic each ‘mxCuBE tab’ • Define functional panels that can be arranged depending on the experiment • Integrate CATs in the data collection

  13. Questions arise… • We think that we have to split the hardware objects’ logic in: • Tango + Taurus for status and notifications • Macros for the procedures or operations • What else do we need to start with STAC+EDNA • Is ISPyB widely used outside the ESRF? • Will be mxCuBE migrated to Qt4? • from the last meeting my feeling is that ‘there was no need’

More Related