Notes |
|
(0000120)
|
wolin
|
2011-06-20 10:16
|
|
Graham...kindly review the task description and modify as required, especially the estimated man-weeks of effort needed. We'll iterate as needed. |
|
|
(0000121)
|
wolin
|
2011-06-20 10:17
|
|
Please update task description as needed |
|
|
(0000148)
|
heyes
|
2011-08-31 07:28
|
|
"Software should include working example that disentangles data from F1TDC, fADC125 and fADC250 modules that will be used in Hall-D".
It isn't clear that this is possible at this time since the data format from the various modules isn't stable yet. A prototype "proof of principle" is possible. |
|
|
(0000251)
|
wolin
|
2012-01-23 10:04
|
|
Probably can disentangle in quad-core or better ROC or in EMU stage. DAQ group will determine how much CPU is available in ROC at high-rates. |
|
|
(0000478)
|
wolin
|
2013-03-19 11:56
|
|
I believe Carl has made progress on this. Different strategies for where to run the disentangler (ROC, EB, both?) will be investigated in the Hall D DAQ test setup by the DAQ group. |
|
|
(0000503)
|
wolin
|
2013-03-21 14:04
|
|
Not sure who will do this. |
|
|
(0000556)
|
wolin
|
2013-07-18 10:12
|
|
Dave and I now realize the two best places to do disentangling are on the ROC and in the L3 farm. I.e. a separate disentangling EB stage may not be the best choice. We need to further investigate these two strategies. |
|
|
(0000600)
|
davidl
|
2014-11-30 08:40
|
|
Event disentangling is currently being handled in the DAQ plugin in the Hall-D software. It will likely stay there since it allows the disentangling job to be distributed to multiple computers rather than be done on a single computer if it were handled in the event builder. |
|