- AliMUONDigit* d = new AliMUONDigit;
- d->SetDetElemId(detElemId);
-/* pc 09/02/06 no need for that anymore : trigger is in local numbering
-
- //FIXME: >> the following code to get the ixGlo and iyGlo is a bad hack
- // because trigger has not yet switched to local numbering of its indices !
- // We should be able to use directly the (local) ix,iy from the pad !
- const AliMUONTriggerSegmentationV2* old =
- dynamic_cast<const AliMUONTriggerSegmentationV2*>
- (Segmentation()->GetDESegmentation(detElemId,cath));
- if ( !old )
- {
- AliFatal("Got a wrong TriggerSegmentation object! Check that!");
+ AliMUONDigit* d = new AliMUONDigit(detElemId,pad.GetLocation(0).GetFirst(),
+ pad.GetLocation(0).GetSecond(),cath);
+ d->SetPadXY(ix,iy);
+
+ //FIXME : a trigger digit can have several locations.
+ //this is not currently supported by the digit class. Change that or not ?
+ d->SetCharge(twentyNano);
+
+ if(fTriggerEfficiency){
+ if(cath==0){
+ Int_t nboard = pad.GetLocation(0).GetFirst();
+ fTriggerEfficiency->IsTriggered(detElemId, nboard,
+ isTrig[0], isTrig[1]);
+ }
+ if(!isTrig[cath]) continue;