Difference between revisions of "Table for inconsistent 3-pass runs"
From Hall A Wiki
| Line 35: | Line 35: | ||
|- | |- | ||
| − | | 1837 || | + | | 1837 || 20743 || inconsistent for Ungated, (+) and (-) || not same run time |
|- | |- | ||
| − | | 1838 || | + | | 1838 || 20744 || inconsistent for Ungated and (-) || not same run time |
|- | |- | ||
Revision as of 16:50, 8 December 2009
| Left run | Right run | scalar issues | comments |
|---|---|---|---|
| 1689 | 20582 | inconsistent for Ungated and (-) | not synchronized, no end of run for 1689 |
| 1704 | 20596 | inconsistent with T1(-) only | unclear since only T1(-) |
| 1707 | 20599 | inconsistent for Ungated and (-) | not same run time; if choose same run time (same clk scalar), consistent |
| 1722 | 20616 | inconsistent for (-) | not same run time for the 2nd (-) state; if choose same run time (same clk scalar), consistent |
| 1738 | 20644 | inconsistent for (-) | only about 700 entries for (-) state |
| 1742 | 20648 | inconsistent for Ungated and (+) | all the scalars start to count from 0 after entry 900788 and 1005133. 2M events in fact while end of run shows only 1M |
| 1795 | 20701 | inconsistent for Ungated and (+) | not same run time, inconsistent |
| 1799 | 20705 | inconsistent for Ungated and (-) | not same run time, no end run information for 20705; if choose same run time (same clk scalar), consistent |
| 1836 | 20742 | inconsistent for Ungated and (-) | not same run time; if choose same run time (same clk scalar), consistent |
| 1837 | 20743 | inconsistent for Ungated, (+) and (-) | not same run time |
| 1838 | 20744 | inconsistent for Ungated and (-) | not same run time |
| 1921 | 20829 | inconsistent for (+) | |
| 1923 | 20831 | inconsistent for Ungated and (-) | |
| 1927 | 20835 | inconsistent for (+) | |
| 1928 | 20836 | inconsistent for (-) | |
| 1959 | 20879 | inconsistent for (-) |
