Avoid duplicate dataset names between lhe and hadronization step in gen-only relvals

[bendavid]

Suffering here from a historically confusing use of "GEN" datatier for lhe event content. Therefore we cannot use the "GEN" datatier for the gen-only output of the hadronization step.

Minimal solution is to use "GEN-SIM" datatier for gen-only output.

Addresses the issue reported by Alan here
https://hypernews.cern.ch/HyperNews/CMS/get/wmDevelopment/642/1/1/1/1/1/1/2/1/1/1/1/1/1/1/1/1/1/1/1/1/1.html

[cmsbuild]

A new Pull Request was created by @bendavid (Josh Bendavid) for CMSSW_7_4_X.

Avoid duplicate dataset names between lhe and hadronization step in gen-only relvals

It involves the following packages:

Configuration/PyReleaseValidation

@cmsbuild, @srimanob, @nclopezo, @boudoul, @franzoni can you please review it and eventually sign? Thanks.
@ghellwig, @Martin-Grunewald this is something you requested to watch as well.
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.
If you are a L2 or a release manager you can ask for tests by saying 'please test' in the first line of a comment.

[cmsbuild]

+1
Tested at: 993411a
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-7101/1809/summary.html

[cmsbuild]

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

[franzoni]

hi Josh @bendavid , I overlooked this PR and placed #7201, which achieves the same goal.
Feel free to close this one.

[bendavid]

Might it not be preferable to modify the tier consistently for all workflows (as opposed to just the two step ones)?

[franzoni]

That's like saying GEN disappears as data tier, and we only use GEN-SIM for everything ?
Let's not do that.

[bendavid]

No, that's saying that the GEN datatier is reserved exclusively for the LHE event content, for which it's already being used in production.

Hadronized output is quite different from just the LHE output (and indeed requires to use RAWSIM event content to get everything consistent)

[franzoni]

Hi Josh @bendavid , we agreed in conversation we would solve this by cleanly asking EDMLHE to be introduced. At that stage, we would even be in position of un-doing #7201, which is solving the problem with a sufficient hack now. Can we close this ?