-
Notifications
You must be signed in to change notification settings - Fork 8
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
New decay tables for two SUSY models #9
Conversation
A new Pull Request was created by @scodella (Luca Scodellaro) for branch master. @SiewYan, @smuzaffar, @efeyazgan, @mkirsano, @mrodozov, @cmsbuild, @agrohsje, @alberto-sanchez, @qliphy can you please review it and eventually sign? Thanks. |
@alberto-sanchez, @qliphy any objections? |
@smuzaffar these files are to be use for susy signal production under different campaigns: RunIISummer15GS, RunIIFall17GS, RunIIFall18GS, RunIISummer16FSPremix, RunIIFall17FSPremix, RunIIAutumn18FSPremix |
Is there any issue on this or can we move forward? |
sorry missed this PR. no objections. |
+1 |
The tests are being triggered in jenkins. |
+1 |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
+externals |
This pull request is fully signed and it will be integrated in one of the next master IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @davidlange6, @silviodonato, @fabiocos (and backports should be raised in the release meeting by the corresponding L2) |
Thanks. We would like to have these files backported to the releases in [1] for SUSY signal production. Could you please remind me the procedure? Who would be the "corresponding L2"? [1] |
Once this is merged I'll backport it. |
@scodella do you really need to backport this in all those six releases? Could you comment on this? If you are interest to produce new signals using UL you can use 10_6_X for all three years. |
@silviodonato we can merge this for CMSSW_11_1_X and decide later on backports |
+1 |
@silviodonato We need the slha files in [1] in the three fastsim releases to prouce signals for analyses aiming to summer conferences. As for [2], they are in principle needed to produce LL stau signals required in fallsim, but we are waiting authors to confirm. [1] |
@mrodozov , I have merged this for CMSSW_11_1_X, please go ahead with back ports PRs for these releases #9 (comment) |
@scodella , do we really need these to be back ported to all releases you mentioned here #9 (comment) |
@smuzaffar We actually just got an update from the authors of LL stau analysis. It seems that we will need to produce only FastSim signal for the GGM model, so the following release will be enough: RunIISummer16FSPremix -> CMSSW_8_0_X |
@mrodozov could you prepare the three PRs (CMSSW_8_0_X, CMSSW_9_4_X, CMSSW_10_2_X) to cmsdist, please? |
they are already merged :) meaning in the latest IBs as well |
Uh, right! Great, thanks! :-) cms-sw/cmsdist#5433 master |
Hi, I'd like to inquire on the status of the cutting for the various releases. I have found the announcement for 10_2_X but not for the others. Is there any timeline for them? Sorry if I missed any announcement. |
@scodella , this has been integrated in CMSSW_8_0_X, CMSSW_9_4_X, CMSSW_10_2_X IBs. It was part of CMSSW_10_2_21 release. We have not build any release for 8.0.X and 9.4.X. When ever we decided to build a full release for these release cycles then this data should be there. @silviodonato , can tell more when he wants to build full releases for these release cycles. |
Hi @scodella , |
I mean: which release do you prefer to have first? |
having already CMSSW_10_2_21, our preferences are: cms-sw/cmsdist#5579 CMSSW_9_4_X first |
@scodella I'm sure you saw the release announcements . |
@silviodonato thanks! |
Already included for production. Thanks so much! |
New decay tables for two SUSY models: