You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Just want to confirm intended TriggerAlg behavior.

current cal portion of TriggerAlg code is as follows.
// CAL CASE 1: Get bits from existing GltDigi class
if( glt!=0 )

Unknown macro: { trigger_bits |= calorimeter(glt,callovector,calhivector) ; //<-- I assume this means we're looking @ real digis }

// CAL CASE 2: Populate new GltDigi class with info from CalTrigTool
else if(cal!=0){
//<-- this means, generate cal trigger bits from simulated CalDigis

I propose to re-replace this code with logic like this

// CAL CASE 1: Get bits from existing GltDigi class
if( glt!=0 )

// CAL CASE 2: Populate new GltDigi class with info from CalTrigTool
else {
//<-- no longer dependent on CalDigis, will work directly from MC data instead.
//<-- My code will fall back to CalDigis if MC is not present.

Remind me, are we still processing CalDigis for real data? If so, is (glt!=0) the right test for real vs MC processing?

  • No labels