-
Notifications
You must be signed in to change notification settings - Fork 24
Updates for EFT basis rotation #495
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.
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
base: master
Are you sure you want to change the base?
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #495 +/- ##
==========================================
+ Coverage 24.58% 24.65% +0.07%
==========================================
Files 36 36
Lines 5516 5520 +4
==========================================
+ Hits 1356 1361 +5
+ Misses 4160 4159 -1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
…er-and-tools Add coverage for canonical process names across data-driven utilities
Updated warning message regarding EFT basis rotation and combine limit scans.
|
I'm trying to figure out whether or not it's expected that the limits for some of the WCs are different, but I'm still working out some toy examples to try and wrap my head around what this rotation actually means. The basic idea here is that we want to compute the limits for a set of WCs: x1, x2, and x3, however, the yield dependence for some of our samples is given based on WCs: x1, x2, and x4. We also having the following mapping that takes x4 <-> x2 - x3. Now lets say we're doing a 1D frozen scan in x3. For the SMEFTsim samples, combine will need to plug in As an explicit concrete example: With the point being that if the two parameterizations are correct and you've made sure that |
I believe that is what it is doing. The figure above is not really a fair comparison for the rotated cases. In TOP-22-006 we fit |

This PR updates the basis rotations so that the SMEFTsim WC names become the POIs and any dim6top names are only used internally. There is also a caveat added to the fitting README about
gladoshaving issues making a workspace withexprinscalings.json. It works fine onlxplus, and the resulting root file can be used on `glados.Here's an example of an (incomplete) 2D scan of

ctBRevsctWRe(rotatingctZandctW). The correlations are much smaller than in TOP-22-006 when usingdim6top.