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
Add "pixel tracking only" workflow to 2017 matrix, and it and "tracking only" workflow to 2018 matrix #21713
Conversation
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-21713/2588 |
A new Pull Request was created by @makortel (Matti Kortelainen) for master. It involves the following packages: Configuration/PyReleaseValidation @perrotta, @prebello, @vazzolini, @kmaeshima, @davidlange6, @civanch, @mdhildreth, @fabozzi, @cmsbuild, @franzoni, @jfernan2, @kpedro88, @slava77, @GurpreetSinghChahal, @vanbesien, @dmitrijus can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cmsbuild, please test workflow 10024.5,10824.1,10824.5 |
The tests are being triggered in jenkins. |
+1 The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: |
Comparison job queued. |
Comparison is ready @slava77 comparisons for the following workflows were not done due to missing matrix map:
Comparison Summary:
|
+1
|
+1 |
+1 |
+1 |
+1 |
merge |
This PR adds a "pixel tracking only" workflow aiming to have a minimal step3 configuration for producing pixel tracks and vertices (+ their validation). Such a workflow is useful e.g. for future tracking R&D.
Tested in CMSSW_10_0_X_2017-12-13-2300, no changes expected in existing workflows.
@VinInn @felicepantaleo @fwyzard