CSC HLT communication and status

Keep track of the CSC HLT configuration change communication

Request from Martin G.:
[For updates] send me a file which containes ONLY the changed modules! Even better would be you put the (changed) modules in your user area in ConfDB.

Procedure:

  • as soon as tag is published that makes a parameter change neccessary, mail Martin and tell him tag name and the changed parameters
  • he will test and negotiate with release managers
  • changes are: name change, type change, value change, presence change

Find the HLT config browser here: http://cms-project-confdb-hltdev.web.cern.ch/cms-project-confdb-hltdev/browser/

CMSSW_3_8_X

Newer changes are listed on top, older ones at the bottom.

Status / Changes so far

  • Done change: RecoLocalMuon/CSCRecHitD V02-04-04: New Tag queued with one changed parameter-value for HLT config


 Dear Martin,

a new tag was published last Friday for RecoLocalMuon/CSCRecHitD V02-04-04
It was added to 38X

This tag brings along one change for the HLT configuration:

It brings a change to an existing parameter, as can be seen here:

http://cmssw.cvs.cern.ch/cgi-bin/cmssw.cgi/CMSSW/RecoLocalMuon/CSCRecHitD/python/cscRecHitD_cfi.py?r1=1.12&r2=1.13

This specifically is changed:

process.hltCsc2DRecHits.CSCUseTimingCorrections = cms.bool(False),

to

process.hltCsc2DRecHits.CSCUseTimingCorrections = cms.bool(True),

Amanda informed me that the parameter "True" will only work with global tags _V5 and later. Will this be a problem?

Maybe you are aware of this release anyway, as it was published by Jean-Roch?

  Cheers, Ingo 

  • Expected change: RecoLocalMuon/CSCRecHitD V02-04-01 or higher : New Tag queued with one new parameter for HLT config

Hi Tim;

No problem, the parameter is already in recent 36X/37X/38X HLT
config dumps.

Best regards

Martin

On Mon, 31 May 2010, Tim Cox wrote:

> Hi Martin,
>
> We have revived the tag we initially intended for 37X, as described by Ingo in the attached email, for 38X. This adds one parameter to the CSC rechit-building config file as part of
> RecoLocalMuon/CSCRecHitD V02-04-01
> in which timing corrections in conditions data are used to improve our rechit times.
>
> The relevant tags on top of 370 are:
>
> CalibMuon/CSCCalibration    V02-02-00
> CondCore/CSCPlugins         V00-03-00
> CondFormats/CSCObjects      V03-05-07
> RecoLocalMuon/CSCRecHitD    V02-04-01
>
> They have been published for 38X where we can, and requested of the Reco and AlCa conveners for inclusion in 38X.
>
> The appropriate tags for the new conditions data are still in preparation, but I presume they'll appear once Gianluca is happy with them.
>
> Regards, Tim
>
> On May 17, 2010, at 12:56 , Ingo Bloch wrote:
>
>> Dear Martin,
>>
>> a new tag was just released for RecoLocalMuon/CSCRecHitD V02-04-01
>>
>> It is queued it for 37X.
>>
>> This tag brings along one change for the HLT configuration:
>>
>> It brings a new parameter, as can be seen here:
>>
>> http://cmssw.cvs.cern.ch/cgi-bin/cmssw.cgi/CMSSW/RecoLocalMuon/CSCRecHitD/python/cscRecHitD_cfi.py?r1=1.11&r2=1.12
>>
>>
>> This specifically is added:
>>
>> process.hltCsc2DRecHits.CSCUseTimingCorrections = cms.bool(False),
>>
>> We hope that in spite of the late time you can still integrate this change into the HLT config.
>>
>>   Cheers, Ingo
>>
>
>

CMSSW_3_7_X

Newer changes are listed on top, older ones at the bottom.

Status / Changes so far

  • Change: RecoLocalMuon/CSCRecHitD V02-03-00, no HLT change!!
    • Original change: RecoLocalMuon/CSCRecHitD V02-04-01 : New Tag queued with one new parameter for HLT config

Dear Martin,

