AtlasPublicTopicHeader.png

Public SCT Plots for Collision Data

Introduction

Approved plots that can be shown by ATLAS speakers at conferences and similar events.
Please do not add figures on your own. Contact the responsible project leader in case of questions and/or suggestions. Please note that the original plots, often in multiple formats, are attached to this page in the attachements tab at the bottom.

Obsolete Plots up to 2012

All plots listed in this section relate to very early Run-1 data and are therefore obsolete. They should not now be used in conferences or papers. They are still listed here for information only.

The document attached to this page (SCTConfigurationMay2010.pdf) details the configuration of the SCT in May 2010. Within that document you will find details of the modules, chips and strips missing from the SCT configuration in the first half of 2010. On the right hand side you can see a snapshot of one of these pages. Users are encouraged to copy the values from the table into their own presentations in a format that is appropriate for them. It SHOULD BE CLEAR that this is only a snapshot and these numbers vary on a day-to-day basis. However, the level of those variations is very small indeed. It is also true that the level of the problems reported in this table have been very similar throughout most of 2011.

Sample.JPG
The plot shows the SCT cluster size (in strips) plotted as a function of the track incidence angle for the 4 layers in the SCT barrel. The incidence angle is measured in degrees. We note that the minimum of the distribution is, in each case displaced, from the zero by the measured Lorentz angle. The value of the minimum with the associated systematic errors are presented in the next plot. This plot was approved on Wednesday 9th December 2009 at an open ATLAS meeting and uploaded on Saturday 12th December 2009.This plot is now out of date and one of the ones below should be used.

ClusterSizevsIncidenceAngleInSCT.jpg
In this plot we see the value of the Lorentz angle extracted from the cluster-size vs angle plot. The extracted value is shown for collision data, cosmic ray data. Also shown are the model predictions. Note that the 4 layers are not all operated at the same temperature and this is reflected in the model prediction value. The errors shown on the data are the statistical values only.This plot was approved on Wednesday 9th December 2009 at an open ATLAS meeting and uploaded on Saturday 12th December 2009. This plot is now out of date and one of the ones below should be used.

LorentzAngleInSCTWithBeam.jpg
In this plot we see the value of the Lorentz angle extracted from the 2011 colliding beam data. For details see the document in CDS https://cdsweb.cern.ch/record/1385910/files/LorentzAngleUpdateOnApprovedPlots2011.pdf

data11_LAPlot.png
In this plot we see the value of the Lorentz angle extracted from the 2011 colliding beam data with Monte Carlo simulation superimposed. dataAndMC_LAPlot.png
In this plot we see the mean cluster size as a function of the incidence angle for the 4 SCT barrels. The cluser size is measured on side 0.

incidentAngle_vs_nStrips_side0.png
In this plot we see the mean cluster size as a function of the incidence angle for the 4 SCT barrels. The cluser size is measured on side 1.

incidentAngle_vs_nStrips_side1.png
In this plot we see the mean cluster size as a function of the incidence angle for the 4 SCT barrels. The cluser size is measured on side 0. In the same plot we also see the same distributions for the Monte Carlo simulation.

incidentAngle_vs_nStrips_DataVsMc_side0.png
In this plot we see the mean cluster size as a function of the incidence angle for the 4 SCT barrels. The cluser size is measured on side 1. In the same plot we also see the same distributions for the Monte Carlo simulation.

incidentAngle_vs_nStrips_DataVsMc_side1.png
In this plot we see the number of strips per module side from the 900GeV run 14291 lumiblock 11-36 compared with a 900GeV minimum bias Monte Carlo sample. The solenoid was on during this run. The number of events from the run is about 10k, and 40k for MC. Both distributions are normalized by number of events and plotted in logarithmic scales in both axes. The plot contains all SCT modules both from barrel and end caps A good agreement is obtained for a wide range of number of strips. The discrepancy at low N arises (at least in part) from the fact that noise in simulation is lower than in data. Noise in the simulation is appropriate for read-out of one bunch-crossing. These data were taken reading out 3 BC, and the noise level is higher (by approx. a factor of 3). The plots were apprved in February 2010.

SCT_NStripPerModuleLogLog900GeV.jpg

This plot shows the intrinsic module efficiency for tracks measured in the SCT Barrel. In these plots we show the number of hits per possible hit where dead modules and chips are taken into account. The efficiency is shown for two different types of tracks; SCT stand alone and combined tracks. We demand a minimum of 20 TRT hits and 6 SCT hits in the silicon detectors (not including the hit under test for efficiency). This plot was approved on Wednesday 16th December 2009 at an open ATLAS meeting and uploaded on Friday 18th December 2009. The alignment used in this plot was derived from collision data.

SCT-summaryeff-SCTB.18.12.09.png

This plot shows the intrinsic module efficiency for tracks measured in the SCT EndCap-A. In these plots we show the number of hits per possible hit where dead modules and chips are taken into account. The efficiency is shown for two different types of tracks; SCT stand alone and combined tracks. We demand a minimum of 20 TRT hits and 6 SCT hits in the silicon detectors (not including the hit under test for efficiency). This plot was approved on Wednesday 16th December 2009 at an open ATLAS meeting and uploaded on Friday 18th December 2009. The plot includes a preliminary alignment derived from beam data.

SCT-summaryeff-SCTEA.18.12.09.png
This plot shows the intrinsic module efficiency for tracks measured in the SCT EndCap-C. In these plots we show the number of hits per possible hit where dead modules and chips are taken into account. The efficiency is shown for two different types of tracks; SCT stand alone and combined tracks. We demand a minimum of 20 TRT hits and 6 SCT hits in the silicon detectors (not including the hit under test for efficiency). This plot was approved on Wednesday 16th December 2009 at an open ATLAS meeting and uploaded on Friday 18th December 2009.The plot includes a preliminary alignment derived from beam data. Note the single low measurement in layer 2 inner is due to a single module with a large number (748) of misbehaving strips.

