with what code exactly?

On Jan 26, 2014, at 9:08 PM, Sven Dildick <notifications@github.com>
 wrote:

> In L1Trigger/CSCTriggerPrimitives/plugins/CSCTriggerPrimitivesProducer.cc:
> 
> > @@ -75,6 +75,16 @@ void CSCTriggerPrimitivesProducer::produce(edm::Event& ev,
> >      edm::ESHandle<CSCGeometry> h;
> >      setup.get<MuonGeometryRecord>().get(h);
> >      CSCTriggerGeometry::setGeometry(h);
> > +    lctBuilder_->setCSCGeometry(&*h);
> > +
> > +    edm::ESHandle<GEMGeometry> h_gem;
> > +    try {
> > +      setup.get<MuonGeometryRecord>().get(h_gem);
> > +      lctBuilder_->setGEMGeometry(&*h_gem);
> 
> 26-Jan-2014 21:04:01 CET Initiating request to open file file:step1.root
> 26-Jan-2014 21:04:02 CET Successfully opened file file:step1.root
> disableME1a = 0
> %MSG-e Specific: MixingModule:mix@beginRun 26-Jan-2014 21:04:10 CET Run: 1
> Could not process q-name of a DDLogicalPart, reason:
> No regex-match for namespace= name=HFFibre.*
> 
> SpecPar selection is:
> //HFFibre.*
> 
> %MSG
> in MuonNumberingInitialization::initializeMuonDDDConstants
> about to make my new muonDDDConst_
> in MuonNumberingInitialization::produce
> Begin processing the 1st record. Run 1, Event 1, LumiSection 1 at 26-Jan-2014 21:04:23.076 CET
> ----- Begin Fatal Exception 26-Jan-2014 21:05:02 CET-----------------------
> An exception of category 'NoProxyException' occurred while
> [0] Processing run: 1 lumi: 1 event: 1
> [1] Running path 'L1simulation_step'
> [2] Calling event method for module CSCTriggerPrimitivesProducer/'simCscTriggerPrimitiveDigis'
> Exception Message:
> No data of type "GEMGeometry" with label "" in record "MuonGeometryRecord"
> Please add an ESSource or ESProducer to your job which can deliver this data.
> ----- End Fatal Exception -------------------------------------------------
> Another exception was caught while trying to clean up files after the primary fatal exception.
> 26-Jan-2014 21:05:02 CET Closed file file:step1.root
> 
> MessageLogger Summary
> 
> type category sev module subroutine count total
> 
> 1 Specific             -e MixingModule:mix                       1        1
> 2 Additional Exception -s PostEndRun                             1        1
> 3 Fatal Exception      -s PostProcessPath                        1        1
> 4 fileAction           -s file_close                             1        1
> 5 fileAction           -s file_open                              2        2
> 
> type category Examples: run/evt run/evt run/evt
> 
> 1 Specific             Run: 1                            
> 2 Additional Exceptions PostEndRun                        
> 3 Fatal Exception      1/1                               
> 4 fileAction           PostEndRun                        
> 5 fileAction           pre-events       pre-events       
> 
> Severity # Occurrences Total Occurrences
> 
> Error 1 1
> System 5 5
> 
> —
> Reply to this email directly or view it on GitHub.
>