| Paper | Title | Page |
|---|---|---|
| MOD002 | TINE Release 4.1: Responding to the User's Needs | 31 |
|
||
| In the period between the shutdown of the HERA collider and the commissioning of the PETRA 3 synchrotron light source the TINE* control system was upgraded and modernized to the next major release level, namely 4.0. Many of the new features and capabilities have been reported before**. As can be expected, when what was 'designed and planned' is actually put to use, various imperfections and deficiencies begin to surface, the natural 'enemy' of the developer being the 'user'. To this end there has been a slow and iterative progression toward TINE Release 4.1 which will be reported on here. Many of the embellishments involve improving data transfer efficiency (such as enforcing the use of multi-channel arrays even when the user makes single channel calls) or meeting the user's expectations of what should be possible (such as allowing variable-length TINE data types to appear within TINE data structures). In addition, TINE Central services have been more systematically integrated into the protocol. | ||
|
Slides | |
| TUP034 | New ACOP Beans and TINE General Purpose Diagnostic Applications | 161 |
|
||
|
One of the strengths of the TINE* control system is the ability to easily make 'simple-client' and 'rich-client' applications. All applications are based on an extensive Java graphics library ACOP**, which provides a vast set of Java Beans for presenting and setting the control system values, such as Slider, Wheelswitch, Button etc. Using any of the standard Rapid Application Development Tools the operators can easily design their own 'simple-client' applications, which are now only a few mouse clicks away. In addition, there are also a large number of 'rich-client', general purpose applications, which offer extensive interactions with the standard TINE systems, such as archiv, alarm, and post-mortem system, as well as scope trace, multi-channel and video analysis, FEC statistics, and general configuration management. Available for many years, these applications have recently been implemented as Java applications using the ACOP beans. They have been iteratively improved and refined after many months of being used by the operators and other users. We offer here a description of these applications as well as the description of the newest ACOP beans available in the ACOP library.
* http://tine.desy.de |
||
| THP034 | TINE Release 4.1: Responding to the User's Needs | 736 |
|
||
|
In the period between the shutdown of the HERA collider and the commissioning of the PETRA 3 synchrotron light source the TINE* control system was upgraded and modernized to the next major release level, namely 4.0. Many of the new features and capabilities have been reported before**. As can be expected, when what was 'designed and planned' is actually put to use, various imperfections and deficiencies begin to surface, the natural 'enemy' of the developer being the 'user'. To this end there has been a slow and iterative progression toward TINE Release 4.1 which will be reported on here. Many of the embellishments involve improving data transfer efficiency (such as enforcing the use of multi-channel arrays even when the user makes single channel calls) or meeting the user's expectations of what should be possible (such as allowing variable-length TINE data types to appear within TINE data structures). In addition, TINE Central services have been more systematically integrated into the protocol.
* http://tine.desy.de |