~ 3.8.X early IB's how to add a Geometry payload into the DB (with current tools/information from Salvatore Di Guida and Gianluca Cerminara)

References:

Overview

Examples lead to cfg's as they currently are in the snapshot on lxr. If they do not link, look at the link and search for the files in your release area. OH! AND this is meant for the geometry payloads only so you can look at it but don't take it for granted that it will work for you as easily :).

Start w/ the usual work area, then

cmsenv
addpkg CondTools/Geometry
addpkg CondFormats/GeometryObjects
cvs co CondTools/OracleDBA

The first is needed by me, your package will vary if you're referring to this doc. The second is needed because the blob_preparation.txt (below) could not find the xml files unless they were checked out locally. The third was needed because the file dropBoxOffline_test.sh (see below) expected to find renameFiles.sh in a particular directory. I will check the above is truly needed if I get the permission to try again. I may also try to load them to some local big file on my own... we'll see. At this time the DropBoxOffline provides the means to get the payloads into the database. I use, in particular: CMS_COND_GEOMETRY (see destDB below).

I'm not sure how best to detail what I do. Basically in outline form

  1. First, I write the payloads into a database. It could be one, it could be many.
  2. If it is only one, I then proceed to do this ( for example ).
       wget http://condb.web.cern.ch/condb/DropBoxOffline/dropBoxOffline_test.sh
       /bin/sh dropBoxOffline_test.sh myfile.db metaGeometryExtendedLiMax.txt
  3. If it is a number of payloads, like all DB sim, reco and etc. geometry payloads, then I first (before the above) get each one out of the big file using as follows: Example
       cmscond_export_iov -s sqlite_file:myfile.db -d sqlite_file:GeometryFileExtended.db -D CondFormatsGeometryObjects  -t XMLFILE_Geometry_Extended_TagXX -l sqlite_file:localpopconlog.db
  4. a. And THEN run a series of the second command such as: Example
       /bin/sh dropBoxOffline_test.sh CASTORRECO_Geometry.db metaCASTORRECO.txt
       /bin/sh dropBoxOffline_test.sh CSCRECODIGI_Geometry.db metaCSCRECODIGI.txt
       

Sometimes the easiest thing to do is to follow the next section. "How to do them all" and only upload the one(s) you really need to upload.

By the way, the meta data files look like this: Example

      destDB oracle://cms_orcoff_prep/CMS_COND_GEOMETRY
      tag XMLFILE_Geometry_ExtendedLiMax_38YV0
      inputtag
      since
      Timetype runnumber
      IOVCheck offline
      usertext Geometry validation for 38Y pre1
   

How to do them all.

As of CMSSW version 3.8.0 pre3 + tags... more like pre4 will work right. A-TAG-HERE is something like 38YV3 that gets appended to all the and is inserted into many of the helper files and etc. When you are done with this, do not try to restart in the same directory. [UNTRIED] You can start by copying writehelpers/* back up to the test level..., oh, and deleting *.db and *.txt.

          scram p CMSSW your-release
          cd your-release/src
          cmsenv
          addpkg CondTools/Geometry
          cd CondTools/Geometry/test
          cp writehelpers/* .
          chmod +x xmlgeometrywriter.sh
          ./xmlgeometrywriter.sh A-TAG-HERE
    

At this point you can run one of the upload*.sh scripts or just upload one at a time on your own.

-- MichaelCase - 14-Sep-2010

Edit | Attach | Watch | Print version | History: r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r1 - 2010-09-14 - MichaelCase
 
    • 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