1 / 10

MUON Progress : Hitreconstruction.

MUON Progress : Hitreconstruction. Standalone run:. Following few slides are the results of standalone hitrec code presented in dimuon meeting :. Result: Resolution.

damia
Download Presentation

MUON Progress : Hitreconstruction.

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. MUON Progress : Hitreconstruction. Standalone run: Following few slides are the results of standalone hitrec code presented in dimuon meeting :

  2. Result: Resolution • To find out resolution of the dHLT algorithm we select “Gun” option in the config file and fire 500 single particle event towards detection element 700,800….(171<θ <178, φ = 0). • The difference of the geant hit position and reconstructed hit position of a given detection element over all the events gives the resolution. • In some cases we found multi-particle hit and hit at the edge, those events are excluded in filling the resolution histograms x x x x x x x x x x

  3. Result: Resolution Resolution in X direction Resolution in Y direction Resolution in Bending direction ~70 µm Resolution in non bending plane ~ 0.8 mm

  4. Result: Timing and Inefficiency • The “Box” option is chosen to generate 500 central PbPb event of 150 particles over φ = 2*π and 171< θ <178 • Reconstruction timing of the algorithm is shown as a function of DC cut. This timing excludes the filling of ROOT Tree written for Offline analysis. • Inefficiency is calculated as a ratio of the number of geant hits that are missing in reconstruction to the total number of original hits.

  5. Summary • The full chamber geometry, segmentation, mapping (as in AliRoot) for station 4 & 5 has been considered. • The realistic rawdata from AliRoot has been used for reconstruction. • The hit reconstruction time for 150 hits per DDL on a 2 GHz machine is within 2 ms. (now it is around 1.2 ms) • 93% of the rechits are within 100 microns of the geanthit. (now it is ) • The accuracy of hit reconstruction is comparable to that in AliRoot. • Merging of hits between bending and non bending planes have been achieved • The DHLT cluster finder is complete for offline. It would go to HLT module of AliRoot.

  6. Pub-Sub Integration: The main processing element for the pub-sub is carried out by three components, which are data source, data sink and file processor. FilePublisher (Source) AliHLTMUONHitReconstructorComponent (processor) DataWriter (Sink) HLTMUONHitReconstructor.h (Indian and/or Itilian code) In the following slide the sample xml file that has been used to run hitrec part for dHLT

  7. [indra@qgp3 PubSub]$ cat test.xml <?xml version="1.0" encoding="ISO-8859-1"?> <SimpleChainConfig1 ID="SampleConfig1" verbosity="0x3F"> <Node ID="Master" hostname="qgp3.phy.uct.ac.za"/> <Node ID="0" hostname="bambino12.phy.uct.ac.za"/> <Proc ID="FilePub" type="src"> <Cmd>FilePublisher -datafile /home/szostak/HLT/DHLT_SINP_26Sep06/RawData/raw0/MUONTRK_2572.ddl -datafile /home/szostak/HLT/DHLT_SINP_26Sep06/RawData/raw1/MUONTRK_2572.ddl -datafile /home/szostak/HLT/DHLT_SINP_26Sep06/RawData/raw2/MUONTRK_2572.ddl -datatype DDLTRACK -dataorigin DIMU -dataspec 13 -eventtime 100000 </Cmd> <Node>0</Node> <Shm blocksize="4k" blockcount="1024" type="sysv"/> </Proc> <Proc ID="HitRec" type="prc"> <Parent>FilePub</Parent> <Cmd>AliHLTMUONHitReconstructorComponent -ddl 13 -lut /home/szostak/HLT/DHLT_SINP_26Sep06/Lut/Lut12.dat -buspatchmap /home/szostak/HLT/DHLT_SINP_26Sep06/Lut/BusToDetElem.dat </Cmd> <Node>0</Node> <Shm blocksize="4k" blockcount="1024" type="sysv"/> </Proc> <Proc ID="DataWriter" type="snk"> <Parent>HitRec</Parent> <Cmd>EventStorageWriter -storage simplefile TestStorage</Cmd> <Node>0</Node> <Shm blocksize="4k" blockcount="1024" type="sysv"/> </Proc> </SimpleChainConfig1>

  8. I am forwarding you two mails of Artur, which explains the last update of dHLT status in UCT. In the first mail Artur said that there is no memory leak in the run for (Indian hit-rec) + tracking code. But the problem in that large run was that the simulated rawdata files (input data) were not good, that is why one cannot argue convinsily that the hitrec+ tracking is woking correctly. (Please enlarge it) the next mail he told that after using pure J/Psi signal the result in dHLTMonitor confirms the successful implementation of hitrec+ tracker. (Pls enlarge the figures)

  9. AliRoot Integration: Presently the one single version of the HLTMUONHitReconstructor is used for online as well as for offline. Online Offline FilePublisher (Source) HLTMUONHitReconstructor.h (Indian and/or Itilian code) AliHLTMUONHitReconstructorComponent (processor) AliHLTMUONHitReconstructor DataWriter (Sink)

  10. The offline code This class reads rawdata for MUON detector and produces reconstructed hit position as output, which is stored in a root file as tree format. It uses another class HLTMUONHitReconstructor of "../PubSub" to perform the hitreconstruction which is the same as it is used in online hitreconstruction. The output data is of type AliMUONRawCluster same as that of produced in Dimuon reconstruction (i.e MUON.RecPoints.root) The offline code is found in $ALICE_ROOT/HLT/MUON/src/AliRoot.

More Related