1 / 6

Summary of recent MET discussions

Summary of recent MET discussions. Our proposal for MET Goodness on the next 4 slides

yvonne
Télécharger la présentation

Summary of recent MET discussions

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. Summary of recent MET discussions • Our proposal for MET Goodness on the next 4 slides • We have discussed this during the week with Donatella, Silvia (the 2 main EtMiss reconstruction developers), Richard Teuscher, Adam, Jet (the last 2 being developers of the MET performance and MET D3PD classes) • Positive feedback everywhere, a few issues came up (overlap with general (jet) cleaning group in Jet/EtMiss CP area), although I had the feeling our proposal was hijacked a bit, and we are now going to also contribute to direct preparations for the 900-GeV data analysis • Which is good, of course • And also need to organise a discussion how to do this data cleaning / cosmics and beam background rejection in sync with the rest of the Jet/EtMiss group • I think eventually this means we take some variables from somewhere else, from tools other people have already written, or we apply cuts other people have optimised • To settle on this we will try to start an email discussion with the O(15) involved people in the Jet/EtMiss group

  2. EtMiss Goodness Basic Idea • Combine selected variables in a data object that allow to assess the quality of EtMiss in the event, and most importantly offer the analysis users the possibility to apply a set of quality cuts and use EtMiss only if these cuts are passed • Our main idea was to inject a concept that allows the EtMiss experts to validate step-by-step, as planned, and communicate the current state of understanding at any given time via the EtMissGoodness object to the analysis users JO part (set and locked centrally, can be overwritten by user like below): EtMissGoodness.CutSet(“tight”) # or loose or medium or more complicated EtMissGoodness.MET(“MET_Final”) EtMissGoodness.JetAlg(“AntiKt4TopoJets”) Per event: If( EtMissGoodness::isMETGood() ) { float met = EtMissGoodness::met(); float sumet = EtMissGoodness::sumet(); if(met > m_MetSusyCut) histogram->Fill( met ); // … }

  3. EtMiss Goodness Variables

  4. EtMiss Goodness Technicalities • Majority of proposed variables are available on AOD level, some (connected to cells) require ESDs • Either EtMiss Goodness is completely transient and bound to be run on AODs only, or it is run at the ESD stage and bit masks are persistified • Mind you: if D3PDs shall be supported, similar arguments hold true. Either all variables we plan to cut on are in the D3PDs, or we persistify bit masks so that people can apply cuts also on D3PDs • The MET performance package was suggested as location for this, since a lot of the variables are already used here • However this would mean that MET performance algorithms have to be run whenever the user wants to access the goodness • Not ideal • If it would still be preferred, wouldn’t it be ideal if this was run as part of the central reconstruction, e.g. in the monitoring job? • The studies to find cut ranges are the hard part, it would be crucial to have all variables we want to study in D3PDs • We are willing to help and add D3PD maker classes for this purpose • In fact what is the general plan in the EtMiss data prep group? Plan on using D3PDs, or dESD / perf. DPDs? • There are a few variables we came up with that aren’t yet part of the MET performance package, these we plan to add shortly • MuonSpShower for jet punch throughs • Dead-cell fraction of lead jets

  5. EtMiss Goodness Rough Plan • One aspect is the pure technical one of gathering the variables, wrapping a UserData object around them, and implementing the possibility to define cut sets • The hard part will be the validation of the different cuts to define ‘safe’ regions for EtMiss • The time schedule of course isn’t so clear given it is late in the year, but we would come up with a cut set based on current knowledge (cosmics, Monte Carlo), and devise this while we go along • With data, we would first apply run selection / data quality cuts, then process different samples for different purposes (minbias, cosmics, random, jet stream) , maybe with some additional cuts (selection certain final states) • 2 approaches, compare 2 different samples to derive cuts (cosmics with collision data), and compare data with simulation • The latter will typically require to make comparison plots data/MC and vary cuts until some understanding can be demonstrated by agreement between data and MC • First steps chronologically: • Run selection, DQ selection, bad channels, noise treatment • Make sure MET is Gaussian in minbias and jet data • MET resolution of EM scale, cell based and topo based (maybe in different versions corresponding to different sigma criteria), compared to simulations • Explore cut parameter space in reasonable limits to reach some degree of agreement • Update cut settings accordingly for reprocessing of data

  6. EtMiss data preparation / access • Sucked a little bit into this now that it turns out the EtMiss folks are pretty ignorant of how they might access the 900 GeV data, and how they organise themselves to get things done quickly in December • So we are putting in our team knowledge to explore how we might do this, maybe also team resources to dump the 900 GeV data to D3PDs quickly Started exploring how we fit into this scheme with our EtMiss needs…

More Related