Skip to content

Commit 4ae56f4

Browse files
committed
correcting README files
1 parent 125ad4c commit 4ae56f4

File tree

1 file changed

+28
-0
lines changed

1 file changed

+28
-0
lines changed

PrivProd/README.md

Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
# Private Production
2+
The folder PrivProd contains the machinery needed to produce simulated private samples for Summer16, Fall17, and Autmn18 scenarios. For all years, the set of files consist of:
3+
4+
- `config.py`: CMSSW configuration file;
5+
- `submitter\*`: Bash macro to split the production in a certain numbers of jobs;
6+
- `script.sh`: Bash macro for LXBATCH job run;
7+
- `condor.sub`: HTCondor script to submit jobs.
8+
9+
The command line directive is:
10+
11+
`./submitter\* [tag] [job_name]`
12+
(`./submitter_pLHEtoGENSIM.sh FPMC_WW_bSM_13tev_a0w_0_aCw_8e-6_lept_pt0 GS17_WW_0_8_lept`)
13+
14+
where [tag] defines the folder names for the output files and the tag to be used in the next steps for automate job submission and [job_name] the HTCondor job label.
15+
16+
## **Instructions**:
17+
18+
- By default, all input/output files are set to the PPS EOS area. Change the paths accordingly to your needs.
19+
20+
- All submitter macros have the line `exit 1` uncommented, which produced the set of files needed for the simulation, but avoid submitting jobs. Comment that line to submit the jobs.
21+
22+
- The DRPremix step requires a GRID certificate to be placed at `~/private` with permission 774.
23+
24+
- Be aware that the template for the DRPremix config file has 27MB, which will be duplicated to the number of jobs required by the user. In the case of 100 jobs, the DRPremix setup will expand to almost 3GB of disk space.
25+
26+
- MINIAOD step is provided for 2017 only; if needed for other years please contact the coordinator.
27+
28+
- Given a past experience with FPMC, a certain number of unknown problematic events had to be removed in the GENSIM step. The corresponding scripts are placed at the folder named `to_extract_bad_events`. Use these files only if specific events have to be removed from the simulation.

0 commit comments

Comments
 (0)