Frontemare di Trieste
Istituto Nazionale di Fisica Nucleare
Sezione di Trieste

Noise Run Analysis - Part 2

General Information (18th November 2008)

The runs were taken after the removal of the mini-frame. This means that only the C-side half-ladders were switched on.

RUNTrigger SequenceTrigger ModeFrequencyEvents
63919L2aBC4 KHz10290
63914L2aBC40 Hz10010
63917L2aBC400 Hz10101

The reconstruction was performed with AliRoot v4-16-Release. The official OCDB files were used from AliEn These files were produced from previous calibration runs.

The analysis of the SSD clusters revealed that we have the following number of golden clusters over all the events for the two runs:

RUNLayer 5Layer 6
639191201453
63914554118
63917632116

OCDB files

The OCDB files that were used for the reconstruction of these noise runs come from the run number 63913.

Run63913-BadChannels.gif

Results from the run 63914

Number of clusters per module/number of events
Run63914-ClusterMap.gif\
Module ID
Run63914-ModuleId.gif\
Cluster size
Run63914-ClusterSize.gif\

Results from the run 63917

Number of clusters per module/number of events
Run63917-ClusterMap.gif\
Module ID
Run63917-ModuleId.gif\
Cluster size
Run63917-ClusterSize.gif\

Results from the run 63919

Number of clusters per module/number of events
Run63919-ClusterMap.gif\
Module ID
Run63919-ModuleId.gif\
Cluster size
Run63919-ClusterSize.gif\

Comparison of the CM from all the runs

Run63914
Run63914-CommonModeMap.gif\
Run63917
Run63917-CommonModeMap.gif\
Run63919
Run63919-CommonModeMap.gif\

General Information (18th November 2008)

The runs were taken after the removal of the mini-frame. This means that only the C-side half-ladders were switched on.

RUNTrigger SequenceTrigger ModeFrequencyEvents
63952L2aBC40 MHz10000
63944L2aBC40 Hz10017
63947L2aBC400 Hz10048
63950L2aBC4 KHz10524

The reconstruction was performed with AliRoot v4-16-Release. The official OCDB files were used from AliEn. These files were produced from previous calibration runs.

The analysis of the SSD clusters revealed that we have the following number of golden clusters over all the events for the two runs:

RUNLayer 5Layer 6
6395213225140185
6394458366
6394754462
639501623524

The OCDB files that were used for the reconstruction of these noise runs come from the run number 63940.

Run63940-BadChannels.gif

Results from the run 63944

Number of clusters per module/number of events
Run63944-ClusterMap.gif\
Module ID
Run63944-ModuleId.gif\
Cluster size
Run63944-ClusterSize.gif\

Results from the run 63947

Number of clusters per module/number of events
Run63947-ClusterMap.gif\
Module ID
Run63947-ModuleId.gif\
Cluster size
Run63947-ClusterSize.gif\

Results from the run 63950

Number of clusters per module/number of events
Run63950-ClusterMap.gif\
Module ID
Run63950-ModuleId.gif\
Cluster size
Run63950-ClusterSize.gif\

Results from the run 63952

Number of clusters per module/number of events
Run63952-ClusterMap.gif\
Module ID
Run63952-ModuleId.gif\
Cluster size
Run63952-ClusterSize.gif\

Comparison of the CM from all the runs

Run63944
Run63944-CommonModeMap.gif\
Run63947
Run63947-CommonModeMap.gif\
Run639450
Run63950-CommonModeMap.gif\
Run639452
Run63952-CommonModeMap.gif\

General Information (25th November 2008)

The runs were taken after the removal of the mini-frame. This means that only the C-side half-ladders were switched on. The ITS ventilation system was switched OFF.

RUNTrigger SequenceTrigger ModeFrequencyEvents
64263L2aBC4 KHz10914
64260L2aBC40 Hz10008
64261L2aBC400 Hz10060

The reconstruction was performed with AliRoot v4-16-Release. The official OCDB files were used from AliEn. These files were produced from previous calibration runs.

The analysis of the SSD clusters revealed that we have the following number of golden clusters over all the events for the two runs:

RUNLayer 5Layer 6
64263833749
64260349156
64261244247

OCDB files

The OCDB files that were used for the reconstruction of these noise runs come from the run number 64259.

Run64259-BadChannels.gif

Results from the run 64260

Number of clusters per module/number of events
Run64260-ClusterMap.gif\
Module ID
Run64260-ModuleId.gif\
Cluster size
Run64260-ClusterSize.gif\

Results from the run 64261

Number of clusters per module/number of events
Run64261-ClusterMap.gif\
Module ID
Run64261-ModuleId.gif\
Cluster size
Run64261-ClusterSize.gif\

Results from the run 64263

Number of clusters per module/number of events
Run64263-ClusterMap.gif\
Module ID
Run64263-ModuleId.gif\
Cluster size
Run64263-ClusterSize.gif\

Comparison of the CM from all the runs

Run64260
Run64260-CommonModeMap.gif\
Run64261
Run64261-CommonModeMap.gif\
Run64263
Run64263-CommonModeMap.gif\

Comparison of the CM with and without the ventilation

Below we plot the map of the CM ratio between the runs with and without the ventilation.The ratio is defined as CM(with ventilation)/CM(without ventilation).

40Hz
Run40-DifferenceCommonModeMap.gif\
400Hz
Run400-DifferenceCommonModeMap.gif\
4kHz
Run4000-DifferenceCommonModeMap.gif\

COMMUNITY

Calendar

NOTE! This site uses cookies and similar technologies.

If you do not change your browser settings, you agree. Learn more

I agree