a new tag was just released for RecoLocalMuon/CSCRecHitD V02-04-01

It is queued it for 37X.

This tag brings along one change for the HLT configuration:

It brings a new parameter, as can be seen here:

http://cmssw.cvs.cern.ch/cgi-bin/cmssw.cgi/CMSSW/RecoLocalMuon/CSCRecHitD/python/cscRecHitD_cfi.py?r1=1.11&r2=1.12


This specifically is added:

process.hltCsc2DRecHits.CSCUseTimingCorrections = cms.bool(False),

We hope that in spite of the late time you can still integrate this
change into the HLT config. 

   Cheers, Ingo

  • It was decided to pull that tag back:
Hi everyone,

Due to the complete confusion arising at the last minute from the
attempted inclusion of CSC cond db updates in 37X it is surely best to
postpone it to 38X. The cond data updates is not critical for ICHEP
analyses (since the analysers don't know about it.) 

I expect you will all breathe a collective sigh of relief. 

I apologize for the trouble that this caused everybody. But both Oana
and I had to dedicate the past long weekend to it so we too have paid
some price  :)  

Here are the replacement tags for CSC reco for 37X WITHOUT any cond
data update: 

 
CSC Tags for 37X decoupled from cond data updates.

Data Structures
================
DataFormats/CSCDigi      V00-17-00 
DataFormats/CSCRecHit    V02-03-00 
DataFormats/MuonDetId    V01-01-00 

Local Reco
==========
RecoLocalMuon/CSCRecHitD V02-03-00
RecoLocalMuon/CSCSegment V00-13-00


For all packages except CSCRecHitD these are the same as I already requested for 37X.

Martin, this version needs no change to ConfDB for HLT.

Regards, Tim

CMSSW_3_6_X

Newer changes are listed on top, older ones at the bottom.

Status / Changes so far

  • Open issue: new tag for RecoLocalMuon/CSCRecHitD V02-02-03
    • value changes in existing parametes (27 changes in total)

Hi Martin,

Stoyan has tagged RecoLocalMuon/CSCRecHitD V02-02-03

We will queue it for 36X.

This tag includes re-tuned error parameters for the rechits
using CRAFT data.

It brings along changes to existing parameters, as can be seen here:
http://cmssw.cvs.cern.ch/cgi-bin/cmssw.cgi/CMSSW/RecoLocalMuon/CSCRecHitD/python/cscRecHitD_cff.py?r1=1.3&r2=1.4

This specifically will need to be changed:

process.hltCsc2DRecHits.XTasymmetry_ME1b  = cms.double(  0.01)
process.hltCsc2DRecHits.XTasymmetry_ME1a = cms.double(0.023)
process.hltCsc2DRecHits.XTasymmetry_ME1b = cms.double(0.01)
process.hltCsc2DRecHits.XTasymmetry_ME12 = cms.double(0.015)
process.hltCsc2DRecHits.XTasymmetry_ME13 = cms.double(0.02)
process.hltCsc2DRecHits.XTasymmetry_ME21 = cms.double(0.023)
process.hltCsc2DRecHits.XTasymmetry_ME22 = cms.double(0.023)
process.hltCsc2DRecHits.XTasymmetry_ME31 = cms.double(0.023)
process.hltCsc2DRecHits.XTasymmetry_ME32 = cms.double(0.023)
process.hltCsc2DRecHits.XTasymmetry_ME41 = cms.double(0.023)

process.hltCsc2DRecHits.ConstSyst_ME1a = cms.double(0.01)
process.hltCsc2DRecHits.ConstSyst_ME1b = cms.double(0.02)
process.hltCsc2DRecHits.ConstSyst_ME12 = cms.double(0.02)
process.hltCsc2DRecHits.ConstSyst_ME13 = cms.double(0.03)
process.hltCsc2DRecHits.ConstSyst_ME21 = cms.double(0.03)
process.hltCsc2DRecHits.ConstSyst_ME22 = cms.double(0.03)
process.hltCsc2DRecHits.ConstSyst_ME31 = cms.double(0.03)
process.hltCsc2DRecHits.ConstSyst_ME32 = cms.double(0.03)
process.hltCsc2DRecHits.ConstSyst_ME41 = cms.double(0.03)