SCT-summaryeff-SCTEC.18.12.09.png
The intrinsic module efficiency is shown for tracks measured in the SCT Barrel. This hit efficiency is the number of hits per possible hit, where dead modules and chips are taken into account. The data used is from run 165591 on 22-09-2010. The efficiency is shown for two different types of tracks: SCT stand-alone and Inner Detector combined tracks, both with the requirement of a transverse momentum of above 1 GeV. For stand-alone tracks we demand at least 7 SCT hits (not including the hit under test for efficiency) while for combined tracks at least 6 SCT Hits are required. The efficiencies in layer ‘0 inner’ and ‘3 outer’ are biased for the SCT stand-alone tracks as holes beyond the last measurement are not counted.

SCTBarrel-eff-APPROVAL2011.png
The intrinsic module efficiency is shown for tracks measured in the SCT EndCap-A. This hit efficiency is the number of hits per possible hit, where dead modules and chips are taken into account. The data used is from run 165591 on 22-09-2010. The efficiency is shown for two different types of tracks: SCT stand-alone and Inner Detector combined tracks, both with the requirement of a transverse momentum of above 1 GeV. For stand-alone tracks we demand at least 7 SCT hits (not including the hit under test for efficiency) while for combined tracks at least 6 SCT Hits are required. The efficiencies in layer ‘0 inner’ and ‘3 outer’ are biased for the SCT stand-alone tracks as holes beyond the last measurement are not counted. SCTEndcapA-eff-APPROVAL2011.png
The intrinsic module efficiency is shown for tracks measured in the SCT EndCap-C. This hit efficiency is the number of hits per possible hit, where dead modules and chips are taken into account. The data used is from run 165591 on 22-09-2010. The efficiency is shown for two different types of tracks: SCT stand-alone and Inner Detector combined tracks, both with the requirement of a transverse momentum of above 1 GeV. For stand-alone tracks we demand at least 7 SCT hits (not including the hit under test for efficiency) while for combined tracks at least 6 SCT Hits are required. The efficiencies in layer ‘0 inner’ and ‘3 outer’ are biased for the SCT stand-alone tracks as holes beyond the last measurement are not counted. SCTEndcapC-eff-APPROVAL2011.png

SCT reads out three 25ns time bins around Level-1 Accept signal. During commissioning, we run in a mode where a hit is recorded in a strip if the charge deposited is greater than the 1fC threshold in any of these time bins.We want the whole detector to be “timed in” with the trigger, so that the modules receive the Level-1 accept signal in the same bunch crossing as the particles from a collision pass through the modules. This involves applying delays to the trigger signal to compensate for the length of the optical fibres that transmit the trigger signal, and for the time-of-flight of particles from the interaction point to the module. We can fill a 3 bin histogram corresponding to whether a strip was over threshold in each of the three bunch crossings that are read out – the first bin corresponds to the bunch crossing before the Level-1 accept, the second bin is the same BC as the LVL1Accept and the third is the BC after. If we are correctly timed in, hits corresponding to tracks from a collision event should follow a “01X” pattern – i.e. nothing in the first bin, over threshold in the second bin, and no requirement on the third bin. For each event, fill one of these 3-bin timebin plots for each layer, using hits-on-track for that layer. Take the mean of this histogram, and fill this as the y-axis variable in a profile plot. Reset the histograms and repeat for all events. Therefore, the y error bars on each point represent the variances in the means of those timebin plots from event-to-event. One unit on the y-axis corresponds to 25ns, and to be correctly timed in, we hope that the mean should be between 1 and 2.

 tbinprofile_142195_approved.gif

tbinhitmaps_142195_approved.gif

This plot shows the fraction of SCT module sides that are reporting errors as a function of time (run number) for the data taken in 2010. The error rate is very low and there is no strong evidence of an increase with increasing luminosity. The report summarizing this can be found here. Error1.gif

This plot shows a breakdown of the different types of error for the data taken in 2010 as seen on the previous plot. It shows that the total fraction of data with errors in the run period was less than 0.25%. The fraction of data with each kind of error can be found in corresponding bins.The report summarizing this can be found here.

Error2.gif
This plot is one of many summarizing the SCT timing scan done in 2010. The report summarizing this can be found here. Please go to this location to pick up more plots. Timing1.gif
This plot is one of many summarizing the performance of the FSI in 2010. The report summarizing this can be found here. Please go to this location to pick up more plots. FSI1.gif
This plot shows a history of the SCT occupancy measured in the ROS in a typical run in 2010. here. Please go to this location to pick up more plots. SCTOcc.GIF
Plots concerning leakage currents, measured fluxes in SCT and RadMod. See more details here. Plot updated in January 2013.

In this plot, the HV current measured in the HV power supply of the ATLAS SCT barrel modules are shown by points at four SCT barrel layers (B3 to B6) . The data were taken when the LHC beams were off. Assuming that all HV currents are due to generation current in the silicon bulk, they are converted to those at the temperature of 0oC using the temperature scaling formula with effective energy Egen =1.21 eV [1]. The predicted leakage currents by the Hamburg /Dortmund model are shown by four lines with colored bands indicating 1 sigma uncertainties, which is obtained by quadratically summing up all uncertainties of the model parameters as well as the temperature measurements. The prediction takes into account of self-annealing effects using the measured sensor temperatures shown at the top of plots. The prediction is based on the total 7 and 8-TeV collision luminosities delivered at Point-1, shown by the black solid line. Results of the FLUKA simulation [2] of minimum bias events at 7 TeV pp collisions (with 5% up at 8 TeV) are used to convert the collision luminosity to 1 MeV neutron-equivalent fluence at each layer. The error of the FLUKA simulation is not included in the estimate of 1 sigma uncertainty. Very good agreements between data and predictions are observed over 4 decades in leakage current as well as over 3 year, indicating (1) observed HV currents are mostly due to bulk generation current, (2) the leakage current models with self-annealing terms are well applicable and (3) the flux simulation is reasonable. In conclusion, the leakage current is one of good measures for the radiation levels at the SCT region. [1] A.Chilingarov, RD50 Technical Note 2013_JINST_8_P10003,
[2] https://twiki.cern.ch/twiki/bin/viewauth/Atlas/BenchmarkingAtTheLHC.

