There are several new classes to implement stop-less recovery and better automatic disabling if interconnected components in area of front-end description. There are the following new classes:
More information for this change and it's purposes is available from the proposal document and related TWiki detectors discussion page:
In release 1.7 there were two co-existing sets of names for applications (control and data-collection), which were different in case of template applications. Since such names were used for error reporting, various messages and publishing of information, this situation was confusing. In the new release 1.8 there is only one set of such names in accordance with the following rules:
Comparing with previous release the names of template applications become shorter by removing class-name and domain name from host ID.
The complete list of applications and their names can be obtained using dal_dump_app_config utility, e.g.:
dal_dump_app_config -d oksconfig:daq/partitions/be_test.data.xml -p be_test
In the release 1.7 the NodeID was calculated using the following rules:
By requests of the users in the release 1.8 the NodeID is calculated only using DAL algorithms for both normal and template applications. The applications may have arbitrary meaningful object IDs, e.g.: "LARG-BARREL-C-1" instead of "ROS-23".
Functions wfrom release 1.7 daq::Application::string2id() and id2string() functions are replaced by the following ones:
The Run Control sends two command line options to all applications:
Such information is also available for applications using Application Control framework (ac package).
The “Name” attribute has been removed in most database classes and the object ID has to be used instead. In many cases (except Variable and SW_Object classes) their coexistence was confusing and in some cases even required they have to be equal.