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

Update Phase2 MC GT to clean up unused Phase1 pixel conditions #42794

Merged
merged 1 commit into from
Sep 19, 2023

Conversation

saumyaphor4252
Copy link
Contributor

PR description:

This is a follow-up on cms-AlCaDB/AlCaTools#88.

With #42612 now merged, we have updated and cut the official versioned Phase2 GT 132X_mcRun4_realistic_v1 that removes the following currently unused Phase-1 pixel conditions:

Record Label 131X_mcRun4_realistic_v6 132X_mcRun4_realistic_v1
SiPixelDynamicInefficiencyRcd - SiPixelDynamicInefficiency_13TeV_v3_mc -
SiPixelFedCablingMapRcd - SiPixelFedCablingMap_mc -
SiPixelGainCalibrationForHLTRcd - SiPixelGainCalibrationForHLT_split_smeared_mc -
SiPixelGainCalibrationOfflineRcd - SiPixelGainCalibration_split_smeared_mc -
SiPixelTemplateDBObjectRcd 0T SiPixelTemplateDBObject_0T_v3_mc -

The difference between the new GT from the last one is here:

PR validation:

Successfully tested locally with runTheMatrix.py -l 22034.0, 23234.0, 24834.0 -j 8 --ibeos which consumes the auto:phase2_realistic key

If this PR is a backport please specify the original PR and why you need to backport that PR. If this PR will be backported please specify to which release cycle the backport is meant for:

Not a backport. Clean-up for future GTs, so no backport is expected so far.

@cmsbuild
Copy link
Contributor

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-42794/36906

  • This PR adds an extra 16KB to repository

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @saumyaphor4252 (Saumya Phor) for master.

It involves the following packages:

  • Configuration/AlCa (alca)

@perrotta, @cmsbuild, @consuegs, @saumyaphor4252 can you please review it and eventually sign? Thanks.
@Martin-Grunewald, @missirol, @mmusich, @fabiocos, @tocheng this is something you requested to watch as well.
@rappoccio, @antoniovilela, @sextonkennedy you are the release manager for this.

cms-bot commands are listed here

@saumyaphor4252
Copy link
Contributor Author

@cmsbuild, please test

@cmsbuild
Copy link
Contributor

-1

Failed Tests: RelVals-INPUT
Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-d917f7/34771/summary.html
COMMIT: e4daf06
CMSSW: CMSSW_13_3_X_2023-09-14-2300/el8_amd64_gcc11
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week0/cms-sw/cmssw/42794/34771/install.sh to create a dev area with all the needed externals and cmssw changes.

RelVals-INPUT

  • 13434.013434.0_TTbar_14TeV+2021FSPU/step2_TTbar_14TeV+2021FSPU.log
  • 14234.014234.0_TTbar_14TeV+2023FSPU/step2_TTbar_14TeV+2023FSPU.log
  • 24834.024834.0_TTbar_14TeV+2026D98/step2_TTbar_14TeV+2026D98.log
Expand to see more relval errors ...

Comparison Summary

Summary:

  • You potentially removed 4 lines from the logs
  • Reco comparison results: 8 differences found in the comparisons
  • DQMHistoTests: Total files compared: 50
  • DQMHistoTests: Total histograms compared: 3348648
  • DQMHistoTests: Total failures: 6
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 3348620
  • DQMHistoTests: Total skipped: 22
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.0 KiB( 49 files compared)
  • Checked 214 log files, 167 edm output root files, 50 DQM output files
  • TriggerResults: no differences found

@mmusich
Copy link
Contributor

mmusich commented Sep 15, 2023

13434.013434.0_TTbar_14TeV+2021FSPU/step2_TTbar_14TeV+2021FSPU.log

failures in run3 fast-sim look spurious...

@mmusich
Copy link
Contributor

mmusich commented Sep 15, 2023

@cmsbuild, please test

  • let's try again

