[IGSTK-Users] Numerous Transform Callback Performance

[Patrick Cheng]

Hi Jake,

Can you tell us a little more about your experiment setup? IGSTK 
versions, system, tracker, and example code.  When you run your test, 
did you observe memory leak? You can check this by using system monitor 
to see the memory usage. Under linux you can use "top" command.

There is also an example application in IGSTKSandbox does exactly the 
same thing. I am wondering if you could run that application and tell us 
about its performance. (IGSTKSandbox/Exampls/TrackerDataLogger)

Patrick

On 5/12/2010 12:04 PM, Jake McIvor wrote:
> I have an application that logs transform data to a file.  A callback
> function is attached to an observer watching for
> TrackerToolTransformUpdateEvent.  Within the callback function I use a
> transform observer to check for and get the latest transform, and then
> log it to a file.
>
> Over time, the rate at which these transforms are recorded drops
> significantly.  I came across a section of Christopher Heath's thesis,
> Disablement of a Surgical Drill Via CT Guidance to Protect Vital Anatomy
> that describes a similar issue:
>
> "A method was added to Landmark3DRegister to allow for pass by reference
> retrieval of transforms instead of using callbacks. This was implemented
> to prevent an issue that occurs with the callback method utilized by
> IGSTK when finding the transform many times."
>
> Does anyone have any insight on what is happening or how to improve
> performance?
>
> Cheers,
>
> Jake
>
> --
> Jake McIvor
> MASc Candidate, Biomedical Engineering
> University of British Columbia
>
>
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/cgi-bin/mailman/listinfo/igstk-users