process.hltCsc2DRecHits.NoiseLevel_ME1a = cms.double(9.0)
process.hltCsc2DRecHits.NoiseLevel_ME1b = cms.double(6.0)
process.hltCsc2DRecHits.NoiseLevel_ME12 = cms.double(7.0)
process.hltCsc2DRecHits.NoiseLevel_ME13 = cms.double(4.0)
process.hltCsc2DRecHits.NoiseLevel_ME21 = cms.double(5.0)
process.hltCsc2DRecHits.NoiseLevel_ME22 = cms.double(7.0)
process.hltCsc2DRecHits.NoiseLevel_ME31 = cms.double(5.0)
process.hltCsc2DRecHits.NoiseLevel_ME32 = cms.double(7.0)
process.hltCsc2DRecHits.NoiseLevel_ME41 = cms.double(5.0)



   Cheers, Ingo

  • Communicated issue: New parameters for SashaFix (fix for numerical instability of matrix + additional pruning of bad hits)
http://cmssw.cvs.cern.ch/cgi-bin/cmssw.cgi/CMSSW/RecoLocalMuon/CSCSegment/python/CSCSegmentAlgorithmST_cfi.py?r1=1.7&r2=1.10
  • Stoyan has taged and queued 100218
  • Ingo has sent a mail to Martin, see below for correspondence.

Hi Ingo;

The HLT side is taken care of:

https://hypernews.cern.ch/HyperNews/CMS/get/swReleases/1660/1/1.html

It is now up to David and Jean-Roch to get the RecoLocalMuon/CSCSegment V00-12-00 past Bill into the IB.

Best regards

Martin

On Thu, 18 Feb 2010, Ingo Bloch wrote:

> > Hi Martin,
> >
> > Stoyan has just tagged RecoLocalMuon/CSCSegment V00-12-00
> >
> > We will queue it today for 36X.
> >
> > This tag includes a fix for numerical instability of the
> > segment fit plus an enhanced hit-pruning step.
> >
> > It brings along a set of new parameters, as can be seen here:
> > http://cmssw.cvs.cern.ch/cgi-bin/cmssw.cgi/CMSSW/RecoLocalMuon/CSCSegment/python
> > /CSCSegmentAlgorithmST_cfi.py?r1=1.7&r2=1.10
> >
> > This specifically will need to be added:
> >
> > process.hltCscSegments.algo_psets[0].algo_psets[0].CorrectTheErrors =
> > cms.bool(True),
> > process.hltCscSegments.algo_psets[0].algo_psets[0].NormChi2Cut2D =
> > cms.double(20.0),
> > process.hltCscSegments.algo_psets[0].algo_psets[0].NormChi2Cut3D =
> > cms.double(10.0),
> > process.hltCscSegments.algo_psets[0].algo_psets[0].prePrun = cms.bool(True),
> > process.hltCscSegments.algo_psets[0].algo_psets[0].prePrunLimit =
> > cms.double(3.17),
> > process.hltCscSegments.algo_psets[0].algo_psets[0].SeedSmall =
> > cms.double(0.000200),
> > process.hltCscSegments.algo_psets[0].algo_psets[0].SeedBig =
> > cms.double(0.001500),
> > process.hltCscSegments.algo_psets[0].algo_psets[0].ForceCovariance =
> > cms.bool(False),
> > process.hltCscSegments.algo_psets[0].algo_psets[0].ForceCovarianceAll =
> > cms.bool(False),
> > process.hltCscSegments.algo_psets[0].algo_psets[0].Covariance =
> > cms.double(0.0)
> >
> > process.hltCscSegments.algo_psets[0].algo_psets[1].CorrectTheErrors =
> > cms.bool(True),
> > process.hltCscSegments.algo_psets[0].algo_psets[1].NormChi2Cut2D =
> > cms.double(20.0),
> > process.hltCscSegments.algo_psets[0].algo_psets[1].NormChi2Cut3D =
> > cms.double(10.0),
> > process.hltCscSegments.algo_psets[0].algo_psets[1].prePrun = cms.bool(True),
> > process.hltCscSegments.algo_psets[0].algo_psets[1].prePrunLimit =
> > cms.double(3.17),
> > process.hltCscSegments.algo_psets[0].algo_psets[1].SeedSmall =
> > cms.double(0.000200),
> > process.hltCscSegments.algo_psets[0].algo_psets[1].SeedBig =
> > cms.double(0.001500),
> > process.hltCscSegments.algo_psets[0].algo_psets[1].ForceCovariance =
> > cms.bool(False),
> > process.hltCscSegments.algo_psets[0].algo_psets[1].ForceCovarianceAll =
> > cms.bool(False),
> > process.hltCscSegments.algo_psets[0].algo_psets[1].Covariance =
> > cms.double(0.0)
> >
> >
> >
> > Cheers, Ingo

