130 likes | 301 Views
6.4.2011. WBM development. New templates. 1) Distributions of the currents for LV and HV channels at a given time. 2) Operations hours counter based on the TTC partition majority state 3) Switching counter based on the TTC partition majority state Under development:
E N D
6.4.2011 WBM development
New templates • 1) Distributions of the currents for LV and HV channels at a given time. • 2) Operations hours counter based on the TTC partition majority state • 3) Switching counter based on the TTC partition majority state Under development: • 5) distributions of the different of the LV and HV currents at a given time with respect to a reference time. • 6) operations hours counter for single power supplies • 7)switching counter for single power supplies • 8) graphical representation of the status of the TK interlocks bits
1. DCS_HV_dist.template, DCS_LV_dist.template • Distributions of the currents for LV and HV channels at a given time. • Under development: displaying plots for all partitions from one template
2.DCS_hours_counter.template • Operations hours counter based on the TTC partition majority state • Under development: passing the custom start and end date as a macro parameter
3.DCS_switching_counter.template • Switching counter based on the TTC partition majority state • Under development: displaying always all states and in the same order
Task Management Tool for WBM requests • http://issues.cern.ch/secure/ComponentBoard.jspa?type=VB&selectedProjectId=10790&selectedBoardId=-1&issueDisplay=summary
Documentation • https://twiki.cern.ch/twiki/bin/viewauth/CMS/HowToCreateWBMToolsTemplates • https://twiki.cern.ch/twiki/bin/view/CMS/TrackerWBMServices
Template development av.time • 2 - 8 h: exploring data, composing and tuning the query • 4-12 h: template¯o development and primary functionality debugging • next day: feedback, adjusting requirements • 8-24h: processing feedback, implementing change requests, secondary debugging • Total: 4-7 days
Challenges Unimplemented WBM features • Multiple queries from one template • Passing date as a macro argument • Passing query parameter to the macro • Argument name (seen by user) vs passed value Data incostistency in database • TTC partition names • Aliases (… and select max(since) from…) • Current states (HAPPY, OFF-LOCKED vs OFF_LOCKED, …) Hardly customizable ROOT features • Rebining histograms with names on axis…