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

Migrate customiseForRunI to era (81X) #13988

Merged

Conversation

makortel
Copy link
Contributor

@makortel makortel commented Apr 7, 2016

This PR is a partial forward-port of #13945, that is, migrating RecoTracker/Configuration/customiseForRunI.customiseForRunI to Run2_2016_trackingLowPU era (I'll leave the DataProcessing part for @slava77 to do). I should also note that the "erafication" is not fully equivalent to the customize:

Compared to #13945, the new configuration code is a bit tidied up, and the tracking validation is also included (was much easier to do here than in 80X thanks to the earlier phase1 era work).

Tested in 8_1_0_pre2 (rebased on top of CMSSW_8_1_X_2016-04-19-2300), no changes expected in standard workflows.

@rovere @VinInn

@cmsbuild
Copy link
Contributor

cmsbuild commented Apr 7, 2016

A new Pull Request was created by @makortel (Matti Kortelainen) for CMSSW_8_1_X.

It involves the following packages:

Configuration/StandardSequences
DQM/TrackingMonitorSource
RecoJets/JetProducers
RecoLocalTracker/SiStripClusterizer
RecoPixelVertexing/Configuration
RecoPixelVertexing/PixelTrackFitting
RecoTracker/ConversionSeedGenerators
RecoTracker/FinalTrackSelectors
RecoTracker/IterativeTracking
RecoTracker/TkTrackingRegions
Validation/RecoTrack

@cvuosalo, @cmsbuild, @franzoni, @deguio, @slava77, @vanbesien, @davidlange6 can you please review it and eventually sign? Thanks.
@ghellwig, @TaiSakuma, @yslai, @forthommel, @yduhm, @rappoccio, @nickmccoll, @cerati, @threus, @ahinzmann, @jdolen, @jlagram, @OlivierBondu, @schoef, @GiacomoSguazzoni, @rovere, @VinInn, @nhanvtran, @wmtford, @mschrode, @dgulhan, @Martin-Grunewald, @gbenelli, @gpetruc, @istaslis, @mariadalfonso this is something you requested to watch as well.
@slava77, @Degano, @smuzaffar you are the release manager for this.

cms-bot commands are list here #13028

@slava77
Copy link
Contributor

slava77 commented Apr 7, 2016

@cmsbuild please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Apr 7, 2016

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/12242/console

@cmsbuild
Copy link
Contributor

cmsbuild commented Apr 7, 2016

@cmsbuild
Copy link
Contributor

cmsbuild commented Apr 7, 2016

@makortel
Copy link
Contributor Author

Ping (the 80X version has been merged already).

_globalreco_tracking_Phase1PU70 = globalreco_tracking.copy()
_globalreco_tracking_Phase1PU70.replace(trackingGlobalReco, recopixelvertexing+trackingGlobalReco)
eras.trackingPhase1PU70.toReplaceWith(globalreco_tracking, _globalreco_tracking_Phase1PU70)
_globalreco_tracking_LowPU_Phase1PU70 = globalreco_tracking.copy()
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see that you merged the names.
I'd rather have a copy-pasted _globalreco_tracking_LowPU and _globalreco_tracking_Phase1PU70

I guess, this assumes that trackingPhase1PU70 will forever remain the SLHC almost-run1-like scenario used in TP, right?
[I was hoping it will go away at some point.]

Imagine we need to define a more proper Phase1 for PU70 in a couple of years. These merged-name LowPU_Phase1PU70 will have to be split up.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@slava77 No, I still intend to clean up the trackingPhase1PU70 after the trackingPhase1 is frozen for next year. Here (and in few other places) I just wanted to avoid copy-paste. I can split them or just rename them to _LowPU if you want (to me it's the same if I do it now or when cleaning up trackingPhase1PU70).

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's OK to stay if you are planning to update or refactor this later

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@slava77 OK. Would it be fine to leave the update to the point where trackingPhase1PU70 is cleaned up, or would you like to see it addressed sooner?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@makortel
it's OK to leave until trackingPhase1PU70 is cleaned up

@slava77
Copy link
Contributor

slava77 commented Apr 17, 2016

+1

for #13988 ee36a37

  • trackingLowPU is ported from 80X, omitting changes in the DataProcessing (to be submitted in a separate PR, likely by myself)
  • jenkins tests pass and comparisons with baseline show no difference
  • comparison of expanded configurations in run2 and 2017 configurations show no relevant differences between the baseline IB (CMSSW_8_1_X_2016-04-14-1100) and that with this PR
  • comparison of expanded configuration built with Run2_2016_trackingLowPU in 804 and in CMSSW_8_1_X_2016-04-14-1100+thisPR show no relevant differences related to this PR

@slava77
Copy link
Contributor

slava77 commented Apr 17, 2016

@deguio
please check this PR and sign if it's OK

@kpedro88
Copy link
Contributor

@deguio @franzoni reminder...

@davidlange6
Copy link
Contributor

@makortel @kpedro88 - this no longer merges - could you have a look

@cmsbuild
Copy link
Contributor

Pull request #13988 was updated. @cvuosalo, @cmsbuild, @franzoni, @deguio, @slava77, @vanbesien, @davidlange6 can you please check and sign again.

@slava77
Copy link
Contributor

slava77 commented Apr 20, 2016

@cmsbuild please test

@cmsbuild
Copy link
Contributor

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/12521/console

@slava77
Copy link
Contributor

slava77 commented Apr 20, 2016

+1

for #13988 164d8a1

  • rebased since the last signoff; manual check of the diffs confirms that this is the same code change as in the previously signed version, as described by @makortel
  • jenkins tests requested (but some will probably fail due to issues in the IB)

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

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

There are some workflows for which there are errors in the baseline:
134.911 step 3
140.53 step 2
1000.0 step 2
1001.0 step 2
1003.0 step 2
The results for the comparisons for these workflows could be incomplete
This means most likely that the IB is having errors in the relvals.The error does NOT come from this pull request

@slava77
Copy link
Contributor

slava77 commented Apr 21, 2016

@deguio
please check and sign this one if it's OK

@deguio
Copy link
Contributor

deguio commented Apr 22, 2016

+1

@davidlange6 davidlange6 merged commit c572228 into cms-sw:CMSSW_8_1_X Apr 22, 2016
@makortel
Copy link
Contributor Author

@rovere @VinInn @slava77 By the way, now that the era migration is merged, is there any reason to keep customiseForRunI and RunI_*_cff.py files around?

@slava77
Copy link
Contributor

slava77 commented Apr 27, 2016

On 4/27/16 10:11 AM, Matti Kortelainen wrote:

@rovere https://github.com/rovere @VinInn https://github.com/VinInn
@slava77 https://github.com/slava77 By the way, now that the era
migration is merged, is there any reason to keep |customiseForRunI| and
|RunI_*_cff.py| files around?

I think these can be removed in 81X.


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#13988 (comment)

@makortel makortel deleted the migrateCustomiseForRunIToEra_81x branch April 19, 2017 09:47
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.

6 participants