80 likes | 216 Vues
EPICS Integration with Web-based Technologies. Presentation by Madhan Sundaram. Outline. Introduction PHP_EPICS Potentials Examples Demo - Proof of concept Conclusion. Introduction . PEMAJAX – PHP EPICS Mysql Asynchronous Javascripting and XML PHP – Server side scripting language
E N D
EPICS Integration with Web-based Technologies Presentation by Madhan Sundaram
Outline • Introduction • PHP_EPICS • Potentials • Examples • Demo - Proof of concept • Conclusion
Introduction • PEMAJAX – PHP EPICS Mysql Asynchronous Javascripting and XML • PHP – Server side scripting language • PHP – EPICS an Open source module by Alain Bertrand, Renata Krempaska of SLS Computing and Control at PSI, Switzerland. • MySql – Popular open source Database • AJAX – Popular web development technique
PHP EPICS • C Library using channel access calls compiled as an extension to PHP. • Common functions are implemented like Caget, Camonitor, Cainfo etc. • Data types like Double, Int, string are supported. • This extension allows us to get the data, process it and put it on a webpage.
Potentials • Interactive websites reduces the need for programming. • Platform independent. • Easy to develop, maintain and implement. • Acts as temporary cache of data when and where the user needs. • Power users can take advantage of scripting support for languages like perl**, python* etc. • Simple experiments can be set up, reports can be generated and settings can be stored under users ucams account*. • Personalized Channels(0|13|14) helps user to see only the instruments that interests them. • Dynamic report generation** helps users to track multiple instruments behavior over time. • Accelerator Message center* can be implemented * Not yet implemented **Partially implemented
Examples • Dynamic experiment setup • Short term analysis of certain PVs • Conditional statement support** • Individual preferences maintained under user id* • Instant plots • Make your own ch13 component* • Generate periodic reports** • Personalized channels (0|13|14) • Only see what interests you. • Individual preferences maintained under user id* • Asynchronous update of widgets *- not yet implemented **-partially implemented
Conclusion • Proof of concept was demonstrated • Server side scripting would help minimize need for programming • All you need is just a browser • Database can be switched to existing Oracle database. • Power users can be allowed to do Caput and control certain instruments based on the Experimental results.
Process Control • On demand service • Data reuse • Minimize server load • The person who requests the PV becomes the owner • The ownership is changed when the user exists or no longer requests update for PV(s)