-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Non-reproducibility in patMETs_slimmedMETsNoHF #36552
Comments
assign reconstruction, xpog |
New categories assigned: xpog,reconstruction @slava77,@jpata,@mariadalfonso,@gouskos,@clacaputo,@fgolf you have been requested to review this Pull request/Issue and eventually sign? Thanks |
A new Issue was created by @makortel Matti Kortelainen. @Dr15Jones, @perrotta, @dpiparo, @makortel, @smuzaffar, @qliphy can you please review it and eventually sign/assign? Thanks. cms-bot commands are listed here |
Maybe not so rare, but recent, occurred again in #36550 (comment) and also in #36507 (comment). |
|
Slava suggested it might be AVX in DeepMET, checking further in the logs... |
Based on recent PRs, it looks like indeed an issue of executing TF on CPUs with different capabilities. PR:
This is a known issue with TF-based deepmet. |
type jetmet |
related to #32628 |
Tests in #36550 (comment) showed a difference in 2026D60 28234.0 all_mini_OldVSNew for patMETs_slimmedMETsNoHF
The PR should be purely technical, and I didn't find any earlier mention of a possible non-reproducibility there.
The text was updated successfully, but these errors were encountered: