Difference: MatchingUnitAlgorithm (1 vs. 6)

Revision 6
18 Jan 2006 - Main.MartinJurkovic
Line: 1 to 1
 
META TOPICPARENT name="MatchingUnit"

What the MU does in words....

Line: 31 to 31
 

Things which are not seen from these numbers:
Changed:
<
<
  1. The MU first just counts the number of number of data-words (it's a lower limit of hits!) in RICH and SHOWER, without unpacking (convert row and colum to theta and phi) them
>
>
  1. The MU first just counts the number of data-words (it's a lower limit of hits!) in RICH and SHOWER, without unpacking (convert row and colum to theta and phi) them
 
  1. if the ENABLE_SHORT_CUT_IF_TOO_MANY_RINGS is defined in scheduler.h, then it checks for the number G_MAX_RICH_RINGS_TO_LOOP_OVER, which in principle can be set via control-files, but up to now is just hardcoded to 6.
  2. If this number is exceeded (number_of_hits_in_RICH >= *G_MAX_RICH_RINGS_TO_LOOP_OVER ) then the event will be triggered positively.
Revision 5
19 Oct 2005 - Main.MichaelTraxler
Line: 1 to 1
 
META TOPICPARENT name="MatchingUnit"

What the MU does in words....

Line: 45 to 45
 
  1. then the hits are really matched (with angles) and the momenta of the leptons are determined
  2. dileptons: implemented by cutting on the invariant mass of all lepton pairs (has to be electron and positron!). (not used in the trigger up to now!)
Added:
>
>

Downscaling and TriggerDecisions

This topic generated a lot of confusion in the past (I don't know why...).
So, it better to let some other person to explain this topic (Joachim Stroth):

LVL1 triggered events are handled by the MU using two different "machines". Machine 1 is the downscaler and machine 2 is the LVL2-Trigger. Both machines work completely independent - and that is very important. Machine 1 does not know what machine 2 does and vice versa. The result of the "handling" is each a bit which can be high or low. Events are transported to mass storage if at least one of the bits is true. In analysis the bit of machine 1 is called DSflag and the other TrigDec (or something like this).
And here is a picture, which illustrates this again... As attachment, as I don't know how to insert it directly into the text...
 

-- MichaelTraxler - 22 Jun 2005
Added:
>
>

 
Added:
>
>
META FILEATTACHMENT attr="" comment="Illustrates the Trigger Decision Flags" date="1129742134" name="Trigger.svg" path="Trigger.svg" size="14782" user="MichaelTraxler" version="1.1"
META FILEATTACHMENT attr="" comment="Illustrates the Trigger Decision Flags" date="1129742231" name="Trigger.pdf" path="Trigger.pdf" size="94203" user="MichaelTraxler" version="1.1"
Revision 4
20 Sep 2005 - Main.MichaelTraxler
Line: 1 to 1
 
META TOPICPARENT name="MatchingUnit"

What the MU does in words....

Line: 38 to 38
 
  1. if( (number_of_hits_in_SHOWER + number_of_hits_in_TOF) * number_of_hits_in_RICH >= *MAX_COMBINATORIAL_VALUE) => trigger positively
  2. The main-logic is used (found number of META-hits is >= trig_meta_hits), currently
  3. before the unpacking and angle matching is done, first it is checked, if the Rich-hits find a corresponding hit in the META in the same sector...
Changed:
<
<
  1. then the hits of RICH, SHOWER and TOF are unpacked, the new corrected number of events for RICH and SHOWER are written in the MU sub-sub-event.
>
>
  1. then the hits of RICH, SHOWER and TOF are unpacked, the new corrected number of events for RICH and SHOWER are written in the MU sub-sub-event.
 
  1. a) RICH unpacker has again a hard coded cut: after finding 6 or more rings in all sectors, it stops unpacking)
  2. b) Shower is only unpacked up to 60 hits, if exceeded triggered pos.due to next cut (3+4) automatically
  3. Then the cut nr. 3+4 is applied again
Revision 3
19 Sep 2005 - Main.MichaelTraxler
Line: 1 to 1
 
META TOPICPARENT name="MatchingUnit"

What the MU does in words....

Line: 31 to 31
 

Things which are not seen from these numbers:
Changed:
<
<
  • The MU first just counts the number of hits in RICH, without unpacking (convert row and colum to theta and phi) them
  • if the ENABLE_SHORT_CUT_IF_TOO_MANY_RINGS is defined in scheduler.h, then it checks for the number
