[IGSTK-Developers] Re: Connection TrackerTool-Physical tracker port

[Luis Ibanez]

Hi Geir,

I'm assuming that these methods are to be implemented only in
the PolarisTrackerTool and AuroraTrackerTool... is that right ?

Also, do you see any reason for disconnecting/connecting the
tools during the surgery ?

I'm reworking the State machine of the TrackerTool, and I was
assuming that the settings of Port, Channel and SROM were done
at the very beginning, (before starting to track) and never
changed afterwards.

The current intention with the state machine is to ignore
subsequent calls to RequesetSetPort() for example.

A sketch of the proposed State Machine is available in the Wiki:

http://public.kitware.com/IGSTKWIKI/index.php/Tracker_interface_changes#Tracker_Tool_State_Machine

This is for the base class TrackerTool.

The derived classes {Polaris,Aurora,FlockOfBirds}TrackerTool,
will have a separate StateMachine where the settings of ports,
channel, bird #, will be made, and a boolean status method will
return if the tool is ready to be used.


  Please let us know what you think of this suggested organization.


     Thanks


        Luis


--------------------
Patrick Cheng wrote:
> Hi Geir Arne,
> 
> I agree, I think it should be a two way street.
> 
> 1. We can give it a port and channel, and get the SROM (ID information) 
> from the physical tool, to verify if that's the correct tool as we 
> expected.
> 
> 2. We should also be able to give it an ID information, and let the 
> tracker figure out which port and channel it's being connected to.
> 
> These fit into the redesigned tracker interface well, since we have 
> access to the TrackerTool object.
> 
> Thank you,
> 
> Patrick
> 
> Geir Arne Tangen wrote:
> 
>> Hi Patrick,
>>
>> Thanks for the response though I still think we need some kind of 
>> verification that the TrackerTool object is connected to
>> the correct physical port.
>>
>> In one of our projects we are simultaneously tracking 4 tools 
>> (reference tool, active fiducial markers + two catheter tools).
>> In this case it can be difficult to verify that the tool cables are 
>> connected to the correct ports without checking the SROM
>> tool information (Reading the SROM information with command PHINF 
>> towards the NDI equipment).
>>
>> Geir Arne
>>
>> On Aug 13, 2007, at 5:33 PM, Patrick Cheng wrote:
>>
>>> Hi Geir Arne Tangen,
>>>
>>>
>>> >RequestSetToolID(string Manufacturer, string ToolRevision, string 
>>> >SerialNumber)
>>>
>>> I think this method is nice to have, but in practice, the needle tool 
>>> we  are using is sterilized and with SROM file pre-burned into the 
>>> tool. We don't have the ID information for those tools.
>>>
>>> What I have been doing in our application is, if the tool is not 
>>> being plugged into the right port and channel, we have the option to 
>>> correct that miss connection error and reinitialize the tracker.
>>>
>>> Patrick
>>>
>>> Geir Arne Tangen wrote:
>>>
>>>> Hi developers,
>>>> I have a suggestion for a new method in the TrackerTool class for 
>>>> identifying the physical tool to
>>>> the TrackerTool object during initialization. This will cover the 
>>>> fault situation when the operator
>>>> connects the wired Polaris/Aurora tool to the wrong physical port on 
>>>> the control box.
>>>> Comments are added to the 'Tracker Interface changes' discussion page :
>>>> http://public.kitware.com/IGSTKWIKI/index.php/Talk:Tracker_interface_changes#New_methods_for_identifying_tracker_tools 
>>>> Geir Arne Tangen
>>>> Research Scientist (MSc)
>>>> SINTEF Health Research, Medical Technology
>>>> E-Mail: Geir.A.Tangen at sintef.no
>>>> Phone : +47 98245142
>>>> Fax : +47 93070800
>>>> Web adress: http://www.sintef.no/medtech
>>>> _______________________________________________
>>>> IGSTK-Developers mailing list
>>>> IGSTK-Developers at public.kitware.com
>>>> http://public.kitware.com/cgi-bin/mailman/listinfo/igstk-developers
>>>
>>>
>>>
>>
>> Geir Arne Tangen
>> Research Scientist (MSc)
>> SINTEF Health Research, Medical Technology
>>
>> E-Mail: Geir.A.Tangen at sintef.no
>> Phone : +47 98245142
>> Fax : +47 93070800
>> Web adress: http://www.sintef.no/medtech
>>
>>
>> _______________________________________________
>> IGSTK-Developers mailing list
>> IGSTK-Developers at public.kitware.com
>> http://public.kitware.com/cgi-bin/mailman/listinfo/igstk-developers
>>
>>
>>
> 
> 
> _______________________________________________
> IGSTK-Developers mailing list
> IGSTK-Developers at public.kitware.com
> http://public.kitware.com/cgi-bin/mailman/listinfo/igstk-developers
>