CMSSW_3_5_X

Status / Changes so far

  • For the tag RecoLocalMuon/CSCSegment V00-10-00 there is one new parameter in RecoLocalMuon/CSCSegment/python/CSCSegmentAlgorithmST_cfi.py: preClusteringUseChaining = cms.bool(True), in both PSets ST_ME1A and ST_ME1234

Dear Martin,

this mail comes late, sorry for that (I was away from the lab today).

Tim has published the tag

RecoLocalMuon/CSCSegment V00-10-00

for the CSC segment algorithm, which impacts on the HLT configuration in 35X when accepted.

There is one new parameter in RecoLocalMuon/CSCSegment/python/CSCSegmentAlgorithmST_cfi.py:

preClusteringUseChaining = cms.bool(True),

in both PSets ST_ME1A and ST_ME1234

Here is the diff to the previous released version: http://cmssw.cvs.cern.ch/cgi-bin/cmssw.cgi/CMSSW/RecoLocalMuon/CSCSegment/python/CSCSegmentAlgorithmST_cfi.py?r1=1.6&r2=1.7

Best regards, Ingo

Tim Cox wrote: > Hi David, Jean-Roch,
>
> This is a tag from Ingo & Stoyan to address a problem discovered in CSC segment building in the first collision events.
>
> It should go into 35X for data-taking.
>
> Thanks, Tim
>
> Begin forwarded message:
>
>
>> From: Tim Cox <Timothy.Cox@cern.ch>
>> Date: January 18, 2010 12:09:40 PM GMT+01:00
>> To: <hn-cms-pkgAnnounce@cern.ch>, <Stefano.Lacaprara@pd.infn.it>, <Timothy.Cox@cern.ch>, <Nicola.Amapane@cern.ch>, <riccardo.bellan@cern.ch>, <ingo.bloch@cern.ch>, <Stoyan.Stoynev@cern.ch>
>> Subject: CmsTC: RecoLocalMuon/CSCSegment V00-10-00 : New publication
>>
>>
>> Package: RecoLocalMuon/CSCSegment V00-10-00
>> Submitted by: Tim Cox Date: Mon Jan 18 12:09:40 CET 2010
>> Bug Fix
>> Not Queued for Release: CMSSW_3_1_X
>> Queued for Release: CMSSW_3_5_X
>> Not Queued for Release: CMSSW_3_4_X
>> Not Queued for Release: CMSSW_3_3_X
>> Tested on: slc4_ia32_gcc345
>>
>>
>> Use z of rechits in CSCSegAlgoTC clustering in order to reduce hyperactive segment production in ME1/1a.
>> Addresses the situation visible in the first muon candidate from collisions:
>> MuonEvent_3D.png
>> Courtesy of Ingo and Stoyan. Supporting evidence at:
>> http://cmsrocstor.fnal.gov/lpc1/cmsroc/ibloch/STZclusTest/ZClus3_winner/.
>>
>>

CMSSW_3_3_X

Status / Changes so far

Newer changes are listed on top, older ones at the bottom.

Dear Martin,

as you probably already are aware of, Tim queued a tag for CSCRecHitD (V02-01-03 for 33X), which includes a parameter change.

This is his summary of the corresponding change:

