User Tools

Site Tools


davinci:samples

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
davinci:samples [2009/03/03 11:32] decianmdavinci:samples [2009/07/02 14:45] (current) decianm
Line 1: Line 1:
-====== Particle Samples ======+====== Particle Samples (DC06) ====== 
 ===== Idea ===== ===== Idea =====
 To perform an analysis in DaVinci, several types of samples can be used, which represent tighter or looser restrictions to the selection of the particles. To perform an analysis in DaVinci, several types of samples can be used, which represent tighter or looser restrictions to the selection of the particles.
Line 48: Line 49:
   * Pion     : det='RICH' DLL(pi/K)  > -5   * Pion     : det='RICH' DLL(pi/K)  > -5
  
-  Containers: +Containers: 
   * "/Event/Phys/StdDC06TightMuons"   * "/Event/Phys/StdDC06TightMuons"
   * "/Event/Phys/StdDC06TightElectrons"   * "/Event/Phys/StdDC06TightElectrons"
Line 55: Line 56:
   * "/Event/Phys/StdDC06TightPions"   * "/Event/Phys/StdDC06TightPions"
  
-<code>  +===== Photons =====
-  <b>Photons</b> +
-  (Cnv)PhotonParticlemaker is used. +
-    - non-converted photons: "/Event/Phys/StdDC06LoosePhotons" +
-    - converted photons:     "/Event/Phys/StdDC06LooseCnvPhotons" +
-    - all photons:           "/Event/Phys/StdDC06LooseAllPhotons" +
- * +
-  @see PhotonParticleMaker +
-  @see CnvPhotonParticleMaker +
- * +
-  The configuration file for "StandardDC06" particles, created "on-demand" +
- *  +
-  There are a set of StandardDC06 basic particle, StandardDC06 Pi0s and a set +
-  of StandardDC06 intermediate states: D0, Ds, D*, J/psi, K*, Phi. +
-   +
-  The relevant algorithms are fired on demand when one wants to read +
-  their outputlocation. See the relevant options for a complete list. +
- * +
-  The cuts coded in this version are 'just a little tighter' than the  +
-  ones applied in the exclusive HLT (with the big exception that PID is used +
-  here but not in the HLT). So hopefully events selected using these particles  +
-  should also pass HLT. This has not been tested. +
- * +
-  The actual definition of the cuts should be defined by the physics WG +
-  for the DC06 stripping. The present first import should be taken as an example +
-  more definitions of 'Tight' 'Looser' or 'NoPID' intermediate states could +
-  be provided if needed. +
- * +
-</code>+
  
-Comment on CombinedParticleMaker and exclusive selection:\+(Cnv)PhotonParticlemaker is used. 
 +  * non-converted photons"/Event/Phys/StdDC06LoosePhotons" 
 +  * converted photons:     "/Event/Phys/StdDC06LooseCnvPhotons" 
 +  * all photons:           "/Event/Phys/StdDC06LooseAllPhotons" 
 +See **PhotonParticleMaker** or **CnvPhotonParticleMaker** in the DaVinci Doxygen for details.
  
-Job option for exclusive selection of particle types.+===== General ===== 
 +There are a set of StandardDC06 basic particle, StandardDC06 Pi0s and a set of StandardDC06 intermediate states: D0, Ds, D*, J/psi, K*, Phi. The relevant algorithms are fired on demand when one wants to read their outputlocation. See the relevant options for a complete list. 
 + 
 +The cuts coded in this version are 'just a little tighter' than the ones applied in the exclusive HLT (with the big exception that PID is used here but not in the HLT). So hopefully events selected using these particles should also pass HLT. This has not been tested. 
 + 
 +The actual definition of the cuts should be defined by the physics WG for the DC06 stripping. The present first import should be taken as an example more definitions of 'Tight' 'Looser' or 'NoPID' intermediate states could be provided if needed. 
 + 
 +===== About Exclusive Selection in the CombinedParticleMaker ===== 
 + 
 +**m_exclusive**: Job option for exclusive selection of particle types.
  
 PIDs are checked in some order and all tracks that are compatible with being a muon are made a muon, then an electron, proton, kaon and pion. What you get will depends on this order, which is already a good enough reason not to want that. If you do B->pipi and one pi decays to a muon, it will never be a pi candidate. Even worse, if you or someone relaxes the mu ID cuts between two jobs or two DaVinci versions, then suddenly what used to be a nice pion in one version of DV might now becomes a muon candidate. Your efficiency decreases although nothing affecting pion or kaon ID changed. That makes it very hard to estimate signal efficiencies as all efficiencies depend on everything. If you want to cut hard on PID, use PID cuts. If you don't want to use the same track several times (which is a valid point for tagging), then use the Overlap Tool and re-weight the track accordingly if needed.  PIDs are checked in some order and all tracks that are compatible with being a muon are made a muon, then an electron, proton, kaon and pion. What you get will depends on this order, which is already a good enough reason not to want that. If you do B->pipi and one pi decays to a muon, it will never be a pi candidate. Even worse, if you or someone relaxes the mu ID cuts between two jobs or two DaVinci versions, then suddenly what used to be a nice pion in one version of DV might now becomes a muon candidate. Your efficiency decreases although nothing affecting pion or kaon ID changed. That makes it very hard to estimate signal efficiencies as all efficiencies depend on everything. If you want to cut hard on PID, use PID cuts. If you don't want to use the same track several times (which is a valid point for tagging), then use the Overlap Tool and re-weight the track accordingly if needed. 
 +
 +===== MC09 =====
 +The corresponding information for MC09 samples can be found in: **$COMMONPARTICLESROOT/python/** in the DaVinci installation
 +
  
davinci/samples.1236076323.txt.gz · Last modified: 2009/03/03 11:32 by decianm