EXO MC&Interpretation
  • EXO MC&Interpretation
  • How-to : Sample Request
    • How to : Request Prelegacy Samples Cloned to Legacy
  • How-to : Sample Production
    • Avoiding wmLHEGEN Step
  • How-to : Gridpack Production
  • How-to : HEPData Preparation
  • Others
    • Finding PrepIds in McM
    • Matching/merging using madgraphMLM
Powered by GitBook
On this page
  • Checklists Before Making the Clone Request
  • Instructions

Was this helpful?

  1. How-to : Sample Request

How to : Request Prelegacy Samples Cloned to Legacy

How to clone your RunII-prelegacy samples for RunII-legacy production.

PreviousHow-to : Sample RequestNextHow-to : Sample Production

Last updated 4 years ago

Was this helpful?

If your analysis is moving from RunII-prelegacy to RunII-legacy, please follow the simplified instructions below to request that your RunII-prelegacy samples get remade as RunII-legacy.

Checklists Before Making the Clone Request

  • Are my gridpacks were made using MadGraph v2.6.X? (IF NOT) Gridpacks should be remade since the gridpacks are likely to be outdated.

  • Are my prelegacy samples made using CPX tunes? (IF NOT) If CPX tunes are not used, simple cloning won't work so please follow the instructions in How-to : Sample Request.

  • Does my prelegacy samples' dataset names contain which generator and hadronizer it uses and also the name of the tune? (IF NOT) If dataset names are missing the necessary information, simple cloning won't work so please follow the instructions in How-to : Sample Request.

  • Is my analysis mature enough to ask for higher priority (heading for preapproval soon, target conference is near, etc.)? (IF SO) We will request for higher priority under other EXO L2 and L3 conveners' approval. So don't hesitate to let us know.

If you are still unsure whether your samples are eligible for clone requests, please send us an email to cms-exo-mcrequests@cern.ch for faster conclusions.

Instructions

PrepIds are the only thing we need fro clone requests. In case you are not sure how to look for your prepIds, take a look at Others - Finding PrepIds in McM.

1. Get the prepIds for every sample that you want to be cloned. We don't need prepIds for all 3 years, 1 year to use as cloning seeds will be enough. Provide us the prepIds with RunIISummer17(wmLHE)GS. 2. Prepare a CSV file. The CSV file needs to contain prepId as a header and then a single prepId on each line of the file. An example CSV file can be found here. 3. Prepare a merge request.

  • Git clone the EXO-MCsampleRequests gitlab repository link.

git clone ssh://git@gitlab.cern.ch:7999/cms-exo-mci/EXO-MCsampleRequests.git
cd EXO-MCsampleRequests

  • Make a directory under requestTickets : YYYYMMDD_CERNID_SampleInfo. 1) YYYYMMDD : Date when the sample request is made, in year-month-date order. 2) CERNID : CERN account. 3) SampleInfo : Brief information of the sample. e.g. 20210127_shjeon_DYJetsToLL

mkdir requestTickets/<Campaign>/<EXO-Subgroup>/<YYYYMMDD_CERNID_SampleInfo>

  • Move your CSV file to the git cloned area.

mv <PathToCSVFile> requestTickets/<Campaign>/<EXO-Subgroup>/<YYYYMMDD_CERNID_SampleInfo>/request.csv

4. Make a merge request.

Make a merge request with the following : 1. The CSV file (named request.csv) containing prepIds that need to be cloned. 2. Briefly explain for which analysis the samples are needed, and what the samples are. 3. Explicitly state how many prepIds need to be cloned so that we don't miss anything. 4. Provide the McM link to one of the prepIds.

If anything is unclear, please contact us through email before making a merge request.

Finding PrepIds in McM