Difference: StreamingTaskForce (30 vs. 31)

Revision 312008-02-27 - AnatolySolomin

Line: 1 to 1
 
META TOPICPARENT name="ComputingModel"
Line: 167 to 167
  past experiments shows that this rarely happens.
  • It is not possible to give special priority to a specific high priority analysis with a narrow exclusive trigger. As nearly every analysis will
Changed:
<
<
rely on larger selections for their result (normalization to J/Ψ
>
>
rely on larger selections for their result (normalization to J/ψ
  signal, flavor tagging calibration) this seems in any case an unlikely scenario.
Line: 215 to 215
  with double counting of events. Lets take the Bs → μ+μ- analysis as an example. The signal will come from the two-body stream while the BR normalization
Changed:
<
<
will come from the J/Ψ stream. In this case the double
>
>
will come from the J/ψ stream. In this case the double
  counting doesn't matter though so the objection is not real. If the signal itself is extracted from more than one stream there is a design error in the stripping for that analysis.
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback