Difference: LHCbSTEmulator (10 vs. 11)

Revision 112009-05-18 - AnneKeune

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

The ST TELL1 Emulator

Changed:
<
<
This page contains information about the ST TELL1 Emulator and how to use it within the Vetra environment (v6r2 and up). The current version of the emulator used is ST/STTELL1Algorithms v3r4. Information on how to run the old Emulator (v2r1, using jobOptions or local Database and without 2nd order header correction) can be found here.
>
>
This page contains information about the ST TELL1 Emulator and how to use it within the Vetra environment (v7r0 and up). The current version of the emulator used is ST/STTELL1Algorithms v3r4.
  The packages used by the Emulator are:
Changed:
<
<
  • ST/STTELL1Algorithms (v3r4)
  • Tell1/TELL1Engine (v2r0)
  • DAQ/Tell1Kernel (v1r5)
>
>
  • ST/STTELL1Algorithms
  • Tell1/TELL1Engine
  • DAQ/Tell1Kernel
  The Emulator is included in the Vetra release, thus there is no need to install these packages locally. We can run the Emulator within the Vetra environment.
Line: 21 to 21
  The first three algorithms function as a wrapping around the C-code written processes (supplied by Guido), which can be found in the TELL1Engine package. STTELL1Algorithms is the only package which is specific to the ST. Both TELL1Engine and Tell1Kernel are also used by the Velo.
Changed:
<
<
Before running the Emulator the raw data must be decoded. This is done using the STFullDecoding algorithm (ST/STOnline). To run the Emulator add the following lines to the options file:
>
>
Before running the Emulator the raw data must be decoded. This is done using the STFullDecoding algorithm (ST/STDAQ). To run the Emulator add the following lines to the options file:
  ApplicationMgr.TopAlg = {"STFullDecoding","ProcessPhase/Emulator" };
Line: 31 to 31
         ,"STTELL1ClusterMaker"
};
Changed:
<
<
Another important algorithm is "RawBanktoSTClusterAlg" (ST/STDAQ). With this algorithm clusters are decoded. To compare TELL1 clusters with Emulator clusters, this algorithm needs to be run twice. Once to decode the clusters in the ZS bank and once to decode the clusters created by the ClusterMaker of the Emulator. For the second, the rawEventLocation needs to be set to "Emu/RawEvent" and as output location you can set the clusterLocation to "Emu/IT/Clusters".
>
>
Another important algorithm is "RawBanktoSTClusterAlg" (also ST/STDAQ). With this algorithm clusters are decoded. To compare TELL1 clusters with Emulator clusters, this algorithm needs to be run twice. Once to decode the clusters in the ZS bank and once to decode the clusters created by the ClusterMaker of the Emulator. For the second, the rawEventLocation needs to be set to "Emu/RawEvent" and as output location you can set the clusterLocation to "Emu/IT/Clusters".
 
Changed:
<
<
Only after this the Monitoring can be run. The monitoring is generally used as a debugging tool. It dumps all information on clusters, but if you like also NZS information etc, in a large TTree. If you choose also to monitor the NZS information, you should put the output in a /tmp location. Here follow the options which can be set.
>
>
The monitoring algorithm dumps all information on clusters and/or nzs information in a large NTuple. This NTuple can contain two TTrees, one called 'nzs' and one called 'zs' (both can be switched on/off). If you choose also to monitor the nzs information, you should put the output in a /tmp location. Here follow the options which can be set.
 

Job Options

The jobOptions which can be set in the Emulator are:

STTELL1PedestalSubtractor STTELL1LCMS STTELL1ClusterMaker STTELL1Monitoring
Changed:
<
<
InputDataLoc
(STTELL1DataLocation::TTFull)
OutputDataLoc
(STTELL1DataLocation::TTPedSubADCs)
SubPedsLoc
(STTELL1DataLocation::TTSubPeds)
TELL1PedestalBankLoc
(STTELL1DataLocation::TTPedestal)
DetType ("TT")
CondPath ("CondDB")
UseTELL1PedestalBank (false)
InputDataLoc
(STTELL1DataLocation::TTPedSubADCs)
OutputDataLoc
(STTELL1DataLocation::TTLCMSADCs)




DetType ("TT")
CondPath ("CondDB")

ConvergenceLimit (0)
InputDataLoc (STTELL1DataLocation::TTLCMSADCs)






DetType ("TT")
CondPath ("CondDB")

ConvergenceLimit (0)








DetType ("TT")
CondPath ("CondDB")

ConvergenceLimit (0)
RootName ("tree.root")
MCTruth (false)
IncludeZS (true)
IncludeNZS (false)
>
>
InputDataLoc
(STTELL1DataLocation::TTFull)
OutputDataLoc
(STTELL1DataLocation::TTPedSubADCs)
SubPedsLoc
(STTELL1DataLocation::TTSubPeds)
TELL1PedestalBankLoc
(STTELL1DataLocation::TTPedestal)
DetType ("TT")
CondPath ("CondDB")
UseTELL1PedestalBank (false)
InputDataLoc
(STTELL1DataLocation::TTPedSubADCs)
OutputDataLoc
(STTELL1DataLocation::TTLCMSADCs)




DetType ("TT")
CondPath ("CondDB")

ConvergenceLimit (0)
InputDataLoc (STTELL1DataLocation::TTLCMSADCs)






DetType ("TT")
CondPath ("CondDB")

