1 / 11

DCOPS DAQ Status

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

ide
Download Presentation

DCOPS DAQ Status

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  2. 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 • 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

  3. Problems • 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

  4. Why are the fits often poor? PT1 ME-2/SLM1 : Laser at PT4 is on

  5. Profiles are often poor Of 40 profiles 12 are saturated 12 laser misses 16 are usable We have very high ambient light levels Temporary light shields are being prepared Laser at this end

  6. Database Read-back Readback of data seems to work fine under program control, though coordination with analog needs tweaking. This will be fixed quickly. Readback of the raw profiles works now.

  7. Other Progress DCOPS calibration database exists and is populated; indexed by new COCOA names Single read utility for alignment works

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

  9. DAQ I/O Requirements Telnet communication with the terminal servers and DIM communication with the DNS node are essential for the operation of any DCOPS DAQ. Designed to use Root/Oracle interface Maintenance requires SSH access Compiling and running uses shared libraries currently found in AFS space.

  10. FireWall 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

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

More Related