Operational Aspects of Dealing with the Large BaBar Data Set

Trunov, Artem G

doi:10.2172/813245

Cited by 1 publication

(1 citation statement)

References 4 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The fully reconstructed physical quantities are written into an object database (Objectivity/DB [1]). The processed data is then transfered to a separate database where users can access it [2].…”

Section: Data Processing Overviewmentioning

confidence: 99%

Distributed Offline Data Reconstruction in BaBar

Pulliam¹,

Elmer²,

Dorigo³

2003

View full text Add to dashboard Cite

For the BABAR Computing GroupThe BABAR experiment at SLAC is in its fourth year of running. The data processing system has been continuously evolving to meet the challenges of higher luminosity running and the increasing bulk of data to re-process each year. To meet these goals a two-pass processing architecture has been adopted, where 'rolling calibrations' are quickly calculated on a small fraction of the events in the first pass and the bulk data reconstruction done in the second. This allows for quick detector feedback in the first pass and allows for the parallelization of the second pass over two or more separate farms. This two-pass system allows also for distribution of processing farms off-site. The first such site has been setup at INFN Padova. The challenges met here were many. The software was ported to a full Linux-based, commodity hardware system. The raw dataset, 90 T B, was imported from SLAC utilizing a 155 M bps network link. A system for quality control and export of the processed data back to SLAC was developed. Between SLAC and Padova we are currently running three pass-one farms, with 32 CPUs each, and nine pass-two farms with 64 to 80 CPUs each. The pass-two farms can process between 2 and 4 million events per day. Details about the implementation and performance of the system will be presented.

show abstract

Section: Data Processing Overviewmentioning

confidence: 99%