Difference: DataStructure (1 vs. 11)

Revision 11
27 Oct 2009 - Main.JanMichel
Line: 1 to 1
Changed:
<
<
META TOPICPARENT name="DaqUpgradeMDCOverview"
>
>
META TOPICPARENT name="MdcDocumentation"
  -- AttilioTarantola - 03 May 2009

Here follows the new data structure for MDC readout(OEPB).
Revision 10
07 Jul 2009 - Main.AttilioTarantola
Line: 1 to 1
 
META TOPICPARENT name="DaqUpgradeMDCOverview"
-- AttilioTarantola - 03 May 2009
Line: 72 to 72
 

-- BurkhardKolb - 03 Jul 2009
Added:
>
>

Data Structure documentation

 
META FILEATTACHMENT attr="" comment="data structure example" date="1241340884" name="data_struct.jpg" path="data_struct.jpg" size="31486" user="AttilioTarantola" version="1.1"
Added:
>
>
META FILEATTACHMENT attr="" comment="MDC datastructure" date="1246959674" name="data_format.pdf" path="data_format.pdf" size="32413" user="AttilioTarantola" version="1.1"
Revision 9
03 Jul 2009 - Main.BurkhardKolb
Line: 1 to 1
 
META TOPICPARENT name="DaqUpgradeMDCOverview"
-- AttilioTarantola - 03 May 2009
Line: 45 to 45
 

-- JoernWuestenfeld - 03 Jul 2009
Added:
>
>

Not so new suggestion by BurkhardKolb

We have two compression modes for the data:
  • compressed data - 2 hits in one 32 bit data word
  • uncompressed data - 1 hit in one 32 bit data word - DEBUG / noise mode

  • These two modes are set for the whole mother board and trigger type and are identified by bit 31.
  • In compressed mode all single hit data words are just discarded - so only good data are transmitted.
  • In order to see the real noise behaviour of a MOB the mode has to be switched to uncompressed mode.

With this the data type word has only the following values:
Data Type Meaning Comments
"000" Normal compressed data  
"001" compressed calibration-dataword  
"010" Normal compressed data with ERROR reserved for token not retrieved
"011" compressed calibration-dataword with ERROR reserved for token not retrieved
"100" single-dataword one hit in one dataword and hit number in bit 11
"101" single calibration one hit in one dataword and hit number in bit 11
"110" single-dataword with ERROR reserved for token not retrieved
"111" single calibration with ERROR reserved for token not retrieved

So with this the data type has three bits with a fixed meaning:
  • bit 31 if 1 signifies uncompressed data
  • bit 30 if 1 signifies ERROR data
  • bit 29 if 1 signifies calibration data

-- BurkhardKolb - 03 Jul 2009
 
META FILEATTACHMENT attr="" comment="data structure example" date="1241340884" name="data_struct.jpg" path="data_struct.jpg" size="31486" user="AttilioTarantola" version="1.1"
Revision 8
03 Jul 2009 - Main.JoernWuestenfeld
Line: 1 to 1
 
META TOPICPARENT name="DaqUpgradeMDCOverview"
-- AttilioTarantola - 03 May 2009
Line: 12 to 12
  * data structure example:
data structure example
Added:
>
>
Structure of OEP header ?!
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Length Source

We should seperate this two informations into two 32 bit datawords, and use one full dataword for the source identification. Se my note in Network addresses for OEP's.
  Here an example of 32 bit Normal-Dataword (D0).

31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Line: 37 to 43
 
"110" Calibration-dataword  
"111" Calibration-dataword error in dataword number
Added:
>
>
-- JoernWuestenfeld - 03 Jul 2009
 
META FILEATTACHMENT attr="" comment="data structure example" date="1241340884" name="data_struct.jpg" path="data_struct.jpg" size="31486" user="AttilioTarantola" version="1.1"
Revision 7
23 Jun 2009 - Main.AttilioTarantola
Line: 1 to 1
 
META TOPICPARENT name="DaqUpgradeMDCOverview"
-- AttilioTarantola - 03 May 2009
Line: 34 to 34
 
"011" Special-dataword reserved for token not retrieved
"100" Special-dataword two hits in one dataword and error flag(TDC nr/ch missmatch)
"101" Special-dataword single hit (0)
Changed:
<
<
>
>
"110" Calibration-dataword  
"111" Calibration-dataword error in dataword number
 

META FILEATTACHMENT attr="" comment="data structure example" date="1241340884" name="data_struct.jpg" path="data_struct.jpg" size="31486" user="AttilioTarantola" version="1.1"
Revision 6
23 Jun 2009 - Main.AttilioTarantola
Line: 1 to 1
 
META TOPICPARENT name="DaqUpgradeMDCOverview"
-- AttilioTarantola - 03 May 2009
Line: 32 to 32
 
"001" Normal dataword  
"010" Special-dataword reserved for 3rd hit
"011" Special-dataword reserved for token not retrieved
Changed:
<
<
"100" Special-dataword ..
"101" Special-dataword ..
>
>
"100" Special-dataword two hits in one dataword and error flag(TDC nr/ch missmatch)
"101" Special-dataword single hit (0)
 

Revision 5
03 May 2009 - Main.AttilioTarantola
Line: 1 to 1
 
META TOPICPARENT name="DaqUpgradeMDCOverview"
-- AttilioTarantola - 03 May 2009

