1 / 16

PHENIX VTX DB Overview

PHENIX VTX DB Overview. Peter Steinberg Rachid Nouicer, Burt Holzman Brookhaven National Laboratory December 9, 2004. PHOBOS Experience. PHOBOS chose a single DB scheme early on Used it comprehensively for a variety of information Si testing C-V curves etc. Module assembly

magdaf
Download Presentation

PHENIX VTX DB Overview

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. PHENIX VTX DBOverview Peter Steinberg Rachid Nouicer, Burt Holzman Brookhaven National Laboratory December 9, 2004

  2. PHOBOS Experience • PHOBOS chose a single DB scheme early on • Used it comprehensively for a variety of information • Si testing • C-V curves etc. • Module assembly • Calibrations, quality, etc. • Detector operation • Pedestals, Gains, etc. • Same DB also used for other subsystems, slow controls, RHIC data, etc.

  3. “Golden Rules” (Bolek Wyslouch) • One central DB • Avoid distributing among institutions • DB must be robust • Commercial products have professional support, are optimized (so faster), etc. • Log all actions, even failures • Must be part of internal Table design • Data visualization must be available ASAP • All first attempts at data entry usually fail – check everything by eye! • Do not reuse another DB implementation • Leverage experience, not actual DB code • DB and web interface should be separated • Each should be replaceable independent of other

  4. PHOBOS Si Testing Roadmap MIT/BNL: Bolek Wyslouch UIC: Rachid NouicerBurt HolzmanMike Reuter MIT:Gerrit van Nieuwenhuizen Kris Gulbrandsen Carla ValePatrick Decowski UIC Si Testing ORACLEServer MIT Si Testing ANL (module testing):Birger BackAlan Wuosmaa Online: PHOBOS CH Offline: RCF, all institutions,etc.

  5. Server History • Silicon Testing and Assembly • 1997 Purchased Windows NT server Pentium Pro 200 MHz, installed Oracle 7.3 (~2 Gbyte) • Main Experimental Database (~ 30 Gbyte) • 1997 Windows NT server, 500 MHz, 18 Gbyte disk (decommissioned) (Oracle 8.0.5) • 2001 Windows NT server 600 MHz, 36 Gbyte + 300 Gbyte RAID (Oracle 8.0.5) • 2003 DELL PowerEdge 2650, Dual 2.8 GHz, Linux, RAID (Oracle 9.2.0.4.0)

  6. PHOBOS Implementation • Oracle chosen in 1996 and used today • Upgraded occasionally • DB Machine upgraded consistently • 200 MHz NT  Dual 2.8 GHz Linux • DB size moderate • 10’s of GB – similar to PHENIX DB • No mirroring • Was tried early on and abandoned • Problems solved by faster networks

  7. Immediate Feedback Test data goes in from Labview Should come out immediately on web

  8. PHOBOS “Portal” Keep everything on one main page (avoid nested links) Done with MS FrontPage (ASP) & Oracle

  9. Scope for PHENIX • VTX project will have several stages • Wafer testing • BNL, SUNYSB, UNM, RIKEN • Assembly & Integration • BNL • Operations • PHENIX • All information gathered at each stage must be persistent and accessible to next stage

  10. Configuration for Wafer Testing RIKEN/BNL UNM RIKEN/JAPAN SUNYSB PHENIX VTX DB Detectorhistory,inventory,properties Sensor inventory,historyproperties Modulehistory,inventory,properties Ladderhistory,inventory,properties

  11. PHENIX VTX DB • PHENIX Experience points to using POSTGRES • No particular reason to use FrontPage/ASP, etc. • Can move to Apache/PHP • Common decision these days • The only tricky issues involve • Configuration • Person-power

  12. Data Types • All modern SQL DB’s support many types of data • At testing phase, emphasis placed on raw sensor values (CV IV curves etc.) • During operations, emphasis should be on the system • Easier to work with objects, arranged geometrically • PHOBOS uses ROOT objects in BLOBS

  13. Proposal for DB Testbed • Main PVD machine • Similar to current PHOBOS setup • DELL Poweredge rack system • Dual CPU, O(100GB local disk) • ~1TB RAID Array (400-1000GB disk) • POSTGRES DB • Apache webserver running PHP (ASP?) • Secondary machine • Backup & mirror • Study failover techniques • Each machine ~$5000, so requesting $12k • Of course can start with one machine • Can also scavenge RCF castoffs • BUT: this machine may well be the production machine – early investment may pay off

  14. Manpower • We have identified several sources • BNL Chemistry • Rachid – expert silicon user • Burt & Peter – past & present PHOBOS computing czars, silicon demi-experts • Bolek will consult on design choices • “Mainstream” PHENIX • Irina – PHENIX DB czar • Dave – PHENIX computing czar • Abhay – can offer student labor

  15. Reasonable Short-Term plan • Provide repository for wafer testing thorughout VTX collaboration • Problem reduces to a few tables • While fully-loaded testbed machine would be ideal, not in principle necessary • Provisional DB could be migrated from a less powerful machine (e.g. RCF salvage) • People: Irina, Rachid, Peter, Burt

  16. Medium-Term plan • Start working towards DB which will be used for VTX integration • Full set of testing data • Hybrid information • Module information • Detector information • Time-dependent information (e.g. slow monitoring) • Will require broader input from various parties • Existing PHOBOS setup can serve as useful template

More Related