Use case for the development of a new selection

Outline of use case

For a new selection access to unstripped data is a requirement. The sample has to be large enough that the rejection factor for even a sparse selection can be calculated with a reasonable accuracy.


This is effectively a random selection. It is important that the selection is not just a few runs but to some degree samples the run period in question. This could be achieved by having a truly random selection at a rate which keeps it no larger than other typical selections.


It has to be ensured tha the selection will run on the rDST and not only the DST. Thus a small sample of rDST data should be made available on disk as well.

We might want to have a selection with random T0 or T0+T1 events as well to allow a new analysis to optimise their HLT selection.


This is for developing the next generation of selections. Hence the production of this selection shoud be done in parallel with all the other selections.

Number of streams from the detector

As the selection is random it will have very little overlap with any other selection. It should clearly have its own stream.

Information required on trigger, stripping and luminosity

Information stored for each event

Maybe one should store information about what other selections passed each event. That would help in subsequent decisisons about if the selection should be grouped with other selections for larger streams.

Edit | Attach | Watch | Print version | History: r3 < r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r3 - 2006-12-12 - UlrikEgede
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    LHCb All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback