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
  • What is a campaign?
  • CMSSW Release
  • Energy
  • Next
  • On Hold
  • Events Per Lumi
  • Sequences
  • No output
  • Generators
  • Memory
  • Type
  • Status
  • Input Dataset
  • Approval
  • Pileup Dataset Name
  • Validation
  • Root

Was this helpful?

  1. Monte Carlo Management (McM): detailed guide

McM glossary: campaigns

In this page, we give a description of icons and features of campaigns in McM

PreviousMcM glossary: chained requestsNextMcM glossary: flows

Last updated 6 years ago

Was this helpful?

What is a campaign?

A campaign defines the condition, i.e. the cmsDriver, of an entire set of requests which will be produced for a standard production (e.g. MC for analysis and comparison of 2018 data) or for a specific collection of requests (e.g. Cosmics).

In the following, the different entries needed for the definition of a campaign are explained.

CMSSW Release

CMSSW version to be used while processing requests that are members of this campaign.

Energy

Energy in to be used.

Next

List of campaigns ("Next Campaign" in Flows) with which this campaign is joined by flows (chained) and is the first campaign ("Allowed Campaigns" in Flows).

On Hold

Flag whether this campaign is on hold.

Events Per Lumi

Work in progress, under construction

Sequences

No output

Generators

Memory

Default amount of memory to be used (in MB).

Type

Status

Input Dataset

Approval

Pileup Dataset Name

Validation

Root

Work in progress, under construction
Work in progress, under construction
Work in progress, under construction
Work in progress, under construction
Work in progress, under construction
Work in progress, under construction
Work in progress, under construction
Work in progress, under construction
Work in progress, under construction
TeV