Home » Blogs » gvisser's blog

IST and GMT fixed busy time, data size, and limiting rate as a function of ntimebins

Updated on Fri, 2016-02-05 14:53. Originally created by gvisser on 2016-02-05 00:21.

The following table shows, for timebin settings from 1 to 15, the required fixed busy setting in RS ticks, and the data size in bytes per fiber per event and the corresponding limiting rate capability in Hz (when the DDL link is maxed out @ 206.7 MB/s).
The data size and rate are listed in the two cases of IST and GMT.

ntimebins fixed deadtime, RS nadc nwords/apv IST datasize IST link rate limit, Hz GMT datasize GMT link rate limit, Hz
1 250 160 60 35808 5772 4272 48377
2 320 300 114 66912 3089 7728 26743
3 390 440 165 96288 2146 10992 18802
4 460 580 219 127392 1622 14448 14304
5 530 720 270 156768 1318 17712 11668
6 600 860 324 187872 1100 21168 9763
7 670 1000 375 217248 951 24432 8459
8 740 1140 429 248352 832 27888 7411
9 810 1280 480 277728 744 31152 6634
10 880 1420 534 308832 669 34608 5972
11 950 1560 585 338208 611 37872 5457
12 1020 1700 639 369312 560 41328 5001
13 1090 1840 690 398688 518 44592 4635
14 1160 1980 744 429792 481 48048 4301
15 1230 2120 795 459168 450 51312 4028
»