@cmsbuild
Copy link
Contributor

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-d917f7/34786/summary.html
COMMIT: e4daf06
CMSSW: CMSSW_13_3_X_2023-09-15-1100/el8_amd64_gcc11
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week0/cms-sw/cmssw/42794/34786/install.sh to create a dev area with all the needed externals and cmssw changes.

Comparison Summary

Summary:

  • You potentially removed 1 lines from the logs
  • Reco comparison results: 8 differences found in the comparisons
  • DQMHistoTests: Total files compared: 50
  • DQMHistoTests: Total histograms compared: 3348648
  • DQMHistoTests: Total failures: 6
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 3348620
  • DQMHistoTests: Total skipped: 22
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.0 KiB( 49 files compared)
  • Checked 214 log files, 167 edm output root files, 50 DQM output files
  • TriggerResults: no differences found

@saumyaphor4252
Copy link
Contributor Author

+alca

  • results clean now
  • only diffs in msg Logger

@cmsbuild
Copy link
Contributor

This pull request is fully signed and it will be integrated in one of the next master IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @rappoccio, @antoniovilela, @sextonkennedy (and backports should be raised in the release meeting by the corresponding L2)

@makortel
Copy link
Contributor

Did this PR cause Alignment/OfflineValidation unit test to fail?

----- Begin Fatal Exception 19-Sep-2023 13:41:57 CEST-----------------------
An exception of category 'NoRecord' occurred while
   [0] Processing global begin Run run: 1
   [1] Calling method for module GeneralPurposeTrackAnalyzer/'trackanalysis'
Exception Message:
No "SiPixelFedCablingMapRcd" record found in the EventSetup.

 Please add an ESSource or ESProducer that delivers such a record.
----- End Fatal Exception -------------------------------------------------

https://cmssdt.cern.ch/SDT/cgi-bin/logreader/el8_amd64_gcc11/CMSSW_13_3_X_2023-09-19-1100/unitTestLogs/Alignment/OfflineValidation#/2510-2510

@kpedro88
Copy link
Contributor

Another test CondTools/RunInfo/test/CondToolsLHCInfoNewPopConTest is also failing:

===== Test "CondToolsLHCInfoNewPopConTest" ====
testing LHCInfoPerFillPopConAnalyzer in EndFill mode for startTime="2022-10-24 01:00:00.000" endTime="2022-10-24 20:00:00.000"
testing LHCInfoPerLSPopConAnalyzer in endFill mode for startTime="2022-10-24 01:00:00.000" endTime="2022-10-24 20:00:00.000"
testing LHCInfoPerLSPopConAnalyzer in endFill mode for startTime="2022-07-11 22:00:00.000" endTime="2022-07-12 18:10:10.000"
Failure LHCInfoPerLSPopConAnalyzer in endFill mode written wrong number of payloads: Expected 69, but got 70: status 1

---> test CondToolsLHCInfoNewPopConTest had ERRORS
TestTime:34
^^^^ End Test CondToolsLHCInfoNewPopConTest ^^^^

https://cmssdt.cern.ch/SDT/cgi-bin/logreader/el8_amd64_gcc11/CMSSW_13_3_X_2023-09-19-1100/unitTestLogs/CondTools/RunInfo#/2

@mmusich
Copy link
Contributor

mmusich commented Sep 19, 2023

Another test CondTools/RunInfo/test/CondToolsLHCInfoNewPopConTest is also failing:

I fail to see how can that be related (i.e. why it should use a Phase-2 GT, the only thing changed here...)

@makortel
Copy link
Contributor

Another test CondTools/RunInfo/test/CondToolsLHCInfoNewPopConTest is also failing:

I fail to see how can that be related (i.e. why it should use a Phase-2 GT, the only thing changed here...)

That test was also failing before this PR was merged.

@mmusich
Copy link
Contributor

mmusich commented Sep 19, 2023

That test was also failing before this PR was merged.

that makes more sense. Thank you.

@mmusich
Copy link
Contributor

mmusich commented Sep 19, 2023

Did this PR cause Alignment/OfflineValidation unit test to fail?