Package: RecoLocalMuon/CSCRecHitD V02-01-03 Submitted by: Tim Cox Date: Mon Aug 17 16:47:05 CEST 2009 New Feature Not Queued for Release: CMSSW_3_1_X Not Queued for Release: CMSSW_3_2_X Queued for Release: CMSSW_3_3_X Tested on: slc4_ia32_gcc345 The config defaults are changed from # Use dead channels information readBadChannels = cms.bool(False), readBadChambers = cms.bool(False), to # Use dead channels information readBadChannels = cms.bool(True), readBadChambers = cms.bool(True), (it was changed in cvs 5 weeks ago: http://cmssw.cvs.cern.ch/cgi-bin/cmssw.cgi/CMSSW/RecoLocalMuon/CSCRecHitD/python/cscRecHitD_cfi.py?revision=1.11&view=markup)

Please let me know if you need further feedback on this upcoming change.

Best regards, Ingo

  • done:
            Package:                 RecoLocalMuon/CSCRecHitD V02-01-03
            
            Submitted by:             Tim Cox
            Date:                    Mon Aug 17 16:47:05 CEST 2009
            New Feature
            Not Queued for Release:  CMSSW_3_1_X
            Not Queued for Release:  CMSSW_3_2_X
            Queued for Release:      CMSSW_3_3_X
            Tested on:               slc4_ia32_gcc345 
            The config defaults are changed from
            
             # Use dead channels information
               readBadChannels = cms.bool(False),
               readBadChambers = cms.bool(False),
             to
                     
             # Use dead channels information
               readBadChannels = cms.bool(True),
               readBadChambers = cms.bool(True), 
            
also registered here: https://twiki.cern.ch/twiki/bin/view/CMS/RecoPlans

CMSSW_3_1_X

Upcoming

  • as of 090521: no current open issues. Martins mail:
         Hi;
         Thanks - HLT updated and tagged for 31X:
         https://hypernews.cern.ch/HyperNews/CMS/get/swReleases/978/2/1/3/2/2/3/1/2/3/1/2/3/1/3/1/1/1/1/1/1/2/1/1/1/1/1/1/1/1/3/1/2/1/2/1/2/1.html
         Best regards
         Martin
        
  • pre 090520: no current open issues, all tags and corresponding parameter changes were communicated and implemented, see this HN message.

Status / Changes so far

