How to freeze cond16boot

Cond16boot was created as a mirror of the MASTER which means that all the constants that were loaded to the MASTER will also be seen in cond16boot. However, new constants for the 18-series are loaded to the MASTER and must not be used an analysis based on a 16-series release. Therefore, con16boot has been modified (or frozen) by changing its identity. It's local-name has been changed from master-core to analysis16-core.

The local-name of a federation is the value of FDB_LOCAL_NAME used at the time a federation was created. This name is stored in a special data structure inside the federation. It is used by CDB to identify it self. The view on the conditions provided by a federation depends on its local-name. This feature has been used to freeze cond16boot. The local-name can be changed after a federation has been created, and therefore there are two possibilities to freeze cond16boot, either create a new one with the correct local-name or change the local-name of an existing fdb.

Will cond16boot be updated in the future? Yes, cond16boot has to be updated as it will be used for Run5 data (until summer 2005). Because cond16boot is not a mirror of the MASTER anymore, new constants have to be made visible by updating the view. Is it safe to update cond16boot? Yes, as long as the federation has been frozen as described in this document. The update will be very simple. All that has to be done is to load a new official CDB snapshot even if this snapshot contains new constants that must not be used in cond16boot.

1. Reinstall a new federation from scratch.
2. Modify an existing cond16boot federation.

Reinstall a new federation from scratch

1. Prepare a .bbobjy file with the following line (in addition to whatever other parameters you put into):

   FDB_LOCAL_NAME=analysis16-core

2. Make sure that your local installation of the BABAR software has the most recent version (dated by March 25, 2005) of the following file:

   $BFROOT/Bdb/Production/global/export/global.bdb

   If not then make a copy of this file from the same location at SLAC. BTW, at SLAC BFROOT translates into:

   /afs/slac.stanford.edu/g/babar/

   
   
3. Proceed with the normal database creation and initialization procedure, namely:

     % gmake database.import
     % gmake database.load SNAPSHOT_DIR=<most_recent_snapshot_dir>
     

   A full snapshot is found at:

   /nfs/objyserv03/objy/databases/snapshots/master/full/current

4. Verify the quality of the installation by running the following test, which must produce exactly the same result as shown below (if you get a more recent snapshot the view might have changed.) :

     % CdbBrowser views | grep DEFAULT
     NAME="ANALYSIS16::Run5_Start"  ID=264::1  STATUS=FROZEN,DEFAULT
     (keep in mind that cond16boot will still be updated so the name
      shown here might be out of date.) 
     

Modify an existing cond16boot

1. Make sure nobody is accessing the federation.
   

2. Refresh a database installation from the most recent snapshot of the MASTER.

   Note, that at this point your CDB will turn into COND18BOOT like CDB, unless you complete two remaining steps explained below.

   The latest CDB snapshot is found in the usual place (also available in slacBabar SRB):

   /nfs/objyserv03/objy/databases/snapshot2/master/analysis/current

3. Update the "global.bdb" (by substituting the file image with its more recent version) of your CDB federation from the following source at SLAC:

   /afs/slac.stanford.edu/g/babar/Bdb/Production/global/export/global.bdb

   You can check that the right dbid's are allocated running:

       % allocateDbId
       .......
       Allocation for "analysis16-core" is [5384, 5399].
       .......
     

   You have to see the line about analysis16-core.
   
4. Turn your CDB from being a cond18boot back into cond16boot by:

   % BdbSetupLocalDb "analysis16-core"

   to test if the local name was changed run:

     % manageDbId -e
     Using the "evs" domain.
   
     Federation Local Name is: analysis16-core
     Total number DbIds allocated: 16
     Number of DbIds used: 0
     Percentage of DbIds used: 0%
     

5. Verify the quality of the installation by running the following test, which must produce exactly the same result as shown below:

     % CdbBrowser views | grep DEFAULT
     NAME="ANALYSIS16::Run5_Start"  ID=264::1  STATUS=FROZEN,DEFAULT
     (keep in mind that cond16boot will still be updated so the name
      shown here might be out of date.)