Here follows the new data structure for MDC readout(OEPB).
Changed:
<
<
In the following picture (taken from Jan's talk, IKF Seminar 30.04.09), 3 OEPB generated data.
>
>
In the following picture (taken from Jan's talk, IKF Seminar 30.04.09), 3 OEPB generate data. These data are then combined in the HUB module (MDC optical addon).
  In each OEPB block the Network Header, Event Information, Length-Source and Network Termination are generated by the TRBnet entity. D0,*D1*,..*Dn* are generated by the readout entity.

Added:
>
>
* data structure example:
data structure example

Here an example of 32 bit Normal-Dataword (D0).
 
Added:
>
>
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Data Type TDC Number (1..12) TDC Channel#(0-7) Data (Hit1-11bit) Data (Hit0-11bit)
 
Changed:
<
<
The Header is generated by the End Point. Here we have the address of the MB (unique, given by the temperature sensor).
>
>
In case of 3 datawords per channel or in case of errors which must be transported with the event (i.e. token not retrieved, event broken, errors in the voltages measurement..) an additional Special-Dataword is generated.
 
Changed:
<
<
The dataword (32 bits) might look like:
>
>

Here an example of 32 bit Special-Dataword:
 
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Changed:
<
<
trigger type TDC number (1..12) TDC Channel# Data (Hit 1) Data (Hit 0)
>
>
Data Type TDC number (1..12) TDC Channel#(0-7) Special-Data_1 (11bit) Special-Data_0 (11bit)
 
Deleted:
<
<
As one can see, we use one 32 bits dataword for both hits (0 and 1). In each dataword we can set the trigger type (calibration, normal,..).
 
Changed:
<
<
The event is terminated with a 32 bits dataword which contains error bits (token back or not..), number of dataword in the event,the trigger tipe and additional statistics...
>
>
Data Type distinguishes between Normal-Dataword and Special-Datawords.
 
Changed:
<
<
-- AttilioTarantola - 29 Apr 2009
>
>
Data Type Meaning Comments
"001" Normal dataword  
"010" Special-dataword reserved for 3rd hit
"011" Special-dataword reserved for token not retrieved
"100" Special-dataword ..
"101" Special-dataword ..
 
Deleted:
<
<
An additional dataword can be added with all debug information which must be sended which the corresponding event. I.e. when token is not retrieved the second dataword can be:
 
Deleted:
<
<
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
10 TDC number (1..12) TDC Channel# - Debug info
  • data structure example:
    data structure example
 

META FILEATTACHMENT attr="" comment="data structure example" date="1241340884" name="data_struct.jpg" path="data_struct.jpg" size="31486" user="AttilioTarantola" version="1.1"
Revision 4
03 May 2009 - Main.AttilioTarantola
Line: 1 to 1
 
META TOPICPARENT name="DaqUpgradeMDCOverview"
Changed:
<
<
-- AttilioTarantola - 11 Mar 2008
>
>
-- AttilioTarantola - 03 May 2009

Here follows the new data structure for MDC readout(OEPB). In the following picture (taken from Jan's talk, IKF Seminar 30.04.09), 3 OEPB generated data. In each OEPB block the Network Header, Event Information, Length-Source and Network Termination are generated by the TRBnet entity. D0,*D1*,..*Dn* are generated by the readout entity.

 
Deleted:
<
<
From a meeting with Jan Michel (10.03.2008) in order to use the TRB net (End point) we should change the dataword structure. Here a first draft we might get as starting point for further discussions:
 

The Header is generated by the End Point. Here we have the address of the MB (unique, given by the temperature sensor).
Line: 23 to 29
 

31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
10 TDC number (1..12) TDC Channel# - Debug info
Added:
>
>
  • data structure example:
    data structure example
 
Added:
>
>
META FILEATTACHMENT attr="" comment="data structure example" date="1241340884" name="data_struct.jpg" path="data_struct.jpg" size="31486" user="AttilioTarantola" version="1.1"
Revision 3
29 Apr 2009 - Main.AttilioTarantola
Line: 1 to 1
 
META TOPICPARENT name="DaqUpgradeMDCOverview"
-- AttilioTarantola - 11 Mar 2008
Line: 15 to 15
 

The event is terminated with a 32 bits dataword which contains error bits (token back or not..), number of dataword in the event,the trigger tipe and additional statistics...
Added:
>
>
-- AttilioTarantola - 29 Apr 2009

An additional dataword can be added with all debug information which must be sended which the corresponding event. I.e. when token is not retrieved the second dataword can be:

31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
10 TDC number (1..12) TDC Channel# - Debug info
Revision 2
11 Mar 2009 - Main.AttilioTarantola
Line: 1 to 1
 
META TOPICPARENT name="DaqUpgradeMDCOverview"
-- AttilioTarantola - 11 Mar 2008
Line: 8 to 8
  The Header is generated by the End Point. Here we have the address of the MB (unique, given by the temperature sensor).

The dataword (32 bits) might look like:
Changed:
<
<
30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
>
>
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
 
trigger type TDC number (1..12) TDC Channel# Data (Hit 1) Data (Hit 0)

As one can see, we use one 32 bits dataword for both hits (0 and 1). In each dataword we can set the trigger type (calibration, normal,..).
 
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)