Newer changes are listed on top, older ones at the bottom.

  • RecoLocalMuon/CSCRecHitD V02-01-01
            In
            RecoLocalMuon/CSCRecHitD/python/cscRecHitD_cfi.py
            csc2DRecHits = cms.EDProducer("CSCRecHitDProducer",
            
            the parameter
            
            UseFourPoleFit = cms.bool(True)
            
            is changed to
            
            UseFivePoleFit = cms.bool(True) 
            
  • EventFilter/CSCRawToDigi V01-18-00
            In
            
            EventFilter/CSCRawToDigi/python/cscUnpacker_cfi.py
            
            muonCSCDigis = cms.EDFilter("CSCDCCUnpacker",
            ...
            
            the following values have become tracked:
            
                UseExaminer = cms.bool(True),
                ExaminerMask = cms.uint32(0x1FEBF3F6),
                UseSelectiveUnpacking = cms.bool(True),
                ErrorMask = cms.uint32(0x0),
                UnpackStatusDigis = cms.bool(False),
                UseFormatStatus = cms.bool(True),
            
            

  • EventFilter/CSCRawToDigi V01-17-01. Removed one parameter and added a new one
    1. a parameter removed:
      isMTCC
      is no more,
    2. a new parameter:
      # Unpack FormatStatus digi?
      UseFormatStatus = cms.untracked.bool(True)

  • RecoLocalMuon/CSCRecHitD V02-01-00. Added 3 more parameters. Also changed all untracked to tracked.
    1. Parameters:
                  #    How to find SCA peak time?
                  #
                   UseAverageTime = cms.bool(False),
                   UseParabolaFit = cms.bool(False),
                   UseFourPoleFit = cms.bool(True),
             
      Explain: Parabola fit for peak time is added but not activated as default.
    2. several variables changed from untracked to tracked. Check that all are communicated.

  • RecoLocalMuon/CSCSegment V00-09-09. CSCSegment has untracked to tracked change in cvs
    1. This was published by Tim
    2. communicate all untracked -> tracked changes

090520 - Tim sent these emails

  1. Mail about Unpacker

For 31X please.

There are likely to be further updates to the sim raw format: at present the sim raw format is a mix of 'old' and 'new' real data formats. But I don't know yet when they'll be ready - it depends on the rather large changes required to one of the trigger data blocks which has been updated in the real data. I guess if we can't make it before the big mc production it's not the end of the world.

This affects HLT config due to change of untracked to tracked parameters:

In

EventFilter/CSCRawToDigi/python/cscUnpacker_cfi.py

muonCSCDigis = cms.EDFilter("CSCDCCUnpacker",
...

the following values have become tracked:

    UseExaminer = cms.bool(True),
    ExaminerMask = cms.uint32(0x1FEBF3F6),
    UseSelectiveUnpacking = cms.bool(True),
    ErrorMask = cms.uint32(0x0),
    UnpackStatusDigis = cms.bool(False),
    UseFormatStatus = cms.bool(True),


Regards, Tim 

  1. Mail about RecHit

For 31X please. This affects HLT config due to the config parameter name change

In
RecoLocalMuon/CSCRecHitD/python/cscRecHitD_cfi.py
csc2DRecHits = cms.EDProducer("CSCRecHitDProducer",

the parameter

UseFourPoleFit = cms.bool(True)

is changed to

UseFivePoleFit = cms.bool(True)

Regards, Tim 

090407 - Sent this email

Dear Martin,

   here is a summary of the 3 tags (for 31X) for the CSCs that influence parameters and the corresponding parameter changes:
Tags are (as we already cross checked on the phone):

1) RecoLocalMuon/CSCSegment V00-09-09 (pending)
2) RecoLocalMuon/CSCRecHitD V02-01-00 (pending)
3) EventFilter/CSCRawToDigi V01-17-04 (pending)



The corresponding parameter changes are

1) Parameters were changed from untracked to tracked. All untracked parameters were changed to tracked, except for CSCDebug, which remains untracked.

The new block should read:

