-
Notifications
You must be signed in to change notification settings - Fork 5
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
Do not use the ECAL calibrated rechits from the GPU workflow #592
Do not use the ECAL calibrated rechits from the GPU workflow #592
Conversation
Validation summaryReference release CMSSW_11_2_0_pre10 at 6c149b2
Validation plots/RelValTTbar_14TeV/CMSSW_11_2_0_pre7-PU_112X_mcRun3_2021_realistic_v8-v1/GEN-SIM-DIGI-RAW
/RelValZMM_14/CMSSW_11_2_0_pre7-112X_mcRun3_2021_realistic_v8-v2/GEN-SIM-DIGI-RAW
/RelValZEE_14/CMSSW_11_2_0_pre7-112X_mcRun3_2021_realistic_v8-v1/GEN-SIM-DIGI-RAW
Validation plots (CPU vs GPU)/RelValTTbar_14TeV/CMSSW_11_2_0_pre7-PU_112X_mcRun3_2021_realistic_v8-v1/GEN-SIM-DIGI-RAW
/RelValZMM_14/CMSSW_11_2_0_pre7-112X_mcRun3_2021_realistic_v8-v2/GEN-SIM-DIGI-RAW
/RelValZEE_14/CMSSW_11_2_0_pre7-112X_mcRun3_2021_realistic_v8-v1/GEN-SIM-DIGI-RAW
Throughput plots/EphemeralHLTPhysics1/Run2018D-v1/RAW run=323775 lumi=53logs and
|
Hi @fwyzard are there any special permissions needed to see the validation plots? I get 404 errors or "not found". |
No - but I need to trigger publishing them by hand...
|
In my test a comparison of uncalibrated RecHits shows agreement between CPU and GPU: Comparing the RecHits shows differences. More RecHits are found for the CPU version (This includes PR #592 so the same RecHit producer should run for the CPU and GPU WFs): |
The trigger report for the GPU configuration is not what I was expecting though. It seems as if the CPU module also runs for the uncalibrated RecHits:
So perhaps the agreement in the post above actually comes from comparing CPU outputs with CPU outputs. For the RecHits the GPU modules do not process events though as expected.
|
Looking closer at the configuration it seems that |
Since the RecHitProducer is the same for CPU and GPU, the differences in the RecHit energy plot probably come from the inputs to the module. Looking a bit closer at the UncalibRecHits there are some variables that do show differences between the CPU and the GPU version. |
Hi @fwyzard what does the error in |
hi @thomreis sorry about that - you can disregard the |
No idea ... |
The ECAL calibrated rechits produced on the GPU are not yet correct.
Disable using them in the
gpu
workflows until they are working and validated.