kinematic labels

[tgiani]

addressing #2025

[tgiani]

regarding ATLAS_WJ_JET_8TEV: is there a reason because of which k2 is set to a placeholder rather than m_W^2?
The original buildmaster implementation is here https://github.com/NNPDF/buildmaster/blob/master/filters/ATLAS_WJET_8TEV.cc

[scarlehoff]

Please use the names from

nnpdf/validphys2/src/validphys/process_options.py

Line 16 in 37f4875

class _Vars:

(so m_W2 instead of MW2...or... in this case, m_V and we will need to add a new variable for that)

[tgiani]

what s the procedure to add a new variable? In the case above we need m_V, for ATLAS_PH_13TEV we need the transverese ewnergy square ET2 and I guess there will be other cases. Is it enought to add these new variables to the _Vars class?

[scarlehoff]

Yes. And then for the processes for which you want to add it, include it in the "accepted variables".

(if the process still doesn't exist you can either create it or leave it for later, it should not matter)

[scarlehoff]

I took the values from the commondata that were available, so I guess at some point it became a placeholder.

If you want to change it feel free. If not... we've lived with that for a while so ¯_(ツ)_/¯

[tgiani]

just to keep track of the new variables:

• ATLAS_DY_13TEV : m_V
• ATLAS_PH_13TEV : ET2
• ATLAS_WPWM_13TEV : m_W
• ATLAS_Z0_7TEV_49FB: m_ll, m_ll2
• ATLAS_Z0_7TEV_LOWMASS: m_ll2
• ATLAS_Z0_8TEV_HIGHMASS: m_ll2
• ATLAS_Z0_8TEV_LOWMASS: m_ll2
• ATLAS_Z0_13TEV: m_Z
• ATLAS_Z0J_8TEV: m_ll2
• DYE605 : m_ll2

[scarlehoff]

Closed since most of them have now been done in the specific PRs.