Simple recipe for filling conditions objects into the DB

under construction

WARNING:

1. never attempt to fill the Hcal offline databases without authorization by the Hcal DPG convenors (see HcalDPG).
2. to successfully perform the filling, you need an authentication file whiMain.ch is not public.
3. after successful populating the DB, contact the HCAL offline database responsible with the payload you just filled and the list_DBwriteXXX file you generated in the attachment

For putting conditions into ORCON or ORCOFF, use the following tags:

• for CMSSW_1_7_x (GREN, GRuMM), use cvs co -r forCMSSW175_v4 CondTools/Hcal (note: there is no working 18X version of PopCon applications).
• for CMSSW_2_0_x, use
• for CMSSW_2_1_x and newer, use the release of CondTools/Hcal

Usually the list_DBwriteXXX-files, mentioned below, have to be checked out separately from the cvs-head, to obtain the latest version. Then:

cd CondTools/Hcal/tools
scramv1 b

The easiest is to copy the fake-files you received also in this directory. Open "list_DBwriteOrcon180.txt" e.g. with emacs. Edit it in the following way: Add on top (after the first big comment block) what you want to do in the following format: database, object (Pedestals or PedestalWidths), the text-file, the tag that it should have in the DB, the keyword indicating whether you want to use "since" or "till" (usually since) and the run number from whiMain.ch the IOV should go. I think/hope it's pretty self-explanatory, just look at what's there already. It might be wise to test first with "sqlite" (I am always doing this, to check that the fake-txt file can be read correctly). In this case, instead of "orcon", you have to write "sqlite" at the beginning of the line.

Next, do: eval `scramv1 r -csh`

Don't forget to copy the authentication.xml into the directory.

To run, type on the command line: ./DBwriteObject.sh list_DBwriteOrcon180.txt

to check, you can use: cmscond_list_iov -c frontier://cmsfrontier.cern.ch:80Main.00/FrontierOn/CMS_COND_ON_18X_HCAL -a (in case of sqlite: cmscond_list_iov -c sqlite_file:DB.db -a) (see also https://twiki.cern.ch/twiki/bin/view/CMS/Main.HowToCheckOfflineDB )

Pedestals into orcon for Global Runs (180-account)

In any case, before trying to fill something into the DB, in case these are pedestals/widths, please make sure that you have received so-called "merged" data (a txt-file) from Mayda/Steve Won. Steve knows what this means and he can produce those and he will be able to answer this question without problems. The reason is: the merging has to be done because eaMain.ch pedestal job yields pedestals only for the cells that were hit during this run. To obtain pedestals for all cells, the resulting file is merged with the previous pedestals, i.e. from the old pedestals file the cells that are in the new file are replaced, the rest stays. Otherwise one would get an inconsistent set of conditions.

Anything that goes into ORCOFF for 2_0_X release

Basically, it's the same as above, just that you have to use the software version for 2_0_X: e.g. in CMSSW_2_0_0_pre6: cvs co -r VMain.02-Main.00-Main.03 CondTools/Hcal

The file you have to edit for orcoff in 2Main.00 is: list_DBwriteOrcoff20x.txt Don't forget to copy the authentication.xml in the directory. To run, type on the command line: ./DBwriteObject.sh list_DBwriteOrcoff20x.txt

-- RadekOfierzynski - Main.08 Apr 20Main.08