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. Computing's corner

Errors in production: explanation

In this section, we comment on the errors observed in production and on the possible solutions that should be adopted to correct them. (page to be completed)

PreviousStatus of requests in computingNextTask chain vs step chain

Last updated 6 years ago

Was this helpful?

The errors observed in production are listed in the following: (twiki page with the job exit codes can be found )

53

  • Phase space integration or un-reweighting efficiency problems

  • Missing text file for fragment

73

  • Missing files at Premix stage

134

  • G4 error

139 - segmentation violation

  • Merging problems

  • Missing gridpacks

  • NanoAOD problem

8001

  • nThread problem

8003

  • Premix error

8021

  • Merging problem

  • Server not available

50664

  • Timeout - due to incorrect tune

60450

  • Merging error due to server problem

99303

  • Stageout problem

99305

  • pLHE problem with too many events for time given

99996

  • Module problem at NanoAOD stage

  • 53 :

    Powheg + JHUGen phase space integration or unreweighting efficiency problems (physics process related errors )

    lhe file contains fewer events than were requested ⇒ phase space problem. (physics process related errors )

    73 :

    Pythia8 :

    vanishing cross section (physics process related errors )

    134:

    Mg leading order patching problem, + nb of threads issue. (not physics process related errors

    139 : mainly : file access , request configuration issues. (not physics process related errors )

    8001:

    Only 1 request with this exit code , error related to premixing step (not physics process related errors )

    50115 :

    Mad + pythia8 : (not a physics process related problem). Issue observed in premixing step.

    Needs more investigation, for few other requests.

here