1 / 17

Conditions Database for Minerva

Conditions Database for Minerva. Jaewon Park University of Rochester. MINER v A/Jupiter group meeting, Nov 07, 2007. Overview. What’s included in CondDb. Alignment Readout Slow/fast control calibration Ex/DetCondExample/v7r7 (sort of old ver.) Example package for LHCb CondDb.

kyran
Download Presentation

Conditions Database for Minerva

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Conditions Database for Minerva Jaewon Park University of Rochester MINERvA/Jupiter group meeting, Nov 07, 2007

  2. Overview • What’s included in CondDb. • Alignment • Readout • Slow/fast control • calibration • Ex/DetCondExample/v7r7 (sort of old ver.) • Example package for LHCb CondDb. • Ex/DetCondExample/v11r2 (recent ver.) • A little bit reorganized structure.

  3. Xml-based Data base • CondDb uses xml files. • Examples are shown next slides • Xml string can be put to actual Db server via COOL package. • What if we need to access Heidi’s hardware Db from Gaudi framework? • It’s possible to convert conventional Db to Xml Db. • Pmt calibration, … • Is it safe to have mutiple Dbs?

  4. Alignment Example XML file <?xml version="1.0" encoding="UTF-8" ?> <!DOCTYPE DDDB SYSTEM “../DTD/structure.dtd”> <!--$Id: alignment.xml,v 1.1 2001/12/17 15:46:30 andreav Exp $ --> <DDDB> <catalog name="Ecal"> <!--Ecal alignment catalog --> <conditionrefhref="#alEcal" /> </catalog> <condition name="alEcal"> <paramVector name="Ecal position" type="double">0. 0. 0.</paramVector> </condition> </DDDB> <?xml version="1.0" encoding="UTF-8" ?> <!DOCTYPE DDDB SYSTEM “../DTD/structure.dtd”> <!--$Id: alignment.xml,v 1.1 2005/08/31 16:02:49 marcocle Exp $ --> <DDDB> <catalog name="Velo"> <conditionrefhref="conddb:/Alignment/Velo/Modules:00#Module00" /> <conditionrefhref="conddb:/Alignment/Velo/Modules:01#Module01" /> <conditionrefhref="conddb:/Alignment/Velo/Modules:02#Module02" /> <conditionrefhref="conddb:/Alignment/Velo/Modules:03#Module03" /> </catalog> </DDDB> Referring to data in real Db

  5. Calibration <?xml version="1.0" encoding="UTF-8" ?> <!DOCTYPE DDDB SYSTEM “../DTD/structure.dtd”> <!--$Id: calibration.xml,v 1.1 2001/12/17 15:46:31 andreav Exp $ --> <DDDB> <catalog name="Ecal"> <!--Ecal calibration catalog --> <conditionrefhref="#caEcal" /> </catalog> <condition name="caEcal"> <param name="ScaleFactor" type="double">1.</param> </condition> </DDDB> Readout <?xml version="1.0" encoding="UTF-8" ?> <!DOCTYPE DDDB SYSTEM “../DTD/structure.dtd”> <!--$Id: readout.xml,v 1.1 2001/12/17 15:46:31 andreav Exp $ --> <DDDB> <catalog name="Ecal"> <!--Ecal readout catalog --> <conditionrefhref="#roEcal" /> </catalog> <condition name="roEcal"> <paramVector name="ChannelMap" type="int">1 2 3 4</paramVector> </condition> </DDDB>

  6. Slowconstrol <?xml version="1.0" encoding="UTF-8" ?> <!DOCTYPE DDDB SYSTEM “../DTD/structure.dtd”> <!--$Id: slowcontrol.xml,v 1.1 2001/12/17 15:46:31 andreav Exp $ --> <DDDB> <catalog name="Ecal"><!--Ecal slow control catalog --> <conditionrefhref="#scEcal" /> </catalog> <condition name="scEcal"> <param name="Temperature" type="double">20.</param> </condition> </DDDB> Fastcontrol <?xml version="1.0" encoding="UTF-8" ?> <!DOCTYPE DDDB SYSTEM “../DTD/structure.dtd”> <!--$Id: fastcontrol.xml,v 1.1 2001/12/17 15:46:31 andreav Exp $ --> <DDDB> <catalog name="Ecal"><!--Ecal fast control catalog --> <conditionrefhref="#fcEcal" /> </catalog> <condition name="fcEcal"> <param name="TFCVoltage" type="double">5.</param> </condition> </DDDB>

  7. Velo/Modules Alignment (v11r2) <?xml version="1.0" encoding="ISO-8859-1" ?> <DDDB> <condition classID="6" name="ModulePU00"> <paramVector name="dPosXYZ" type="double">0 0 0</paramVector> <paramVector name="dRotXYZ" type="double">0 0 0</paramVector> </condition> <condition classID="6" name="ModulePU01"> <paramVector name="dPosXYZ" type="double">0 0 0</paramVector> <paramVector name="dRotXYZ" type="double">0 0 0</paramVector> </condition> <condition classID="6" name="ModulePU02"> <paramVector name="dPosXYZ" type="double">0 0 0</paramVector> <paramVector name="dRotXYZ" type="double">0 0 0</paramVector> </condition> <DDDB>

  8. Running test program • I could run a test program that reads file-based Db and prints out the values. • I couldn’t test example that works with actual Db. • The package includes: • Algorithm that fills xml to Db. • Algorithm that loads xml from Db. • A script that creates Db. • A script that copies xml to Db.

  9. Update Manager Service

  10. What we’ll need • Alignment data • It should be given to reconstruction package(i.e. tracker finder, track fitter) and calibration package. • DAQ Conditions/calibration • It should be given to Sergei’s Readout packages. • Cosmic calibration • Need calibration package that calculate calibration date. • The calibration output will be used to other packages.

  11. Mapper software • Using root • Read Leo’s manual scan data text file in new Framework. • Some of code is imported from old one. • Plan to add a piece that handle binary data from real mapper DAQ. • What’s been done • Basic framework and data class • Data is organized into tree structure, so easy to handle for further complicated analysis • Pedestal curve is fitted and pedestal shift is calculated. • Transverse scan fit is progress.

  12. Lorenzian functions doesn’t fit data. Asymmetric Tail points are higher than curve

More Related