A   B   C   D   F   G   H   I   J   K   L   M   N   O   P   Q   R   S   T   U   V   W   Y   Z  

Hardy, L.

Paper Title Page
TUX03 Evolution and Status of the e-Logbooks at the ESRF 49
 
  • L. Hardy, J. M.C. Chaize, O. Goudard
    ESRF, Grenoble
  • S. D. Cross, D. R. Fraser, N. V. Hurley
    St James Software, Cape Town
 
  In 2004 the ESRF moved to electronic logbooks. Such logbooks should be configurable enough to be used in several situations: document management, exchange of technical information and, in the Control Room, as a powerful tool for storing and retrieving information at a glance. The St James software company developed such a product which met our constraints and which is easy to configure. Moreover, this product can be tailored and evolved with time by its users and allows automatic access to control system parameters. After gaining experience with several logbooks using the old version 4 system, a new more user-friendly version which offers extensive customisation possibilities has been launched. This new version, J5, has already been interfaced to the ESRF control system (Tango) through a Python binding. This allows automatic triggering of records on specific events and the generation of automatic reports from the history database system. J5 can use an LDAP server for security management.  
slides icon Slides  
TUX04 j5 Logbook - A Commercial e-logbook 52
 
  • D. G. Moore
    St James Software, Cape Town
  • O. Goudard, L. Hardy
    ESRF, Grenoble
 
  j5's EventStream module provides an interface for exchanging data with services such as Tango and OPC. j5 models this data as a series of events. Each combines information on the source of the data, its reliability, when it was generated and whether it represents an alarm condition, with the actual data from the external device. Adding a new type of data source requires only the implementing of the very modest data device API. For Tango, the implementation built on PyTango while for OPC Windows COM was used. Data devices support both pulling values and subscription to event channels. Once in j5, events may flow through event pipes, being transformed and triggering actions such as the addition of logbook entries. In other cases, j5 may pull events from the data server, e.g. to populate data fields automatically when new log entries are created. A key feature enabled by EventStream is the ability to attach graphs of 1D and 2D arrays directly to logbook entries as they are added. This combines the event processing capabilities of j5 with its document attachment and thumbnail generation to make the information present in such arrays immediately available to logbook users.  
slides icon Slides