[Gate-users] (sans objet)

[davguez at free.fr]

Hi again,
Actually, this solution may not fully work, because the made in
GateCoincidenceSorter to decide that the current list is finished is callling
the "IsAfterWindow()" method of the GateCoincidencePulse object. Due to the
resolution you have, this test is no longer valid... The solution should be to
integrate a security zone of 1 or 2 resolution width, so the "IsAfterWindow"
become : "return
newPulse->GetTime()>m_startTime+m_coincidentWindow+2.*m_timeResolution")
you should add a m_timeResolution field in GateCoincidencePulse class , and a
messenger to be able to set the "m_timeResolution" by macro, or just hard code
it to get fast answer..
As you can see, the assumption of ascending time order seems to be important
in the coincidence algorithm and the solution may be not so easy to find...
I'm not sure that the solution I proposed will work (please let me know the
result of your investigation)

Cheers,

D. Guez

>Thnx David,
>Those are actually the lines of code I was about to change, but it is good to
>get some confirmation. ;-)

>Best Regards,
>Pedro


At 22:22 09/11/2006, you wrote:
>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>X-MIME-Autoconverted: from 8bit to quoted-printable by relay.upm.es id
>kA9LOYww009595
>
>Pedro Guerra a écrit :
>>Hi,
>>During the workshop held at the MIC conference San Diego, some of the
>>attendees
>>raised the question of some problems with the timing window. I wonder
>>whether they