History of all problematic towers and current status
updated based on MIP reco with L3 tracks done by Piotr for eta bins[4-12], June 20-03 (JB)

Subsector 05A
Subsector 05B
Subsector 05C
05TC07
anal=use it for now
fires too often for pi0 reco, JB April 03
05TC12=bad
anal=off
no LED spectra -- marked bad tube in DB, 4/22/03, RF
ped OK, double ped seen, no signal, HV setH, 4/25/03 JB
no L3 MIP for day120-124, 6/20/03, PZ
Subsector 05D
05TD04=bad
anal=off
no LED spectra -- marked bad tube in DB
Why does slope in first setE.dat files looks fine?, 4/22/03, RF
ped OK, double ped seen, no signal, HV setH, 4/25/03 JB
no L3 MIP for day120-124, 6/20/03, PZ
05TD10=bad
anal=off
no LED spectra -- marked bad tube in DB, 4/22/03, RF
ped OK, double ped seen, no signal, HV setH, 4/25/03 JB
no L3 MIP for day120-124, 6/20/03, PZ
Subsector 05E

Subsector 06A
06A07
anal=use
trig=?
marked at bad tube in DB but showed LED response
as well as slope in first setE.dat file. HV set
by calculation from first setE slope, 4/22/03, RF
HV setH, 4/25/03, has grounded 2 lower bits, JB
reasonable L3 MIP for day120-124, 6/20/03, PZ
06A12=bad
anal=off
no LED spectra -- marked bad tube in DB, 4/22/03, RF
ped OK, double ped seen, no signal, HV setH, 4/25/03 JB
no L3 MIP for day120-124, 6/20/03, PZ
Subsector 06B
06B04=bad
anal=off
no LED spectra -- marked bad tube in DB, 4/22/03, RF
ped OK, double ped seen, no signal, HV setH, 4/25/03 JB
no L3 MIP for day120-124, 6/20/03, PZ
Subsector 06C
06C09=bad
anal=off
ped OK, double ped seen, no signal HV setH & setDefault, 4/25/03 JB
no L3 MIP for day120-124, 6/20/03, PZ
Subsector 06D
Subsector 06E
06D04=still good 1% of entries has ADC=32, the spectrum look normal. It is below HT threshold so the tube is stll fine, 4-1-03, JB

Subsector 07A
Subsector 07B
07B09=bad
anal=off
no LED spectra -- WAS FINE in Au-D running, 4/22/03, RF
ped OK, double ped seen, no signal, HV setH, 4/25/03 JB
no L3 MIP for day120-124, 6/20/03, PZ
Subsector 07C
07TC07
anal=use it for now
fires too often for pi0 reco, JB April 03
Subsector 07D
07D08=bad
anal=off
no LED spectra -- marked bad tube in DB, 4/22/03, RF
ped OK, double ped seen, no signal, HV setH, 4/25/03 JB
no L3 MIP for day120-124, 6/20/03, PZ
Subsector 07E

Subsector 08A
Subsector 08B
08TB02=good Good LED spectra but marked bad tube in DB and shows bad slope in both setE files., 4/22/03, RF
if gain is set to 0 in the offline DB, slope is not calculated.
Now spectrum looks fine, ped is OK. I'll use this tower, HV setH, 4/25/03, JB
08TB07
anal=use for now
trig=?
Good LED spectra and reasonable slope in first setE.dat file. HV set using slope from first setE.dat file. , 4/22/03, RF
Tower has grounded 2 lower bits bits and spectrom has only pedestal and high double pedestal . HV setH, 4/25/03 JB
suspicious L3 MIP for day120-124, 6/20/03, PZ
Subsector 08C
Subsector 08D
08TD04=bad
anal=off
Good LED spectra but shows bad slopes in each setE.dat files but not marked as bad tube in DB, 4/22/03, RF
Spectrum is almost empty , looks like broken FEE channel or negative pedestaland only double pedestal visible . HV setH, 4/25/03 JB
no L3 MIP for day120-124, 6/20/03, PZ
08TD08=bad
anal=off
Good LED spectra but not responsive to HV change. Set back to HV in original source q files, 4/22/03, RF
ped OK, double ped seen, no signal, HV setH, 4/25/03 JB
no L3 MIP for day120-124, 6/20/03, PZ
08D09
anal=use for now
trig=off
spectrum looks fine, but large ADC apear too often. It kills the HT trigger, HV set H was 747 V, 4-1-03, JB
suspicious L3 MIP for day120-124, 6/20/03, PZ
Subsector 08E
08E04
anal=off
trig=off
spectrum looks fine, but large ADC apear too often. It kills the HT trigger, HV set H was 1152 V, 4-1-03, JB
fires too often for pi0 reco, JB April 03
08TE12=bad
anal=off
Good LED spectra and ok slope in first setE.dat file. Bad slope in second setE.dat files. Used first slope to set HV. 4/22/03, RF
ped OK, double ped seen, no signal, HV setH, 4/25/03 JB
no L3 MIP for day120-124, 6/20/03, PZ

Use the folowwing script to inspect spectra:

 
pedHist ( int sec=5, char sub='A'){
  gStyle->SetOptStat(1111111);
  char *name="outH.hist.root";

  TFile *f=new TFile(name);
  TCanvas *c=new TCanvas("bb","ccc",800,800);
  c->Divide(3,4);

  int mxPseudo=12,k;
  int ic=0;
  for(k=1;k<=mxPseudo;k++) { // pseudorapidity
    char tt1[100];
    sprintf(tt1,"%2.2dT%c%2.2dc%d",sec,sub,k,ic);
    c->cd(k);
    TH1F* h= (TH1F*) f->Get(tt1);
    h->Draw();
    h->SetAxisRange(0,100);
    gPad->SetLogy();
  }
}


minb trig Apr1/run2 subsec 6TE: #4- chan 32 fires too often

minb trig Apr1/run2 subsec 8TD: #9-noisy, #4-dead or negative pedestal, #8-dead

minb trig Apr1/run2 subsec 8TE: #4-noisy, #12- dead