Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • athena athena
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Jira
    • Jira
  • Merge requests 143
    • Merge requests 143
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Issue
    • Repository
  • Activity
  • Graph
  • Commits
Collapse sidebar
  • atlas
  • athenaathena
  • Merge requests
  • !27627

Merged
Created Oct 30, 2019 by Tomas Dado@tdadoDeveloper

Added warning when actual mu reweighting is not used for mc16d/e samples

  • Overview 5
  • Commits 1
  • Pipelines 1
  • Changes 1

Adding warning to AnalysisTop when actual mu reweighting is not used for mc16d/e.

One interesting observation: we wanted to check the campaign type by retrieving RunNumber from Metadata:

if (m_aodMetaData->valid()) {
      const std::string runNumberString = m_aodMetaData->get("/Simulation/Parameters","RunNumber");
      try {
        const int runNumber = std::stoi(runNumberString);
        if (runNumber >= 300000) {
          if ((!m_isAFII && m_pileup_reweighting.actual_mu_FS.size() == 0) ||
            (m_isAFII && m_pileup_reweighting.actual_mu_AF.size() == 0)) {
            std::cout << "WARNING: You are running over mc16d or mc16e samples but you are not using actual mu reweighting!\n";
            std::cout << "You are strongly advised to use the actual mu reweighting\n";
            std::cout << "Check: https://twiki.cern.ch/twiki/bin/view/AtlasProtected/TopxAODStartGuideR21#PRW_and_Lumicalc_files\n";
          }
        }
      } catch(std::invalid_argument& e) {
        std::cout << e.what() << "\n";
        std::cout << "WARNING: Cannot properly convert RunNumber from metadata to integer.\n";
        std::cout << "Skipping check for actual mu reweighting\n";
      }
    }

But we found out that the runNumber is the same for all campaigns, is this expected?

Due to this issue we have to retrieve the runNumber during the event loop from eventInto

Edited Oct 30, 2019 by Tomas Dado
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: 21.2-AT-actualMuWarning