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

sync OMTF code (as in tag omtfdev_mk20). #24539

Conversation

rekovic
Copy link
Contributor

@rekovic rekovic commented Sep 14, 2018

PR 10_3_X
Changes includes:

  • fix for missing CSC offset in raw to digi in (in packer and unpacker)
  • fixed mem leaks
  • emulator: allow for emulator reconstruction in bx other than 0.
  • emulator: new omtf algorithm (sc-called v5, compatible with the one prepared for P5 running);
    the new algo is planned to be enabled by o2o with omtf algo key 'omtf_algo_base/v4';
    until then old algorithm is enabled.
  • emulator: new omtf algorithm v6 which improves eta assignment w.r.t. v5
    The above changes in packer/unpacker and algorithm in emulator is only affecting re-emulation of data (DQM offline/online) and not effecting MC production. Change in emulator does not effect MC production since the MC Global Tag is not updated.

Changes includes:
 - fix for missing CSC offset in raw to digi
 - fixed mem leaks
 - allow for emulator reconstruction in bx other than 0.
 - new omtf algorithm (sc-called v5, compatible with the one prepared for P5 running);
   the new algo is planned to be enabled by o2o with omtf algo key 'omtf_algo_base/v4';
   until then old algorithm is enabled.
@cmsbuild cmsbuild added this to the CMSSW_10_3_X milestone Sep 14, 2018
@rekovic
Copy link
Contributor Author

rekovic commented Sep 14, 2018

please test

@cmsbuild
Copy link
Contributor

The code-checks are being triggered in jenkins.

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

cmsbuild commented Sep 14, 2018

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/30411/console Started: 2018/09/14 11:02

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @rekovic for master.

It involves the following packages:

EventFilter/L1TRawToDigi
L1Trigger/L1TMuonOverlap

@nsmith-, @rekovic, @cmsbuild, @thomreis can you please review it and eventually sign? Thanks.
@Martin-Grunewald, @thomreis this is something you requested to watch as well.
@davidlange6, @slava77, @fabiocos you are the release manager for this.

cms-bot commands are listed here

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

Comparison job queued.

@cmsbuild
Copy link
Contributor

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

Comparison Summary:

  • No significant changes to the logs found
  • Reco comparison results: 0 differences found in the comparisons
  • DQMHistoTests: Total files compared: 32
  • DQMHistoTests: Total histograms compared: 3147366
  • DQMHistoTests: Total failures: 167
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 3147002
  • DQMHistoTests: Total skipped: 197
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.0 KiB( 31 files compared)
  • Checked 133 log files, 14 edm output root files, 32 DQM output files

   The improvement is based on assigning eta from vetoed muon candidates
   in GM, in case the best candidate is based on hit from DT and has
   no eta assigned (frequent for DT hits in wheel2).
   The switch to new eta assignment based on o2o'ed config.
2) minor bugfix in emulator wrt firmware
   for negative phi assigned use floor instead
   of taking int. It is very rare case, in most have positive resulting phi is positive.
3) minor bugfix in emulator wrt firmware
   in cases where there are 2 hits of the same parameters does not try to merge them
   (for DT and CSC hits). In firmware they occupy tow inputs. Very rare usecase.
@rekovic rekovic changed the title sync OMTF code (as in tag omtfdev_mk20) with CMSSW_2_1_0. sync OMTF code (as in tag omtfdev_mk20). Sep 18, 2018
@rekovic
Copy link
Contributor Author

rekovic commented Sep 18, 2018

please test

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

cmsbuild commented Sep 18, 2018

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/30471/console Started: 2018/09/18 09:56

@cmsbuild
Copy link
Contributor

Pull request #24539 was updated. @nsmith-, @rekovic, @cmsbuild, @thomreis can you please check and sign again.

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

Comparison job queued.

@rekovic
Copy link
Contributor Author

rekovic commented Sep 18, 2018

+1

@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. @davidlange6, @slava77, @smuzaffar, @fabiocos (and backports should be raised in the release meeting by the corresponding L2)

@cmsbuild
Copy link
Contributor

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

The workflows 4.53 have different files in step1_dasquery.log than the ones found in the baseline. You may want to check and retrigger the tests if necessary. You can check it in the "files" directory in the results of the comparisons

Comparison Summary:

  • No significant changes to the logs found
  • Reco comparison results: 0 differences found in the comparisons
  • DQMHistoTests: Total files compared: 32
  • DQMHistoTests: Total histograms compared: 2681819
  • DQMHistoTests: Total failures: 167
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 2681482
  • DQMHistoTests: Total skipped: 170
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.0 KiB( 27 files compared)
  • Checked 119 log files, 10 edm output root files, 32 DQM output files

@fabiocos
Copy link
Contributor

@rekovic I see that not only 2018 workflows are affected (136.85) but also 2017 ones (136.788). Is this intended?

@fabiocos
Copy link
Contributor

@rekovic could you please answer my question? I would like to merge this PR, but I would like to be sure that the DQM checks are understood

@rekovic
Copy link
Contributor Author

rekovic commented Sep 25, 2018

@fabiocos Yes, this will affect re-emulation of both 2017 and 2018 data.

@fabiocos
Copy link
Contributor

+1

@cmsbuild cmsbuild merged commit 4626d53 into cms-sw:master Sep 25, 2018
@kpedro88 kpedro88 mentioned this pull request Sep 28, 2018
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.

None yet

4 participants