The enviornment needs to be setup for the recent Gauss version which evolves over time.
The following recipes are examples of what was used in April,8 2013:
- For the first time when you don't have a private copy of Gauss yet
LbLogin -c x86_64-slc5-gcc43-opt
SetupProject Gauss v44r3 --build-env
(The --build-env is needed only for the first time when you do not yet have)
getpack Sim/Gauss v44r3
cd Sim/Gauss_v44r3/Sim/Gauss/cmt
cmt br make
- To run Gauss the following times:
LbLogin -c x86_64-slc5-gcc43-opt
SetupProject Gauss v44r3
3: To run from the Upgrade database in the dev area,
Avoid to have a local copy of Det/SQLDDDB in your area.
SetupProject Gauss v46r4 --dev --force
setenv SQLITEDBPATH /afs/cern.ch/lhcb/software/DEV/DBASE/Det/SQLDDDB/db
When the running the program use the various
CondDB options as appropriate.
4: Using your local version of the
DataBase
Extract the database using the instrctions from the
CondDB twiki page.
https://twiki.cern.ch/twiki/bin/view/LHCb/CondDBHowTo#Generate_XML_Files_from_the_Cont
Use the tags as indicated in this twiki page under
https://twiki.cern.ch/twiki/bin/view/LHCb/GeometryActivationExamples
When extracting the local tags, add a -f option to the dump_db_to_files.py
Example:
SetupProject LHCb
setenv tagA dddb-20130408
setenv tagB simcond-20121001-vc-md100
setenv tagC VP-CompactPocofoamOptimize-Local-20130408
setenv SQLITEDBPATH /afs/cern.ch/lhcb/software/DEV/DBASE/Det/SQLDDDB_Upgrade/db
dump_db_to_files.py -c sqlite_file:$SQLITEDBPATH/DDDB.db/DDDB -T $tagA -d myDDDB_Directory
dump_db_to_files.py -c sqlite_file:$SQLITEDBPATH/SIMCOND.db/SIMCOND -T $tagB -d myDDDB_Directory
dump_db_to_files.py -c sqlite_file:$SQLITEDBPATH/DDDB.db/DDDB -T $tagC -d myDDDB_Directory -f
--
SajanEaso - 29-Sep-2012