LeakCurrent_2010_2012.png
Plots concerning leakage currents, measured fluxes in SCT and RadMod. See more details here. Plot updated in January 2013.

This plot shows the leakage current distribution of the SCT modules of four barrel layers (B3 to B6) on Dec 5, 2012 when the LHC beam off. Out of 2112 barrel modules, 2060 modules (97.5%) satisfy the cuts of HV=150+5-2V with reasonable hybrid temperatures. The currents measured by the HV PS are converted to those at the temperature of 0oC using the temperature scaling formula. The leakage currents are plotted in 12 groups, each of which contains all the modules placed at the same z (beam direction) position. Values of modules in each group are plotted in series starting from 0 to 360 degree in phi direction. The distribution of currents is very flat along z (eta) except for B3 in which the central part (|z| < 30 cm) shows about 7% excess. This flat distribution is a good reflection of the flat eta distribution of secondary particles around the center of the minimum bias events.

LeakCurrentDistribution_2012End.png
This table demonstrates the rate limitations of the SCT for various occupancies. It shows that at 1% link occupancy that the event size is 2 kB/ROD and that SCT rate limitation is dominated by the S-links at a value of 89Khz. SCTRateLimitations.GIF

Plots added from 2013

Leakage Currents and Temperatures

Numder of active cooling loops for SCT as a function of time from 2010 to 2012. Occasional interuptions by for example power-line cuts are seen but the recoveries have been prompt. ActiveCoolingLoops_sct.png

Distribution of the HV currents of all the barrel modules as of Dec. 5, 2012. Regular bump patterns in the layer B3 are due to one cooling loop set at higher temperature. The flat distribution along z (beam) axisi is a reflection of the flat pseudorapidity distribution of secondary particles in minimum bias events. MD20121205_LC_Barrel.png

Distribution of the HV currents of all the end-cap modules as of Dec. 5, 2012. Modules of sides C and A and those with Hamamatsu and CiS sensors are shown in different colors. The HV currents in side A are systematically larger by about 20% probably due to different sensor temperatures. MD20121205_LC_Endcap.png

Distribution of the temperatures of all the barrel modules as of Dec. 5, 2012. There are two thermistors on each module. Points labeled as link 0 (red) are for the outer hybrid circuits, while those labeled as kink 1 (blue) are for the inner hybrid circuits. The regular bumps in the layer B3 are due to one cooling loop set at higher temperature. MD20121205_Temp_Barrel.png

Distribution of the temperatures of all the end-cap modules as of Dec. 5, 2012. Each module has one thermistor to measure the temperature of the hybrid circuit. Side A and C are shown with different colors.

MD20121205_Temp_Endcap.png

Mean hybrid temperatures as a function of time (averaged every 5 days). In the endcap case, they are separately shown for sides A and C.

Tmean_5days.png

Status of the Barrel layer B3 as of Dec. 5, 2012: (Top) High Voltage, (2nd) Hybrid temperatures of link-0 and link-1, (3rd) Raw HV current per module, and (Bottom) Normalized leakage curret at 0 degree C. The left-most block in the plot corresponds to 32 modules at Eta=-6 closest to the C-side. Blue horizontal lines show HV and temperature cuts to exclude modules in the bottom plot. Regular bump patterns in the 2nd and 3rd plots are due to one cooling loop set at higher temperature. However these these bumps disappear after the temperature normalization. The flat distribution along z in the bottom plot is a reflection of the flat pseudorapidity distribution in minimum bias events. Similar flat distributions are seen in all other barrel layers. MD20121205_B3_z.png

This plot shows a typical evolution of the HV current(blue) and bias voltage(red) of one of end-cap modules with CiS sensors in late May 2012. It exhibits anomalously high and varying HV currents during beam collisions. Such poor behaviours were suppressed by setting the standby voltage to 5V (instead of 50V) and lowering the bias voltage to 80-120V for some modules. cis_current.png

This plot shows typical beam-time behaviors of bias voltages and HV currents during November 2012 runs. Modules with Hamamatsu sensors(left) show flat current profiles while those with CiS sensors(right) exibit varying current behaviors during beam times. The last run corresponds to 1-day long calibration with no beam in which all currents stayed constant.

cis_current_Hamamatsu-CiS.png

Noise and Gain

