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

Alignment LA correction for pixels #2067

Merged
merged 20 commits into from
Mar 13, 2014
Merged

Conversation

dkotlins
Copy link
Contributor

Include alignment LA correction in pixel RecHit, in both CPEs, generic and templates.
Split LA-width from LA-offset in CPEGeneric, they will be adjusted separately.
New DB objects still to come.

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @dkotlins for CMSSW_7_1_X.

Danek pre10

It involves the following packages:

EventFilter/SiPixelRawToDigi
RecoLocalTracker/SiPixelClusterizer
RecoLocalTracker/SiPixelRecHits
SimTracker/SiPixelDigitizer

@civanch, @nclopezo, @mdhildreth, @cmsbuild, @anton-a, @thspeer, @slava77, @Degano can you please review it and eventually sign? Thanks.
@gpetruc, @cerati, @GiacomoSguazzoni, @rovere this is something you requested to watch as well.
You can sign-off by replying to this message having '+1' in the first line of your reply.
You can reject by replying to this message having '-1' in the first line of your reply.

@nclopezo
Copy link
Contributor

-1

When I ran the RelVals I found an error in the following workflows:

4.53 step2
401.3 step1
5.1 step1
8.0 step2
1306.0 step2
25.0 step2

----- Begin Fatal Exception 20-Jan-2014 14:55:23 CET-----------------------
An exception of category 'Configuration' occurred while
   [0] Processing run: 1
   [1] Calling beginRun for unscheduled module EventSetupRecordDataGetter/'hltGetConditions'
   [2] Using EventSetup component PixelCPETemplateRecoESProducer/'hltESPPixelCPETemplateReco' to make data PixelClusterParameterEstimator/'hltESPPixelCPETemplateReco' in record TkPixelCPERecord
Exception Message:
MissingParameter: Parameter 'DoLorentz' not found.
----- End Fatal Exception -------------------------------------------------

You can see the results of the tests here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-2067/3/summary.html

@dkotlins
Copy link
Contributor Author

Hello,
Sorry for this.
I have added one more parameter to:
RecoLocalTracker/SiPixelRecHits/python/PixelCPETemplateReco_cfi.py

DoLorentz = cms.bool(False),

