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

Request checking script

This page describes the usage of monte carlo request checking script in CMS that uses McM info and gridpacks and does automated patches for certain type of problem in MG5_aMC in the CMSSW setup.

In lxplus, do:

$ git clone git@github.com:cms-sw/genproductions.git
$ cd genproductions/bin/utils
$ python request_fragment_check.py -h

This will bring up a list of things that the script checks. It also displays the list of optional arguments:

optional arguments:
  -h, --help            show this help message and exit
  --prepid PREPID [PREPID ...]
                        check mcm requests using prepids
  --ticket TICKET       check mcm requests using ticket number
  --bypass_status       don't check request status in mcm
  --bypass_validation   proceed to next prepid even if there are errors
  --apply_many_threads_patch
                        apply the many threads MG5_aMC@NLO LO patch if
                        necessary
  --dev                 Run on DEV instance of McM
  --debug               Print debugging information

Note that the code acceps list of prepids, but a single ticket (not to kill the database with too much access). When you use a list of prepids or the --ticket option locally, you should also specify --bypass_validation.

Unless the --apply_many_threads_patch is specified it won't do any patches but will still check the existence of the patch.

PreviousScripting in McMNextNews and current request policy

Last updated 6 years ago

Was this helpful?