Documentation

Parameters controlling the operation of the mMuiSelectEvent_ module.

Currently, mMuiSelectEvent counts raw hits in the MuID detector planes. If one of the planes in the RequiredGaps list in the dMuiEventControl table has no hits in a given event, processing for that event will stop, and the next event will be processed.

The position of an entry in a RequiredGaps array is not significant. For example, SouthRequiredGaps[] = {1,4,3} is equivalent to SouthRequiredGaps[] = {3,1,4}.

The ArmRequired variables override the RequiredGaps arrays; if one of these flags is zero, none of the gaps in the corresponding arm will be required, no matter what the RequiredGaps array contains.

The EventOK flag contains the decision of the mMuiSelectEvent module. If the flag is 0, don't process the event; otherwise, proceed as usual. Here is how it might look in a ROOT macro:

      if (dMuiEventControl->get_EventOK((size_t)0)>0) {
         printf("Now processing the rest of this event ...\n");
         ...
      }
 

Note the oddball gap-numbering convention used here: first gap is 1, second gap is 2, ..., last gap is 5. Subtract one to be consistent with the convention used in the rest of the code! I'm trying to avoid the situation where table elements are initialized to 0. If "0" is a valid gap identifier, that gap might be required when you don't want it to be required!