Added patch for decay of K0 and antiK0

[civanch]

This patch for K0 and antiK0 decay should fix XeXE production but not change simulation histories.

[cmsbuild]

A new Pull Request was created by @civanch (Vladimir Ivantchenko) for branch IB/CMSSW_9_3_X/gcc630.

@cmsbuild, @smuzaffar, @gudrutis, @mrodozov can you please review it and eventually sign? Thanks.
You can sign-off by replying to this message having '+1' in the first line of your reply.
You can reject by replying to this message having '-1' in the first line of your reply.

[civanch]

please test

[cmsbuild]

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/23822/console

[cmsbuild]

+1
Tested at: 92afbee
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-3505/23822/summary.html

[cmsbuild]

Comparison job queued.

[cmsbuild]

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

Comparison Summary:

• No significant changes to the logs found
• Reco comparison results: 0 differences found in the comparisons
• DQMHistoTests: Total files compared: 26
• DQMHistoTests: Total histograms compared: 2708283
• DQMHistoTests: Total failures: 233
• DQMHistoTests: Total nulls: 0
• DQMHistoTests: Total successes: 2707863
• DQMHistoTests: Total skipped: 187
• DQMHistoTests: Total Missing objects: 0
• Checked 107 log files, 9 edm output root files, 26 DQM output files

[mrodozov]

+1

[cmsbuild]

This pull request is fully signed and it will be integrated in one of the next IB/CMSSW_9_3_X/gcc630 IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @davidlange6, @slava77, @smuzaffar (and backports should be raised in the release meeting by the corresponding L2)

[civanch]

@davidlange6 , the fix help to keep sim histories.

[davidlange6]

hi @civanch - do we need both this and #3510?

[civanch]

Hi @davidlange6 , we have production gcc/architecture and another one, I would keep cmsdist the same for both - it is more clear for the long term maintenance. So, to me an optimal solution is to merge both PRs.

[davidlange6]

merge