| |
|
FAQ: How do I load conditions?
Most users don't need to load conditions into their test federations. You only need to do it if you want to write into conditions domain, or you want to work with the same set of conditions for long periods of time. So, consider an alternative to loading conditions: divested domains. This technique gives you access to a conditions snapshot that is used in public analysis federations. You link some foreign federation to your own as conditions and configuration domains, so when your app needs conditions, it will get them from that other federation! And there is no need to keep conditions in you test federation!
Here is the recipe for both loading conditions and linking foreign domains.
Assuming you have the BaBar software release in ReleaseDir, and the test federation created (see How do I create a test federation?).
cd ReleaseDir
srtpath
setbootLoading conditions
If you do need to load conditions into your federation, for example, if you want to test your code writing to conditions, give it this option:
gmake database.load SNAPSHOT_DIR=default
This will take a conditions snapshot from /nfs/objyserv03/objy/databases/snapshots/master/full/current/, where the current is a link to a specific date when the snapshot was taken from opr, usually on Mondays. If you need a specific snapshot, give a dir path to it instead of using the default.
Also, you'll need some additional setup for CDB. Please read the document Dealing with test CDB installations to get neccessary info.
Upgrading conditions
If you have loaded conditions into your own test federation and now want up uprade them to more recent snapshot, use the same command you used to load conditions initially.
gmake database.load SNAPSHOT_DIR=default
This will take a conditions snapshot from /nfs/objyserv03/objy/databases/snapshots/master/full/current/, where the current is a link to a specific date when the snapshot was taken from opr, usually on Mondays. If you need a specific snapshot, give a dir path to it instead of using the default.
Also, you'll need some additional setup for CDB. Please read the document Dealing with test CDB installations to get neccessary info.
Do not use this command and CDB setup, if you use divested conditions domain.
Note that this will also reload global database, but the rest of federation configuration will be retained.
Using divested domains
BdbDomainBootNames con Bootfile
BdbDomainBootNames cfg Bootfilewhere Bootfile is the federation whose conditions you want to use. In the most recommended case, this is the boot file of the public analysis conditions federation:
/nfs/objyboot2/objy/databases/production/boot/physics/V1/ana/conditions/BaBar.BOOT
You are done. Check you divested domains with:
BdbDomainBootNames
It should show what domains are linked to what federations.
BaBar Public Site | SLAC | News | Links | Who's Who | Contact Us
Page Owner: Jacek Becla
Last Update: September 02, 2003