Presentation is loading. Please wait.

Presentation is loading. Please wait.

1 James N. Bellinger University of Wisconsin-Madison 30 January 2008 DCOPS Software Report.

Similar presentations


Presentation on theme: "1 James N. Bellinger University of Wisconsin-Madison 30 January 2008 DCOPS Software Report."— Presentation transcript:

1 1 James N. Bellinger University of Wisconsin-Madison 30 January 2008 DCOPS Software Report

2 2 James N. Bellinger 30-January-2008 Effort Division Main DAQ PVSS controls Supplementary programs Commissioning tests Upgrades requested

3 3 James N. Bellinger 30-January-2008 Main DAQ Milestones Test bug fixes Finish the day after hardware is operational Package code and libraries Requires 1 day for simple package Package accepted by DCS Final shakedown No problems expected

4 4 James N. Bellinger 30-January-2008 PVSS Controls Milestones Package fwDCOPS component: (Learning how) Integrated with CMS’ PVSS hierarchy: (Learning how) Install component on CMS machine: at CERN Successful DCOPS control in situ : at CERN Successful generic control by hierarchy : at CERN Successful readback of data w/ final chain Package accepted by DCS Non-expert successfully operates panel : at CERN

5 5 James N. Bellinger 30-January-2008 PVSS Controls Time Estimates Package fwDCOPS component Integrated with CMS’ PVSS hierarchy 1-3 days to communicate and modify. Both of the above in parallel? Install component on CMS machine Successful DCOPS control in situ Successful generic control by hierarchy Requires someone at CERN to work with me. XiaoFeng? 1 day if no problems. If hardware is working all three of these may be tested in a day. N days if have to iterate. Successful readback of data w/ final chain Day after successful test above Package accepted by DCS No idea. Non-expert successfully operates panel Need a volunteer to attempt to use the system

6 6 James N. Bellinger 30-January-2008 Panel In Use Communicating with fake readout at Wisconsin

7 7 James N. Bellinger 30-January-2008 Supplementary Software Complete and test Single-Line readout 2-3 days

8 8 James N. Bellinger 30-January-2008 Commissioning Tests Read out Transfer Lines Readout: day after hardware is operational Analysis: day? Depends on what we find UPDATE: Hardware is partly operational

9 9 James N. Bellinger 30-January-2008 Commissioning Tests: 1 Transfer Line 1 ME+4 Transfer Line 2 ME+3ME+2ME+1 No data for MABs

10 10 James N. Bellinger 30-January-2008 Commissioning Tests: 2 Transfer Line 3 ME+4 Transfer Line 4 ME+3ME+2ME+1 No data for MABs

11 11 James N. Bellinger 30-January-2008 Commissioning Tests: 3 Transfer Line 5 ME+4 Transfer Line 6 ME+3ME+2ME+1 No data for MABs

12 12 James N. Bellinger 30-January-2008 Upgrades Requested Online display of profiles Modify Main DAQ to support profile thumbnails Creation Buffering (present on demand) Space reserved on panel, needs coding No effort is scheduled for this project Expert control interface Turn off/on readout for unused DCOPS Turn off/on writing profiles to database Requires 1-2 days of documentation if we use DID


Download ppt "1 James N. Bellinger University of Wisconsin-Madison 30 January 2008 DCOPS Software Report."

Similar presentations


Ads by Google