Difference: MatchingUnitDataFormat (1 vs. 7)

Revision 7
23 Jan 2006 - Main.MichaelTraxler
Line: 1 to 1
 
META TOPICPARENT name="MatchingUnit"

/* Version:
$Source: /var/www/hades-wiki.gsi.de/data/DaqSlowControl/MatchingUnitDataFormat.txt,v $
Changed:
<
<
$Id: MatchingUnitDataFormat.txt,v 1.5 2005/09/19 17:01:59 MichaelTraxler Exp www-data $
>
>
$Id: MatchingUnitDataFormat.txt,v 1.6 2006/01/20 17:18:14 MichaelTraxler Exp www-data $
  */
Line: 49 to 49
 

## Important change: all data taken from 31.08.2001 18:00 will have the following ## order of the following two words. This was switched before!
Changed:
<
<
6 trigger code trigger code of subevent
>
>
6 trigger code lower 4 bits: trigger code of subevent bits 4-7: trigger decision as described further down bit 12 marks, if trigger condition is encoded

  5 MU-data length MU-data length, length in 16-bit words, without this length, minumum = 0 , data can end here 7 matching-data see below for description
Revision 6
20 Jan 2006 - Main.MichaelTraxler
Line: 1 to 1
 
META TOPICPARENT name="MatchingUnit"

/* Version:
$Source: /var/www/hades-wiki.gsi.de/data/DaqSlowControl/MatchingUnitDataFormat.txt,v $
Changed:
<
<
$Id: MatchingUnitDataFormat.txt,v 1.4 2005/09/19 15:27:11 MichaelTraxler Exp www-data $
>
>
$Id: MatchingUnitDataFormat.txt,v 1.5 2005/09/19 17:01:59 MichaelTraxler Exp www-data $
  */
Line: 68 to 68
  ## for(i=1; i<= (1,2 ... or 6), i++) { x+1 IPU header(MSW) see below for description, length included x+2 IPU header(LSW) see below for description, length included
Changed:
<
<
x+3 IPU data(MSW) see below for description
>
>
x+3 IPU data(MSW) data is optional, but can be up to 42 long words per IPU, see below for description
  x+4 IPU data(LSW) see below for description
Added:
>
>
... ...
  ## }
Revision 5
19 Sep 2005 - Main.MichaelTraxler
Line: 1 to 1
 
META TOPICPARENT name="MatchingUnit"

/* Version:
$Source: /var/www/hades-wiki.gsi.de/data/DaqSlowControl/MatchingUnitDataFormat.txt,v $
Changed:
<
<
$Id: MatchingUnitDataFormat.txt,v 1.3 2005/06/02 12:30:17 SimonLang Exp www-data $
>
>
$Id: MatchingUnitDataFormat.txt,v 1.4 2005/09/19 15:27:11 MichaelTraxler Exp www-data $
  */
Line: 160 to 160
  2 => positive, but stopped analyzing due to to many leptons (>=7) or dileptons (>=x)
Changed:
<
<
ATTENTION: The num_of_hits_in_RICH and num_of_hits_in_SHOWER are not final number, only a lower
>
>
ATTENTION: The num_of_hits_in_RICH and num_of_hits_in_SHOWER are not final numbers, only a lower
  limit for the MU, to find out very fast if it can trigger pos. without analysing the event. In fact, they are just the number of data-words. For RICH the real number could be 4 times more, for shower I don't know exactly, but theoretically 16 times more (8 times is more likely!)
Added:
>
>
When no cut-condition was applied, then the MU unpacks the data correctly and will also write the correct numbers in these variables.
 

1 num_of_hits_in_RICH these words tells how many hits the different IPUs found in the detectors
Revision 4
19 Sep 2005 - Main.MichaelTraxler
Line: 1 to 1
 
META TOPICPARENT name="MatchingUnit"

/* Version:
Changed:
<
<
$Source: /var/lib/twiki/data/Hadesdaq/MatchingUnitDataFormat.txt,v $ $Id: MatchingUnitDataFormat.txt,v 1.2 2005/05/18 08:47:49 MichaelTraxler Exp www-data $
>
>
$Source: /var/www/hades-wiki.gsi.de/data/DaqSlowControl/MatchingUnitDataFormat.txt,v $ $Id: MatchingUnitDataFormat.txt,v 1.3 2005/06/02 12:30:17 SimonLang Exp www-data $
  */
Line: 160 to 160
  2 => positive, but stopped analyzing due to to many leptons (>=7) or dileptons (>=x)
Added:
>
>
ATTENTION: The num_of_hits_in_RICH and num_of_hits_in_SHOWER are not final number, only a lower limit for the MU, to find out very fast if it can trigger pos. without analysing the event. In fact, they are just the number of data-words. For RICH the real number could be 4 times more, for shower I don't know exactly, but theoretically 16 times more (8 times is more likely!)
  1 num_of_hits_in_RICH these words tells how many hits the different IPUs found in the detectors 2 num_of_hits_in_SHOWER
Revision 3
02 Jun 2005 - Main.SimonLang
Line: 1 to 1
Added:
>
>
META TOPICPARENT name="MatchingUnit"
 

/* Version:
$Source: /var/lib/twiki/data/Hadesdaq/MatchingUnitDataFormat.txt,v $
Changed:
<
<
$Id: MatchingUnitDataFormat.txt,v 1.1 2005/01/28 14:25:00 MichaelTraxler Exp www-data $
>
>
$Id: MatchingUnitDataFormat.txt,v 1.2 2005/05/18 08:47:49 MichaelTraxler Exp www-data $
  */
Revision 2
18 May 2005 - Main.MichaelTraxler
Line: 1 to 1
 

/* Version:
Changed:
<
<
$Source: /u/hadaq/CVS/doc/MU_Subevent_DataFormat.txt,v $ $Id: MU_Subevent_DataFormat.txt,v 1.3 2004/09/03 22:21:24 hadaq Exp $
>
>
$Source: /var/lib/twiki/data/Hadesdaq/MatchingUnitDataFormat.txt,v $ $Id: MatchingUnitDataFormat.txt,v 1.1 2005/01/28 14:25:00 MichaelTraxler Exp www-data $
  */
Line: 221 to 221
  Detector Bit: 0 => TOF 1 => Shower
Added:
>
>

momentum: 255 units corresponds to 1 GeV/c momentum of the lepton. Every lepton above 1GeV/c is clipped to the 1Gev/c bin. All is dependent of the momentum-table from Manual Sanchez generated with the kick-plane Ansatz. Important issue: to get correct momenta, the magnetic_field current have to be set correctly, in the MU and in the analysis!
 
- dilepton:
 
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)