WW Production Run 2 XSec MC Truth-Level Tupling. (Signal)

GaudiPython DaVinci script for getting truth level information out of MC files for the Run 2 p p -> W+ W- -> l+ l- vu_l ~vu_l cross-section analysis. This AnalysisProduction can be used to analyze signal (W+W- -> l+ l-) and background (t tbar -> b ~b l+ l-, tau+ tau- -> v_tau ~v_tau l+ l-) processes.

This version runs over WW NLO dilepton MC.

added QEE label

assigned to @ganowak

Welcome to Analysis Productions!

This is a summary of the productions requested in this merge request:

Step	Production ID	Num Test LFNs	Run time	Estimated Output Size (MB)
WW_NLO_2016_MagDown_Job	151218	1	0:39:56.427603	0.9
WW_NLO_2016_MagUp_Job	151219	1	0:43:41.657837	0.9
WW_NLO_2017_MagDown_Job	151220	1	0:41:00.041624	0.8
WW_NLO_2017_MagUp_Job	151221	1	1:04:14.687394	0.8
WW_NLO_2018_MagDown_Job	151222	1	0:32:20.990506	0.9
WW_NLO_2018_MagUp_Job	151223	1	1:12:04.758831	0.9

added MCrun1/2 label

requested review from @lugrazet

Hi @ganowak, once it's ready and the ci-test is passing, can you undraft and re-request review from me?

Hello @lugrazet, sorry that was my bad for requesting review a bit early. It is ready now.

Sorry for the delay in getting back to you . The code looks fine to me and the tupling job looks healthy in the ci. I have a few minor questions about the production before merging

You've had several AnaProds at this point over the last however long (no issue it's just my memory is running out ), does this supersede any previous production?
If not, how is it different?
Then, are there any samples in the completed productions that could be archived.

Hello @lugrazet, all good! All of the different Analysis Productions from me have been running the same script over different samples for my WW-> e mu analysis. Some of the productions are for signal processes (like this one) or for background processes such as ttbar or Different Flavor Drell Yan. This request differs from the last signal request as it is run over a NLO simulated sample as opposed to a LO sample.

I am unfamiliar with the archiving process. How does that work?

Thanks for the reminder, sounds good to me .
Will you want to keep the NLO and LO signal sample for comparisons? Perhaps no need to archive (but can't hurt for you to check your production files and verify )

Archival of AnaProd output should be pretty simple (unless something changed since last time I did it ) and described here:

• https://lhcb-ap.docs.cern.ch/user_guide/housekeeping.html#ok-i-have-samples-that-i-don-t-need-anymore-how-do-i-archive-them

Yes exactly, the plan would be to compare the NLO and LO signal samples.

Thank you for the link, I will look into archiving the samples!

Great makes sense to me. Let me know if you run into problems with archival

removed review request for @lugrazet

added 2 commits

• a632f39a - Corrected WW MG5 NLO Bookkeeping path.
• 0ec641bd - Change Job.py to skip non-WW events.

Compare with previous version

added 1 commit

• 62f85e18 - Run on all events.

Compare with previous version

marked this merge request as ready

requested review from @lugrazet

approved this merge request

merged

mentioned in commit 19b0ad25

mentioned in issue #1078 (closed)

mentioned in commit f831f1d8