>
>
  1. The MU first just counts the number of number of data-words (it's a lower limit of hits!) in RICH and SHOWER, without unpacking (convert row and colum to theta and phi) them
  2. if the ENABLE_SHORT_CUT_IF_TOO_MANY_RINGS is defined in scheduler.h, then it checks for the number
  G_MAX_RICH_RINGS_TO_LOOP_OVER, which in principle can be set via control-files, but up to now is just hardcoded to 6.
Changed:
<
<
If this number is exceeded (number_of_hits_in_RICH >= *G_MAX_RICH_RINGS_TO_LOOP_OVER ) then the event will be triggered positively.
  • If not, then the hits are counted in META (without full unpacking!)
  • The main-logic is used (found number of META-hits is >= trig_meta_hits)
  • before the unpacking and angle matching is done, first it is checked, if the Rich-hits find a corresponding hit in the META in the same sector...
  • then the hits of RICH, SHOWER and TOF are unpacked (where the RICH unpacker has again a hard coded cut: after finding 6 or more rings in all sectors, it stops unpacking, but this should not happen, as the G_MAX_RICH_RINGS_TO_LOOP_OVER is set to 6, too!)
  • then the hits are really matched (with angles) and the momenta of the leptons are determined
  • dileptons: implemented by cutting on the invariant mass of all lepton pairs (has to be electron and positron!). (not used in the trigger up to now!)
>
>
  1. If this number is exceeded (number_of_hits_in_RICH >= *G_MAX_RICH_RINGS_TO_LOOP_OVER ) then the event will be triggered positively.
  2. if( (number_of_hits_in_SHOWER + number_of_hits_in_TOF) * number_of_hits_in_RICH >= *MAX_COMBINATORIAL_VALUE) => trigger positively
  3. The main-logic is used (found number of META-hits is >= trig_meta_hits), currently
  4. before the unpacking and angle matching is done, first it is checked, if the Rich-hits find a corresponding hit in the META in the same sector...
  5. then the hits of RICH, SHOWER and TOF are unpacked, the new corrected number of events for RICH and SHOWER are written in the MU sub-sub-event.
  6. a) RICH unpacker has again a hard coded cut: after finding 6 or more rings in all sectors, it stops unpacking)
  7. b) Shower is only unpacked up to 60 hits, if exceeded triggered pos.due to next cut (3+4) automatically
  8. Then the cut nr. 3+4 is applied again
  9. then the hits are really matched (with angles) and the momenta of the leptons are determined
  10. dileptons: implemented by cutting on the invariant mass of all lepton pairs (has to be electron and positron!). (not used in the trigger up to now!)
 

-- MichaelTraxler - 22 Jun 2005
Revision 2
22 Jun 2005 - Main.MichaelTraxler
Line: 1 to 1
 
META TOPICPARENT name="MatchingUnit"

What the MU does in words....

Line: 19 to 19
  set mu(trig_dileptons) 0
Changed:
<
<
Basically, these values control the trigger algorith of the MU.
>
>
Basically, these values control the trigger algorithm of the MU.
  The above means the following:
  • Check if there is at least 1 hit in the RICH
  • if yes, then check if there is at least 1 hit in META
Line: 34 to 34
 
  • The MU first just counts the number of hits in RICH, without unpacking (convert row and colum to theta and phi) them
  • if the ENABLE_SHORT_CUT_IF_TOO_MANY_RINGS is defined in scheduler.h, then it checks for the number G_MAX_RICH_RINGS_TO_LOOP_OVER, which in principle can be set via control-files, but up to now is just hardcoded to 6.
Changed:
<
<
If this number is exceeded (number_of_hits_in_RICH >= *G_MAX_RICH_RINGS_TO_LOOP_OVER ) then the event will just be triggered positively.
>
>
If this number is exceeded (number_of_hits_in_RICH >= *G_MAX_RICH_RINGS_TO_LOOP_OVER ) then the event will be triggered positively.
 
  • If not, then the hits are counted in META (without full unpacking!)
Changed:
<
<
  • The main-logic is used ( found number of META-hits is >= trig_meta_hits) (
>
>
  • The main-logic is used (found number of META-hits is >= trig_meta_hits)
 
  • before the unpacking and angle matching is done, first it is checked, if the Rich-hits find a corresponding hit in the META in the same sector...
  • then the hits of RICH, SHOWER and TOF are unpacked (where the RICH unpacker has again a hard coded cut: after finding 6 or more rings in all sectors, it stops unpacking, but this should not happen, as the G_MAX_RICH_RINGS_TO_LOOP_OVER is set to 6, too!)
  • then the hits are really matched (with angles) and the momenta of the leptons are determined
Changed:
<
<
  • dileptons (never used up to now!)
>
>
  • dileptons: implemented by cutting on the invariant mass of all lepton pairs (has to be electron and positron!). (not used in the trigger up to now!)
 

-- MichaelTraxler - 22 Jun 2005
 
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Hades Wiki? Send feedback
Imprint (in German)
Privacy Policy (in German)