1. STAR Conditions Database What is it? Tools Conditions DB API Beyond Conditions Technical Issues Activities of General Interest R. Jeff Porter 1/31/98 STAR Collaboration Meeting

2. What Is It? Two definitions - at least that I use Informal: Database for storing the experimental conditions that existed during data taking. Formal: A specific (STAR-BaBar-Objectivity) database API used to store and access conditions data.

3. What Is It? (continued) The informal (task) definition sets criteria that the formal (technical) definition needs to meet. Database Access Data valid over many events Data access by time-stamp query Update Frequency pre-determined updates (e.g. ~hourly system wide snap-shots) alarm activated updates (of individual data-objects) Data Volume moderate per update (~Mbyte) moderately large in aggregate (~Gbytes)

4. Tools Objectivity/DB –Commercial Object Oriented DateBase w/ C++ API BaBar Objectivity Software –“production” quality Objectivity Database Design & Implementation BaBar Conditions DB API –Specific Objectivity implementation for conditions data STAR Conditions DB API –STAR specific implementation of BaBar Conditions DB (e.g. tpc, svt, emc, …)

5. Tools (continued) BaBar Packages STAR Extensions BaBar/ BdbAccess/ BdbApplication/ BdbClustering/ StBdbInterface/ BdbCond/ StOdbCond/ >> ConditionsDB BdbEvent/ StOdbEvent/ BdbEventStore/ BdbTools/ BdbUtil/ StUtil/

6. BaBar Conditions DB API DB-Set per SubSystem (tpc, svt, emc, … ) –One Index DB (file) + Many Conditions Data DBs (files) Index DB –time-Interval object for each data grouping (“Group-Obj”) instance –Index (+ Versioning) on the time-Interval objects –Separate Index for each “Group-Obj” Conditions Data DBs –Mix of “Group-Obj”s per Database (file)

7. BaBar Conditions DB API Data Access –BdbDatabase->store( ObjH, indexContainer, beginTime, [endTime],...) –BdbDatabase->fetch( ObjH, indexContainer, theTime,...)

8. Beyond Conditions While the (Formal) Conditions DB solves a specific Database task, it is applicable to many other “time-indexed” Database types needed by STAR. Conditions DB(measured values) Configuration DB(set values) Calibration/Geometry DB There will be additional access routes (e.g. via “Keyed” or “named” reference) but the base support of the time-stamp access will be via the Conditions DB API.

9. Technical Issues All Objectivity database access is by Federation –tightly couples Online & Offline development –single point vulnerability Lockserver & BOOT file & Federation file Limit vulnerability – Use Objectivity Autonomous Partitions for Offline & Online – Separate Online & Offline Federations with Data-Replication Platform Dependencies – Objectivity: Solaris, Win-95/NT, Linux, HP-UX, AIX, IRIX, DEC-Unix – BaBar-Objectivity: Solaris, HP-UX, AIX, DEC-Unix – STAR Online: Solaris, Windows-NT – STAR Offline: Solaris, Linux

10. Activities of General Interest Calibration & Database Issues –Tomorrow’s presentations –Bi-weekly Calibration Meetings (starcalib-l@bnl.gov) Needed Tutorials for DataBase Users –Access to DB data with Offline Infrastructure –Access to DB data with Online Infrastructure –Database Developers Workshop