Ticket #715 (closed defect: fixed)
Opened 2012-06-12T12:03:16-05:00
Last modified 2012-06-15T18:40:28-05:00
Single exponential results disagree
| Reported by: | aivar | Owned by: | aivar |
|---|---|---|---|
| Priority: | major | Milestone: |
|
| Component: | slim-plugin | Severity: | serious |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | #674 |
Description
Sometimes TRI2 and SLIM Plugin results are close but disagree.
100611-YG-256.sdt at (146, 230) cursors 0.0/2.15/11.23 Poisson Data:
SLIM Plugin: A 71.28562 T 2.092129 Z 0.99059045 X2 0.32557997
TRI2: A 69.08 T 2.13 Z 0.92 X2 1.007875
(When the cursors were 0.0/2.1484/11.2305 TRI2 and SLIM Plugin agreed except for chi square [see #697]. In other words for TRI2 cursors 0.0/2.1484/11.2305 and 0.0/2.15/11.23 are equivalent, for SLIM Plugin they are not. Suggests a rounding technique discrepancy.)
Change History
comment:1 Changed 2012-06-12T15:24:25-05:00 by aivar
comment:2 Changed 2012-06-12T15:38:50-05:00 by aivar
Some other results:
0/2.15/11.2305 A 71.221 T 2.094 Z 0.983
0/2.1484/11.23 A 69.132 T 2.133 Z 0.929
These agree in TRI2 and SLIMPlugin (except for the chisquare see #697)
comment:3 Changed 2012-06-15T18:40:28-05:00 by aivar
- Status changed from new to closed
- Resolution set to fixed
This particular discrepancy was due to comparison with an older version of TRI2. With latest 2.7.3.1 results agree.
'A rounding technique discrepancy' referred to issues associated with converting a floating point time based start/stop value to be a start/stop bin number.
For non-prompt fitting I was able to match SP and TRI2. I changed the data start and transient end parameters in increments of .0001 and obtained matching values even as the resultant bin numbers changed.
For example with 100611-YG-256.sdt, Gaussian noise, triple exponential at (146, 230), I got Z=1.529, A3=20.045, T3=0.6403 for cursors 0/2.0507/11 and Z=1.553, A3=2.132, T3=0.5906 for cursors 0/2.0508/11. I got Z=1.529, A3=20.045, T3=0.6403 for cursors 0/2.0507/11.0351 and Z=1.419, A3=19.224, T3=0.6401 for cursors 0/2.0507/11.0352.
Problem goes away with the latest TRI2: With my Windows 7 VM and TRI2 version 2.731 I get:
0/2.15/11.23 A 71.286 T 2.092 Z 0.991 X2 1.015688
0/2.1484/11.2305 A 69.081 T 2.135 Z 0.922 X2 1.007875
Earlier I was testing with version 2.5.2.1 modified to add SLIMCurve, on XP.