Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

document patches with mc naming #2

Open
wants to merge 2 commits into
base: mc-docs
Choose a base branch
from
Open

document patches with mc naming #2

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
400e3ac
dataset name patches
sihyunjeon Nov 22, 2024
eebe7f4
patch
sihyunjeon Nov 22, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions mccontact/rules-for-run3-2024-dataset-names.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -82,7 +82,7 @@ To unify this part we suggest to use the following conventions:
* Using **WZto3LNu** instead of WZtoLNu2L
* Using **WWto4Q** instead of WWto2Q2Q

**IMPORTANT**: Use the `Jet` keyword with caution. We're operating a hadron collider, there are jets all over the place. We propose to use it only if there are matrix elements in the generation that explicitly include the higher QCD multiplicity diagrams, i.e. MadGraph, Alpgen and Sherpa, and some matching procedure had/has to be applied. From this definition the keyword `Jet` should never appear in a leading order MC generator sample. If there are cuts on pthat, this should be indicated using the dedicated keywords. A an example `ZJet` in Pythia6, which is nothing but Z production with a cut on pthat of the hard interaction should become `Z`, or `ZmumuJet` simply `ZToMuMu`. In case of decay products, e.g. RS Gravitons decaying into quarks and gluons, use the keyword `J`, e.g. `RSGravToJJ`.
**IMPORTANT**: Use the `Jet` keyword with caution. We're operating a hadron collider, there are jets all over the place. We propose to use it only if there are matrix elements in the generation that explicitly include the higher QCD multiplicity diagrams, i.e. MadGraph, Alpgen and Sherpa, and some matching procedure had/has to be applied. If there are cuts on pthat, this should be indicated using the dedicated keywords. A an example `ZJet` in Pythia6, which is nothing but Z production with a cut on pthat of the hard interaction should become `Z`, or `ZmumuJet` simply `ZToMuMu`. In case of decay products, e.g. RS Gravitons decaying into quarks and gluons, use the keyword `J`, e.g. `RSGravToJJ`.

### **BINNING**

Expand All @@ -99,7 +99,7 @@ Other binning cases are trivial, e.g., DYto2L-4Jets\_Bin-MLL-60to90, DYto2L-4Jet

For bins without an upper boundary no need to add `Inf`: e.g. `600toInf` should be `600` directly.

If sample is binned in multiple variables, separate the various parts with `-` and list bins in alphabetical order, e.g. `Bin-HT-100to400-MLL-50to120`.
If sample is binned in multiple variables, separate the various parts with `-` and list the bins. The bins should be first ordered with number of jets (if it is binned in number of jets) and then the rest should be listed in alphabetical order, e.g. `Bin-HT-100to400-MLL-50to120`, `Bin-1J-MLL-50to120`.

<span style="color:red;">N.B.:The only exception to this rule is for jet bins (for historical reasons). In this case you should use the format `Bin-0J`, `Bin-1J`, ...</span>

Expand Down