hopefully #42826 should fix the unit tests failures.

@mmusich
Copy link
Contributor

mmusich commented Sep 20, 2023

in addition there are three failing relval workflows in IB: https://cmssdt.cern.ch/SDT/html/cmssdt-ib/#/relVal/CMSSW_13_3/2023-09-19-2300?selectedArchs=el8_amd64_gcc11&selectedFlavors=X&selectedStatus=failed:

  • 20834.501
  • 20834.502
  • 24834.5

All failing with:

----- Begin Fatal Exception 20-Sep-2023 06:37:25 CEST-----------------------
An exception of category 'NoRecord' occurred while
   [0] Processing  Event run: 1 lumi: 64 event: 6303 stream: 2
   [1] Running path 'RECOSIMoutput_step'
   [2] Prefetching for module PoolOutputModule/'RECOSIMoutput'
   [3] Calling method for module SiPixelRawToDigi/'siPixelDigis@cpu'
Exception Message:
No "SiPixelFedCablingMapRcd" record found in the EventSetup.

 Please add an ESSource or ESProducer that delivers such a record.
----- End Fatal Exception -------------------------------------------------

@perrotta
Copy link
Contributor

in addition there are three failing relval workflows in IB: https://cmssdt.cern.ch/SDT/html/cmssdt-ib/#/relVal/CMSSW_13_3/2023-09-19-2300?selectedArchs=el8_amd64_gcc11&selectedFlavors=X&selectedStatus=failed:

  • 20834.501
  • 20834.502
  • 24834.5

All failing with:

----- Begin Fatal Exception 20-Sep-2023 06:37:25 CEST-----------------------
An exception of category 'NoRecord' occurred while
   [0] Processing  Event run: 1 lumi: 64 event: 6303 stream: 2
   [1] Running path 'RECOSIMoutput_step'
   [2] Prefetching for module PoolOutputModule/'RECOSIMoutput'
   [3] Calling method for module SiPixelRawToDigi/'siPixelDigis@cpu'
Exception Message:
No "SiPixelFedCablingMapRcd" record found in the EventSetup.

 Please add an ESSource or ESProducer that delivers such a record.
----- End Fatal Exception -------------------------------------------------

Uhm, weird...
@mmusich do you have already a fix in mind also for SiPixelRawToDigi (for example adding a UsePhase2 flag in analogy to UsePhase1, or replace the bool by an integer phase...). Or do you suggest to put back the SiPixelFedCablingMapRcd in the Phase2 GTs, instead?

@mmusich
Copy link
Contributor

mmusich commented Sep 20, 2023

do you have already a fix in mind also for SiPixelRawToDigi

we definitely should NOT run the phase-1 Pixel RawToDigi in a Phase-2 workflow. runTheMatrix should be patched in order to not run the pixel unpacker in phase2.

@kpedro88
Copy link
Contributor

runTheMatrix is just executing the workflows as they're written. Perhaps something in https://github.com/cms-sw/cmssw/blob/master/SimGeneral/MixingModule/python/pixelDigitizer_cfi.py or https://github.com/cms-sw/cmssw/blob/master/SimGeneral/MixingModule/python/SiPixelSimParameters_cfi.py needs to be changed for phase 1 vs. phase 2 (using appropriate Eras). Probably worth posting a dedicated issue for this.

@mmusich
Copy link
Contributor

mmusich commented Sep 20, 2023

@kpedro88

the unpacker has absolutely nothing to do with simulation (as you seem to imply, which I find quite worrisome). It's actually used in reconstruction.
In any case this is the line forcing to run the phase-1 unpacker:

upgradeWFs['pixelTrackingOnly'].step3 = {
'-s': 'RAW2DIGI:RawToDigi_pixelOnly,RECO:reconstruction_pixelTrackingOnly,VALIDATION:@pixelTrackingOnlyValidation,DQM:@pixelTrackingOnlyDQM',
'--datatier': 'GEN-SIM-RECO,DQMIO',
'--eventcontent': 'RECOSIM,DQM',
}

