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

Validation modules for ME0 Detector (Phase2 Upgrade) #11941

Closed

Conversation

cmsbuild
Copy link
Contributor

Validation modules for ME0 Detector (Phase2 Upgrade)

This PR include Validation/MuonME0Hits, MuonME0Digis, MuonME0RecHits module to validate ME0 simulation.

  • MuonGEMHits module is related to SimHit on ME0 Detector.
  • MuonGEMDigis module is related to Digi step about ME0.
  • MuonGEMRecHits module is related both to ME0 RecHits and ME0 Segments.

This PR does not affect other modules.

These module are only run by a specific customize options. (Validation/MuonME0Hits/python/me0Custom.py)
Automatically ported from CMSSW_7_6_X #11461 (original by @clacaputo).

Compilation --> OK
Run --> Not already tested

- Validation/MuonME0Hits/interface/ME0BaseValidation.*
   Abstract Class for the ME0 validation packages
- Validation/MuonME0Hits/src/ME0HitsValidation.*
   Book histos, loop on simHits, fill histos
- Validation/MuonME0Hits/plugins/MuonME0HitsValidator.cc
   Plugin definition
- Validation/MuonME0Hits/python/MuonME0Hits_cfi.py
   PSet for the ME0HitsValidation module
Compilatio -->OK
Run --> toBe tested

new file:   Validation/MuonME0Digis/interface/ME0DigisValidation.h
new file:   Validation/MuonME0Digis/src/ME0DigisValidation.cc
- Inherited from ME0BaseValidation class
Compilation --> OK
Testing     --> NO

Structure of the package Validation/MuonME0RecHits is similar to
the digi packages.

modified:   SLHCUpgradeSimulations/Configuration/python/fixMissingUpgradeGTPayloads.py
- "connect" parameter changed to "untracked" in "fixRPCConditions"

new file:   Validation/MuonME0Hits/test/Generate.sh
- collection of "cmsDriver.py" commands for the GEN-SIM-DIGI step,
  Validation step and Harvest Step
Compiling ----> Ok
running   ----> Ok
@cmsbuild
Copy link
Contributor Author

A new Pull Request was created by @cmsbuild for CMSSW_8_0_X.

Validation modules for ME0 Detector (Phase2 Upgrade)

It involves the following packages:

Validation/MuonME0Digis
Validation/MuonME0Hits
Validation/MuonME0RecHits

The following packages do not have a category, yet:

Validation/MuonME0Digis
Validation/MuonME0Hits
Validation/MuonME0RecHits

@cmsbuild can you please review it and eventually sign? Thanks.
You can sign-off by replying to this message having '+1' in the first line of your reply.
You can reject by replying to this message having '-1' in the first line of your reply.
If you are a L2 or a release manager you can ask for tests by saying 'please test' in the first line of a comment.
@Degano you are the release manager for this.
You can merge this pull request by typing 'merge' in the first line of your comment.

@deguio
Copy link
Contributor

deguio commented Nov 16, 2015

please test

@cmsbuild
Copy link
Contributor Author

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

@cmsbuild
Copy link
Contributor Author

-1
Tested at: cf0a3e2
I found a compilation error while trying to compile with clang:
I used this command:
scram b vclean && scram build -k -j 8 USER_CXXFLAGS='-fsyntax-only' COMPILER='llvm compile'

Entering library rule at src/Validation/MuonME0Digis/plugins
>> Compiling  /tmp/cmsbuild/workspace/ib-any-integration/CMSSW_8_0_X_2015-11-15-2300/src/Validation/MuonME0RecHits/src/ME0RecHitsValidation.cc 
>> Compiling  /tmp/cmsbuild/workspace/ib-any-integration/CMSSW_8_0_X_2015-11-15-2300/src/Validation/MuonME0RecHits/src/ME0SegmentsValidation.cc 
Entering library rule at src/Validation/MuonME0RecHits/plugins
>> Compiling edm plugin /tmp/cmsbuild/workspace/ib-any-integration/CMSSW_8_0_X_2015-11-15-2300/src/Validation/MuonME0Hits/plugins/MuonME0HitsValidator.cc 
/tmp/cmsbuild/workspace/ib-any-integration/CMSSW_8_0_X_2015-11-15-2300/src/Validation/MuonME0Hits/src/ME0HitsValidation.cc:87:23: error: unused variable 'Gp0' [-Werror,-Wunused-variable]
    const GlobalPoint Gp0(ME0Geometry_->idToDet(hits->detUnitId())->surface().toGlobal(p0));
                      ^
/tmp/cmsbuild/workspace/ib-any-integration/CMSSW_8_0_X_2015-11-15-2300/src/Validation/MuonME0Hits/src/ME0HitsValidation.cc:96:22: error: unused variable 'hitEP' [-Werror,-Wunused-variable]
    const LocalPoint hitEP(hits->entryPoint());
                     ^


you can see the results of the tests here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-11941/9746/summary.html

@cmsbuild
Copy link
Contributor Author

@deguio
Copy link
Contributor

deguio commented Nov 19, 2015

-1
to be fixed

@cmsbuild
Copy link
Contributor Author

Pull request #11941 was updated. @cmsbuild, @vanbesien, @deguio, @davidlange6 can you please check and sign again.

@clacaputo
Copy link
Contributor

Dear @deguio, I've just updated the code following your suggestions. Could you please trigger the test?
Thanks

@deguio
Copy link
Contributor

deguio commented Dec 16, 2015

please test

@cmsbuild
Copy link
Contributor Author

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

@cmsbuild
Copy link
Contributor Author

@cmsbuild
Copy link
Contributor Author

@deguio
Copy link
Contributor

deguio commented Dec 17, 2015

+1

@cmsbuild
Copy link
Contributor Author

This pull request is fully signed and it will be integrated in one of the next CMSSW_8_0_X IBs (tests are also fine). This pull request requires discussion in the ORP meeting before it's merged. @slava77, @davidlange6, @Degano, @smuzaffar

@davidlange6
Copy link
Contributor

@ciacaputo, @deguio - sorry for my slow review - this all looks good, however could you put it in one instead of 3 new packages? Thanks!

@clacaputo
Copy link
Contributor

Dear @davidlange6, I split the validation in three different packages because this is the usual structure already implemented in the other subdetector validation packages. Should I move to the "one-package" solution or I could keep the "three-packages" solution?

@calabria
Copy link
Contributor

Please @davidlange6 let us know what you prefer to do here, this PR is pending since long time and we need to have it included in 800. Thanks a lot.

@davidlange6
Copy link
Contributor

@calabria @clacaputo - sorry to not answer - please stick to one package. Thanks!

@clacaputo
Copy link
Contributor

Dear @davidlange6 , should I make a new PR with the one-package solution? Or simply push to ME0_DQM_Validation_Porting_76X ? Thanks.

@davidlange6
Copy link
Contributor

@clacaputo - it looks like you will need to open a new PR as this one is owned by cmsbuild (you can just modify your old branch if you still have it)

@davidlange6
Copy link
Contributor

I will close this PR while a new one is made by @clacaputo

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

5 participants