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

scenario HeavyIons and --himix decoupled #3694

Merged
merged 1 commit into from May 6, 2014

Conversation

yetkinyilmaz
Copy link
Contributor

This fix is needed for our pPb MC production. This is the reason:
For pPb analyses, we use pp-reconstruction, so HI scenario is not wanted.
On the other hand, the same mixing workflow is applied, using the option --himix, and HI event content (which is a strict superset of pp event content) is needed to keep the signal event (hiSignal).
Therefore the scenario has to be decoupled from himix, but EventContent should always be imposed.
The fix pull-requested here does exactly the above, and nothing else.

@cmsbuild
Copy link
Contributor

cmsbuild commented May 6, 2014

A new Pull Request was created by @yetkinyilmaz for CMSSW_5_3_X.

scenario HeavyIons and --himix decoupled

It involves the following packages:

Configuration/PyReleaseValidation

@nclopezo, @vlimant, @cmsbuild, @franzoni, @Degano, @davidlange6 can you please review it and eventually sign? Thanks.
@ghellwig 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.
@smuzaffar you are the release manager for this.
You can merge this pull request by typing 'merge' in the first line of your comment.

davidlange6 added a commit that referenced this pull request May 6, 2014
scenario HeavyIons and --himix decoupled
@davidlange6 davidlange6 merged commit e7a28c8 into cms-sw:CMSSW_5_3_X May 6, 2014
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.

None yet

3 participants