HowTo request events by Level-1, Level-2 or Level-3 trigger names

New functionality of the ConsumerInput module is to enable
users to request events by Level-1, Level-2 or Level-3 trigger names.
The default tcl file fragment will still look like this:

  anyStreamBit   set true
  anyLevel3Bit   set true
  anyLevel2Bit   set true
  anyLevel1Bit   set true

If you want to request only events which pass the Level-1
minimum_bias trigger you should do this:

  anyStreamBit   set true
  anyLevel3Bit   set true
  anyLevel2Bit   set true
  anyLevel1Bit   set false
  level1NameList set minimum_bias

It is not case sensitive.
If you want to request events which pass Level-1 
DIRAC_TRACK_PT3 or 
DIRAC_TRACK_PT8 or 
DIRAC_TRACK_PT1.5 
you can do this:

  anyStreamBit   set true
  anyLevel3Bit   set true
  anyLevel2Bit   set true
  anyLevel1Bit   set false
  level1NameList set DIRAC_TRACK

If you want to request events which pass Level-2 MISS_ET you can do
this:
  anyStreamBit   set true  
  anyLevel3Bit   set true
  anyLevel2Bit   set false
  anyLevel1Bit   set true
  level2NameList set miss_et


A more complicated example:

  anyStreamBit   set true
  anyLevel3Bit   set false
  anyLevel2Bit   set true 
  anyLevel1Bit   set false 
  level1NameList set JET_ET DIELECTRON
  level3NameList set EmCluster

This will request events which pass
any level1 trigger that has JET_ET or DIELECTRON in the name
  AND
any level2 trigger
  AND
any level3 trigger that has EmCluster in the name

The first event received by the consumer may be of any type.
The following events will satisfy the request.

Note that if you make a mistake and request 
a trigger name that does not exist then the ConsumerInputModule
might wait forever for an event. This is a problem for the
event display because while the input module waits for an event,
the event display buttons are not active.

Thanks to Tony Vaiciulis for this howto.