Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
daq:mode3 [2012/05/18 08:30] weisshaa created |
daq:mode3 [2014/02/27 16:14] (current) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Severity ====== | ====== Severity ====== | ||
| + | We need to know that mode 3 is not missing data | ||
| ====== Problem ====== | ====== Problem ====== | ||
| + | We know that we lose data with mode 2. Same test for Mode 3 + S800 needs to be done | ||
| ====== Progress ====== | ====== Progress ====== | ||
| + | - 5/18/2012 Data taken in coincidence with S800 and using different configurations with Decomp and sendRaw, using mode 2,3 (Run 588) and 2 only (Run 587). | ||
| + | |||
| + | - 5/21/2012 Inspected the TS of the mode3: They are ordered. The events look like readout buffer rather than 40ch events. | ||
| + | Kathrin started modifying her program to merge the data in mode3 | ||
| + | |||
| + | - 5/22/2012 (kathrin): | ||
| + | * simple mode3-s800 merger program shows that there is no mode3 data lost, except for the very last event, which might be a problem of my code. for every s800 timestamp there is a corresponding mode3 gretina LED timestamp. | ||
| + | * this is tested for run588 only | ||