ConvergenceLimit (0)
RawDataLoc (STTELL1DataLocation::ITFull)
PedsubDataLoc (STTELL1DataLocation::ITPedSubADCs)
LCMSDataLoc (STTELL1DataLocation::ITLCMSADCs)
PedestalLoc (STTELL1DataLocation::ITSubPeds)
TELL1PedestalLoc (STTELL1DataLocation::ITPedestal)
ClusterLoc ("Raw/IT/Clusters")
EmuClusterLoc ("Emu/IT/Clusters")
ErrorLoc (STTELL1BoardErrorBankLocation::ITErrors)
SigNoiseTool ("STSignalToNoiseTool")
DetType ("TT")
CondPath ("CondDB")
ConvergenceLimit (0)
SkipIfErrorBank (true)
MCTruth (false)
IncludeZS (true)
IncludeNZS (false)
  The ConvergenceLimit is the number of events used to calculate a good pedestal. For these events only the Pedestal Subtraction algorithm will run. Only when the ConvergenceLimit is reached will the CMS and the ClusterMaker run. (Example: If a strip is off, i.e. it always has ADC 0 and we start with subtracting the default value of 128 (see next section), then it takes the Pedestal Update about 12000 events to get the pedestal to the right value of 0.)
Changed:
<
<
Difference with the previous (v2r1) version of the Emulator is that the conditions database is always used from now on, we don't need to use configuration parameters in the jobOptions anymore. We can still change the configuration settings using the jobOptions (ConditionsOverride) however. This is now the preferred method as this new version does not require the installation of a local database. Therefore we always need to set the path of the conditions database.
>
>
For the monitoring: IncludeZS and IncludeNZS refer to the TTrees you'd like in the NTuple.
 

Configuration Parameters in the Conditions Database

This section explains which parameters are in the conditions database. For information on how to set these parameters, please read the section "Setting/Changing the conditions database parameters".
Line: 51 to 51
 Each condition (or TELL1Board) contains the following parameters (specified per algorithm). These are their names as they are in the conditions database.

STTELL1PedestalSubtractor
Changed:
<
<
Header_correction_analog_link_0, size:4
Header_correction_analog_link_1, size:4
...
Header_correction_analog_link_95, size:4
Header_threshold, size:2
Pedestal_mask, size:3072
Pedestal_value, size:3072
Pedestal_enable
Update_enable
ZS_enable
Header_enable
>
>
Header_correction_analog_link_00, size:4
Header_correction_analog_link_01, size:4
...
Header_correction_analog_link_95, size:4
Header_threshold, size:2
Pedestal_mask, size:3072
Pedestal_value, size:3072
Pedestal_enable
Update_enable
ZS_enable
Header_enable
 
Changed:
<
<
The Pedestal_mask is a vector of size 3072, which entries can be set to either 0 or 1. 1 meaning that a certain strip is masked for pedestal subtraction and header correction. The Pedestal_value contains the initial pedestals to be subtracted per link. To enable the pedestal subtraction,
>
>
The Pedestal_mask is a vector of size 3072, which entries can be set to either 0 or 1. 1 meaning that a certain strip is masked (ADC set to 0). The Pedestal_value contains the initial pedestals to be subtracted per link. To enable the pedestal subtraction,
 both Pedestal_enable and ZS_enable must be set to 1. Pedestal Following is enabled by setting Update_enable to 1.
Changed:
<
<
There are two types of header , a "negative" header (below pedestal line) and a "positive" header (above pedestal line). Cross talk between the last header and first strip (strip 0) occurs and also second order crosstalk between the second to last header and the first strip (strip 0) occurs. We can therefore set 4 corrections (for "negative/negative", "negative/positive", "positive/negative" and "positive/positive" headers) per link (32 channels). In total there are 96 links per TELL1. To enable the header correction set Header_enable to 1. Note: In previous versions the second order header correction was not included and only 2 corrections were used.
>
>
Although Header_enable and Header_correction_analog_link_## are in the list, the header correction is currently being revised and not used at the moment.
 
STTELL1LCMS
CMS_threshold, size:3072
CMS_enable
Line: 72 to 69
 To enable the ZS process set ZS_enable to 1. There are three thresholds used in the ZS process: The Hit_threshold is per individual strip and thus the charge of each strip in a cluster needs to exceed this threshold. The total charge of the cluster needs to exceed the Confirmation_threshold. When the total charge of the clusters is higher than the SpillOver_threshold the SpillOver bit is set. Both Confirmation_threshold as SpillOver_threshold can be set per processing channel (64 strips), but clusters are searched for per beetle (128 strips). The 'Disable_beetles' are simply set with either 1 or 0. However, the 'Disable_links_per_beetle' needs a number between 0 (no links disabled) and F (all links disabled).

Setting up the Conditions Database

Changed:
<
<
In order to use the database, Vetra v6r3 needs to be installed: getpack Tell1/Vetra v6r3.
>
>
In order to use the database, Vetra v7r0 needs to be installed: getpack Tell1/Vetra v7r0. (or there may even be a more recent version).
 There are 2 steps we need to take. First, we need to create our own file with configuration parameters. This is done by going to the python folder and running:

python write_it_xml_cond.py (or tt)

Added:
>
>
This is however a standard file without the latest settings in them. For a file with the latest settings contact me.
 After this the conditions database can be set up; go to the scripts folder and run:

source create_it_sqlite_file_from_xml.sh (or tt)

 
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