LHCb Stripping page

Processing passes for all Stripping productions

An exhaustive list of the processing passes including database tags, DaVinci versions etc can be found here.

The definitions of all the stripping campaigns can be found in the stripping documentation here

New StrippingSelections framework

Concurrent stripping of 2018 data (aka Stripping S34)

Concurrent stripping of 2017 data (aka Stripping S29)

Restripping of 2016 data (aka Stripping S28)

Incremental stripping of Run I data (aka Stripping S21(r0,r1)p1)

ReStripping for 25ns run (aka Stripping24) after Technical Stop

Stripping for 25ns run (aka Stripping23)

EM Stripping

FAQ for Stripping21

Stripping Stream Definitions

The complete documentation of the stripping line cuts, prescales and streams definition is available at the Stripping Project page.

not listed on that page are future strippings and too-long-ago strippings:

  • Stripping 14: second 2010 reprocessing to fix broken lines (excluding the first bit)
  • Stripping 13: prompt 2011 stripping (verify?)
  • Stripping 12: 2010 reprocessing

The stream definitions for different strippings can be found here:

The configuration of Stripping21 and Stripping21r1 can be found here:

Stripping Statistics

See StrippingStatistics page.

Status of stripping production

Stripping FAQ

See StrippingFAQ page.

Common Particles Change

The proposed changes to Common Particles, to be discussed are presented on the CommonParticles page.

How to add a line

So far we have always included the head of the stripping selections in DaVinci. We cannot continue like that. Since the beginning of the year I have asked everyone to present their stripping selection at T&S meeting. One such talk is scheduled today. Now that we'll soon start stripping real data we also need to discuss any change to what we've been using. By default, what goes in the head of cvs will not be used in the stripping. Only what's blessed by the PPG and OPG will be used.

Practically, if you want to add a line, or change a line, you must

  1. Get the change approved by your WG.
  2. Present it at T&S if it does not comply with the rate and cpu guidelines, of if asked to by the stripping coordinators.
  3. If agreed by the T&S meeting, the proposed change (practically, a bunch of changes) will make it to a production release. The green light has to be given by OPG and PPG to use this release in production.

Stripping Settings and the Stripping Archive

See the StrippingSettings page.

Stripping Framework

See StrippingLines page.

Stripping DST

The stripping DST contains the full DST, plus a MicroDST partition containing the full decay tree of the stripping line selected candidates. It also contains the necessary particle to primary vertex (PV) relations in order to guarantee that the same PV is used to apply further cuts and estimate PV-dependent quantities. If PV re-fitting has been used in the selection, the re-fitted PVs are also saved. The relations point to these.

See the DaVinciTutorial for examples of how to run on a stripped DST.

What version of which application was run on

You can either look up the processing pass or get the production ID, which is part of the LFN (a directory). In that case 5614. Now go to the Production monitor web page and search for production 5614. Click on a file and select "Show Details". This will give you the details of the whole production workflow. I read:

Merge Production 5614 for event type 30000000 has following parameters:

Production priority: 9
BK Config Name Version: MC MC09
BK Processing Pass Name: MC09-Stripping02
CondDB Tag: sim-20090402-vc-md100
DDDB Tag: MC09-20090602

====> DaVinci v24r4 Step0
  DaVinci Option Files:
  ExtraPackages: AppConfig.v3r20
====> Brunel v34r7 Step1
  Brunel Option Files:
  ExtraPackages: AppConfig.v2r9p1
====> DaVinci v24r4 Step2
  DaVinci Option Files:
  ExtraPackages: AppConfig.v3r20
====> LHCb v28r0 Step3
  LHCb Option Files:
BK Input Data Query:
    EventType = 30000000
    FileType = JPSI.DST
    ProductionID = 5600

BK Browsing Paths:

Stripping liaisons of WGs

Stripping liaisons mailing list is lhcb-stripping-liaisons@cernNOSPAMPLEASE.ch. The WG contacts are listed here.

Responsibilities of stripping liaisons of WGs

  • Put together the Stripping lines of your WG shortly after the deadline, so that we can fix the Stripping and launch the validation production as quickly as possible to spot out any problem.
  • Make sure that all the stripping lines of your WG are included, i.e., by asking people to check once a draft of Stripping is announced.
  • Once the validation production data of Stripping is available (announced to the mailing list), have a look at them as quickly as possible. You should at least check one of the most interested channel (with high yield) of your WG for all the streams in which there are stripping lines from your WG. If everything is OK, e.g., no problem in running over the data, everything (e.g., luminosity) you need is there, give the green light; otherwise report immediately the problem.
  • Inform your WG if changes made/proposed to Stripping affect your WG.
  • See StrippingLiaisonCheatsheet

Stripping coordinator's cheatsheet

See StrippingCoordinatorsCheatsheet

Correlations of Stripping and Hlt Lines

See HltCorrelations.

Outdated pages

The page OldStrippingStuff contains links to pages which are now outdated.

-- JuanPalacios - 09-Oct-2009 -- PatrickSKoppenburg - 20-Nov-2009 -- JuanPalacios - 25-Jun-2010 -- JuanPalacios - 13-Oct-2010 -- UlrikEgede - 12-Jan-2011

Edit | Attach | Watch | Print version | History: r119 < r118 < r117 < r116 < r115 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r119 - 2020-05-06 - OliverLupton
    • 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-2023 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