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
migration to 8_0_17 including fix for btag calibrator and BTV mitigation recipe #537
Conversation
…er_80X Protection against empty globalDirs
…rate_to_L1Stage2_80x TriggerResultsFilter: migrate to L1 Stage2 (80x)
80X HLT June15th train
…_json Extended hltDiff with CVS/JSON/ROOT output formats [8_0_X]
add V0 monitoring
tracking and strip DQM : trigger selection via DB + stage2 L1 handling in GenericTriggerEventFlag
adding new path to SUSY DQM and removing disabled path
…dFixEmptyHistograms Add ak8 dqm and fix empty histograms
fix HLT tracking client
…ErrorsA suppress LogError for somewhat clearly bad input of TrajectoryStateCombiner (backport of cms-sw#15016)
…ons80X Customization of pp reco for heavy ions (backport from 81X)
Reduce PCL disk space 80X
…ct_from-CMSSW_8_0_12 Protection in HistoryBase cycle against unfulfilled condition
Adding Layer number to bad module list
…5-2300_fixTrackingHLT add DCA plots in tracking@HLT DQM
…PrimitiveProducer cfi file as in RawToDigi_cff.py. In FullSimTP import Ecal and Hcal TrigPrimitiveProducers from individual cfi files.
It caused the log file to explode for a single specific application.
get 81x GetLumi.h
…ing of multiple IVF sequences
…nators with HIP mitigation
…ion available in PAT
…ded for only one track selection at a time; adding c-taggers
…n legacy SV TagInfos
fine with me On 9/2/16 11:23 AM, arizzi wrote:
|
in fact we could even move further to 8_0_19 merging from colin branch
@perrozzi @degrutto @bianchini please comment