-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
update navigation graph tool for SLHC #3071
update navigation graph tool for SLHC #3071
Conversation
A new Pull Request was created by @cerati for CMSSW_6_2_X_SLHC. update navigation graph tool for SLHC It involves the following packages: RecoTracker/TkNavigation @nclopezo, @cmsbuild, @anton-a, @thspeer, @slava77, @Degano can you please review it and eventually sign? Thanks. |
why are we going away from using TrackerTopology ? |
Because it is not working - at least in this piece of code |
@davidlange6 : is that expected? Can't it be fixed? Are we sure that the DetId classes are correct for the upgrade geometry? Or maybe it is just a matter of updating TrackerTopology with the latest change in the detid classes, if any? We can't make step backward |
I guess its a cfg problem. Please explain the error |
it returns always layer=0 |
It seems you cfg lacks customize statements needed by the tracker. I can suggest something later. On Mar 28, 2014, at 4:13 PM, "cerati" <notifications@github.commailto:notifications@github.com> wrote: it returns always layer=0 — |
you need the same as in the customize function for the tracker slhc geometries (clearly a more robust solution is needed here, but its what we have today) def customise_condOverRides(process): On Mar 28, 2014, at 4:23 PM, David Lange David.Lange@cern.ch wrote:
|
ok using topology+all the TLR above gives the same output as this PR. |
I think it is better to use TrackerTopology and the proper configuration. |
merge passes all working tests |
update navigation graph tool for SLHC
In .cc: - TrackerTopology migration - Change in printout logic In _cfg.py: - Add upgrade stuff in comments
not run in any workflow but useful for producing nice debugging graphs