Interestingly enough the CSCTF did not trigger on all sectors at the same time from the counters.

Timing Results

Two are the timing studies to be carried on:

• The chamber-by-chamber results → these are reported on Joe's timing analysis twiki page
• Since the ecal trigger is used as baseline we can monitor how the CSCTF behaves w.r.t. ecal trigger by looking at the timing distributions. It was observed that the CSCTF on the downstream endcap (ME+ for beam 2) was early 1/2 bx while on the upstream endcap (ME- for beam 2) was early 2/3 bx. So between run 120015 and run 120020 the upstream endcap was delayed 2 bx (maximum delay allowed by modifying the TTCrx coarse delay). This can be visible in the time shift for the event recorded by the CSCTF for the minus endcap

Show CSCTFTrackTiming Hide CSCTFTrackTiming .

• SECTOR 1:

                RUN 120015                         RUN 120020

→

• SECTOR 2:

                RUN 120015                         RUN 120020

→

• SECTOR 3:

                RUN 120015                         RUN 120020

→

• SECTOR 4:

                RUN 120015                         RUN 120020

→

• SECTOR 5:

                RUN 120015                         RUN 120020

→

• SECTOR 6:

                RUN 120015                         RUN 120020

→

• SECTOR 7:

                RUN 120015                         RUN 120020

→

• SECTOR 8:

                RUN 120015                         RUN 120020

→

• SECTOR 9:

                RUN 120015                         RUN 120020

→

• SECTOR 10:

                RUN 120015                         RUN 120020

→

• SECTOR 11:

                RUN 120015                         RUN 120020

→

• SECTOR 12:

                RUN 120015                         RUN 120020

→

CSCTF Occupancy

• Online DQM Occupancy Plot

.

• OCCUPANCY PLOTS FROM ONLINE DQM:

                RUN 120015                         RUN 120020

→

During run 120015 it is visible the hole due to the lack of VMEp1/8 and VMEp1/9. During the nightly run 120020 a problem with the high voltage happened and it should have been responsible for the lack of data in the minus endcap. This lack is also confirmed by the CSC Summary plots. More details on the HV error occurred are here and here.

• Local TF DQM Occupancy Plot

Show CSCTFLocalDQMOccupancy Hide CSCTFLocalDQMOccupancy

• OCCUPANCY PLOTS FROM LOCAL TF DQM:

                RUN 120020 (ME+)                         RUN 120020 (ME-)

→

It seems we are getting a strange pattern for the occupancy which is sort of confirmed by the CSC Summary plots, e.g. the segment distribution:

It is not clear to me the reason why, maybe it is due to the chamber decision making when the chambers is full of LCTs.

Interesting Links:

• Darin's blog: http://cmsdoc.cern.ch/cms/performance/FirstBeam/cms-e-commentary09.htm
• Michael Schmitt's presentation: http://indico.cern.ch/getFile.py/access?subContId=1&contribId=0&resId=1&materialId=slides&confId=73558
• Andy Kubik's CSC Summary page:
  • run 120015: http://cms-project-csc-validation.web.cern.ch/cms-project-csc-validation/run120015/beamhalo/Site/Summary.html
  • run 120020: http://cms-project-csc-validation.web.cern.ch/cms-project-csc-validation/run120020/beamhalo/Site/Summary.html

-- GianPieroDiGiovanni - 08-Nov-2009