SLAC PEP-II
BABAR
SLAC<->RAL
Babar logo
HEPIC E,S & H Databases PDG HEP preprints
Organization Detector Computing Physics Documentation
Personnel Glossary Sitemap Search Hypernews
Unwrap page!
Comp. Search
Who's who?
Meetings
FAQ Homepage
Archive
Environment
Administration
New User Info.
Web Info/Tools
Monitoring
Training
Tools & Utils
Programming
C++ Standard
SRT, AFS, CVS
QA and QC
Remedy
Histogramming
Operations
PromptReco
Simulation Production
Online SW
Dataflow
Detector Control
Evt Processing
Run Control
Calibration
Databases
Offline
Workbook
Coding Standards
Simulation
Reconstruction
Prompt Reco.
BaBar Grid
Data Distribution
Beta & BetaTools
Kanga & Root
Analysis Tools
RooFit Toolkit
Data Management
Data Quality
Event display
Event Browser
Code releases
Databases
Check this page for HTML 4.01 Transitional compliance with the
W3C Validator
(More checks...)

BABAR Reference and Migration Platforms

5 November 1998
Related pages: [BaBar Home Page] [Computing]

Introduction

Reference and Migration Platforms represent the set of computers used to develop and test code within BABAR. A "reference platform" is a computer architecture that is fully-supported by the BABAR computing organization; code is expected to compile/link/execute perperly. A "migration platform" is one that is unsupported, but is expected to receive full support at some time in the future. A "private platform" is an unsupported platform that may or may not become supported at a future date; essentially no effort is expended by the BABAR computing organization to investigate this class of machines.

This page lists machines available for BABAR use. Some of these machines are owned and operated by the SLAC Computing Services (SCS), while others may be scattered around the collaboration. The SCS portion of the Porting Lab (i.e. most of it) is supported by the High-Performance Computing Group of SCS. It is located at the third floor of SLAC Computer building. The contact person is Randy Melen (randym@slac.stanford.edu), although BABAR users should contact Terry Hung (terryh@slac.stanford.edu) rather than SCS.

It is expected that these machines will typically be used by package coordinators who wish to verify the functioning of their software packages prior to tagging a new release; by the release coordinator to build new releases; by architecture specialists to understand and solve problems associated with a specific platform; and, by users wishing to develop code.


The following list includes the IP name (all are .slac.stanford.edu, unless otherwise noted) for each platform.

Reference Platforms

Migration Platforms (possible/probable future support)

Private Platforms (not supported or maintained by BABAR)



Maintained by Terry Hung and Paul Raines. Send suggestions and additions to
terryh@slac.stanford.edu, or raines@slac.stanford.edu.