Change of the chip-averaged noises as a function of chip numbers, during second half of year 2010 (top) and from 2011 to 2012(bottom) for Barrel layer B3. Noises of the modules with <100> crystal orientation are separately plotted, showing negligible dependence on chip numbers. The noise mystariously decreased by about 7% in late 2010 when the fluence level was at about 1.e10 cm-2, a few Gy. Such noise drops strongly depended on the strip location as shown by the chip-number dependence in the top plot, while such initial decrease stopped and the strong chip-number dependence disappered in 2011 and 2012 shown in bottom plot. noise_glass.png
Time dependence of integrated luminosityuminosity(top), input equivalent noise charges ENC(middle) and gains of front-end amplifiers(bottom) from March 2010 till December 2012. Modules are divided into ten different groups according as module types, crystal orientations of <111> vs <100> and sensor manufactures of Hamamatsu vs CiS. ENCs and gains are the results of the 3-point gain calibration scans. noise_gain.png
This figure shows the module-averaged noises (ENCs) of all end-cap modules, taken in a response curve test in December 2012. Modules of side-A and side-C with Hamamatsu and CiS sensors are marked with different colors. Noticeable enhancement of noise is seen in the middle modules with CiS sensors. noise_EC_216516.png
The figure shows the distributions of module-averaged responce-curve noises (ENCs) as of October 2010 for end-cap outer, middle and inner layers. Modules of sides A and C and those with Hamamatsu and CiS sensors are shown in different colors. ENCs of the middle short modules in disk 8 is plotted using right scale. noise_EC_166544.png
The figure shows the distributions of module-averaged responce-curve noises (ENCs) as of December 2012 for Barrel layers B3 to B6. ENCs of modules with <100> sensors are shown by blue points, systematically lower that those with <111> sensors (red). noise_Barrel_216516.png
The figure shows the distributions of chip-averaged responce-curve noises as of October 2010 (top) and December 2012 (bottom). Only modules with HV values greater than 145V are selected. For the barrels, only modules with <111> sensors are plotted, while for the end-caps, chips with Hamamatsu and CiS sensors are shown separately. After receiving 30 fb-1,the noises stayed nearly at the original level for barrel and end-cap outer modules, while they increased about 15% in the end-cap middle modules with CiS sensors and about 5\% in inner modules both with Hamamatsu and CiS sensors. noise_166544-216516.png
The figure shows the log-scale distributions of chip-averaged responce-curve noises as of October 2010 (top) and December 2012 (bottom). Only modules with HV values greater than 145V are selected. For the barrels, only modules with <111> sensors are plotted, while for the end-caps, chips with Hamamatsu and CiS sensors are shown separately. After receiving 30 fb-1,the noises stayed nearly at the original level for barrel and end-cap outer modules, while they increased about 15% in the end-cap middle modules with CiS sensors and about 5\% in inner modules both with Hamamatsu and CiS sensors. noise_166544-216516_log.png

Configuration

Total number of active strips as a function of time from the start of data-taking in 2010 to the end of data-taking in 2013. One point is plotted for each physics run with at least one hour of stable beam. The left-hand axis shows the number of strips, and the right-hand axis the corresponding fraction of the detector in %. The runs with fewer than 98.5% of strips active correspond to periods when a cooling loop was off, so the modules served by that loop could not be powered. The runs at the end of 2010 with ~98.6% strips active correspond to a period when a TX fibre connector was broken, affecting 12 modules. ActiveStrips.png
Number of disabled modules as a function of time from the start of data-taking in 2010 to the end of data-taking in 2013. One point is plotted for each physics run with at least one hour of stable beam. The left-hand axis shows the number of modules, and the right-hand axis the corresponding fraction of the detector in %. The numbers include 13 modules on the outermost disk of endcap C which are disabled permanently due to an inaccessible leak in one cooling loop. The runs with more than 60 disabled modules correspond to periods when a cooling loop was off, so the modules served by that loop could not be powered. The runs at the end of 2010 with around 40 disabled modules correspond to a period when a TX fibre connector was broken, affecting 12 modules. The variations late in 2010 and throughout 2011 correspond to TX deaths where we could not use redundancy; in those cases the module was disabled until the TX was replaced. ModOut.png
Number of disabled readout chips as a function of time from the start of data-taking in 2010 to the end of data-taking in 2013. One point is plotted for each physics run with at least one hour of stable beam. The left-hand axis shows the number of chips, and the right-hand axis the corresponding fraction of the detector in %. The numbers exclude chips on disabled modules. The majority of the disabled chips (roughly 2/3) are on barrel modules read out through one link; in this case, the master chip on the side with the non-functioning link cannot be read out. NEED TO ADD SOMETHING ABOUT RISE. BadChips.png
Number of disabled individual strips as a function of time from the start of data-taking in 2010 to the end of data-taking in 2013. One point is plotted for each physics run with at least one hour of stable beam. The left-hand axis shows the number of strips, and the right-hand axis the corresponding fraction of the detector in %. The numbers exclude strips in disabled modules and whole chips. The most common reason for disabling a strip is excessive noise. Once a strip has been disabled, no attempt is made to re-enable it. The occasional dips seen in the number correspond to runs where extra modules were disabled, for example due to a cooling loop failure, so any individual disabled strips in these modules are not counted in this plot. BadStripsConfig.png
Number of noisy strips determined offline in the prompt calibration loop as a function of time from the start of data-taking in 2010 to the end of data-taking in 2013. One point is plotted for each physics run with at least one hour of stable beam. The left-hand axis shows the number of strips, and the right-hand axis the corresponding fraction of the detector in %. A noisy strip is defined as one with an average occupancy of more than 1.5% in empty bunch-crossings. Strips which were noisy, or showed other problems, in the previous online calibration run are excluded. The rate of noisy strips is observed to rise with luminosity, as radiation affects the effective readout thresholds. Often whole chips are affected, leading to large run-to-run fluctuations in the number of noisy strips. The number is relatively stable during the periods of heavy-ion running at the end of 2011 and in 2013, when the luminosity was relatively low. NoisyStripsMon.png

Performance

The mean intrinsic hit efficiency for each layer of the SCT measured in 8 TeV proton-proton collisions. The hit efficiency is the number of hits per possible hit, where dead modules and chips are taken into account. The data used is from run 200805 on 5th April 2012, with a mean number of interactions per bunch crossing below one. The efficiency is measured using inner detector tracks with a transverse momentum of above 1 GeV and at least 6 SCT hits other than the one under consideration. The blue line and right-hand axis indicates the fraction of disabled strips in each layer. OneSide_with_nBad.png
The mean occupancy of the barrel layers vs pileup. The data below a pileup of 40 were taken at 7TeV. The data above 40 were taken in special high pileup runs at 8TeV with just a few bunches. barrel_occupancy.png

2014 Performance Paper Plots

Almost all of the above plots are available in very latest form in the SCT Performance Paper

Other plots are listed below.