the issue is in runTheMatrix and nowhere else!

@kpedro88
Copy link
Contributor

Apologies, I just misread the comment. Indeed, pixel RawToDigi is already excluded in

from Configuration.Eras.Modifier_phase2_tracker_cff import phase2_tracker
# Remove siPixelDigis until we have phase2 pixel digis
# No Strips in the Phase-2 tracker
phase2_tracker.toReplaceWith(RawToDigiTask, RawToDigiTask.copyAndExclude([siPixelDigis,siStripDigis])) # FIXME
from standard workflows, but apparently not the special workflow as you point out.

@mmusich
Copy link
Contributor

mmusich commented Sep 20, 2023

I guess we could make this line

RawToDigi_pixelOnly = cms.Sequence(RawToDigiTask_pixelOnly)

an empty sequence with an era modifier (waiting to have a real phase-2 pixel unpacker)

@kpedro88
Copy link
Contributor

Yes, I'm just now preparing a PR with that change.

@perrotta
Copy link
Contributor

@mmusich what about adding a line

phase2_tracker.toReplaceWith(siPixelDigisTask, cms.Task())

in EventFilter/SiPixelRawToDigi/python/siPixelDigis_cff.py?

It seems to me the right place where to apply the modification, and easier to revert when we'll have a real phase-2 pixel unpacker.

By the way, I checked that it actually fixes the now failing workflows

@mmusich
Copy link
Contributor

mmusich commented Sep 20, 2023

@perrotta

that about adding a line

isn't this exactly what I suggested at: #42794 (comment)

By the way, I checked that it actually fixes the now failing workflows

also, I am afraid it does not...

@perrotta
Copy link
Contributor

@perrotta

that about adding a line

isn't this exactly what I suggested at: #42794 (comment)

Well, you were suggesting to replace it in Configuration/StandardSequences/python/RawToDigi_cff.py, I am suggesting instead to modify it directly in siPixelDigis_cff.py

By the way, I checked that it actually fixes the now failing workflows

also, I am afraid it does not...

I succesfully run step3 of wf 24834.5 with it...

@mmusich
Copy link
Contributor

mmusich commented Sep 20, 2023

I succesfully run step3 of wf 24834.5 with it...

try the ones with the gpu modifier.... :D

@mmusich
Copy link
Contributor

mmusich commented Sep 20, 2023

for the record, #42830 solves. We can discuss if we instead we want to go #42794 (comment) (I need to ponder a bit pros and cons)

@kpedro88
Copy link
Contributor

I think the advantage of #42794 (comment) is that it avoids the need to remove siPixelDigis with phase2_tracker.toReplaceWith(... in two different places in RawToDigi_cff.py. One could also turn siStripDigis into a Task and then the phase2_tracker.toReplaceWith(... could be removed entirely from RawToDigi_cff.py.

@perrotta
Copy link
Contributor

One could also turn siStripDigis into a Task and then the phase2_tracker.toReplaceWith(... could be removed entirely from RawToDigi_cff.py.

Well, for siStrip the situation is different: it will not be there in Phase 2.

I would suggest to empty the siPixelDigisTask in siPixelDigis_cff.py (with the intent to have it back in at some time) but keep removing the siStripDigis from RawToDigi_cff.py, as it is done now, because they are not supposed to get back.

@mmusich
Copy link
Contributor

mmusich commented Sep 20, 2023

Well, for siStrip the situation is different: it will not be there in Phase 2.

I agree with this assessment, that's why I originally remove it from the raw2digi in 1647c50

I would suggest to empty the siPixelDigisTask in siPixelDigis_cff.py (with the intent to have it back in at some time) but keep removing the siStripDigis from RawToDigi_cff.py, as it is done now, because they are not supposed to get back.

I couldn't think of adverse effects, hence that's what's currently implemented in #42830

@saumyaphor4252 saumyaphor4252 deleted the alca_Update_Phase2_GT branch October 13, 2023 15:05
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.

7 participants