Difference: RecommendedTags (1 vs. 21)

Revision 212019-01-22 - AdamMorris

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"

Recommended DataBase tags

Line: 94 to 94
 
    • A list of all productions including database tags is maintained here

Where do I find information about global tags

Changed:
<
<
>
>
 
  • Example 1 "DC06-20081002":
    • DDDB: based on "DC06-20080930"
    • LHCBCOND: based on "DC06-20080930" plus:calo-DC06-20081002 …

Revision 202018-02-16 - TimonSchmelzer

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"

Recommended DataBase tags

Line: 78 to 78
 
      • { randomSeeds : [340212, 5501, 540002744, 0] ...
      • condDBTags : [(DDDB, head-20081002), (SIMCOND, head-20081002)]
  • Bookkeeping using dirac tools (SetupProject Dirac, lhcb-proxy-init):
Changed:
<
<
    • dirac-bookkeeping-production-informations 4918
>
>
    • dirac-bookkeeping-production-information 4918
 
      • Step0:Gauss-v37r2 Option files: $APPCONFIGOPTS/Gauss/MC09-b5TeV-md100.py;$APPCONFIGOPTS/Conditions/MC09-20090602-vc-md100.py;$DECFILESROOT/options/30000000.opts;$LBPYTHIAROOT/options/Pythia.opts DDDb: MC09-20090602 CondDb: sim-20090402-vc-md100; ...
      • Step2:Brunel-v34r7 Option files: $APPCONFIGOPTS/Brunel/MC09-WithTruth.py; $APPCONFIGOPTS/Conditions/MC09-20090602-vc-md100.py DDDb: MC09-20090602, CondDb: sim-20090402-vc-md100
  • Bookkeeping GUI (lhcb_bkk)

Revision 192017-11-09 - SaschaStahl

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"

Recommended DataBase tags

Line: 8 to 8
 This is based on Thomas Ruf's talk at T-rec on 13/7/09.

Which database tags should I use?

Changed:
<
<
As a general rule, for real data it should always be safe to use in the analysis the latest available LHCBCOND and DDDB global tags. Unfortunately this may not always be possible due to incompatibilities in the software that we try to avoid but which sometimes creep in nevertheless. For simulation, you should use the same DDDB and SIMCOND tags as in the production, with the same caveat about software compatibilty.
>
>
As a general rule, for real data it should always be safe to use in the analysis the latest available LHCBCOND, DDDB and DQFLAGS global tags. The latter has a direct effect on which events are processed. So it is recommended to use the latest to use the best knowledge of the Data Quality. Unfortunately this may not always be possible due to incompatibilities in the software that we try to avoid but which sometimes creep in nevertheless. For simulation, you should use the same DDDB and SIMCOND tags as in the production, with the same caveat about software compatibilty.
 

Why different tags for MC?

For real data, new tags mean better description of existing detector. For MC data, the best description is the one used during the simulation step. Therefore, why different Tags for MC ?
Line: 31 to 31
 

Knobs

DataType, DDDBtag, CondDBtag, Simulation flag. The DaVinci and Brunel configurable has a variable called DataType, which is the main knob for most use cases. The information is forwarded to the LHCbApp configurable. Known DataTypes are: %SYNTAX{ syntax="python"}%
Changed:
<
<
LHCbApp().DataType = 'MC09' # or 'DC06, '2008', '2009'
>
>
LHCbApp().DataType = 'MC09' # or 'DC06, '2008', '2009', ..., '2018'
 %ENDSYNTAX% If nothing else specified, the LHCbApp will be instrumented to use the default tag: %SYNTAX{ syntax="python"}%
Line: 44 to 44
 %ENDSYNTAX% In some cases, 'DC06', 'MC09', implicitly set by choice of DataType.
Added:
>
>
To get the latest tags according to DataType for every partition, one can specify
<!-- SyntaxHighlightingPlugin -->
from Configurables import CondDB
CondDB( LatestGlobalTagByDataType = "2016" )
<!-- end SyntaxHighlightingPlugin -->

To get the latest tag according to DataType for selected partitions (available for versions released after September 2016) , one can specify

<!-- SyntaxHighlightingPlugin -->
CondDB( Tags = {"LHCBCOND":"<latest:2016>",
                "DDDB":"<latest:2016>",
                "DQFLAGS":"<latest:2016>"} )
<!-- end SyntaxHighlightingPlugin -->
E.g. one could set production specific tags for CondDB and DDDB as specified above and use the latest Data Quality tags.
 Leaving the choice of Tag to the DDDB configurable will solve most use cases. Only needed to specify the DataType corresponding to the data to be used. NOTE: Only one set of tags can be used in one execution. It is not possible to mix data which would require different Tags.
Added:
>
>
 

Default tags

The default tag is resolved by DDDB/Configuration.py. Which means, the actual Tag used depends on the version of LHCb. The person changing DDDB/Configuration.py has to make sure that a new Tag is compatible with the DataType. For example LHCB v27r3:
  • 'DC06': “DC06-20081002“ for DDDB and LHCBCONDNote: SIMCOND does not exist for DC06, Simulation flag set to False, bfield polarity = -1 forced
Line: 75 to 90
 
    • Go to the dirac monitoring, look for the production ID (it's part of the LFN), click on the production and ask for "Show details". Voilą
  • Bender
    • Use the command "lb-run Bender/latest db-tags FILE", where FILE can be the LFN or PFN. It prints you the database tags used in production.
Added:
>
>
  • Production twiki
    • A list of all productions including database tags is maintained here
 

Where do I find information about global tags

Revision 182017-02-20 - SaschaStahl

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"

Recommended DataBase tags

Line: 74 to 74
 
  • DIRAC monitoring
    • Go to the dirac monitoring, look for the production ID (it's part of the LFN), click on the production and ask for "Show details". Voilą
  • Bender
Changed:
<
<
    • Use the command "lb-run Bender latest db-tags FILE", where FILE can be the LFN or PFN. It prints you the database tags used in production.
>
>
    • Use the command "lb-run Bender/latest db-tags FILE", where FILE can be the LFN or PFN. It prints you the database tags used in production.
 

Where do I find information about global tags

Revision 172016-08-31 - SaschaStahl

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"

Recommended DataBase tags

Line: 73 to 73
 
      • Click on the tab corrsponding to the step you are interested in (e.g. 2009-Stripping02 in above example)
  • DIRAC monitoring
    • Go to the dirac monitoring, look for the production ID (it's part of the LFN), click on the production and ask for "Show details". Voilą
Changed:
<
<
>
>
  • Bender
    • Use the command "lb-run Bender latest db-tags FILE", where FILE can be the LFN or PFN. It prints you the database tags used in production.
 

Where do I find information about global tags

Revision 162012-10-29 - MarcoCattaneo

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"

Recommended DataBase tags

Line: 91 to 91
 
      • DDDB: ot-20090519 Fixed wrong material for the Roha component of a coupling.
        • Global tag "MC09-20090526": DDDB: based on "MC09-20090519" plus:velo-20090526, particles-20090526
Changed:
<
<

When should I use the Oracle CondDB?

If you get an error like:
ONLINE_201005       ERROR Database not up-to-date. Latest known update is at 1274248453.0, event time is 1274595459.928
it means that the real data you are analysing was taken after the last release of SQLDDDB. In this case you have to take the ONLINE information from the Oracle DB. You do this by adding to your job the lines:
from Configurables import CondDB
CondDB(UseOracle = True)

In addition you need a valid grid proxy and to use the "--use-grid" option of SetupProject. Initialize the grid proxy:

lhcb-proxy-init
and enter your certificate password. It is propagated automatically to your job if you use the Dirac back-end of Ganga. Then, setup the project environment (e.g. DaVinci):
SetupProject DaVinci --use-grid 
Note: The use of the Oracle DB should be necessary only for analysing data taken after the last release of SQLDDDB. If you are analysing older data, or MonteCarlo, you are much better off keeping the default (UseOracle = False)

Temporary workaround for "Persistency/LFC" problem (April 2010, DaVinci versions earlier than v25r4)

If you have CondDB(UseOracle = True), and you are using the Dirac back end of Ganga, you should also add the option
importOptions("$APPCONFIGOPTS/DisableLFC.py")
It will ensure that your jobs bypass the Persistency/LFC lookup and are therefore much more likely to succeed

If you have CondDB(UseOracle = True), and you are not using the Dirac back end of Ganga, you have a high probability of running into the Persistency/LFC problem and, worse, you are making the problem worse for yourself and for everybody else.

>
>

When should I use the Oracle CondDB?

NEVER! In the past, it was necessary to use Oracle to get the most recent Online conditions when analysing recent real data. These conditions are no longer distributed via Oracle: now, up to date snapshots are automatically made available at the end of each run as part of the standard distribution of SQLite files via the cvmfs file system.
  -- ThomasRuf - 14 Jul 2009
Changed:
<
<
-- MarcoCattaneo - 20-Apr-2010
>
>
-- MarcoCattaneo - 29-Oct-2012
 -- VincentTisserand - 15-Mar-2011

Revision 152011-07-12 - PlamenHopchev

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"

Recommended DataBase tags

Line: 101 to 101
 from Configurables import CondDB CondDB(UseOracle = True)
Changed:
<
<
This should be the only reason for using the Oracle CondDB. If you are analysing older data, or MonteCarlo, you are much better off keeping the default (UseOracle = False) If you do need to use Oracle, you need a valid grid proxy (which is propagated automatically to your job if you use the Dirac back end of Ganga)
>
>
In addition you need a valid grid proxy and to use the "--use-grid" option of SetupProject. Initialize the grid proxy:
lhcb-proxy-init
and enter your certificate password. It is propagated automatically to your job if you use the Dirac back-end of Ganga. Then, setup the project environment (e.g. DaVinci):
SetupProject DaVinci --use-grid 
Note: The use of the Oracle DB should be necessary only for analysing data taken after the last release of SQLDDDB. If you are analysing older data, or MonteCarlo, you are much better off keeping the default (UseOracle = False)
 

Temporary workaround for "Persistency/LFC" problem (April 2010, DaVinci versions earlier than v25r4)

If you have CondDB(UseOracle = True), and you are using the Dirac back end of Ganga, you should also add the option

Revision 142011-03-15 - VincentTisserand

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"

Recommended DataBase tags

Line: 15 to 15
 
  • Special settings, Velo open, B field off, ... are identified with a Tag and this Tag needs to be used when reconstructing and analysing the data
  • There can be changes in the software which require changes in the databases. Newer software versions might not work anymore with old Tag of database. Requires some intelligence for defining compatible tags.
Added:
>
>
For MC it is useful to employ the tags that where used to produce the simulation data files:

for this one can use the book keeping information provided by Fecim the LHCb Bookkeeping Browser: for a given file

one can just cick (mouse right button) to get the "More information" to retrieve the conDB and DDDb tags

 

Why is setting tags required?

Which database tag to use may change, such as when a new mandatory datapoint is added, or when a genuine and post-correctable error is noticed, or if there are updates on ancilliary information, such as (in the future) luminosity information.

Line: 108 to 115
  -- ThomasRuf - 14 Jul 2009 -- MarcoCattaneo - 20-Apr-2010 \ No newline at end of file
Added:
>
>
-- VincentTisserand - 15-Mar-2011

Revision 132010-11-25 - MarcoCattaneo

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"

Recommended DataBase tags

Line: 6 to 6
 

Introduction

This is based on Thomas Ruf's talk at T-rec on 13/7/09.
Added:
>
>

Which database tags should I use?

As a general rule, for real data it should always be safe to use in the analysis the latest available LHCBCOND and DDDB global tags. Unfortunately this may not always be possible due to incompatibilities in the software that we try to avoid but which sometimes creep in nevertheless. For simulation, you should use the same DDDB and SIMCOND tags as in the production, with the same caveat about software compatibilty.
 

Why different tags for MC?

For real data, new tags mean better description of existing detector. For MC data, the best description is the one used during the simulation step. Therefore, why different Tags for MC ?
  • Special settings, Velo open, B field off, ... are identified with a Tag and this Tag needs to be used when reconstructing and analysing the data

Revision 122010-11-11 - PatrickSKoppenburg

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"

Recommended DataBase tags

Line: 60 to 60
 
    • Otherwise, locate a processing pass, e.g. LHCb - Collision09 - Beam450GeV-VeloOpen-MagDown - RealData+RecoToDST-07+2009-Stripping02
      • Right click on the processing pass name and choose "More Information"
      • Click on the tab corrsponding to the step you are interested in (e.g. 2009-Stripping02 in above example)
Added:
>
>
  • DIRAC monitoring
    • Go to the dirac monitoring, look for the production ID (it's part of the LFN), click on the production and ask for "Show details". Voilą
 

Where do I find information about global tags

Revision 112010-09-02 - GiacomoGraziani

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"

Recommended DataBase tags

Line: 25 to 25
 If nothing else specified, the LHCbApp will be instrumented to use the default tag: %SYNTAX{ syntax="python"}% LHCbApp().DDDBtag = 'default'
Changed:
<
<
LHCbApp().ConDBtag = 'default'
>
>
LHCbApp().CondDBtag = 'default'
 %ENDSYNTAX% The simulation flag is used to switch from LHCbCONDto SIMCOND database for conditions. %SYNTAX{ syntax="python"}%
Line: 53 to 53
 
      • condDBTags : [(DDDB, head-20081002), (SIMCOND, head-20081002)]
  • Bookkeeping using dirac tools (SetupProject Dirac, lhcb-proxy-init):
    • dirac-bookkeeping-production-informations 4918
Changed:
<
<
      • Step0:Gauss-v37r2 Option files: $APPCONFIGOPTS/Gauss/MC09-b5TeV-md100.py;$APPCONFIGOPTS/Conditions/MC09-20090602-vc-md100.py;$DECFILESROOT/options/30000000.opts;$LBPYTHIAROOT/options/Pythia.opts DDDb: MC09-20090602 ConDDb: sim-20090402-vc-md100; ...
      • Step2:Brunel-v34r7 Option files: $APPCONFIGOPTS/Brunel/MC09-WithTruth.py; $APPCONFIGOPTS/Conditions/MC09-20090602-vc-md100.py DDDb: MC09-20090602, ConDDb: sim-20090402-vc-md100
>
>
      • Step0:Gauss-v37r2 Option files: $APPCONFIGOPTS/Gauss/MC09-b5TeV-md100.py;$APPCONFIGOPTS/Conditions/MC09-20090602-vc-md100.py;$DECFILESROOT/options/30000000.opts;$LBPYTHIAROOT/options/Pythia.opts DDDb: MC09-20090602 CondDb: sim-20090402-vc-md100; ...
      • Step2:Brunel-v34r7 Option files: $APPCONFIGOPTS/Brunel/MC09-WithTruth.py; $APPCONFIGOPTS/Conditions/MC09-20090602-vc-md100.py DDDb: MC09-20090602, CondDb: sim-20090402-vc-md100
 
  • Bookkeeping GUI (lhcb_bkk)
    • If you know the production ID, check the "Production Lookup" check box, type in the production ID and click OK. This gives a table with the same information as the dirac-bookkeeping-production-informations tool.
    • Otherwise, locate a processing pass, e.g. LHCb - Collision09 - Beam450GeV-VeloOpen-MagDown - RealData+RecoToDST-07+2009-Stripping02

Revision 102010-06-11 - PeterJones

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"

Recommended DataBase tags

Line: 91 to 91
 This should be the only reason for using the Oracle CondDB. If you are analysing older data, or MonteCarlo, you are much better off keeping the default (UseOracle = False) If you do need to use Oracle, you need a valid grid proxy (which is propagated automatically to your job if you use the Dirac back end of Ganga)
Changed:
<
<

Temporary workaround for "CORAL/LFC" problem (April 2010, DaVinci versions earlier than v25r4)

>
>

Temporary workaround for "Persistency/LFC" problem (April 2010, DaVinci versions earlier than v25r4)

 If you have CondDB(UseOracle = True), and you are using the Dirac back end of Ganga, you should also add the option
importOptions("$APPCONFIGOPTS/DisableLFC.py")
Changed:
<
<
It will ensure that your jobs bypass the CORAL/LFC lookup and are therefore much more likely to succeed
>
>
It will ensure that your jobs bypass the Persistency/LFC lookup and are therefore much more likely to succeed
 
Changed:
<
<
If you have CondDB(UseOracle = True), and you are not using the Dirac back end of Ganga, you have a high probability of running into the CORAL/LFC problem and, worse, you are making the problem worse for yourself and for everybody else.
>
>
If you have CondDB(UseOracle = True), and you are not using the Dirac back end of Ganga, you have a high probability of running into the Persistency/LFC problem and, worse, you are making the problem worse for yourself and for everybody else.
 

Revision 92010-06-01 - MarcoCattaneo

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"

Recommended DataBase tags

Line: 79 to 79
 
        • Global tag "MC09-20090526": DDDB: based on "MC09-20090519" plus:velo-20090526, particles-20090526

When should I use the Oracle CondDB?

Changed:
<
<
The only reason why you would want to access conditions data from the Oracle database is if you want to analyse real data taken since the last release of SQLDDDB. You do this by adding to your job the lines:
>
>
If you get an error like:
ONLINE_201005       ERROR Database not up-to-date. Latest known update is at 1274248453.0, event time is 1274595459.928
it means that the real data you are analysing was taken after the last release of SQLDDDB. In this case you have to take the ONLINE information from the Oracle DB. You do this by adding to your job the lines:
 
from Configurables import CondDB
CondDB(UseOracle = True)
Changed:
<
<
If you are analysing older data, or MonteCarlo, you are much better off keeping the default (UseOracle = False)
>
>
This should be the only reason for using the Oracle CondDB. If you are analysing older data, or MonteCarlo, you are much better off keeping the default (UseOracle = False)
 If you do need to use Oracle, you need a valid grid proxy (which is propagated automatically to your job if you use the Dirac back end of Ganga)
Changed:
<
<

Temporary workaround for "CORAL/LFC" problem (April 2010)

>
>

Temporary workaround for "CORAL/LFC" problem (April 2010, DaVinci versions earlier than v25r4)

 If you have CondDB(UseOracle = True), and you are using the Dirac back end of Ganga, you should also add the option
importOptions("$APPCONFIGOPTS/DisableLFC.py")
It will ensure that your jobs bypass the CORAL/LFC lookup and are therefore much more likely to succeed

Revision 82010-05-31 - RobLambert

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"

Recommended DataBase tags

Line: 10 to 10
 For real data, new tags mean better description of existing detector. For MC data, the best description is the one used during the simulation step. Therefore, why different Tags for MC ?
  • Special settings, Velo open, B field off, ... are identified with a Tag and this Tag needs to be used when reconstructing and analysing the data
  • There can be changes in the software which require changes in the databases. Newer software versions might not work anymore with old Tag of database. Requires some intelligence for defining compatible tags.
Added:
>
>

Why is setting tags required?

Which database tag to use may change, such as when a new mandatory datapoint is added, or when a genuine and post-correctable error is noticed, or if there are updates on ancilliary information, such as (in the future) luminosity information.

So in general it is best to allow the tags to change, which is difficult in the book-keeping, so requires user-input. However, core-software is working on a solution to this issue where the tags are stored in the file itself, and may be overwritten with a centrally maintained map should such updates occur.

 

Knobs

DataType, DDDBtag, CondDBtag, Simulation flag. The DaVinci and Brunel configurable has a variable called DataType, which is the main knob for most use cases. The information is forwarded to the LHCbApp configurable. Known DataTypes are: %SYNTAX{ syntax="python"}%

Revision 72010-04-20 - MarcoCattaneo

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"

Recommended DataBase tags

Line: 71 to 71
 
      • DDDB: ot-20090519 Fixed wrong material for the Roha component of a coupling.
        • Global tag "MC09-20090526": DDDB: based on "MC09-20090519" plus:velo-20090526, particles-20090526
Added:
>
>

When should I use the Oracle CondDB?

The only reason why you would want to access conditions data from the Oracle database is if you want to analyse real data taken since the last release of SQLDDDB. You do this by adding to your job the lines:
from Configurables import CondDB
CondDB(UseOracle = True)
If you are analysing older data, or MonteCarlo, you are much better off keeping the default (UseOracle = False) If you do need to use Oracle, you need a valid grid proxy (which is propagated automatically to your job if you use the Dirac back end of Ganga)

Temporary workaround for "CORAL/LFC" problem (April 2010)

If you have CondDB(UseOracle = True), and you are using the Dirac back end of Ganga, you should also add the option
importOptions("$APPCONFIGOPTS/DisableLFC.py")
It will ensure that your jobs bypass the CORAL/LFC lookup and are therefore much more likely to succeed

If you have CondDB(UseOracle = True), and you are not using the Dirac back end of Ganga, you have a high probability of running into the CORAL/LFC problem and, worse, you are making the problem worse for yourself and for everybody else.

 -- ThomasRuf - 14 Jul 2009
Added:
>
>
-- MarcoCattaneo - 20-Apr-2010
 \ No newline at end of file

Revision 62010-03-29 - MarcoCattaneo

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"

Recommended DataBase tags

Line: 48 to 48
 
    • dirac-bookkeeping-production-informations 4918
      • Step0:Gauss-v37r2 Option files: $APPCONFIGOPTS/Gauss/MC09-b5TeV-md100.py;$APPCONFIGOPTS/Conditions/MC09-20090602-vc-md100.py;$DECFILESROOT/options/30000000.opts;$LBPYTHIAROOT/options/Pythia.opts DDDb: MC09-20090602 ConDDb: sim-20090402-vc-md100; ...
      • Step2:Brunel-v34r7 Option files: $APPCONFIGOPTS/Brunel/MC09-WithTruth.py; $APPCONFIGOPTS/Conditions/MC09-20090602-vc-md100.py DDDb: MC09-20090602, ConDDb: sim-20090402-vc-md100
Added:
>
>
  • Bookkeeping GUI (lhcb_bkk)
    • If you know the production ID, check the "Production Lookup" check box, type in the production ID and click OK. This gives a table with the same information as the dirac-bookkeeping-production-informations tool.
    • Otherwise, locate a processing pass, e.g. LHCb - Collision09 - Beam450GeV-VeloOpen-MagDown - RealData+RecoToDST-07+2009-Stripping02
      • Right click on the processing pass name and choose "More Information"
      • Click on the tab corrsponding to the step you are interested in (e.g. 2009-Stripping02 in above example)
 

Where do I find information about global tags

Revision 52010-02-14 - Ishapoval

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"

Recommended DataBase tags

Line: 50 to 50
 
      • Step2:Brunel-v34r7 Option files: $APPCONFIGOPTS/Brunel/MC09-WithTruth.py; $APPCONFIGOPTS/Conditions/MC09-20090602-vc-md100.py * DDDb: MC09-20090602, ConDDb: sim-20090402-vc-md100*

Where do I find information about global tags

Changed:
<
<
>
>
 
  • Example 1 "DC06-20081002":
    • DDDB: based on "DC06-20080930"
    • LHCBCOND: based on "DC06-20080930" plus: calo-DC06-20081002 …

Revision 42009-07-28 - MarcoCattaneo

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"

Recommended DataBase tags

Line: 50 to 50
 
      • Step2:Brunel-v34r7 Option files: $APPCONFIGOPTS/Brunel/MC09-WithTruth.py; $APPCONFIGOPTS/Conditions/MC09-20090602-vc-md100.py * DDDb: MC09-20090602, ConDDb: sim-20090402-vc-md100*

Where do I find information about global tags

Changed:
<
<
>
>
 
  • Example 1 "DC06-20081002":
    • DDDB: based on "DC06-20080930"
    • LHCBCOND: based on "DC06-20080930" plus: calo-DC06-20081002 …

Revision 32009-07-14 - unknown

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"
Changed:
<
<

Recommended DataBase tags

>
>

Recommended DataBase tags

 
Line: 11 to 11
 
  • Special settings, Velo open, B field off, ... are identified with a Tag and this Tag needs to be used when reconstructing and analysing the data
  • There can be changes in the software which require changes in the databases. Newer software versions might not work anymore with old Tag of database. Requires some intelligence for defining compatible tags.

Knobs

Changed:
<
<
DataType, DDDBtag, CondDBtag, Simulation flag. The DaVinci and Brunel configurable has a variable called DataType, which is the main knob for most use cases. The information is forwarded to the LHCbApp configurable. Known DataTypes are:
>
>
DataType, DDDBtag, CondDBtag, Simulation flag. The DaVinci and Brunel configurable has a variable called DataType, which is the main knob for most use cases. The information is forwarded to the LHCbApp configurable. Known DataTypes are:
 
<!-- SyntaxHighlightingPlugin -->
LHCbApp().DataType = 'MC09' # or 'DC06, '2008', '2009'
<!-- end SyntaxHighlightingPlugin -->
Changed:
<
<
If nothing else specified, the LHCbApp will be instrumented to use the default tag:
>
>
If nothing else specified, the LHCbApp will be instrumented to use the default tag:
 
<!-- SyntaxHighlightingPlugin -->
LHCbApp().DDDBtag = 'default' 
LHCbApp().ConDBtag = 'default' 
<!-- end SyntaxHighlightingPlugin -->
Changed:
<
<
The simulation flag is used to switch from LHCbCONDto SIMCOND database for conditions.
>
>
The simulation flag is used to switch from LHCbCONDto SIMCOND database for conditions.
 
<!-- SyntaxHighlightingPlugin -->
LHCbApp().Simulation = 'True' # or 'False'
<!-- end SyntaxHighlightingPlugin -->
Changed:
<
<
In some cases, 'DC06', 'MC09', implicitly set by choice of DataType.
>
>
In some cases, 'DC06', 'MC09', implicitly set by choice of DataType.
 
Changed:
<
<
Leaving the choice of Tag to the DDDB configurable will solve most use cases. Only needed to specify the DataType corresponding to the data to be used. NOTE: Only one set of tags can be used in one execution. It is not possible to mix data which would require different Tags.
>
>
Leaving the choice of Tag to the DDDB configurable will solve most use cases. Only needed to specify the DataType corresponding to the data to be used. NOTE: Only one set of tags can be used in one execution. It is not possible to mix data which would require different Tags.
 

Default tags

Changed:
<
<
The default tag is resolved by DDDB/Configuration.py. Which means, the actual Tag used depends on the version of LHCB. The person changing DDDB/Configuration.py has to make sure that a new Tag is compatible with the DataType. For example LHCB v27r3:
>
>
The default tag is resolved by DDDB/Configuration.py. Which means, the actual Tag used depends on the version of LHCb. The person changing DDDB/Configuration.py has to make sure that a new Tag is compatible with the DataType. For example LHCB v27r3:
 
  • 'DC06': “DC06-20081002“ for DDDB and LHCBCOND Note: SIMCOND does not exist for DC06, Simulation flag set to False, bfield polarity = -1 forced
  • '2008': “head-20090330” for DDDB, “head-20090402” for LHCBCOND and “sim-20090212” for SIMCOND
  • 'MC09': “MC09-20090602” for DDDB and “sim-20090402-vc-md100” for SIMCOND, Simulation flag ignored
Line: 46 to 46
 
      • condDBTags : [(DDDB, head-20081002), (SIMCOND, head-20081002)]
  • Bookkeeping using dirac tools (SetupProject Dirac, lhcb-proxy-init):
    • dirac-bookkeeping-production-informations 4918
Changed:
<
<
      • Step0:Gauss-v37r2 Option files: $APPCONFIGOPTS/Gauss/MC09-b5TeV-md100.py;$APPCONFIGOPTS/Conditions/MC09-20090602-vc-md100.py;$DECFILESROOT/options/30000000.opts;$LBPYTHIAROOT/options/Pythia.opts *DDDb: MC09-20090602 ConDDb: sim-20090402-vc-md100 *; ...
      • Step2:Brunel-v34r7 Option files: $APPCONFIGOPTS/Brunel/MC09-WithTruth.py; $APPCONFIGOPTS/Conditions/MC09-20090602-vc-md100.py * DDDb: MC09-20090602, ConDDb: sim-20090402-vc-md100*
>
>
      • Step0:Gauss-v37r2 Option files: $APPCONFIGOPTS/Gauss/MC09-b5TeV-md100.py;$APPCONFIGOPTS/Conditions/MC09-20090602-vc-md100.py;$DECFILESROOT/options/30000000.opts;$LBPYTHIAROOT/options/Pythia.opts *DDDb: MC09-20090602 ConDDb: sim-20090402-vc-md100 *; ...
      • Step2:Brunel-v34r7 Option files: $APPCONFIGOPTS/Brunel/MC09-WithTruth.py; $APPCONFIGOPTS/Conditions/MC09-20090602-vc-md100.py * DDDb: MC09-20090602, ConDDb: sim-20090402-vc-md100*
 
Changed:
<
<

Where do I find information about global tags:

>
>

Where do I find information about global tags

 
Line: 65 to 65
 
      • DDDB: ot-20090519 Fixed wrong material for the Roha component of a coupling.
        • Global tag "MC09-20090526": DDDB: based on "MC09-20090519" plus: velo-20090526, particles-20090526
Changed:
<
<

-- PatrickKoppenburg - 13 Jul 2009

>
>
-- ThomasRuf - 14 Jul 2009

Revision 22009-07-14 - ThomasRuf

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"

Recommended DataBase tags

Line: 7 to 7
 

Introduction

This is based on Thomas Ruf's talk at T-rec on 13/7/09.

Why different tags for MC?

Added:
>
>
For real data, new tags mean better description of existing detector. For MC data, the best description is the one used during the simulation step. Therefore, why different Tags for MC ?
  • Special settings, Velo open, B field off, ... are identified with a Tag and this Tag needs to be used when reconstructing and analysing the data
  • There can be changes in the software which require changes in the databases. Newer software versions might not work anymore with old Tag of database. Requires some intelligence for defining compatible tags.
 

Knobs

Added:
>
>
DataType, DDDBtag, CondDBtag, Simulation flag. The DaVinci and Brunel configurable has a variable called DataType, which is the main knob for most use cases. The information is forwarded to the LHCbApp configurable. Known DataTypes are:
 
<!-- SyntaxHighlightingPlugin -->
LHCbApp().DataType = 'MC09' # or 'DC06, '2008', '2009'
<!-- end SyntaxHighlightingPlugin -->
Added:
>
>
If nothing else specified, the LHCbApp will be instrumented to use the default tag:
<!-- SyntaxHighlightingPlugin -->
LHCbApp().DDDBtag = 'default' 
LHCbApp().ConDBtag = 'default' 
<!-- end SyntaxHighlightingPlugin -->
The simulation flag is used to switch from LHCbCONDto SIMCOND database for conditions.
<!-- SyntaxHighlightingPlugin -->
LHCbApp().Simulation = 'True' # or 'False'
<!-- end SyntaxHighlightingPlugin -->
In some cases, 'DC06', 'MC09', implicitly set by choice of DataType.

Leaving the choice of Tag to the DDDB configurable will solve most use cases. Only needed to specify the DataType corresponding to the data to be used. NOTE: Only one set of tags can be used in one execution. It is not possible to mix data which would require different Tags.

 

Default tags

Changed:
<
<
bla bla bla
>
>
The default tag is resolved by DDDB/Configuration.py. Which means, the actual Tag used depends on the version of LHCB. The person changing DDDB/Configuration.py has to make sure that a new Tag is compatible with the DataType. For example LHCB v27r3:
  • 'DC06': “DC06-20081002“ for DDDB and LHCBCOND Note: SIMCOND does not exist for DC06, Simulation flag set to False, bfield polarity = -1 forced
  • '2008': “head-20090330” for DDDB, “head-20090402” for LHCBCOND and “sim-20090212” for SIMCOND
  • 'MC09': “MC09-20090602” for DDDB and “sim-20090402-vc-md100” for SIMCOND, Simulation flag ignored
  • '2009': “head-20090617” for DDDB, “head-20090508” for LHCBCOND and “sim-20090508-vc-md100” for SIMCOND. Simulation flag for switching between SIMCOND and LHCBCOND

Where do I find information about used tags:

  • Start of job, tells what will be used:
    • # WARNING: Default tag requested for partition DDDB (using DC06-20081002)
    • # WARNING: Default tag requested for partition LHCBCOND (using DC06-20081002)
  • In each event, Rec/Header for example contains information which Tag had been used during reconstruction
    • <!-- SyntaxHighlightingPlugin -->
>>> evt['Rec/Header']
       
<!-- end SyntaxHighlightingPlugin -->
      • { randomSeeds : [340212, 5501, 540002744, 0] ...
      • condDBTags : [(DDDB, head-20081002), (SIMCOND, head-20081002)]
  • Bookkeeping using dirac tools (SetupProject Dirac, lhcb-proxy-init):
    • dirac-bookkeeping-production-informations 4918
      • Step0:Gauss-v37r2 Option files: $APPCONFIGOPTS/Gauss/MC09-b5TeV-md100.py;$APPCONFIGOPTS/Conditions/MC09-20090602-vc-md100.py;$DECFILESROOT/options/30000000.opts;$LBPYTHIAROOT/options/Pythia.opts *DDDb: MC09-20090602 ConDDb: sim-20090402-vc-md100 *; ...
      • Step2:Brunel-v34r7 Option files: $APPCONFIGOPTS/Brunel/MC09-WithTruth.py; $APPCONFIGOPTS/Conditions/MC09-20090602-vc-md100.py * DDDb: MC09-20090602, ConDDb: sim-20090402-vc-md100*

Where do I find information about global tags:

  • LHCb->Computing->DDDB http://lhcb-release-area.web.cern.ch/LHCb-release-area/DOC/dbase/conddb/release_notes.xml
  • Example 1 "DC06-20081002":
    • DDDB: based on "DC06-20080930"
    • LHCBCOND: based on "DC06-20080930" plus: calo-DC06-20081002 …
      • Global tag "DC06-20080930": DDDB: based on "DC06-20080904" plus: calo-20080923, calo-20080905
        • 2008-09-23 - Olivier Deschamps
        • DDDB: calo-20080923 (show files)
        • LHCBCOND: calo-20080923 (show files)
        • SIMCOND: calo-20080923 (show files)
        • Reorganized conditions with some new ones.
  • Example 2 "MC09-20090602":
    • DDDB: based on "MC09-20090526" plus: ot-20090519
      • DDDB: ot-20090519 Fixed wrong material for the Roha component of a coupling.
        • Global tag "MC09-20090526": DDDB: based on "MC09-20090519" plus: velo-20090526, particles-20090526
  -- PatrickKoppenburg - 13 Jul 2009 \ No newline at end of file

Revision 12009-07-13 - unknown

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="LHCbComputing"

Recommended DataBase tags

Introduction

This is based on Thomas Ruf's talk at T-rec on 13/7/09.

Why different tags for MC?

Knobs

<!-- SyntaxHighlightingPlugin -->
LHCbApp().DataType = 'MC09' # or 'DC06, '2008', '2009'
<!-- end SyntaxHighlightingPlugin -->

Default tags

bla bla bla

-- PatrickKoppenburg - 13 Jul 2009

 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright &© 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback