The activities in the tracker DQM group can be subdivided in terms of  "source" and "client" specific tasks. The "source" defines and fills the Monitoring Elements and the "client" accesses them for visualisation and further analysis (creation of summary, comparison with reference etc).

Sources :

the sources are responsible to produce monitoring elements at different levels of reconstruction and are supposed to run on Filter Unit nodes during online operation and can be used for offline as well. They are EDAnalyser modules and separate modules are deployed for each type of  Monitoring Element (MEs) which includes  Digi, Cluster, Tracks etc.

• SiStrip : the sources for individual tasks already exist. We need to refine and maintain them and add more MEs according to the need following MTCC, Sector Tests.

        [Medium priority : well covered by S. Gennai, D. Kcira and I Goitom]

• SiPixel : Monitoring source for Digis ready. Develop monitoring source for Clusters.

       [Medium priority : V. Chiochia ]

• Higher level DQM sources to monitor alignment, primary vertex position, V0, Z0 reconstruction

       [Low priority : no one ]

• Physics DQM sources to monitor b and tau tagging

       [Low priority : no one ]

• Monitoring elements can be organised in logical folders in terms of geometry, control/readout  electronics structure during booking. The organisation following the power groups is still to be done.

Clients:

• the client is based on the BaseClient provided by the DQM framework. The SiStrip and SiPixel DQM clients exist. It needs continuous developments to to cover various aspects of it which are discussed below.

          [Medium priority : S. Dutta (SiStrip), V. Chiochia and P. Merkel (SiPixel)]

• Creation of summary ME from detector level MEs : Adopt framework already used in the Commissionig sw for summary histograms

[High priority : S. Dutta (SiStrip), P. Merkel (SiPixel)]

• Comparison of MEs with reference ones and visualisation of results :  the tool is provided by the DQM framework. The implementation exists for both SiStrip and SiPixel systems and needs continuous development   The comparison is performed automatically once defined in the configuration time. The display of the resulting flags should be further refined.

[Medium priority : S. Dutta (SiStrip), V. Chiochia and P. Merkel (SiPixel)]

•   Refine the Web Interface of the Client for better access/plotting  of MEs

[Medium priority : S. Dutta (SiStrip), SiPixel will follow the developments]

•   Visualisation of MEs using the TrackerMap facility using Web Browser and actual Graphical User Interface utilising Qt. Being developed in a general way so that both SiStrip and SiPixel can use it
• The TrackerMap in terms of FED connections is almost ready (to be integrated to the client) we need the one for FEC connections as well

[Medium priority : G. Zito and M. Mennea]  

• A historical client is being developed for the SiStrip system which would allow viewing of historical information like average data over a few weeks/months etc. Storage of information to Data Base

[Medium priority : D. Kcrira ]

• Adopt the client to access slow control information

[Medium priority : People from US-CMS have shown interest]

• Define run quality flags based on output of DQM.
• Development of a tool to switch between different views (geometrical <-> Control <-> Readout) to be used in the Client

[High priority : S. Khalatian, E. Shabalina]

• Development of an offline Web Interface to access monitoring information (MEs and Alarms) stored in root file for different runs. The interface should be as similar as possible to that of the online one

[High  priority : S. Dutta ]

Standalone DQM application :

DQM application can run in the offline mode as well where events are accessed from file and MEs created/filled are saved at the end in  root file. We do not need to run the full chain of  Source-Collector-Client framework. The standalone application basically merges the source and client actions in the same code.

[ Work Done ! Need maintenance : S. Khalatian, E. Shabalina]