Skip to content
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

Merged
merged 2 commits into from
Jan 31, 2020
Merged

Conversation

scodella
Copy link
Contributor

New decay tables for two SUSY models:

  1. long lived Stau
  2. General Gauge Mediation model

@cmsbuild
Copy link
Contributor

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.
@Martin-Grunewald this is something you requested to watch as well.
cms-bot commands are listed here

@smuzaffar
Copy link
Contributor

@alberto-sanchez, @qliphy any objections?
@scodella , these are new files, is there any cmssw PR to make use of these?

@scodella
Copy link
Contributor Author

@smuzaffar these files are to be use for susy signal production under different campaigns: RunIISummer15GS, RunIIFall17GS, RunIIFall18GS, RunIISummer16FSPremix, RunIIFall17FSPremix, RunIIAutumn18FSPremix

@scodella
Copy link
Contributor Author

Is there any issue on this or can we move forward?

@agrohsje
Copy link

sorry missed this PR. no objections.
+1

@agrohsje
Copy link

+1

@cmsbuild
Copy link
Contributor

cmsbuild commented Jan 16, 2020

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-run-pr-tests/4244/console Started: 2020/01/16 11:41

@cmsbuild
Copy link
Contributor

+1
Tested at: 9c385b8
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-762036/4244/summary.html
CMSSW: CMSSW_11_1_X_2020-01-15-2300
SCRAM_ARCH: slc7_amd64_gcc820

@cmsbuild
Copy link
Contributor

Comparison job queued.

@cmsbuild
Copy link
Contributor

Comparison is ready
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-762036/4244/summary.html

Comparison Summary:

  • No significant changes to the logs found
  • Reco comparison results: 0 differences found in the comparisons
  • DQMHistoTests: Total files compared: 34
  • DQMHistoTests: Total histograms compared: 2711715
  • DQMHistoTests: Total failures: 1
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 2711368
  • DQMHistoTests: Total skipped: 346
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.0 KiB( 33 files compared)
  • Checked 147 log files, 16 edm output root files, 34 DQM output files

@mrodozov
Copy link
Contributor

+externals

@cmsbuild
Copy link
Contributor

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)

@scodella
Copy link
Contributor Author

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]
RunIISummer15GS -> CMSSW_7_1_X
RunIIFall17GS -> CMSSW_9_3_X
RunIIFall18GS -> CMSSW_10_2_X
RunIISummer16FSPremix -> CMSSW_8_0_X
RunIIFall17FSPremix -> CMSSW_9_4_X
RunIIAutumn18FSPremix -> CMSSW_10_2_X

@mrodozov
Copy link
Contributor

Once this is merged I'll backport it.

@silviodonato
Copy link

@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
Copy link

@scodella @mrodozov

@mrodozov
Copy link
Contributor

@silviodonato we can merge this for CMSSW_11_1_X and decide later on backports

@silviodonato
Copy link

+1
@mrodozov ok

@scodella
Copy link
Contributor Author

@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 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]
https://github.com/scodella/Configuration-Generator/tree/master/SUSY/GGM_Full
[2] https://github.com/scodella/Configuration-Generator/tree/master/SUSY/LongLivedStau

@smuzaffar
Copy link
Contributor

@mrodozov , I have merged this for CMSSW_11_1_X, please go ahead with back ports PRs for these releases #9 (comment)

@smuzaffar
Copy link
Contributor

@scodella , do we really need these to be back ported to all releases you mentioned here #9 (comment)

@scodella
Copy link
Contributor Author

@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
RunIIFall17FSPremix -> CMSSW_9_4_X
RunIIAutumn18FSPremix -> CMSSW_10_2_X

@silviodonato
Copy link

@mrodozov could you prepare the three PRs (CMSSW_8_0_X, CMSSW_9_4_X, CMSSW_10_2_X) to cmsdist, please?
cc: @smuzaffar @makortel

@mrodozov
Copy link
Contributor

mrodozov commented Feb 24, 2020

they are already merged :) meaning in the latest IBs as well

@silviodonato
Copy link

Uh, right! Great, thanks! :-)

cms-sw/cmsdist#5433 master
cms-sw/cmsdist#5582 CMSSW_7_1_X
cms-sw/cmsdist#5581 CMSSW_8_0_X
cms-sw/cmsdist#5579 CMSSW_9_4_X
cms-sw/cmsdist#5578 CMSSW_10_2_X

@scodella
Copy link
Contributor Author

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.

@smuzaffar
Copy link
Contributor

@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.

@silviodonato
Copy link

Hi @scodella ,
the releases are made when they are needed by somebody. We can update the releases by next week. Do you have any preference about the order?

@silviodonato
Copy link

I mean: which release do you prefer to have first?

@scodella
Copy link
Contributor Author

scodella commented Mar 27, 2020

Hi @silviodonato

having already CMSSW_10_2_21, our preferences are:

cms-sw/cmsdist#5579 CMSSW_9_4_X first
cms-sw/cmsdist#5581 CMSSW_8_0_X later

@silviodonato
Copy link

@scodella I'm sure you saw the release announcements .
Just to be 100% sure, the releases are ready:
https://github.com/cms-sw/cmssw/releases/CMSSW_9_4_17
https://github.com/cms-sw/cmssw/releases/CMSSW_8_0_35

@scodella
Copy link
Contributor Author

@silviodonato thanks!

@agrohsje
Copy link

Already included for production. Thanks so much!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants