Import Conditions and Configuration Datasets

This page describes the required steps to import Conditions Database (CDB) or Configuration Database (CfgDB) snapshots implemented in ROOT. The basic steps involved are:

1. Pick the proper dataset and tag in the bookkeeping.
2. Transfer the dataset files to the local site and make it accessible to clients (e.g.: nfs, Xrootd)..
3. Update the naming rules files in order to point to the new snapshot.

Requirements

The following prerequisites are required in order for the import to succeed:

1. $BFROOT is defined

The $BFROOT env variable has to be defined because the rules files are created below this directory. There is an options to specify this directory on the command line. The directory has to be writable by the user id that does the import.

2. Initial setup of rules files must exist

The rule files consists of generic files and snapshot/dataset specific files. the specific files are update by the import. To create the generic files use the command KanInitRulesFiles.

3. KanAccess.cfg has to be configured to access CDB and CfgDB files

See the KanAccess.cfg description how to update this file.

4. BbkImport

BbkImport is used for the transfer of the files. The package

BbkDataDist     tja060727a     (or later) is required.
SkimTools     (they default one that comes with a the 20 series release)

are needed for BbkImport to work with the the CDB and CfgDB collections.

Import

The command KanImportCdbCfgDB is used to do the import. It is located in the packages KanNonEventUtils.

KanImportCdbCfgDB -t cond22boot -p /scratch/imp

This would imported the latest tagged full cond22boot snapshot. The file are put into /scratch/imp (e.g.: /scratch/imp/store/cdb/cond22boot/full/....). The rules file for a betamini snapshot are updated (in $BFROOT/kanga/config/cdb).

Check the tools page for tools to check a snapshot.

KanImportCdbCfgDB -t cfg -p /scratch/imp