Skip to content

Refactoring of DB Monitoring code#27

Open
mverzett wants to merge 46 commits intoventuria:CMSSW_7_4_Xfrom
mverzett:from-CMSSW_7_4_0_pre2
Open

Refactoring of DB Monitoring code#27
mverzett wants to merge 46 commits intoventuria:CMSSW_7_4_Xfrom
mverzett:from-CMSSW_7_4_0_pre2

Conversation

@mverzett
Copy link

No description provided.

Igor and others added 30 commits November 10, 2014 23:28
of the  DYT TeV refit code presently under development toghether
with the trivial code to populate it from txt.
Add new callback that services can register for
that will deliver information about the paths,
end paths, and modules on them. It will also deliver
information about the dependencies between modules
in the current process based on the consumes information.
It also makes available the information in the
consumes declarations. Also includes a new configuration
option to the Tracer that will dump this information
and the Tracer code is an example of how a service
accesses this information. New and expanded unit
tests included.
fixed chi2 constraint on pedestal and time
…SSW_7_4_X

Conflicts:
	RecoLocalCalo/HcalRecAlgos/src/PulseShapeFitOOTPileupCorrection.cc
…ed out with the delta HT kept as zero. Added a new option setDPhiZero, that is defaulted to reproduce old behaviour
CondFormat storing configuration parameters for the new DYT
In order to make it easier to compare different configurations, we now sort the named items used in the configuration.
adding puppi fix for miniAOD definitions of charged particles
cmsbuild and others added 16 commits December 12, 2014 07:52
Add service callback with path and consumes info
Option to use old CPE error if charge exceeds one MIP
Anonymous namespace here can cause build warnings
Migration of standard fullsim/fastsim relvals to Pythia 8
…_bug_fix

remove nbins factor as done already in 73x
…mplate

74X: Moving HLT config to use 730 template
…and allow the addition of strip tracker-wide plots
@venturia
Copy link
Owner

I am not sure I have understood. There are plenty of commits that have nothing to do with DB monitoring

@mverzett
Copy link
Author

I know, I have no clue where they come from (still a bit confused by CMSSW flavor of git). Maybe I asked to PR to the wrong branch?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.