This code is based on IOVDbTestAlg.

I have written an AlgTool which writes an entry to the Database for a module, with examples of how to enter information at a per module, per chip or defects at a per strip level. The exact structure of the SCT Monitoring table from the forthcoming Online SCT Monitoring is currently being designed by LucaFiorini At the present i am using COOL for the Cosmic run, but this will be updated to CORAL.

I envisage two seperate AlgTools, one for reading/writing for the SCT and one for the TRT. I will concentrate on an AlgTool for the SCT, but whenever the TRT table is designed it should be trivial to convert my code.

To Do List

  • Name for AlgTool
  • Location for AlgTool: SCT_Monitoring or SCT_Conditions ??
  • Structure of SCT Table
  • Functions to read data
  • SCT Offline Identifier

Current SCTMonitorConditionsTool

The tool currently located in ~hhayward/public/11.0.4/AtlasTest/DatabaseTest/IOVDbTestAlg/offline-11-00-41/src/SCTMonitorConditionsTool.cxx An example algorithm using this tool is in the same directory called SCTConditionsTest.cxx

The jobOptions file to write to the database, using SCTConditionsTest is located in share/UseToolWrite.py

At present i am writing a table of structure:

  • attrList0["SampleSize"].setValue((int)samplesize); (the size of the data sample used for the monitoring.... more useful for offline perhaps
  • attrList0["barrel_endcap"].setValue((int)barrel_ec);
  • attrList0["Layer"].setValue((int)layer);
  • attrList0["Phi"].setValue((int)phi);
  • attrList0["Eta"].setValue((int)eta);
  • attrList0["ChipData"].setValue((std::string)chiplist);
  • attrList0["DefectList"].setValue((std::string)defectList);

each row of the table corresponds to an integer coded from the module barrel/layer/eta/phi data. Currently i am using my own identifier, but i will change this to the same offline identifier as Bilge, as soon as a standard identifier has been agreed on.

The columns ChipData and DefectList contain strings which encode arrays. In SCTMonitoringTest, i am filling ChipData with the efficiency per chip, but his can be trivially changed. The DefectList contains an array of the same format as that which is online. It is of format: std::string defectType, int defectBeginChannel, int defectEndChannel, bool hasDefectParameter, double defectParameter. SCTMonitorConditionsTool contains functions to create these strings and to add to them.

Reading Data from Database.

Only basic functionality exists at the moment, But more functions will be added soon.

-- HelenHayward - 22 Mar 2006

-- HelenHayward - 10 Apr 2006

Edit | Attach | Watch | Print version | History: r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r1 - 2006-04-10 - HelenHayward
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Main All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback