Monte Carlo production tools
  • Introduction
  • Monte Carlo production overview
  • Monte Carlo Management (McM): introduction
  • Analyzer's corner
    • Monitoring submitted requests
    • How to search for datasets in DAS and McM
    • How to find the fragment of a request in McM
    • How to find the cmsDriver used for a certain request
    • How to use randomized parameters samples
  • Monte Carlo contact's corner
    • Rules for dataset names
    • Rules for Run3 dataset names
    • Rules for Run3 2024 dataset names
    • How to create a new ticket
    • High priority requests
    • Scripting in McM
    • Request checking script
    • News and current request policy
    • Interactive MC contact exercises
    • Randomized Parameters
    • Info for MC production for Ultra Legacy Campaigns 2016, 2017, 2018
    • Info for MC production for Run3 Campaigns
  • Request manager's corner
    • [DRAFT] MultiValidation in McM
    • Procedure how to create and setup a campaign
    • Fast Simulation Campaigns
    • "Dead" requests and tickets
  • Computing's corner
    • Status of requests in computing
    • Errors in production: explanation
    • Task chain vs step chain
  • cmsDriver argument and meaning
    • runTheMatrix and release validation
  • Monte Carlo Management (McM): detailed guide
    • McM Glossary: requests
    • McM glossary: chained requests
    • McM glossary: campaigns
    • McM glossary: flows
    • McM glossary: tickets
  • Production Monitoring Platform (pMp): detailed guide
  • Data reprocessing (old injection method via script)
  • FAQ
  • Contacts
  • Group Analysis Samples Page: GrASP
    • Tagging on GrASP
Powered by GitBook
On this page

Was this helpful?

  1. Monte Carlo contact's corner

News and current request policy

This page tries to keep track of updated information about chains, campaigns and priority blocks currently used in production.

PreviousRequest checking scriptNextInteractive MC contact exercises

Last updated 6 years ago

Was this helpful?

Links to the root campaigns used for each Monte Carlo production per RunII-year:

  • 2016:

  • 2017:

  • 2018:

An overview of the CMSSW releases, global tags and campaigns can be found in the PdmV analysis summary table:

  • Priority blocks:

    • BLOCK1: Moriond (very exceptional) requests, PhaseIIMTDTDR requests, RunIIWinter19CosmicsGS requests.

    • BLOCK2: HINPbPbAutumn18 high-priority requests

    • BLOCK3: LHCP requests (tag them with “PAGLHCP19” -> will be increased to 86k), other requests of summer conferences

    • BLOCK4, 5 and 6 not used for now

  • Chains and campaigns to use:

    • 2016: RunIISummer15 (GS,wmLHEGS) with chain: chain_RunIISummer15*_flowRunIISummer16DR80PremixPUMoriond17_flowRunIISummer16MiniAODv3_flowRunIISummer16NanoAODv4

    • 2017: RunIIFall17 (GS, wmLHEGS, pLHE) with chain: chain_RunIIFall17*_flowRunIIFall17DRPremixPU2017_flowRunIIFall17MiniAODv2_flowRunIIFall17NanoAODv4

    • 2018: RunIIFall18 (GS, wmLHEGS, pLHE) with chain: chain_RunIIFall18*_flowRunIIAutumn18DRPremix_flowRunIIAutumn18MiniAOD_flowRunIIAutumn18NanoAODv4

    • 3 campaigns per year (for root requests), 1 DR, 1DRPremix, 1MiniAOD, 1NanoAOD

    • Everything handled by chains (which define the conditions for each year)

    • 3 campaigns per year (for root requests), 1 DR, 1DRPremix, 1MiniAOD, 1NanoAOD

    • Everything handled by chains (which define the conditions for each year)

Plan for UL campaigns defined at the workshop:

Plan for PFCalib campaigns defined at the workshop:

Link
https://cms-pdmv.cern.ch/mcm/campaigns?prepid=RunIISummer19UL*&page=0&shown=63
Link
https://cms-pdmv.cern.ch/mcm/campaigns?prepid=*PFCalib*GS&page=0&shown=63
RunIISummer15*GS
RunIIFall17*GS
RunIIFall18*GS
Taken from last version of https://docs.google.com/presentation/d/1YTANRT_ZeL5VubnFq7lNGHKsiD7D3sDiOPNgXUYVI0I/edit?ts=5c08ea2e#slide=id.g54ddca43ca_6_0