50 likes | 190 Views
Planning for the Luminosity Constant Change. Elizabeth Gallas Fermilab Computing Division / D0 Computing and Analysis Group. Luminosity meeting May 18, 2006. Plan for LumDB implementation. DBA’s: export production (d0oflump) import production data to development (d0oflumd)
E N D
Planning for the Luminosity Constant Change Elizabeth Gallas Fermilab Computing Division / D0 Computing and Analysis Group Luminosity meeting May 18, 2006 ElizabethGallas
Plan for LumDB implementation • DBA’s: • export production (d0oflump) • import production data to development (d0oflumd) • Dan Krop will reload DQ data to facilitate ongoing DQ testing • Luminosity/D0 Database Group: • Luminosity measurement stored in 8 columns in 3 tables • Create 8 new columns for new calculation • Populate 8 new columns with new calculated values • Compare old 8 columns to new 8 column values: • lmAccess (I don’t know how easy it is to look at new column names) • Operations Reports (have new sister version using new columns) • ROOT Oracle ? new interface with plotting potential • Kayle, Elizabeth will meet with CD expert later today • GetLums.py • Drop old calculated value columns, Rename new columns ElizabethGallas
Delivered_Lums (DL) and Exposed_Lums (EL) ElizabethGallas
LBN_Triggers (LT) Table ElizabethGallas
The Luminosity Database “Schema” ElizabethGallas