Maximum sustainable level-1 trigger rate for the transfer of data from front-end chip to ROD as a function of the mean number of interactions per bunch crossing, μ. Values are calculated from measured event sizes in pp interactions at √{s} = 14 TeV assuming 90% of the available data-link bandwidth is used. Each link is shown as a separate curve. Increasing numbers of superimposed curves are indicated by changes of colour from blue through green and yellow to red. The dashed lines indicate the typical anticipated maximum first level trigger rate of 100kHz. LimitRateForLinkAsAFunctionOfMu_removed_2.png
Maximum sustainable level-1 trigger rate for the transfer of data from the ROD to ATLAS DAQ chain as a function of the mean number of interactions per bunch crossing, μ. Values are calculated from measured event sizes in pp interactions at √{s} = 14 TeV assuming 90% of the available data-link bandwidth is used. Each link is shown as a separate curve. Increasing numbers of superimposed curves are indicated by changes of colour from blue through green and yellow to red. The dashed lines indicate the typical anticipated maximum first level trigger rate of 100kHz. LimitRateInModifiedCondensedAsAFunctionOfMu.png

Run2 Plots

Public Link CDS record (ATLAS) Full Title Publication Date Approval meeting
SCT-2015-003 ATL-COM-INDET-2015-037 Early Run2 plots, before collisions: Noise, leakage current, timing 01/06/2015 28/05/2015
SCT-2015-001 ATL-INDET-INT-2015-007 Hit efficiency as function of bcid during first 2015 Collisions at √s = 13 TeV 21/09/2015 21/09/2015
SCT-2015-002 ATL-INDET-INT-2015-011 Lorentz angle data measured with the SCT detecor in the first 13TeV pp collisions 01/12/2015 30/11/2015
SCT-2016-001 ATL-COM-INDET-2016-032 Hit Efficiency, leakage currents, noise and detector status at start of 2016 23/05/2016 23/05/2016
SCT-2016-002 ATL-COM-INDET-2016-065 Bandwidth limits, IPIN trends, SEU effects on chip occupancy, long term link noise and gain, long term current and depletion projections, noisy strips and active strips 21/09/2016 21/09/2016
SCT-2017-001 ATL-COM-INDET-2017-043 ABCD Error rates as function of product of pileup and trigger rate 21/09/2017 11/09/2017
SCT-2017-002 N/A Updated bandwidth limitation plots, and barrel leakage currents 06/09/2017 06/09/2017
SCT-2017-003 N/A SCT p-i-n radiation damage effects 08/11/2017 08/11/2017
SCT-2017-004 N/A Currents, noise, gain and depletion evolution 16/11/2017 15/11/2017
SCT-2018-001 N/A Noisy strip and disabled strip evolution - updates 17/11/2018 17/01/2018
SCT-2018-002 ATL-COM-INDET-2018-024 Current projection updates, and link error counts 19/04/2018 18/04/2018
SCT-2018-003 N/A Opto link radiation damage and stability plots 19/04/2018 18/04/2018

Links


Responsible: Project leaders
Last reviewed by: Never reviewed

