90 likes | 243 Views
ACORDE Status Report. ALICE Offline Week Mario Rodríguez Cahuantzi Nov. 15th 2010. Outline. ACORDE Survey & Alignment - Method - Residuals - Removing Overlaps - Aligment Aware ACORDE - DQM. ACORDE Survey Alignment: Method.
E N D
ACORDE Status Report • ALICE Offline Week • Mario Rodríguez Cahuantzi • Nov. 15th 2010
Outline • ACORDE Survey & Alignment • - Method • - Residuals • - Removing Overlaps • - Aligment Aware • ACORDE - DQM
ACORDE Survey Alignment: Method We find the angles between the ideal mid planes and the straight line by module. We also check the ideal midplane. And the survey average mid planes and the residuals are ~ 0.001 degress (almost negligible). As we can see, the mean angle ~ 0.075 , thus we have to correct in at least one degree.
ACORDE Survey Alignment: Overlaps We had over 60 overlaps after the alignment correction, mainly from the support and the modules in the end we found a small bug in the height of the support and we corrected the error was around 1 cm, we checked again all the geometry no overlaps found. We also modified the values of the means for the following macros and find no overlaps. We put some realistic values. ACORDEFullMissalignment.cxx ACORDEResidualMissalignmnet.cxx
ACORDE Survey Alignment: Alignment aware reconstruction and simulatio In our case, for the simulation there was nothing to do since ACORDE is a hit’s detector (the module is fired or not). For reconstruction we generated a particle just above the edge of the scintillator and reconstructed with the missaligned/aligned geometry, we can see how the hits per module appears in one and not in the other aligned geometry. Hits without alignment X Y 360.03 872.898 360.03 870.07 Hits with alignment X Y 360.03 876.106 360.03 873.206
ACORDE - DQM • The ACORDE - DQM is set according to the QA AMORE agent. • The DQM-plots depend of the types of trigger: • Single: when at least one module is fired. • Multi: when at least two modules (or more) are fired. • The plots are divided into 2 groups corresponding each one to the trigger class programmed by the electronic. Plot 1 (top, left side): ACORDE scinitillator module activity (SINGLE muon mode). Each bin corresponds to one ACORDE module. We have 60 scintillator modules. Warnings: a) Any bin appears empty (PMT broken) Error: >= 5 bins empty b) Any bin appears "very high" respect to the others (PMT broken or FEE card open) Plot 2 (top, right side): ACORDE scinitillator module activity (MULTI muon mode). Each bin corresponds to one ACORDE module. We have 60 scintillator modules. Warnings: a)Any bin appears empty (PMT broken) Error:>= 5 bins empty b) Any bin appers "very high" respecto to the others (PMT borken of FEE card open) Plot 3(bottom, left side): ACORDE modules hit, per event (SINGLE muon mode). If we have an entry in bin=30, means that 30 ACORDE modules were fired, in one event. NOTE: Better in log scale. Plot 4 (bottom, right side): Same as plot 3, Multi muon mode. NOTE: Better in log scale if both histograms (plots 3 & 4) show high multiplicity events for the ACORDE fired modules, the shifter has to make emphasis of this situation in DQM-ACO and report to the ACORDE expert. Warnings: a) if all the bins are empty: Fatal error-> report immediately to the ACORDE expert.
ACORDE - DQM Work in progress under modifications on QA for ACORDE (almost done) -> Once finished it will be commited to the AliRoot trunk • Up to now, the current information available should be enought: • For p-p and Pb-Pb runs, we have to put attention at the multiplicity in ACORDE modules. • Per module, we only have hits.
Final remarks • Survey & Alignment Task are done: not commited jet, code under debugging • DQM update required is in progress: to be commited (for PbPb runs upt to now, ACORDE-DQM is enought). • For further comments mailto: • Pedro Podesta <pedro.podesta@cern.ch> • Arturo Fernández <afernan@mail.cern.ch>