Closed tschuh closed 2 years ago
Since Demonstrator.cc is used to test both Hybrid & TMTT, consider: 1) Moving Demonstrator.cc, .h & _cfi.py to TrackTrigger/ , where the _cfi.py file would have dummy values, such as "LabelIn = cms.string("InputEDProductName") 2) Add Demonstrator_cff.py to both TrackerTFP/python/ and TrackFindingTracklet/python/ . It would read in Demonstrator_cfi.py and override the dummy values there with the correct ones or Hybrid & TMTT.
@tschuh I'm ready to approve this, except that a few comments above have not been responded to.
sorry, somehow missed that there are outstanding comments.
After answering the trivial remaining comments above, the git complaint about "conflicts" needs resolving. I suspect this can be done by following the instructions in https://twiki.cern.ch/twiki/bin/view/CMS/L1TrackSoftware obtained under the heading "If other people have made changes the code above since you checked it out" for "(c) complicated case".
Since Demonstrator.cc is used to test both Hybrid & TMTT, consider:
- Moving Demonstrator.cc, .h & _cfi.py to TrackTrigger/ , where the _cfi.py file would have dummy values, such as "LabelIn = cms.string("InputEDProductName")
- Add Demonstrator_cff.py to both TrackerTFP/python/ and TrackFindingTracklet/python/ . It would read in Demonstrator_cfi.py and override the dummy values there with the correct ones or Hybrid & TMTT.
@tschuh any thoughts on this comment?
the values of hybrid demonstrator will be modified with a customize function living in TrackFindingTracklet in future. I would move Demonstrator to TrackTrigger if I can use it for the DTC.
This PR does:
This PR depends on https://github.com/cms-L1TK/cmssw/pull/110 This PR allows me to compare s/w with f/w for any event