Difference: CosmicsCondDb (2 vs. 3)

Revision 32005-09-06 - PaulBell

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

Using the COOL Conditions Database in the cosmics

Line: 8 to 8
 
Changed:
<
<

Masking of missing modules

>
>

Features

 
Changed:
<
<
Cosmic setup uses barrel modules only 2 segements 504 modules. before 10.0.x this was hard coded into SCT_ModuleStatusAlg of SCT_ConditionsAlgs. See notes there. Got the tool in digitization and would say if module present or not. Since version xxx instead uses the database. The tool fills a map of module serial numbers to offline ids and then as each hit is looked at we consult the map, not the db. since may be fragile have retained option to fill map hardcoded. so there is the option viadb. once map filled used in same way. have option to use two setups with hard wired. for db only setup 2 modules in the db.
>
>

Masking of Missing Modules in SCT_Digitization

 
Changed:
<
<

Module serial numbers

>
>
The proposed cosmic setup uses 504 barrel modules arranged in two phi segments. Up to and including version 00-00-19 of SCT_ConditionsAlgs the tool SCT_ModuleStatusAlg contained the offline locations of these modules hard coded. SCT_Digitization would then retrieve the SCT_ModuleStatusAlg tool and thus determine if a given hit (real or noise) took place in a module which was present in the arrangement.
 
Changed:
<
<
For hard cdoded only if module there. from db have msn too. basis for more data etc. return unknown or msn. will say using from db or using hardwired
>
>
The new version of SCT_ModuleStatusAlg, found in SCT_ConditionsAlgs-00-01-00 and later, fills a map of the modules which are present from a table of those modules listed by serial number and offline identifiers in the COOL conditions database. After the map is filled (through a callback) it can be interrogated for each hit which is processed in SCT_Digitization.
 
Changed:
<
<

Controlling job options

>
>

Accessing Module serial numbers

 
Changed:
<
<
so the options are....
>
>
If the map of the modules used in the cosmic arrangement is filled from the database, the mapping of module serial numbers to offline positions is known. With the module serial numbers available in the offline, it will then be possible in the future to access further conditions data associated with the modules.
 
Changed:
<
<

Use of conditions database: what remains

>
>
Alternatively, if the database is not used, the offline locations of the modules present are known but not their serial numbers.
 
Changed:
<
<
cabling - post initialise for bs conv. nuno barros. Dead and noisy channels. Similar to test beam. use pool file map object. not done. part of monitoring and need sctdaq input.
>
>

Usage

 
Added:
>
>

The methods

To use the tool, for example in SCT_Digitization, the SCT_ModuleStatusAlg tool must first be retrieved. The method getModuleSn(vector) can then be called, which given the identifiers layer, phi, eta (barrel only for now) returns the module serial number if present. If the map was not filled from the DB, the serial number is returned as "UNKNOWN" if the module is present.

Controlling job options

In InDetCosmicDig_topOptions.py the user chooses whether the module mapping is filled from the database or not with the flag:

SCTUseCondDb = True

The arrangement is also chosen:

SCTCosmicSetup = 2

NOTE: The choice of arrangement only applies when not using the database. The modules in the database assume arrangement type 2.

The above arguments are passed to InDetCosmicDig_jobOptions.py which in turn set flags in the SCT_ModuleStatusAlg tool. From the point of view of SCT_Digitization, it does not matter whether the DB is used or not:

ToolSvc.SCT_ModuleStatusAlg.CosmicSetup = SCTCosmicSetup
ToolSvc.SCT_ModuleStatusAlg.ModuleCondDb = SCTUseCondDb
if ToolSvc.SCT_ModuleStatusAlg.ModuleCondDb:
   include("InDetCosmicSimExample/InDetCosmicDig_condDbOptions.py")
   include ("SCT_ConditionsAlgs/SCT_ConditionsReadMapping.py")

The job option fragment InDetCosmicDig_condDbOptions.py specifies the database connection.

 

-- PaulBell - 04 Sep 2005

Added:
>
>
META FILEATTACHMENT attr="h" comment="" date="1126012428" name="InDetCosmicDig_condDbOptions.py" path="\\cern.ch\dfs\users\p\pbell\InDetCosmicDig_condDbOptions.py" size="1440" user="pbell" version="1.1"
META FILEATTACHMENT attr="h" comment="" date="1126012411" name="InDetCosmicDig_jobOptions.py" path="\\cern.ch\dfs\users\p\pbell\InDetCosmicDig_jobOptions.py" size="4609" user="pbell" version="1.1"
 
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