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 ticket?
  • mccms pwg
  • mccms notes
  • mccms meeting
  • mccms deadline
  • mccms staged
  • mccms threshold
  • mccms chains
  • mccms repetitions
  • mccms size
  • mccms block
  • mccms special

Was this helpful?

  1. Monte Carlo Management (McM): detailed guide

McM glossary: tickets

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

PreviousMcM glossary: flowsNextProduction Monitoring Platform (pMp): detailed guide

Last updated 6 years ago

Was this helpful?

What is a ticket?

A ticket is the way to communicate and present the requests to be submitted in central production. In a ticket, a MC contact places the list of requests to submit, the priority at which the requests will be submitted and the chain to use, which defines among other things the PU scenario and the reconstruction conditions which will be used for the requests.

In the following, the different entries for a ticket are explained (not all are mandatory).

mccms pwg

This is the pwg that has made a request for chains. It can be different than the pwg of the requests to be chained.

mccms notes

This should contain enough information to understand the origin and the need of the request.

mccms meeting

This is assigned automatically to the .

mccms deadline

This is an indication of the required deadline for the chains to complete, as an indication for now, it might get used automatically in the future to set the priority accordingly.

mccms staged

In case the ticket needs to create chains for which only part of the processing will be done at the end-point (digi-reco), this number should indicate the amount of events required

mccms threshold

In case the ticket needs to create chains for which only part of the processing will be done at the end-point (digi-reco), this number should indicate the fraction of events required.

mccms chains

These are the aliases of the chained campaigns that chains need to be created in.

mccms repetitions

If the root request needs to be chains multiple times within the same chained campaign, this should indicate the number of chains required (defaults to 1).

mccms size

As an indication of the total amount of events expected in the end (repetitions times chains times requests times ...)

mccms block

mccms special

This is the priority block number

In case the ticket needs to be hosting from , this should be ticked to true.

special requests
special chains
next MccM meeting date
mapped to priority