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

TTI (Track Trigger Integration) descope scenarios #8518

Merged
merged 3 commits into from Mar 26, 2015

Conversation

boudoul
Copy link
Contributor

@boudoul boudoul commented Mar 25, 2015

Propagating the Tracker Descope scenarios (defined in the PR #8008) into the TTI scenario.
I didn't define anything in runthematrix, as this is not intended (for the moment) to be used in any central production but for track trigger studies - It should not interfere with anything.

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @boudoul (boudoul) for CMSSW_6_2_X_SLHC.

TTI (Track Trigger Integration) descope scenarios

It involves the following packages:

Configuration/Geometry
Geometry/CMSCommonData
SLHCUpgradeSimulations/Configuration

@civanch, @Dr15Jones, @ianna, @mdhildreth, @cmsbuild, @nclopezo, @ktf 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.
@fratnikov, @mark-grimes you are the release manager for this.
You can merge this pull request by typing 'merge' in the first line of your comment.

@ghost
Copy link

ghost commented Mar 26, 2015

please test

@cmsbuild
Copy link
Contributor

The tests are being triggered in jenkins.

@cmsbuild
Copy link
Contributor

-1
Tested at: cad9d95
The relvals timed out after 2 hours.

you can see the results of the tests here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-8518/3814/summary.html

@mark-grimes
Copy link

There are reports of database read problems, so I wouldn't worry too much about the "timed out after 2 hours", particular since this doesn't touch the standard tests.
I'm in the process of privately testing 12800 (normal TTI with muons) but with TTI replaced with TTILHCC in the relevant places. I'll report when done.

@mark-grimes
Copy link

merge

Tried the aforementioned tests and everything went fine. No idea about physics results though.
Get a few printouts of

Warning did not find digi

but that happens in the bare 12800 test. It's been a while since I've looked through the logs for that one.

cmsbuild added a commit that referenced this pull request Mar 26, 2015
TTI (Track Trigger Integration) descope scenarios
@cmsbuild cmsbuild merged commit bd874ff into cms-sw:CMSSW_6_2_X_SLHC Mar 26, 2015
@boudoul
Copy link
Contributor Author

boudoul commented Mar 26, 2015

thanks Mark! If I remember correctly, I asked in the past to remove the message ' did not find digi ' as it is supposed to be harmless - But seems to be still there - Maybe we need a confirmation that it is really harmless and then eventually remove it : @EmanuelPerez ? @aryd? - This message is coming from this code [1] ; can you comment on this? Thanks.

[1] https://github.com/cms-sw/cmssw/blob/CMSSW_6_2_X_SLHC/L1Trigger/TrackFindingTracklet/interface/slhcevent.hh#L1670

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