Difference between revisions of "FA125 firmware check"
| Line 24: | Line 24: | ||
There were a few problems in the firmware which Cody described & fixed week. Remaining issues are not critical. | There were a few problems in the firmware which Cody described & fixed week. Remaining issues are not critical. | ||
| − | Run 4062: | + | Run 4062:<br/> |
Integral differences are from very late times where there is a small peak at the end of the hit search window that only just clears the threshold crossing, followed by a larger peak a few samples later. The timing algorithm returns the time for the larger peak and the emulated integral is 0 because it is out of the window. | Integral differences are from very late times where there is a small peak at the end of the hit search window that only just clears the threshold crossing, followed by a larger peak a few samples later. The timing algorithm returns the time for the larger peak and the emulated integral is 0 because it is out of the window. | ||
Revision as of 11:40, 6 January 2016
Used the raw samples to emulated the fa125's calculated values and compared them with the fa125 output.
Looked at the first evio files from runs 3293 (2 weeks old) and 4062 (this week).
| Run | events | time | amplitude | pedestal | integral | overflow count |
| 3923 | 16582555 | 1160 | 1942 | 3547 | 15609 | 1 |
| 3923 minus 2 bad fadcs | 15914850 | 378 | 1877 | 288 | 12798 | 1 |
| 4062 | 10247801 | 0 | 98 | 0 | 3 | 0 |
Many of the problems in 3923 were due to hardware faults in roc28 slots 5&6.
11770 of the 12798 difference in integral were due to faulty assignment of the overflow bit. This has been fixed.
There were a few problems in the firmware which Cody described & fixed week. Remaining issues are not critical.
Run 4062:
Integral differences are from very late times where there is a small peak at the end of the hit search window that only just clears the threshold crossing, followed by a larger peak a few samples later. The timing algorithm returns the time for the larger peak and the emulated integral is 0 because it is out of the window.
2/3 of the amplitude differences are where the samples at the start of the window are over threshold & the time reported is very early. Still looking at this.
Also:
Pulse & Window raw data are separate objects in the evio eventloop, not linked yet. One out of sync pair causes the rest of the data for that trigger to be out of step.
Run 3923 had 7600 entries with pulse and WRD out of step due to 252 hiccups.
Run 4062 had 1317 entries with pulse and WRD out of step due to 33 hiccups.
