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

Critical revision of the CASTOR monitor package... + postprocessing + hiding 4 histograms #7499

Merged

Conversation

vanbesien
Copy link
Contributor

This PR supersedes #7365

We additionally commented away 4 very large histograms.

... so that at least this PR can be accepted and in a later stage the 4 histograms can be added again in a "smaller" version.

popovvp and others added 30 commits January 16, 2015 12:29
CastorDataIntegrityMonitor

These files were intended to be removed, but somehow ended up being just
"empty". The files still existed, but had no content and size 0.
New deleting the different sub modules in the destructor.
Removed beginJob and placed content in dqmbeginrun (since it needs
iSetup)
Removed endJob and also removed the corresponding done() methods in the
subclasses. Only one of these done() had content, which was stricly
verbose output.
@cmsbuild
Copy link
Contributor

cmsbuild commented Feb 2, 2015

@deguio
Copy link
Contributor

deguio commented Feb 2, 2015

+1

@cmsbuild
Copy link
Contributor

cmsbuild commented Feb 2, 2015

This pull request is fully signed and it will be integrated in one of the next CMSSW_7_4_X IBs unless changes (tests are also fine). This pull request will be automatically merged.

cmsbuild added a commit that referenced this pull request Feb 2, 2015
Critical revision of the CASTOR monitor package... + postprocessing + hiding 4 histograms
@cmsbuild cmsbuild merged commit cdf9ac9 into cms-sw:CMSSW_7_4_X Feb 2, 2015
@cmsbuild
Copy link
Contributor

cmsbuild commented Feb 3, 2015

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