1 / 6

PHENIX Online Computing System Development and Configuration Overview

The PHENIX Online Computing System (ONCS) experienced significant advancements in its configuration and data control mechanisms as of August 1999. This included the use of four DCM crates, simultaneous operations with two DCM crates, and enhancements in data handling rates, achieving up to 1 Mbyte/sec. Key upgrades involved an Arcnet server capable of self-managing downloads, improved logging systems, and real-time monitoring. The integration of new hardware and software tools aimed to streamline communication between detector groups while refining user interfaces for greater efficiency in data tracking and diagnostics across the whole system.

laban
Download Presentation

PHENIX Online Computing System Development and Configuration 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. ONCS Year 1 configuration C.Witzig PHENIX DC meeting Aug 12, 99

  2. In ER experimented with... • 4 DCM crates - usually controlled one at a time during data taking, experimented on a regular basis with 2 DCM crates • 2 GTM crates: controlled one or two • 1 GL1 crate • NT-based SEB/ATP • one arcnet server program: ~ dozen FEMs • one event pool/logger on phoncs0 • data rates <= ~ 1 Mby/sec • many standalone/debugging programs

  3. Upgrades of existing software • Arcnet server: • it remembers what has been downloaded when and can determine whether a new download is needed without operator intervention • speed up the corba server part • work on core arcnet code • DCM control: • allow crate/partition wide operation [logical unit is partition module] • DD/Logger/Monitoring: • allow parallel logging based on trigger types • have more than one monitor process • monitoring on other hosts in real time • User interface to run control • Central control of >1 granule (partition server) • Look into HV speed improvements (low priority), finish and use of HV OODBMS

  4. New Hardware/Software • Counting house network/RCF connection: • purposely left out for ER • email on phenix-online-l and phenix-dc-l on Mar 23, 99 • formally adopted in April 99 core week • need to specify hardware first • More computing (PCs/Linux) in 1008 • Adding support for databases • run log • arcnet server • storing configuration information • More online diagnostic tools of all of the online system (ONCS and non-ONCS) • LV remote control (replace Genie with EPICS control)

  5. Online Monitoring • Interface between detector groups and online group • Common setup between offline and online (RCF/1008) • Consistent interface between offline/online (fileEventIterator / ddEventIterator) • Preparations: • One day online monitoring workshop Nov 98 • Presentations in • a) computing meetings Jan (MLP), Feb(MLP), April (CW), May (MLP) • b) run meeting (July/MLP) • Code templates available on • common tool box • oMonitor classes • Manuals in place (ONCS homepage) • Importance of adopting this framework by all subsystems • PHENIX-wide monitoring czar (we have one candidate)

  6. Conclusions The online system took data The two sides of developing/debugging online system/code and helping detector people to using it

More Related