Introduction
The complete documentation for the DAQ -
DCS Communication package may be found at CERN/EDMS as https://edms.cern.ch/document/684955/5.5
Improvements/Fixes of ddc-05-08-02 (Feb
2014)
All should be transparent for the users
- Release for 64 bits SLC6
platform is in place now
- DIM library is based on DIM
version 20.07 currently used also in DCS
Improvements/Fixes of ddc-05-08-03 –
ddc-05-08-08 (Mar – May 2014)
All should be transparent for the users
DDC Command Transfer
- Fixed bug in execution of a
transition command without parameters
- User-defined IS data types for
NT-commands (introduced in ddcInfo package) are used; As a result,
suppressed DdcData.hxx and RuntimeRequest.hxx
DDC Data Transfer
- Publishing in IS message “Data
unavailable” instead of unavailable data (and, therefore, possible change
of data type) is cancelled. This concerns, in particular, StableBeamsFlag
publication, where changing data type is problematic for some TDAQ applications.
- Fixed bug in skipping a record
filed of types int64/uint64
Improvements/Fixes of ddc-05-09-01 –
ddc-05-09-03 (July 2014)
All should be transparent for the users.
DDC
Data Transfer
- Fixed bug in transfer to DCS a
record, where a field (not the first one) of the type array of strings
does not contain any member (the previous string field has been published)
- Introduced mechanism of
transfer to DCS of (u)int64_t data type. As soon as these types cannot be
accepted explicitly by PVSS/WCCOA, they are being published in DIM as an
array of uint. Every (u)int64-T is being represented by two 32-bits uint
variables, where the first represents the least significant 32 bits, the
second – most significant bits. It is for the WCC OA project developer to
treat that representation
The ddc-05-09-02
version differs from ddc-05-09-01 with presence of these release notes, in
ddc-05-09-03 requirements for ddc_recpublisher are corrected.
Improvements/Fixes of ddc-05-09-03 –
ddc-05-11-02 (June 2015)
DDC
Data Transfer
- Fixed bug of high verbosity
causing quick filling log files while DAQ -> DCS data transfer with
high rates
- Fixed issue of re-publishing
DAQ data in DIM within the callback of IS data change that could cause the
application crash. Now the callback only puts the request of updating a
TDAQ data in DIM into a queue, which is handled by application in its own
thread out of callback.
Two fixes above are transparent for the users. The third one
extends the set of data object names allowed for using in DDC-DT configuration
- Introduced the facility of
using the symbol ‘:’ (colon) within the DdcDataTargetList’s object name -
this is often used in TDAQ DF publications. As the colon symbol is used in
the DDC-DT configuration as a separator between the name of a data
structure and its fields, for using it within the data object name one
should precede it by the ‘\’ (back-slash) symbol.
Examples of data objects:
1.
MyStructure:,,
f1,f2,, f3 – to take the third, fourth and sixth fields of the data
structure MyStructure with the DIM publication
names MyStructure.f1, MyStructure.f2 and
MyStructure.f3.
2.
MyData\:SectionOne\:dd
– to use the IS publication MyData:SectionOne:dd and republish it in DIM with this name.