6-25-01 vsn 1 6-28-01 vsn 1.1 TEST VECTORS FROM THE STT TRIGGER SIMULATOR Silvia Tentindo-Repond, FSU Introduction - Test Vectors are ascii files produced by the STT Trigger Simulator to provide the necessary input to the Trigger Cards of STT to run their VHDL code, or to provide the output from the simulator that will be compared to the output of the VHDL processors. There are two types of Test Vector files, the ones that must comply with the bit word format, and the ones that are produced in free format. To the first category belong the Test Vectors that provide the input stream to STC from the SMT detector ( ``SMTOutput'' ), and the Test Vectors that provide the Output to TFC from STC for the STC (``STC2TFCOutput'') ; free format are instead the Test Vectors for the filter output of STC (`STCOutput''), and for the Centroids output of STC (``CLUSOutput''). The file 'FRCOutput'' provides to STC the information of all the CTT Tracks as it is forwarded to FRC from L1, and adds up Header and Trailer, in different flavors ( depending on specific modes of running the STC Logic,'original', 'test' or 'strip' mode). This is the organization of the following sections: Section 1) describes the Test Vectors file that contains SMT Data Stream, that are used in STC as input to the Clusters and Centroid FPGA; Section 2) describes the file that contains the FRC data, ie all the track information provided by the CFT detector, and that is used as input in the STC Filter FPGA; Section 3) describes the test vectors file that contains , in a free format, the output from STC ( roads and clusters in road). THis file is provided for comparison of the hits in roads as produced by the simulator, and the output from the STC cards. Section 4) describes the output as produced by the simulator about Clusters and centroids. THis file is provided in free format, and is expected to be used for comparison with the output produced by the Centroids FPGA in STC. Section 5) describes the Test Vectors file STC2TFCOutput that contains in the bin word fo , as required for the output from STC to TFC. As it is at present, the input to TFC of the FRC data could be chosen to be the FRCOutput file, f.ex. chosen in the ``original FRC'' mode. Or it could be the `STCOutput'' file as well, : this last one would contain only the CFT tracks that have been associated to SMT hits in STC; the first file would contain ALL the CFT tracks, independently from STC filtering. The bin format specifications frot he input Test Vectorsa to TFC need still to be precisely defined. 1 ) TEST VECTORS FOR INPUT TO STC CLUSTERS (``SMTOutput'') The data stream from the SMT detector is the input to the Cluster Finding FPGAs in the STC, that use SMT hits to calculate clusters and centroids. The detailed description of the SMT Data Stream has been given in previous documents (1). The file's first word gives the Event number, and the total number of SMT hits in the event, in decimal format, the rest of the file is in exadecimal words. Input MC file : ( single muon track events ) : "/tmp_root/716/fsu_2/silvia/STT/musingle_mcrunjob_1000_170_1752" STT Simulator : CVS t01.45.00 - 22 May 2001 Selection: Barrel = 4 Layer = 1 Ladder = 1 Output file : SMTOutput_mus_1000ev_4_1_1_70_15.txt Format of Output file as of todate ( 5-22-01 ): ______________________________________________________________ example of data stream: line 1 38 3 Event Number and number of SMT hits 2 5 Sequencer id (0 to 255, actual 150) 3 3 HDI id ( from 0 to 7; the status bits are ignored ) 4 82 Chip id (0 to 8, MSB always 1) 5 0 zero 6 a Channel id ( strip number, MSB always 0) 7 3 Channel content ( 0 to 255) 8 b Channel id 9 18 Channel content 10 83 Chip id 11 0 zero 12 1d Channel id 13 1b Channel content 14 c0 Trailer C0 15 c0 Trailer C0 16 148 4 .............. next Event Number 17 5 18 0 19 82 (1) ``The Input Data Flow to L2STT trigger Card from SMT Front-Ends'' D0Note 3599, 22-Jan-99, S.Tentindo-Repond, B.Connolly 2) TEST VECTORS FOR INPUT TO STC FILTER ( ``FRCOutput'') There are more than one mode to create this file: 1 -``original'', creates data as they are sent from FRC 2 - ``reformatted for STC'' - bit words for header/ trailer etc are added (also defined ``test'' mode) 3 - ``stripped''- all header/trailer are stripped off. Input MC file : ( single muon track events ) : "/tmp_root/716/fsu_2/silvia/STT/musingle_mcrunjob_1000_170_1752" STT Simulator : CVS t01.45.00 - 22 May 2001 Selection: Barrel = 4 Layer = 1 Ladder = 1 Output file : FRCOutput_mus_1000ev_4_1_1_70_15_test_stripped.txt Format of Output file as of todate ( 5-22-01 ): ______________________________________________________________ example of data stream: 38 1 Event Number and number of roads in event 7d01 FRC word for first road 148 1 new Event number etc ............... 4004103 156 1 5902 162 1 810f NOTE - When the ``test'' mode is selected, a second word is created after the \ FRC word, that describes the SMT strip range : it is 22 bits long, and is composed by ``strip high'' (the first lowest 11 bits(LSB) ) and ``strip low'' (the highest 11 bits ( MSB)). example: 4 12 Event number number of roads 2c009c00 6887e FRC word for first road and strip range 74002c02 5c065 FRC word for second road and strip range c000640c 3fffff FRC word for third road ; the equivalent road doesn't intersect the special ladder etc When the ``range'' mode is selected, write out the strip range in terms of max and min roads ( max FRC road and min FRC road calculated by using the LUT filter table ). 3 ) TEST VECTORS FOR COMPARISON TO STC OUTPUT (FILTER) ( ``STCOutput'') This file produces the output of the simulator that describes roads and clusters associated to each road: this information is produced in free format, for general uses. The road information is given by a 17 bits long word ( printed in exadecimal), and the cluster is described by the hardware address of its centroid ( Sequ encer, HDI , Chip and Channel address ) also exadecimal. FRC word: |17 12|11 6| 5 |4 3 |2 0| |---------------------------------------------------------------------| |L1CTT Sector mod20 |H Layer fiber # |Pt sign |Pt bin |extended Pt bin| Input MC file : ( single muon track events ) : "/tmp_root/716/fsu_2/silvia/STT/musingle_mcrunjob_1000_170_1752" STT Simulator : CVS t01.45.00 - 22 May 2001 Selection: Barrel = 4 Layer = 1 Ladder = 1 Output file : STCOutput_mus_1000ev_4_1_1_70_15.txt Format of Output file as of todate ( 5-22-01 ): ______________________________________________________________ example of data stream: line 1 38 1 1 Event number + number of roads + number of clusters 2 17e0 FRC word (17 bits long) with road info 3 5 0 2 b SEQ, HDI,Chop,Chan for Cluster 4 148 1 2 new Event number etc .......... 5 3421 6 5 0 2 51 7 5 0 2 55 8 156 1 1 9 25a0 10 5 0 2 2d 4 ) TEST VECTORS FOR COMPARISON TO STC OUTPUT (CLUSTERS/STRIPS) (``CLUSOutput'') This file is produced in free format (decimal), and is provided to allow the comparison in bwetween the output from the simulator and the output from the VHDL of the STC card that calculates clusters and centroids. The algo rithms that calculate clusters and centroids in the simulator have been written to reproduce the VHDL code as much as possible. For each Centroid, the cluster general information is saved, and also the hardware address for each of the compnents strips. Input MC file : ( single muon track events ) : "/tmp_root/716/fsu_2/silvia/STT/musingle_mcrunjob_1000_170_1752" STT Simulator : CVS t01.45.00 - 22 May 2001 Selection: Barrel = 4 Layer = 1 Ladder = 1 Output file : CLUSOutput_mus_1000ev_4_1_1_70_15.txt Format of Output file as of todate ( 5-22-01 ): ______________________________________________________________ example of data stream: 4 1 1 38 1 3 0 5 0 2 11 1 27 1 0 2 10 3 1 1 2 11 24 1 4 1 1 0 5 0 3 29 2 27 2 0 3 29 27 1 148 1 5 0 5 0 2 81 2 2 1 0 2 81 2 1 4 1 1 0 5 0 2 85 2 17 1 0 2 85 12 1 1 2 86 5 1 4 1 1 0 5 0 3 76 2 22 2 0 3 76 22 1 4 1 1 156 1 3 0 5 0 2 45 2 24 1 0 2 45 13 1 1 2 46 11 1 4 1 1 0 5 0 5 36 2 23 2 0 5 36 23 1 4 1 1 162 1 3 0 5 0 0 4 2 21 1 0 0 3 3 1 1 0 4 9 1 2 0 5 9 1 4 1 1 0 5 0 4 47 2 20 2 0 4 47 20 1 ____________________________________________________________ General information: Line 1 : 4 1 1 BARREL number LAYER number LADDER number Line 2 : 38 1 1 Event number Cluster number total number of clusters obeyng the selection in Event Cluster Centroid information : Line 3: 0 5 0 2 11 1 27 1 Crate SEQ HDI Chip Channel fraction PulseHeight View Strips associated to Cluster : ( one line each strip ) Line 4: 0 2 10 3 1 number of strip Chip Channel PulseHeight Type assoc. to cluster Line 5: 1 2 11 24 1 .. same as above .. Next Cluster Centroid: . . =============================================================================== 5) TEST VECTORS FOR INPUT TO TFC (TRACK FIT CARD) (``STC2TFCOutput'') This file contains the information produced by the STC, i.e. the clusters in roads information (``Hits'') (2), and is encoded in the format required by bit words. The L1CTT Header and Trailer are also included THis is the information as it is forwarded from STC to TFC. (2) ``Specifications for the STC Control Logic'' W.E.Earle- Nov,10,2000 Input MC file: (single muon tracks events): ``/tmp_root/716/fsu_2/silvia/STT/musingle_mcrunjob_1000_170_1752'' STT Simulator: CVS t01.50.00 - 24 Jun 2001 Selection: Barrel = 4 Layer = 1 Ladder = 1 Output file: STC2TFCOutput_mus_1000ev_4_1_1_70_15.txt STC2TFCOutput_mus_1000ev_4_1_1_70_15.debug (for bin display) ------------------------------------------------------------------------------ example of Data Stream: line 1 0 2 0 3 0 4 1 5 c0000026 6 785040b 7 f07f0100 8 0 9 0 10 0 11 0 12 1 13 c0000094 14 7850451 15 7850455 16 f07f0100 17 0 ----------------------------------------------------------------------------- Description of content , by line: - All words format is exadecimal Beginning of Event Line 1 0 L1CTT HEADER word 1 = 0 Line 2 0 `` `` 2 = 0 Line 3 0 `` `` 3 = 0 Line 4 1 `` `` 4 = multiplicity of CTT tracks Line 5 c0000026 HIT HEADER word : equivalent binary: 11000000 00000000 00000000 0010010 |31 30 29 28 27| |7 0| |--------------|----------------------------|-----------| | 1 1 0 0 0| |EVENT # | (*) (*) At present temporarily the Event Number written here is tha absolute event number, and it can occupy more than 8 bits. Finally, this word will contain the Event Number as given in FRC ( at present not simulated), and will be constrained to 8 bits lenght. Line 6 785040b HIT word equivalent binary: 00000111 10000101 00000100 00001011 |31 26|25 23|22 16|15 13|12 9|8 0| |-------------------------------------------------------------------| | Track |dE/dX |SEQ |HDI |CHIP |STRIP | 1 111 (*) 101 0 100 1011 (*) At present temporarily the dE/dX value is not calculated, and set to 111. Line 7 f07f0100 HIT TRAILER word equivalent binary: 11110000 01111111 00000001 00000000 |31 27|26 24|23 16|15 8| 7 | 6 | 5 | 4 | | |-----------------------------------------------------------------------------| |11110 | | Event | # of HITS |SERR|MM|RERR|EERR| | 111111 (*) 1 0 0 0 0 (*) Event Number as in FRC, not provided yet by Simulator, set arbitrarily to 127 decimal ( 1111111) SERR,etc.: give detailed inof about SMT inputs errors. Not provided by simulator. Set to zero. Line 8 : 0 L1CTT TRAILER word Set to zero. From Line 9 on, a new event begins ...... ***********************************************************************8 . . . . TEST VECTORS FOR THE TRACK FIT CARD OF STT as generated by the STT Trigger Simulator Input MC file: (single muon tracks events): ``/tmp_root/716/fsu_2/silvia/STT/musingle_mcrunjob_1000_170_1752'' STT Simulator: CVS t01.50.00 - 24 Jun 2001 Selection: Barrel = 4 Layer = 1 Ladder = 1 Output file: STC2TFCOutput_mus_1000ev_4_1_1_70_15.txt STC2TFCOutput_mus_1000ev_4_1_1_70_15.debug (for bin display) ------------------------------------------------------------------------------ example of Data Stream: line 1 0 2 0 3 0 4 1 5 c0000026 6 785040b 7 f07f0100 8 0 9 0 10 0 11 0 12 1 13 c0000094 14 7850451 15 7850455 16 f07f0100 17 0 ----------------------------------------------------------------------------- Description of content , by line: - All words format is exadecimal Beginning of Event Line 1 0 L1CTT HEADER word 1 = 0 Line 2 0 `` `` 2 = 0 Line 3 0 `` `` 3 = 0 Line 4 1 `` `` 4 = multiplicity of CTT tracks Line 5 c0000026 HIT HEADER word : equivalent binary: 11000000 00000000 00000000 0010010 |31 30 29 28 27| |7 0| |--------------|----------------------------|-----------| | 1 1 0 0 0| |EVENT # | (*) (*) At present temporarily the Event Number written here is tha absolute event number, and it can occupy more than 8 bits. Finally, this word will contain the Event Number as given in FRC ( at present not simulated), and will be constrained to 8 bits lenght. Line 6 785040b HIT word equivalent binary: 00000111 10000101 00000100 00001011 |31 26|25 23|22 16|15 13|12 9|8 0| |-------------------------------------------------------------------| | Track |dE/dX |SEQ |HDI |CHIP |STRIP | 1 111 (*) 101 0 100 1011 (*) At present temporarily the dE/dX value is not calculated, and set to 111. Line 7 f07f0100 HIT TRAILER word equivalent binary: 11110000 01111111 00000001 00000000 |31 27|26 24|23 16|15 8| 7 | 6 | 5 | 4 | | |-----------------------------------------------------------------------------| |11110 | | Event | # of HITS |SERR|MM|RERR|EERR| | 111111 (*) 1 0 0 0 0 (*) Event Number as in FRC, not provided yet by Simulator, set arbitrarily to 127 decimal ( 1111111) SERR,etc.: give detailed inof about SMT inputs errors. Not provided by simulator. Set to zero. Line 8 : 0 L1CTT TRAILER word Set to zero. From Line 9 on, a new event begins ...... ************************************************************************** . . . TEST VECTORS FOR THE OUTPUT OF THE TRACK FIT CARD OF STT as generated by the STT Trigger Simulator Input MC file: (single muon tracks events): ``/tmp_root/716/fsu_2/silvia/STT/musingle_mcrunjob_1000_170_1752'' STT Simulator: CVS t01.54.00 - 06 Aug 2001 Selection: Barrel = 4 Layer = 1 Ladder = 1 Output file: TFCOutput_mus_1000ev_4_1_1_70_15.txt ------------------------------------------------------------------------------ example of Data Stream: line 1 Event Number and Number of STT Tracks 2 38 1 3 -4.58e-05 0.137111 1.89327 65.415 10906.9 -1490.77 108-4.6 -1 21 0.00295 3 0 4 Event Number and Number of STT Tracks 5 148 1 . . ----------------------------------------------------------------------------- Description of content , by line: - All words format is exadecimal Beginning of Event Line 1 comment Line 2 38 1 TFC HEADER word contains Abs. event number and number of STT Tracks in event Line 3 0 STT Track attributes ( in decimal format): word 1 kappa word 2 phi0 word 3 chi2 word 4 pt word 5 rc word 6 xc word 7 yc word 8 skipped_layer not implemented word 9 serial_number word 10 b impact parameter Line 4 0 TFC Trailer word From line 5 a new event begins . . ********************************************************************