hltCscSegments = cms.EDProducer( "CSCSegmentProducer",
   inputObjects = cms.InputTag( "hltCsc2DRecHits" ),
   algo_type = cms.int32( 1 ),
   algo_psets = cms.VPSet(
     cms.PSet(  chamber_types = cms.vstring( 'ME1/a',
 'ME1/b',
 'ME1/2',
 'ME1/3',
 'ME2/1',
 'ME2/2',
 'ME3/1',
 'ME3/2',
 'ME4/1',
 'ME4/2' ),
       algo_name = cms.string( "CSCSegAlgoST" ),
       algo_psets = cms.VPSet(
         cms.PSet(  maxRatioResidualPrune = cms.double( 3.0 ),
           yweightPenalty = cms.double( 1.5 ),
           maxRecHitsInCluster = cms.int32( 20 ),
           hitDropLimit6Hits = cms.double( 0.3333 ),
           tanPhiMax = cms.double( 0.5 ),
           onlyBestSegment = cms.bool( False ),
           dRPhiFineMax = cms.double( 8.0 ),
           curvePenalty = cms.double( 2.0 ),
           dXclusBoxMax = cms.double( 4.0 ),
           BrutePruning = cms.bool( True ),
           tanThetaMax = cms.double( 1.2 ),
           hitDropLimit4Hits = cms.double( 0.6 ),
           useShowering = cms.bool( False ),
           CSCDebug = cms.untracked.bool( False ),
           curvePenaltyThreshold = cms.double( 0.85 ),
           minHitsPerSegment = cms.int32( 3 ),
           dPhiFineMax = cms.double( 0.025 ),
           yweightPenaltyThreshold = cms.double( 1.0 ),
           hitDropLimit5Hits = cms.double( 0.8 ),
           preClustering = cms.bool( True ),
           maxDPhi = cms.double( 999.0 ),
           maxDTheta = cms.double( 999.0 ),
           Pruning = cms.bool( True ),
           dYclusBoxMax = cms.double( 8.0 ),
           BPMinImprovement = cms.double( 10000.0 )
         ),
         cms.PSet(  maxRatioResidualPrune = cms.double( 3.0 ),
           yweightPenalty = cms.double( 1.5 ),
           maxRecHitsInCluster = cms.int32( 24 ),
           hitDropLimit6Hits = cms.double( 0.3333 ),
           tanPhiMax = cms.double( 0.5 ),
           onlyBestSegment = cms.bool( False ),
           dRPhiFineMax = cms.double( 8.0 ),
           curvePenalty = cms.double( 2.0 ),
           dXclusBoxMax = cms.double( 4.0 ),
           BrutePruning = cms.bool( True ),
           tanThetaMax = cms.double( 1.2 ),
           hitDropLimit4Hits = cms.double( 0.6 ),
           useShowering = cms.bool( False ),
           CSCDebug = cms.untracked.bool( False ),
           curvePenaltyThreshold = cms.double( 0.85 ),
           minHitsPerSegment = cms.int32( 3 ),
           dPhiFineMax = cms.double( 0.025 ),
           yweightPenaltyThreshold = cms.double( 1.0 ),
           hitDropLimit5Hits = cms.double( 0.8 ),
           preClustering = cms.bool( True ),
           maxDPhi = cms.double( 999.0 ),
           maxDTheta = cms.double( 999.0 ),
           Pruning = cms.bool( True ),
           dYclusBoxMax = cms.double( 8.0 ),
           BPMinImprovement = cms.double( 10000.0 )
         )
       ),
       parameters_per_chamber_type = cms.vint32( 2, 1, 1, 1, 1, 1, 1, 1, 1, 1 )
     )
   )
)

###############################################################################
###############################################################################
###############################################################################

2) There are 3 new parameters (
   UseAverageTime = cms.bool(False),
    UseParabolaFit = cms.bool(False),
    UseFourPoleFit = cms.bool(True),                 ) and several untracked values were changed to tracked.

The new block should read:

hltCsc2DRecHits = cms.EDProducer( "CSCRecHitDProducer",
    XTasymmetry_ME1a = cms.double(0.0),
    XTasymmetry_ME1b = cms.double(0.0),
    XTasymmetry_ME12 = cms.double(0.0),
    XTasymmetry_ME13 = cms.double(0.0),
    XTasymmetry_ME21 = cms.double(0.0),
    XTasymmetry_ME22 = cms.double(0.0),
    XTasymmetry_ME31 = cms.double(0.0),
    XTasymmetry_ME32 = cms.double(0.0),
    XTasymmetry_ME41 = cms.double(0.0),
    NoiseLevel_ME1a = cms.double(7.0),
    NoiseLevel_ME1b = cms.double(8.0),
    NoiseLevel_ME12 = cms.double(9.0),
    NoiseLevel_ME13 = cms.double(8.0),
    NoiseLevel_ME21 = cms.double(9.0),
    NoiseLevel_ME22 = cms.double(9.0),
    NoiseLevel_ME31 = cms.double(9.0),
    NoiseLevel_ME32 = cms.double(9.0),
    NoiseLevel_ME41 = cms.double(9.0),
    ConstSyst_ME1a = cms.double(0.022),
    ConstSyst_ME1b = cms.double(0.007),
    ConstSyst_ME12 = cms.double(0.0),
    ConstSyst_ME13 = cms.double(0.0),
    ConstSyst_ME21 = cms.double(0.0),
    ConstSyst_ME22 = cms.double(0.0),
    ConstSyst_ME31 = cms.double(0.0),
    ConstSyst_ME32 = cms.double(0.0),
    ConstSyst_ME41 = cms.double(0.0),

    CSCStripPeakThreshold = cms.double(10.0),

    UseAverageTime = cms.bool(False),
    UseParabolaFit = cms.bool(False),
    UseFourPoleFit = cms.bool(True),                
    readBadChannels = cms.bool(False),
    CSCUseStaticPedestals = cms.bool(False),
    stripDigiTag = cms.InputTag("muonCSCDigis","MuonCSCStripDigi"),
    readBadChambers = cms.bool(False),
    CSCStripxtalksOffset = cms.double(0.03),
    CSCstripWireDeltaTime = cms.int32(8),
    CSCUseCalibrations = cms.bool(True),
    CSCNoOfTimeBinsForDynamicPedestal = cms.int32(2),
    wireDigiTag = cms.InputTag("muonCSCDigis","MuonCSCWireDigi"),
    CSCDebug = cms.untracked.bool(False),
    CSCWireClusterDeltaT = cms.int32(1),
    CSCStripClusterSize = cms.untracked.int32(3),
    CSCStripClusterChargeCut = cms.double(25.0)
)

