GEM-CSC integrated local trigger (part I)

[dildick]

This PR includes changes in L1Trigger/CSCTriggerPrimitives due to the GEM-CSC trigger port (from 62X SLHC)

• GEMCSCLCTDigi is a new dataformat which will contain the GEM-CSC bending angle - until we know how the bending will be used by the CSC TrackFinder
• Assignment of bending is currently disabled; will be enabled soon.
• Integrated local triggers are by default disabled
• All untracked parameters are now tracked

[cmsbuild]

A new Pull Request was created by @dildick (Sven Dildick) for CMSSW_7_5_X.

Changes due to GEM-CSC trigger

It involves the following packages:

DataFormats/CSCDigi
L1Trigger/CSCTriggerPrimitives

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

[cmsbuild]

This pull request is fully signed and it will be integrated in one of the next CMSSW_7_5_X IBs (tests are also fine). This pull request requires discussion in the ORP meeting before it's merged. @davidlange6, @Degano, @smuzaffar

[davidlange6]

@dildick - sorry for my slow review here - but I had a generic question - in other PRs we had CSC dependencies in GEM packages (eg, new code depends on old) - here it seems to be the reverse - that we've added GEM dependencies in CSC packages. Is this design discussed and agreed / needed?

[dildick]

It was approved by Tim Cox.

[davidlange6]

+1