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
Geometry data xml description #252
Conversation
ianna
commented
Aug 7, 2013
- Remaining XML data files from external data package are now back in CMSSW (as discussed with Giulio)
- Upgrade scenarios up-to-date
- New FastSim scenario for PhaseI (note it's in PhaseI/Forward)
- Geometry/CaloEventSetup corrections for HE corner and center references used in a test
- Geometry/MuonCommonData tag V01-08-06 was taken with changes in GEM in v4: Correcting the partitioning og 8-etaPartition GEM chamber
Hi, I took CMSSW_7_0_X_2013-08-08-0200, pulled these changes, and ran the RelVals (It tested the changes including also the ones in #257, to avoid unrelated errors) and unit tests, all tests passed. |
The following categories have been signed by yana (a.k.a. @ianna on GitHub): Geometry @cms-git-visualization, @cms-git-geometry |
…move commented out lines from geometry definition. Add sensitive volume sim definition.
…move commented out lines from geometry definition. Add sensitive volume sim definition.
The following categories have been signed by yana (a.k.a. @ianna on GitHub): Geometry @cms-git-visualization, @cms-git-geometry |
1 similar comment
The following categories have been signed by yana (a.k.a. @ianna on GitHub): Geometry @cms-git-visualization, @cms-git-geometry |
@nclopezo can you test again with the new additions? |
Hi I tested it again with CMSSW_7_0_X_2013-08-09-0200. All tests passed. Building, unit tests logs and RelVals logs can be found here: |
…s_PRs_223_227_noEleMVA Port some PRs into Heppy branch
no -k option for building cmssw-tool-conf; same cmsBuild options passed everywhere
Make unit tests that require a CUDA device skip the test and exit succesfully if the CUDA runtime is not available, or no CUDA devices are available.
* energy scale, smearing corrector * update foresting configs
Make unit tests that require a CUDA device skip the test and exit succesfully if the CUDA runtime is not available, or no CUDA devices are available.