DCOPS DAQ Status

11
James Bellinger, CMS Week June 2007 1 DCOPS DAQ Status DCOPS DAQ Status James N. Bellinger University of Wisconsin at Madison June CMS Week 2007

description

James N. Bellinger University of Wisconsin at Madison June CMS Week 2007. DCOPS DAQ Status. Review. Multiple-fork program runs on a Linux PC Reads selected DCOPS based on configuration in database Reads DCOPS via terminal server Controls lasers using DIM - PowerPoint PPT Presentation

Transcript of DCOPS DAQ Status

Page 1: DCOPS DAQ Status

James Bellinger, CMS Week June 2007 1

DCOPS DAQ StatusDCOPS DAQ StatusDCOPS DAQ StatusDCOPS DAQ Status

James N. BellingerUniversity of Wisconsin at Madison

June CMS Week 2007

Page 2: DCOPS DAQ Status

James Bellinger, CMS Week June 2007 2

ReviewReviewReviewReview

•Multiple-fork program runs on a Linux PC•Reads selected DCOPS based on configuration in database•Reads DCOPS via terminal server•Controls lasers using DIM•Writes fitted data to database on omdb•Writes profiles to database on omdb (will purge periodically)•Provides error information via DIM•Does not include DCOPS calibration info

Page 3: DCOPS DAQ Status

James Bellinger, CMS Week June 2007 3

ProblemsProblemsProblemsProblems

•Intermittent crashes, apparently in the DIM interface•Minus side ambient light levels are so high that the DCOPS are often saturated. Light shields are being designed; not a big problem when disks closed•Commissioning Plus side:➔Secure network →Separate instance of DAQ (hack needed)➔Questions about DIM visibility through firewall●May need revision in table for compatibility

Page 4: DCOPS DAQ Status

James Bellinger, CMS Week June 2007 4

Why are the fits often poor?Why are the fits often poor?

ME-2/SLM1 : Laser at PT4 is on

PT1

Page 5: DCOPS DAQ Status

James Bellinger, CMS Week June 2007 5

Profiles are often poorProfiles are often poor

Laser at this end

Of 40 profiles12 are saturated12 laser misses16 are usable

We have very highambient light levels

Temporary light shields arebeing prepared

Page 6: DCOPS DAQ Status

James Bellinger, CMS Week June 2007 6

Database Read-backDatabase Read-backDatabase Read-backDatabase Read-back

Readback of data seems to work fine under program control, thoughcoordination with analog needs tweaking. This will be fixed quickly.

Readback of the rawprofiles works now.

Page 7: DCOPS DAQ Status

James Bellinger, CMS Week June 2007 7

Other ProgressOther ProgressOther ProgressOther Progress

DCOPS calibration database exists and is populated; indexed by new COCOA names

Single read utility for alignment works

Page 8: DCOPS DAQ Status

James Bellinger, CMS Week June 2007 8

Immediate Plans for DAQImmediate Plans for DAQImmediate Plans for DAQImmediate Plans for DAQ

•Debug DIM interface (?) crash•SL4 for final system and Plus side commissioning•SL3 for Minus side commissioning•Coordinate DCOPS and Analog

Page 9: DCOPS DAQ Status

James Bellinger, CMS Week June 2007 9

DAQ I/O RequirementsDAQ I/O RequirementsDAQ I/O RequirementsDAQ I/O Requirements

Telnet communication withthe terminal servers and DIMcommunication with the DNSnode are essential for theoperation of any DCOPS DAQ.

Designed to use Root/Oracle interface

Maintenance requires SSH access

Compiling and running uses shared libraries currentlyfound in AFS space.

Page 10: DCOPS DAQ Status

James Bellinger, CMS Week June 2007 10

FireWallFireWallFireWallFireWall

Telnet blocked: Not a problem

SSH blocked: Gateway system is planned

Keep local copies of libraries for reliability

DIM: I assume DIM command will pass through the firewall, but need confirmation

Oracle: Need confirmation

Page 11: DCOPS DAQ Status

James Bellinger, CMS Week June 2007 11

Other PlansOther PlansOther PlansOther Plans

•Clean up database•Work out details for using DCOPS calibration and create tool for applying them usefully