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
pixel DQM@HLT #18252
pixel DQM@HLT #18252
Conversation
A new Pull Request was created by @mtosi (mia tosi) for CMSSW_9_0_X. It involves the following packages: DQM/HLTEvF @cmsbuild, @silviodonato, @dmitrijus, @Martin-Grunewald, @fwyzard, @vanbesien, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@mtosi @fioriNTU since it's for online DQM workflow, I added this PR to https://twiki.cern.ch/twiki/bin/view/CMS/DQMP5TagCollector |
please test |
The tests are being triggered in jenkins. |
Hi, you need to make a 91X PR which gets integrated first (in 91X) |
yes, thanks Martin
I'm working on it
but the pixel and strip DQM in 91x is different (I've just realized)
and I have to patch some files
I'm doing it, now
mia
…On Fri, Apr 7, 2017 at 12:42 PM, Martin Grunewald ***@***.***> wrote:
Hi, you need to make a 91X PR which gets integrated first (in 91X)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#18252 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AEt589pAAx3SRe8-g9LcR1ci8NqRKbs9ks5rthMJgaJpZM4M2pbt>
.
|
thanks !
mia
…On Fri, Apr 7, 2017 at 12:25 PM, threus ***@***.***> wrote:
@mtosi <https://github.com/mtosi> @fioriNTU <https://github.com/fioriNTU>
I added this PR to https://twiki.cern.ch/twiki/
bin/view/CMS/DQMP5TagCollector
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#18252 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AEt58wpB_E5VvuPmjZ8zUUP4SIcZgVtsks5rtg8AgaJpZM4M2pbt>
.
|
Comparison job queued. |
Comparison is ready Comparison Summary:
|
+1 |
while testing this PR on the DQM playback I need to update this PR [1]Begin processing the 1st record. Run 500150, Event 1, LumiSection 1 at 10-Apr-2017 10:00:34.241 CEST
|
Comparison job queued. |
Comparison is ready Comparison Summary:
|
@mtosi : there are indeed a handful of other differences between this PR and the one merged in the master. First of all, the ones I don't care about (just for your info):
Then, in the following I notice that L162 was removed in #18264 and not here:
Are you sure that it had to be removed from #18264? (It doesn't look so to me; but then, if it is correct you would like to remove that line also from here) Finally, about what mostly refers to reco in this PR: the protections added to
are all quite reasonable, but I don't see them in your 91X PR, and not even merged in the master with some other pull request. Is there any reason why they should only stay here and not in the master? (Or perhaps they are already queued with some other PR and I just did not spot them)? |
opsi ok, let me check
point 1. and 2. probably should not be in any PR :( the differences in point 3. should simply reflect the differences between the 2 releases of the main SiPixelPhase1 DQM code (there are some updates / new features only available in the master)
=> if you agree, I would leave this PR as it is now thanks again for your help/support (and patience !) |
Fine with me if you integrate in this PR the "best possible" version, and propagate it to the master with another dedicated PR. If you keep the codes in the different releases synchronized (unless needed otherwise) it then becomes easier for you to propagate the possible fixes... and for us to review! Ciao, |
ehehe ;) |
+1 |
+1
|
@dmitrijus |
+1 |
This pull request is fully signed and it will be integrated in one of the next CMSSW_9_0_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_9_2_X is complete. This pull request requires discussion in the ORP meeting before it's merged. @davidlange6, @smuzaffar |
+1 |
--finally--
we have the pixel@HLT DQM
this PR add the pixel@HLT DQM on both online and offline workflow
@fioriNTU
while testing this w/ runTheMatrix.py --limited
I saw that SiPixelPhase1TrackCluster was not checking the validity of the input collections,
not it is fixed
I also add the lumiMonitoring to the HLT offline DQM
(even if this module makes use of the lumi measurement from the scaler)
in addition, I fixed the strip DQM in the HLT online DQM as well
and add the monitoring of the HLT_ZeroBias_FirstCollisionAfterAbortGap
which is one of the calibration triggers for the tracker DPG (used for the strip APV gain)
finally, I add the client in the online DQM,
as now for both the tracking (iterative and GSF) and pixel