I forgot that all these parameters are also repeated in HLT config files in
HLTrigger/Configuration/python/*.py .

I suppose there is an automatic way to do it. I have to find out how to do it.

Best regards,
Danek


Danek Bohdan Kotlinski
danek.kotlinski@psi.ch
Phone: +41 563104030 (PSI), 0764875909 or 165909 (CERN)
Paul Scherrer Institut OFLC/004

On 20 Jan 2014, at 16:51, David Mendez notifications@github.com wrote:

-1

When I ran the RelVals I found an error in the following workflows:

4.53 step2
401.3 step1
5.1 step1
8.0 step2
1306.0 step2
25.0 step2

----- Begin Fatal Exception 20-Jan-2014 14:55:23 CET-----------------------
An exception of category 'Configuration' occurred while
[0] Processing run: 1
[1] Calling beginRun for unscheduled module EventSetupRecordDataGetter/'hltGetConditions'
[2] Using EventSetup component PixelCPETemplateRecoESProducer/'hltESPPixelCPETemplateReco' to make data PixelClusterParameterEstimator/'hltESPPixelCPETemplateReco' in record TkPixelCPERecord
Exception Message:
MissingParameter: Parameter 'DoLorentz' not found.
----- End Fatal Exception -------------------------------------------------
You can see the results of the tests here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-2067/3/summary.html


Reply to this email directly or view it on GitHub.

@dkotlins
Copy link
Contributor Author

Hello,
I found out from Martin Grunewald that the HLT configurations will be automatically
updated.
Best regards,
Danek

-----Original Message-----
From: David Mendez [mailto:notifications@github.com]
Sent: Mon 1/20/2014 4:51 PM
To: cms-sw/cmssw
Cc: Kotlinski Bohdan
Subject: Re: [cmssw] Danek pre10 (#2067)

-1

When I ran the RelVals I found an error in the following workflows:

4.53 step2
401.3 step1
5.1 step1
8.0 step2
1306.0 step2
25.0 step2

----- Begin Fatal Exception 20-Jan-2014 14:55:23 CET-----------------------
An exception of category 'Configuration' occurred while
   [0] Processing run: 1
   [1] Calling beginRun for unscheduled module EventSetupRecordDataGetter/'hltGetConditions'
   [2] Using EventSetup component PixelCPETemplateRecoESProducer/'hltESPPixelCPETemplateReco' to make data PixelClusterParameterEstimator/'hltESPPixelCPETemplateReco' in record TkPixelCPERecord
Exception Message:
MissingParameter: Parameter 'DoLorentz' not found.
----- End Fatal Exception -------------------------------------------------

You can see the results of the tests here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-2067/3/summary.html


Reply to this email directly or view it on GitHub:
#2067 (comment)

@cmsbuild
Copy link
Contributor

@mdhildreth
Copy link
Contributor

+1
On Jan 17, 2014, at 12:58 PM, cmsbuild notifications@github.com wrote:

A new Pull Request was created by @dkotlins for CMSSW_7_1_X.

Danek pre10

It involves the following packages:

EventFilter/SiPixelRawToDigi
RecoLocalTracker/SiPixelClusterizer
RecoLocalTracker/SiPixelRecHits
SimTracker/SiPixelDigitizer

@civanch, @nclopezo, @mdhildreth, @cmsbuild, @anton-a, @thspeer, @slava77, @Degano can you please review it and eventually sign? Thanks.
@gpetruc, @cerati, @GiacomoSguazzoni, @rovere this is something you requested to watch as well.
You can sign-off by replying to this message having '+1' in the first line of your reply.
You can reject by replying to this message having '-1' in the first line of your reply.


Reply to this email directly or view it on GitHub.


Mike Hildreth e-mail: mikeh@undhep.hep.nd.edu
Department of Physics mikeh@fnal.gov
225 Nieuwland Sciences Hall telephone: 574-631-6458 (office)
University of Notre Dame 574-631-5952 (FAX)
Notre Dame, IN 46556 http://www.hep.nd.edu/MikeHildreth

@nclopezo nclopezo modified the milestones: CMSSW_7_1_0_pre3, CMSSW_7_1_0_pre2 Feb 5, 2014
@@ -41,6 +41,7 @@

#include <iostream>

const bool MYDEBUG = false;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this constant is too generic and should not be in the header file.
Please, use LogDebug in this file.

@slava77
Copy link
Contributor

slava77 commented Feb 13, 2014

Hi Danek,

If these changes are expected to introduce changes in physics results,
please add some notes and maybe a few plots on what kind of change is coming.

Thanks

@slava77
Copy link
Contributor

slava77 commented Feb 13, 2014

-1

to 34c5307

based on the code review:

  • couts to be removed or changed to LogDebug or LogInfo
  • untracked parameters to be changed to tracked.

Please follow up and update in the same PR (my -1 will get reset then).

@dkotlins
Copy link
Contributor Author

Slava,
These changes are part of an bigger update. I just thought it was convenient to do it
in smaller steps.

The main purpose is to:

  1. be able to use the LA (lorentz angle) determined by the alignment group
  2. decouple LA value used for the hit resolution from the one used for hit offset
  3. separate the generic error parametrisation from the template objects.
    (1) and (2) is to better deal with radiation effects in the future, (3) is just for speed reasons
    and was discussed with Vincenzo.

By itself this does not change any physics results. If the same value is used the results
will be the same. But it gives us more flexibility to handle radiation.
So the validation will be to show that after introducing all these changes the resolution stays the same.

Most of you comments are simple and can be done easily.
I use the untracked parameter for a parameter which
should not be used from the python script but only from the DB. The option from the script is only for testing
purposes, when we test/optimize resolution it is much easier to have in as an input parameter instead of having
to create many DB objects. This usage is protected by a bool variable which is a tracked.
For the couts, I find them very convenient for debugging but will try to delete them in the final code.

I can make the corrections sometime next week and re-commit or simply wait for more modifications to come.
The idea is that it should all be ready before we restart data taking in 2015.

If you see a fundamental reason that the changes I have outline above cannot be implemented let us know
ASAP since several people are working on it now.

Best,
Danek


Danek Bohdan Kotlinski
danek.kotlinski@psi.ch
Phone: +41 563104030 (PSI), 0764875909 or 165909 (CERN)
Paul Scherrer Institut OFLC/004

On 13 Feb 2014, at 15:19, slava77 notifications@github.com wrote:

Hi Danek,

If these changes are expected to introduce changes in physics results,
please add some notes and maybe a few plots on what kind of change is coming.

Thanks


Reply to this email directly or view it on GitHub.

@slava77
Copy link
Contributor

slava77 commented Feb 21, 2014

Hi Danek,

Thank you for the explanations and the follow up.
For the couts, I can suggest something like
VinInn@27bbeb8#diff-7b9c837596d23ae09d2cd2a322051d5aR7
With a special flag, you should be able to recompile with couts showing up as you need, else they will just be hidden by LogTrace.
If you can live with LogTrace or LogDebug (requires recompilation anyways, but gives you more info on the origin of the printout), I'd suggest to just move to LogTrace.

@Dr15Jones
Copy link
Contributor

It is also important to remember that cout is not thread safe so your ouput could be garbled when run under the threaded framework. The MessageLogger is thread safe.

@dkotlins
Copy link
Contributor Author

Salvatore, its done.
But I thought that in test directories we are more free to do whatever is more convenient
for us. The code from test is never used in any official reconstruction/simulation process.
It is just for testing.
Best regards,
Danek

@diguida
Copy link
Contributor

diguida commented Mar 12, 2014

@dkotlins
In the tests you can do what you want, provided that you follow the rules of the CMSSW framework, I'd say (e.g., you crete histograms with TFileService, not bare ROOT).

@diguida
Copy link
Contributor

diguida commented Mar 12, 2014

+1
@slava77 no changes in the RECO code.

@slava77
Copy link
Contributor

slava77 commented Mar 12, 2014

+1

for #2067 8f0eaf3
just compiled as a sanity check (visually code diff ok)

@civanch
Copy link
Contributor

civanch commented Mar 13, 2014

+1

@cmsbuild
Copy link
Contributor

This pull request is fully signed and it will be integrated in one of the next CMSSW_7_1_X IBs unless changes or unless it breaks tests. @nclopezo, @ktf can you please take care of it?

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

This pull request is fully signed and it will be integrated in one of the next CMSSW_7_1_X IBs unless changes (tests are also fine). @nclopezo, @ktf can you please take care of it?

ktf added a commit that referenced this pull request Mar 13, 2014
Reco -- Alignment LA correction for pixels
@ktf ktf merged commit 4d4633d into cms-sw:CMSSW_7_1_X Mar 13, 2014
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.