Status of the analysis by the analysis team!

Join the stimulus Last meeting we were in a deep crisis… and we decided to sign a stimulus plan! We organized a one-week workshop and we successfully restarted the engine. Now we should keep the pace in view of the new beam campaigns and on…

A word about the workshop Apr 20 --> Apr 24 in DESY 11 participants. Not too many but very effective! Four different goals: 1.Basic tutorial for normal users 2.Advanced tutorial for power users 3.Get user involved 4.Task share and ToDo list. All very successfully accomplished!

Important tasks Analysis robots –Make the analysis submission so stupid that even a robot can do it! Pre-inclusion of M26 –Prepare a M26DataGenerator and then test the rest of the analysis chain Improve the DUT integration and plots Finish up the analysis

pysub A set of python scripts (Object Oriented) almost fool proof! –Check input file –Generate steering file from a template –Run Marlin –Check the output file Leave to the user just a limited freedom: stable and working configuration Run in the same way on the local PC or on the GRID! myjob-status.py submit-align.py submit-clusearch.py submit-converter.py submit-eta.py submit-filter.py submit-fitter.py submit-hitmaker.py submit-native-copy.py submit-pedestal.py

Automatic alignment? Alignment is not like pedestals. –It is very hard to make it a blind procedure, but… Our procedure (Mille + Pede) is working with both high (>7 tracks) and low multiplicity. –Low multiplicity can be easily almost-automatized –High multiplicity more critical but if you have a similar LM run, it’s easy!

Semi-auto with LM Clear peak on the backgroud. Definition of “residual cuts” (human intervention). Complete background removal.

Where is the peak? With HM data the peak is well behind the combinatorial background! It is impossible to define residual cuts!

A needle in a haystack Can you use the same residual cuts of the LM? If the answer is yes, it means the telescope didn’t move in between, then you can go straight to the second iteration. But the number of track candidates is much higher and the number of loops is increasing more than exponentially! Brute force approach –Split the input file in several chunks, –Run on the GRID in parallel –Sum up the statistics! Best approach –Further optimize the code –Get a smart idea!

Some 15 days later… 30 jobs x 1000 evt. X 43 sec = days But running on 30 CPUs it boils done to ~12 hours that is still a lot but reasonable! Single runMerged statistics

And if I was wrong? How do I know if the residual cuts taken from the LM are good also for the HM? –Make a test setting residual cuts wrong on purpose (out of 100 um). The residual distributions on other sensors is absolutely flat! Conclusion: always check histos!

And if I don’t have a LM? You always have LM! –In a HM you can always find few events with a single track. Use them only! –Very time consuming because you need to go through the full statistics to find the residual cuts and then go back again for the real alignment. Conclusion: always take a LM! Question: do we really need HM?

Is the alignment stable? Slice down a 220k events in group of 5k (44 jobs) The blue region is the value obtained by considering the full sample Similar behavior on y, more flat on phy. 1k events ~ 24 minutes wall clock. Question: are those fluctuations important?

Test the fluctuations Do the track fitting over the 220k statistics using: a)Only one alignment constant set b)One alignment constants every 25k events (~ 2 hours) Conclusion: the difference is almost negligible. But it costs nothing! It is probably more important with M18

Does the resolution degrade with HM? Compare the residual widths in DUT mode on a LM and HM A bit worse resolution, probably due to a not perfect alignment. ~100 times slower processing for HM.

Does the resolution degrade removing one plane? It is to say, allowing the fitter to reconstruct using also 4 points? Motivation: since we are running asynchronously not all planes are capturing the same particles (but one). So the number of reco tracks is much higher if you allow at least missing hit.

Conclusion In 1.5 months we did really a lot partially recovering the “lost” time. We got a lot of momentum we should try to maintain if not increase. We are ready for the next test beam and on the good track for the M26.

Last slide Thank you all