Topic attachments
I Attachment History Action Size Date Who Comment
Unknown file formateps ActiveCoolingLoops_sct.eps r1 manage 2435.0 K 2013-08-15 - 15:55 DaveRobinson History of active cooling loops
PNGpng ActiveCoolingLoops_sct.png r1 manage 85.5 K 2013-08-15 - 15:55 DaveRobinson History of active cooling loops
Unknown file formateps ActiveStrips.eps r1 manage 15.7 K 2013-08-23 - 14:22 DaveRobinson  
PDFpdf ActiveStrips.pdf r1 manage 34.7 K 2013-08-23 - 14:22 DaveRobinson  
PNGpng ActiveStrips.png r1 manage 23.0 K 2013-08-23 - 14:22 DaveRobinson  
GIFgif ApprovedPlotLeakgeCurrents.GIF r1 manage 17.6 K 2011-06-20 - 22:00 SteveMcMahon  
JPEGjpg ApprovedPlotLeakgeCurrents.JPG r1 manage 70.9 K 2011-06-20 - 21:47 SteveMcMahon  
Unknown file formateps BadChips.eps r1 manage 15.3 K 2013-08-21 - 17:32 DaveRobinson  
PDFpdf BadChips.pdf r1 manage 28.2 K 2013-08-21 - 17:32 DaveRobinson  
PNGpng BadChips.png r1 manage 18.6 K 2013-08-21 - 17:32 DaveRobinson  
Unknown file formateps BadStripsConfig.eps r1 manage 15.6 K 2013-08-21 - 17:32 DaveRobinson  
PDFpdf BadStripsConfig.pdf r1 manage 29.3 K 2013-08-21 - 17:32 DaveRobinson  
PNGpng BadStripsConfig.png r1 manage 22.1 K 2013-08-21 - 17:32 DaveRobinson  
PNGpng Barrel_HVchCurr_both.png r1 manage 222.0 K 2015-06-01 - 20:41 DaveRobinson  
PNGpng Barrel_leak_current_201112.png r1 manage 29.9 K 2012-02-27 - 15:36 SteveMcMahon  
Unknown file formateps Barrel_log_2011end_2.eps r1 manage 30.8 K 2012-03-22 - 11:39 SteveMcMahon  
PDFpdf Barrel_log_2011end_2.pdf r1 manage 26.2 K 2012-03-22 - 11:39 SteveMcMahon  
PNGpng Barrel_log_2011end_2.png r1 manage 30.1 K 2012-03-22 - 11:39 SteveMcMahon  
JPEGjpg ClusterSizevsIncidenceAngleInSCT.jpg r1 manage 54.1 K 2009-12-12 - 17:44 SteveMcMahon  
PDFpdf ClusterSizevsIncidenceAngleInSCT.pdf r2 r1 manage 77.9 K 2009-12-12 - 16:33 SteveMcMahon  
PNGpng ECA_HVchCurrent_both.png r1 manage 174.0 K 2015-06-01 - 20:41 DaveRobinson  
PNGpng ECC_HVchCurrent_both.png r1 manage 167.1 K 2015-06-01 - 20:41 DaveRobinson  
GIFgif Error1.gif r1 manage 37.7 K 2011-05-20 - 13:21 SteveMcMahon  
GIFgif Error2.gif r1 manage 48.2 K 2011-05-20 - 13:25 SteveMcMahon  
GIFgif FSI1.gif r1 manage 107.2 K 2011-05-20 - 13:35 SteveMcMahon  
PNGpng HitPatternOffset.png r1 manage 33.2 K 2015-06-01 - 20:55 DaveRobinson  
JPEGjpg LAInSCTWithCollisions.jpeg.jpg r1 manage 48.5 K 2009-12-12 - 17:07 SteveMcMahon  
PNGpng LeakCurrentDistribution_2012End.png r2 r1 manage 179.6 K 2013-02-22 - 13:56 SteveMcMahon  
PNGpng LeakCurrent_2010_2012.png r1 manage 80.6 K 2013-02-06 - 15:04 SteveMcMahon SCT BAR Leakage current history from 2010 to 2012
GIFgif LimitRateForLinkAsAFunctionOfMu_removed_2.gif r1 manage 40.7 K 2014-09-26 - 11:10 DaveRobinson Rate limit plots for 14TeV and 25ns
PDFpdf LimitRateForLinkAsAFunctionOfMu_removed_2.pdf r1 manage 968.9 K 2014-09-26 - 11:10 DaveRobinson Rate limit plots for 14TeV and 25ns
PNGpng LimitRateForLinkAsAFunctionOfMu_removed_2.png r1 manage 62.2 K 2014-09-26 - 11:10 DaveRobinson Rate limit plots for 14TeV and 25ns
GIFgif LimitRateInModifiedCondensedAsAFunctionOfMu.gif r1 manage 20.4 K 2014-09-26 - 11:10 DaveRobinson Rate limit plots for 14TeV and 25ns
PDFpdf LimitRateInModifiedCondensedAsAFunctionOfMu.pdf r1 manage 224.5 K 2014-09-26 - 11:10 DaveRobinson Rate limit plots for 14TeV and 25ns
PNGpng LimitRateInModifiedCondensedAsAFunctionOfMu.png r1 manage 36.4 K 2014-09-26 - 11:10 DaveRobinson Rate limit plots for 14TeV and 25ns
JPEGjpg LorentzAngleInSCTWithBeam.jpg r1 manage 48.5 K 2009-12-12 - 17:22 SteveMcMahon  
PDFpdf LorentzAnglesInSCTwithCollisions.pdf r1 manage 73.8 K 2009-12-12 - 09:19 SteveMcMahon  
Unknown file formateps MD20121205_B3_z.eps r1 manage 561.4 K 2013-08-15 - 16:13 DaveRobinson  
PDFpdf MD20121205_B3_z.pdf r1 manage 303.3 K 2013-08-15 - 16:13 DaveRobinson  
PNGpng MD20121205_B3_z.png r1 manage 147.2 K 2013-08-15 - 16:15 DaveRobinson  
Unknown file formateps MD20121205_LC_Barrel.eps r1 manage 2818.9 K 2013-08-15 - 16:01 DaveRobinson  
PDFpdf MD20121205_LC_Barrel.pdf r1 manage 355.4 K 2013-08-15 - 16:01 DaveRobinson  
PNGpng MD20121205_LC_Barrel.png r1 manage 151.6 K 2013-08-15 - 16:01 DaveRobinson  
Unknown file formateps MD20121205_LC_Endcap.eps r1 manage 3143.9 K 2013-08-15 - 16:04 DaveRobinson  
PDFpdf MD20121205_LC_Endcap.pdf r1 manage 384.3 K 2013-08-15 - 16:04 DaveRobinson  
PNGpng MD20121205_LC_Endcap.png r1 manage 188.2 K 2013-08-15 - 16:04 DaveRobinson  
Unknown file formateps MD20121205_Temp_Barrel.eps r1 manage 3464.3 K 2013-08-15 - 16:07 DaveRobinson  
PDFpdf MD20121205_Temp_Barrel.pdf r1 manage 457.3 K 2013-08-15 - 16:07 DaveRobinson  
PNGpng MD20121205_Temp_Barrel.png r1 manage 240.7 K 2013-08-15 - 16:07 DaveRobinson  
Unknown file formateps MD20121205_Temp_Endcap.eps r1 manage 3226.1 K 2013-08-15 - 16:08 DaveRobinson  
PDFpdf MD20121205_Temp_Endcap.pdf r1 manage 387.4 K 2013-08-15 - 16:08 DaveRobinson  
PNGpng MD20121205_Temp_Endcap.png r1 manage 202.0 K 2013-08-15 - 16:08 DaveRobinson  
Unknown file formateps ModOut.eps r1 manage 16.6 K 2013-08-21 - 17:32 DaveRobinson  
PDFpdf ModOut.pdf r1 manage 29.3 K 2013-08-21 - 17:32 DaveRobinson  
PNGpng ModOut.png r1 manage 20.9 K 2013-08-21 - 17:32 DaveRobinson  
PNGpng ModuleTimingFit.png r1 manage 41.3 K 2015-06-01 - 20:48 DaveRobinson Typical timing curve for a module
Unknown file formateps NoisyStripsMon.eps r1 manage 15.4 K 2013-08-21 - 17:49 DaveRobinson  
PDFpdf NoisyStripsMon.pdf r1 manage 34.8 K 2013-08-21 - 17:49 DaveRobinson  
PNGpng NoisyStripsMon.png r1 manage 22.2 K 2013-08-21 - 17:49 DaveRobinson  
Unknown file formateps OneSide_with_nBad.eps r1 manage 12.7 K 2013-09-02 - 14:07 DaveRobinson  
PDFpdf OneSide_with_nBad.pdf r1 manage 15.4 K 2013-09-02 - 14:07 DaveRobinson  
PNGpng OneSide_with_nBad.png r1 manage 34.2 K 2013-09-02 - 14:07 DaveRobinson  
PDFpdf SCT-summaryeff-SCTB.18.12.09.pdf r1 manage 13.2 K 2009-12-18 - 10:40 SteveMcMahon  
PNGpng SCT-summaryeff-SCTB.18.12.09.png r1 manage 16.7 K 2009-12-18 - 10:40 SteveMcMahon  
PNGpng SCT-summaryeff-SCTB.png r1 manage 16.2 K 2009-12-12 - 16:57 SteveMcMahon  
PDFpdf SCT-summaryeff-SCTEA.18.12.09.pdf r1 manage 14.6 K 2009-12-18 - 10:41 SteveMcMahon  
PNGpng SCT-summaryeff-SCTEA.18.12.09.png r1 manage 18.7 K 2009-12-18 - 10:41 SteveMcMahon  
PDFpdf SCT-summaryeff-SCTEC.18.12.09.pdf r1 manage 14.7 K 2009-12-18 - 10:41 SteveMcMahon  
PNGpng SCT-summaryeff-SCTEC.18.12.09.png r1 manage 18.8 K 2009-12-18 - 10:41 SteveMcMahon  
PDFpdf SCTBarrel-eff-APPROVAL2011.pdf r1 manage 13.9 K 2011-04-14 - 14:10 SteveMcMahon  
PNGpng SCTBarrel-eff-APPROVAL2011.png r1 manage 24.6 K 2011-04-14 - 14:10 SteveMcMahon  
Postscriptps SCTBarrel-eff-APPROVAL2011.ps r1 manage 9.1 K 2011-04-14 - 14:09 SteveMcMahon  
PDFpdf SCTConfigurationMay2010.pdf r1 manage 228.7 K 2010-05-31 - 10:38 SteveMcMahon  
PDFpdf SCTEndcapA-eff-APPROVAL2011.pdf r1 manage 14.9 K 2011-04-14 - 14:10 SteveMcMahon  
PNGpng SCTEndcapA-eff-APPROVAL2011.png r1 manage 27.8 K 2011-04-14 - 14:11 SteveMcMahon  
Postscriptps SCTEndcapA-eff-APPROVAL2011.ps r1 manage 11.8 K 2011-04-14 - 14:10 SteveMcMahon  
PDFpdf SCTEndcapC-eff-APPROVAL2011.pdf r1 manage 14.8 K 2011-04-14 - 14:10 SteveMcMahon  
PNGpng SCTEndcapC-eff-APPROVAL2011.png r1 manage 27.7 K 2011-04-14 - 14:11 SteveMcMahon  
Postscriptps SCTEndcapC-eff-APPROVAL2011.ps r1 manage 11.8 K 2011-04-14 - 14:10 SteveMcMahon  
GIFgif SCTOcc.GIF r1 manage 28.5 K 2011-05-20 - 13:45 SteveMcMahon  
JPEGjpg SCTOcc.JPG r1 manage 58.1 K 2011-05-20 - 13:41 SteveMcMahon  
GIFgif SCTRateLimitations.GIF r1 manage 12.8 K 2011-06-20 - 22:11 SteveMcMahon  
PDFpdf SCTSingleHitEfficiencyWithBeam.pdf r1 manage 15.8 K 2009-12-12 - 09:13 SteveMcMahon  
GIFgif SCT_NStripPerModuleLogLog900GeV.gif r1 manage 13.4 K 2010-03-16 - 11:56 SteveMcMahon  
JPEGjpg SCT_NStripPerModuleLogLog900GeV.jpg r1 manage 27.5 K 2010-03-16 - 11:56 SteveMcMahon  
JPEGjpg Sample.JPG r1 manage 75.8 K 2010-05-31 - 10:43 SteveMcMahon  
GIFgif Timing1.gif r1 manage 30.9 K 2011-05-20 - 13:29 SteveMcMahon  
Unknown file formateps Tmean_5days.eps r1 manage 2517.6 K 2013-08-15 - 16:11 DaveRobinson  
PDFpdf Tmean_5days.pdf r1 manage 326.1 K 2013-08-15 - 16:11 DaveRobinson  
PNGpng Tmean_5days.png r1 manage 139.9 K 2013-08-15 - 16:11 DaveRobinson  
Unknown file formateps barrel_occupancy.eps r1 manage 17.4 K 2013-11-19 - 13:30 DaveRobinson Barrel occupancy vs pileup
PDFpdf barrel_occupancy.pdf r1 manage 20.0 K 2013-11-19 - 13:30 DaveRobinson Barrel occupancy vs pileup
PNGpng barrel_occupancy.png r1 manage 16.0 K 2013-11-19 - 13:30 DaveRobinson Barrel occupancy vs pileup
Unknown file formateps cis_current.eps r1 manage 485.7 K 2013-08-15 - 16:16 DaveRobinson  
PDFpdf cis_current.pdf r1 manage 244.2 K 2013-08-15 - 16:16 DaveRobinson  
PNGpng cis_current.png r1 manage 119.4 K 2013-08-15 - 16:16 DaveRobinson  
Unknown file formateps cis_current_Hamamatsu-CiS.eps r1 manage 438.0 K 2013-08-15 - 16:18 DaveRobinson  
PDFpdf cis_current_Hamamatsu-CiS.pdf r1 manage 207.0 K 2013-08-15 - 16:18 DaveRobinson  
PNGpng cis_current_Hamamatsu-CiS.png r1 manage 81.0 K 2013-08-15 - 16:18 DaveRobinson  
Unknown file formateps data11_LAPlot.eps r1 manage 10.2 K 2012-03-11 - 22:09 SteveMcMahon  
GIFgif data11_LAPlot.gif r1 manage 10.4 K 2012-03-11 - 22:09 SteveMcMahon  
PDFpdf data11_LAPlot.pdf r1 manage 14.3 K 2012-03-11 - 22:09 SteveMcMahon  
PNGpng data11_LAPlot.png r1 manage 15.0 K 2012-03-11 - 22:14 SteveMcMahon  
Unknown file formateps dataAndMC_LAPlot.eps r1 manage 11.1 K 2012-03-11 - 22:09 SteveMcMahon  
GIFgif dataAndMC_LAPlot.gif r1 manage 12.1 K 2012-03-11 - 22:10 SteveMcMahon  
PDFpdf dataAndMC_LAPlot.pdf r1 manage 14.6 K 2012-03-11 - 22:15 SteveMcMahon  
PNGpng dataAndMC_LAPlot.png r1 manage 17.6 K 2012-03-11 - 22:10 SteveMcMahon  
PDFpdf incidentAngle_vs_nStrips_DataVsMc_side0.pdf r1 manage 27.9 K 2012-03-11 - 22:16 SteveMcMahon  
PNGpng incidentAngle_vs_nStrips_DataVsMc_side0.png r1 manage 26.9 K 2012-03-11 - 22:10 SteveMcMahon  
Unknown file formateps incidentAngle_vs_nStrips_DataVsMc_side1.eps r1 manage 30.0 K 2012-03-11 - 22:25 SteveMcMahon  
PDFpdf incidentAngle_vs_nStrips_DataVsMc_side1.pdf r1 manage 28.0 K 2012-03-11 - 22:11 SteveMcMahon  
PNGpng incidentAngle_vs_nStrips_DataVsMc_side1.png r1 manage 26.4 K 2012-03-11 - 22:11 SteveMcMahon  
Unknown file formateps incidentAngle_vs_nStrips_side0.eps r1 manage 18.7 K 2012-03-11 - 22:23 SteveMcMahon  
PDFpdf incidentAngle_vs_nStrips_side0.pdf r1 manage 21.0 K 2012-03-11 - 22:11 SteveMcMahon  
PNGpng incidentAngle_vs_nStrips_side0.png r1 manage 23.6 K 2012-03-11 - 22:12 SteveMcMahon  
Unknown file formateps incidentAngle_vs_nStrips_side1.eps r1 manage 18.7 K 2012-03-11 - 22:24 SteveMcMahon  
PDFpdf incidentAngle_vs_nStrips_side1.pdf r1 manage 21.0 K 2012-03-11 - 22:12 SteveMcMahon  
PNGpng incidentAngle_vs_nStrips_side1.png r1 manage 23.2 K 2012-03-11 - 22:12 SteveMcMahon  
GIFgif leak_current_20110814.GIF r1 manage 43.6 K 2011-09-30 - 11:30 SteveMcMahon  
Unknown file formateps leak_current_20110814_log.eps r1 manage 25.0 K 2011-09-30 - 11:19 SteveMcMahon  
PDFpdf leak_current_20110814_log.pdf r1 manage 25.8 K 2011-09-30 - 11:19 SteveMcMahon  
Unknown file formateps noise_166544-216516.eps r1 manage 495.1 K 2013-08-16 - 13:47 DaveRobinson  
PDFpdf noise_166544-216516.pdf r1 manage 251.6 K 2013-08-16 - 13:47 DaveRobinson  
PNGpng noise_166544-216516.png r1 manage 113.4 K 2013-08-16 - 13:47 DaveRobinson  
Unknown file formateps noise_166544-216516_log.eps r1 manage 3134.5 K 2013-08-16 - 13:50 DaveRobinson  
PNGpng noise_166544-216516_log.png r1 manage 123.4 K 2013-08-16 - 13:48 DaveRobinson  
Unknown file formateps noise_Barrel_216516.eps r1 manage 3364.4 K 2013-08-16 - 13:43 DaveRobinson  
PDFpdf noise_Barrel_216516.pdf r1 manage 407.5 K 2013-08-16 - 13:43 DaveRobinson  
PNGpng noise_Barrel_216516.png r1 manage 179.8 K 2013-08-16 - 13:43 DaveRobinson  
Unknown file formateps noise_EC_166544.eps r1 manage 3542.6 K 2013-08-16 - 13:35 DaveRobinson  
PDFpdf noise_EC_166544.pdf r1 manage 435.5 K 2013-08-16 - 13:34 DaveRobinson  
PNGpng noise_EC_166544.png r1 manage 230.6 K 2013-08-16 - 13:35 DaveRobinson  
Unknown file formateps noise_EC_216516.eps r1 manage 3495.0 K 2013-08-16 - 13:30 DaveRobinson  
PDFpdf noise_EC_216516.pdf r1 manage 429.0 K 2013-08-16 - 13:30 DaveRobinson  
PNGpng noise_EC_216516.png r1 manage 227.6 K 2013-08-16 - 13:30 DaveRobinson  
Unknown file formateps noise_gain.eps r1 manage 2087.4 K 2013-08-16 - 13:26 DaveRobinson  
PDFpdf noise_gain.pdf r1 manage 274.3 K 2013-08-16 - 13:26 DaveRobinson  
PNGpng noise_gain.png r1 manage 168.4 K 2013-08-16 - 13:26 DaveRobinson  
Unknown file formateps noise_glass.eps r1 manage 441.1 K 2013-08-16 - 13:22 DaveRobinson  
PDFpdf noise_glass.pdf r1 manage 209.4 K 2013-08-16 - 13:21 DaveRobinson  
PNGpng noise_glass.png r1 manage 130.6 K 2013-08-16 - 13:21 DaveRobinson  
PNGpng noise_noise_10PtGain.png r1 manage 102.9 K 2015-06-01 - 20:41 DaveRobinson  
GIFgif tbinhitmaps_142195_approved.gif r1 manage 67.3 K 2010-03-16 - 16:55 SteveMcMahon  
GIFgif tbinprofile_142195_approved.gif r1 manage 15.3 K 2010-03-16 - 16:54 SteveMcMahon  
Edit | Attach | Watch | Print version | History: r49 < r48 < r47 < r46 < r45 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r49 - 2018-05-04 - DaveRobinson
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Atlas All webs login

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