170 likes | 292 Views
TANGO New Diagnostic Tools and Application Updates. Summary. Class release. Jive/Astor - Who do what ? Events testing. Polling profiling. Class release. Problems: Which device server release is running ? Which class(es) version is(are) used ?
E N D
Summary • Class release. • Jive/Astor - Who do what ? • Events testing. • Polling profiling.
Class release • Problems: • Which device server release is running ? • Which class(es) version is(are) used ? • Could I know if this executable file the is expected one ?
Class release • First idea: • Add a“static const char *TagName»in MyServerClass.cpp file containing the CVS tag release. • Append it to the string returned by get_info command on administrative device. • Could be seen with ident command.
Class release • Limits of this solution: • The device server source files must be deleted, re-checked out with rtag option and re-compiled after cvs tagging. • In case of multiple classes, the command: Ident | grep Name returns: $Name: Release_1_0 $ $Name: Release_2_1 $ Which classes ? Which is the first one ?
Class release • Implemented solution: • Pogo generate a Makefile containing the possibility to do “make tag” after increasing release number. • It does: • Cvs tag with class name and release number found in Makefile (i.e. Serial-Release_2_1). • It patch the file with tag name (replacing “rm *; cvs co rtag release_2_1 my_module). • It re-build the device server. • The command “ident | grep Name” returns: $Name: HdbEventHandler-Release_1_0 $ $Name: HdbAccess-Release_2_1 $
Class release • Limits of this solution: • The Makefile must be updated by Pogo. • A script file must be installed in $PATH • The release number must be modified by hand in the Makefile.
Jive/Astor - Who do what ? • Problems: • What is the real borderline ? Device oriented / Server oriented is so clear ? • Today, some features are available in the two tools. • A new Feature must be implemented in Jive, in Astor or in both ?
Jive/Astor - Who do what ? • New idea (to be discussed): • The main function of Jive is database browsing. • Jive is mainly used for multiple selected devices actions. • Astor is mainly used for device server management. • Astor manage devices served by the same device server. • Conclusion: • Many features are implemented in both tools. • Astor and Jive will use the same panels to do be more homogeneous.
Events testing • Tango events are used by: • ATK components • Astor • ESRF hdb writer (hold archiving ESRF system interfaced with Tango). • Eletra, Soleil….? • How to check the event behaviour ? • A generic event tester tool.
Events testing From Astor device browser