###############################################################################
###############################################################################
###############################################################################

3) one parameter was removed (isMTCCData) and one new one introduced (UseFormatStatus).

The new block should read:

hltMuonCSCDigis = cms.EDProducer( "CSCDCCUnpacker",
    PrintEventNumber = cms.untracked.bool(False),
    UseExaminer = cms.untracked.bool(True),
    Debug = cms.untracked.bool(False),
    ErrorMask = cms.untracked.uint32(0),
    InputObjects = cms.InputTag("source"),
    ExaminerMask = cms.untracked.uint32(535557110),
    UnpackStatusDigis = cms.untracked.bool(False),
    UseFormatStatus = cms.untracked.bool(True),
    UseSelectiveUnpacking = cms.untracked.bool(True)
)


###############################################################################
###############################################################################
###############################################################################

I hope this is digestible information.

   Cheers, Ingo 

090318 - Sent these cards

HLT_2E30_cff_r1_149_ibl.py
HLT_2E30_cff_r1_149_iblJR.py

to which Martins final reply was:
Thanks for the clarification. The change to hltCsc2DRecHits is now in ConfDB - /dev/CMSSW_3_1_0/pre2/HLT/V238. The changes as reported by ConfDB are:

-------------------------------------------------------------------------------
Modules (1):
  -> hltCsc2DRecHits [CSCRecHitDProducer] CHANGED
       double NoiseLevel_ME1b = 8.0 [7.0]
       double ConstSyst_ME1b = 0.0070 [0.02]
       double NoiseLevel_ME12 = 9.0 [7.0]
       double XTasymmetry_ME12 = 0.0 [0.025]
       double ConstSyst_ME12 = 0.0 [0.045]
       double NoiseLevel_ME13 = 8.0 [7.0]
       double XTasymmetry_ME13 = 0.0 [0.025]
       double ConstSyst_ME13 = 0.0 [0.065]
       double NoiseLevel_ME21 = 9.0 [7.0]
       double XTasymmetry_ME21 = 0.0 [0.025]
       double ConstSyst_ME21 = 0.0 [0.06]
       double NoiseLevel_ME22 = 9.0 [7.0]
       double XTasymmetry_ME22 = 0.0 [0.025]
       double ConstSyst_ME22 = 0.0 [0.06]
       double NoiseLevel_ME31 = 9.0 [7.0]
       double XTasymmetry_ME31 = 0.0 [0.025]
       double ConstSyst_ME31 = 0.0 [0.06]
       double NoiseLevel_ME32 = 9.0 [7.0]
       double XTasymmetry_ME32 = 0.0 [0.025]
       double ConstSyst_ME32 = 0.0 [0.06]
       double NoiseLevel_ME41 = 9.0 [7.0]
       double XTasymmetry_ME41 = 0.0 [0.025]
       double ConstSyst_ME41 = 0.0 [0.06]

CMSSW_2_2_X

Upcoming

  • change in unpacker for new firmware
    • parameter changes?
    • code/Tag changes? Is this even possible? How is this communicated? Does the HLT take a cvs release?

Status / Changes so far

Nothing exchanged for this release so far.
Edit | Attach | Watch | Print version | History: r18 < r17 < r16 < r15 < r14 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r18 - 2010-07-05 - IngoBloch
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Main All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback